When you run DeployAnywhere on a Syspreped image file, Windows appears to remain in Audit mode after the image has been restored.
Last Updated September 10, 2013
You need to know why your image is restored in Audit mode and how to correct the problem.
Symptoms Instead of seeing the Windows Welcome screen as you normally would when Windows boots up, you are automatically logged into Windows instead. Even after rebooting the system, it continues to auto-login.
You might also notice that the Windows\Setup\State\state.ini file indicates that Windows is running in Audit mode as follows:
With DeployAnywhere, the contents of this file reads: ImageState=IMAGE_STATE_SPECIALIZE_RESEAL_TO_AUDIT\ Without DeployAnywhere, the contents of this file reads: ImageState=IMAGE_STATE_COMPLETE
DeployAnywhere makes use of the Sysprep /audit parameter when injecting mass storage controller or network controller drivers into a restored image file.
To exit out of Audit mode, Sysprep has to be ran with the /oobe parameter.
To correct the problem on a one-time basis, you can run Sysprep again with the /oobe parameter.
For a more permanent solution, you should recreate your Syspreped image file, this time using the /oobe parameter along with any other Sysprep parameter you normally use prior to capturing the image.