Description :When deploying user to a windows Dollar Universe V6 node, in some cases, deployments ends in error.
If policy is set to skip, and user already exist, service is recreated. If user already exist, policy is set to skip, service is deleted, but user still exist. I user already exist, policy is set to overwrite, service is deleted, but user still exist.
When using "redeploy" on a deployment done with skip policy, redeployment is set to overwrite. And, as you can't set password in redeploy, redeployment will always fail, destroying user service.
Cause type: Defect Root Cause: N/A
OS: Windows OS Version: All supported.
Definitive behaviour is : The SA object will be created before the creation of the Windows service.
In case of a conflict with an existing SA, we'll then have:
(Conflict Policy == Skip) => do not create service (Conflict Policy == Overwrite) => create service and try to start it If the password provided for a non-Local System User is erroneous, the Service is created/recreated, but not started. Deployment still ends in an error, but log is explicit about the existence of the unstarted service.
Skip policy will then result in really skipping the creation. Re-deployment has been corrected too. Documentation will be updated.