Direkt zum Inhalt

Snap Deploy 5 and sysprep problems

Thread needs solution

With snap deploy 4 we would create a master image, sysprep it and image it to our snap deploy server. When we image new machines we would create a deployment task and select create new SID, and join the system to our domain automatically.

With snap deploy 5 we seem to be unable to do this, we can not change the SID or automatically join the domain. We do not even get the options to choose adding to domain or rest SID any longer.

What are we doing wrong, or what should we be doing different?

0 Users found this helpful

Hello, John

There is a known issue with adding the target machine to a domain when Acronis Universal Deploy (AUD) was used and DNS IP address was not specified in the network connection settings of the source machine before master image creation.

1. Please clarify operating system of the source machine;

2. Was the source machine joined the domain before image creation?

3. If hardware of the source machine is the same as target one, try to disable Acronis Universal Deploy in the deployment template settings;

4. Could you take a screenshot of template settings where "Change SID" and "Add the machine to domain" option should be present?

P.S. 

Source machine - a machine the image was taken from;

Target machine - a machine the image was deployed to.

Thanks for the reply.

We seem to have a working deployment, but not sure if it is "right".

It was more convenient under SD4 when we could build the image, sysprep it and upload the image. Then after sending the image to new hardware have the Windows Out of Box Experience and run through the mini setup wizard. But this works for now.