Skip to main content

SysPrep & Snap Deploy 3 w/ Universal Deploy

Thread needs solution

Should a machine be syspreped if the master image is being deployed to dissimilar hardware?

Based on the article @ http://kb.acronis.com/content/4326 it would seem it shouldn't since "OS Patcher does not support master OS images of Windows systems prepared with sysprep." & "Acronis Universal Deploy does not support master OS images of Windows systems prepared with sysprep."

However, after testing with a sysprepped image it seems Acronis does make the changes after the first reboot caused by sysprep.

Thoughts?

0 Users found this helpful

Hello Jerrod!

Thank you for your question.

It is highlited that Acronis Universal Deploy doesn't support syspreped systems due to our software can deploy such system only "as is" due to no OS can be detected after sysprep.

I'll be glad to provide you with detailed answer, but could you please kindly specify what exact changes fter the first reboot caused by sysprep you mean? 

Thank you in advance for cooperation!

After sysprep does its thing and the machine reboots Acronis then applies networks settings, renames the machine, etc.

We have just started to use Acronis Deploy 3 moved away from Ghost Server, having problems with sysprep system how do you get around the naming of the client after a sysprep when Acronis should do all that for you? I have created 2 image one sysprep and the other not sysprep not having any luch sofar :( any help would be great?:) A step by step on creating a image should be helpful to see if its something we have missed...

Dear Paul!

Welcome to our Forum, and thank you for finding time to report about the issue, I really appreciate it.

Unfortunately due to the lack of sufficient investigation information it is difficult to identify the exact cause of the problem. So this situation requires investigation. But before we get started I would advise you to check Template Creation chapter (Chapter 9, p. 52) in the User's Guide (since you can assign a Username with password and other settings with the help of template).

Please try suggested settings and should the issue persist, provide us with the following information:

  1. Exact sequence of steps performed before you faced the issue
  2. Detailed description of the issue
  3. OS Patcher logs
    - Please send us a copy of %Windows%\Debug\ folder from the restored system (after boot up) and the logs of Snap Deploy "patcher", the names of which look like "os_patcher[dd.mm.yy].log" and are located in %Windows%\System32\ folder.
    - If there is a window with message saying that the system is being patched and it prevents you from logging into Windows, then please click on the red "X" to close the window. This should allow you to log into the system.

This information will shed some light to the situation and help us to find the cause of the problem.

Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!

Thank you!