UIU Blog

Windows 8 Sysprep Error
If you're deploying Windows 8 in your environment, you may want to be aware of a little undocumented feature that is certain to cause you some time-consuming headaches.

In preparing to capture a Windows 8 (or 8.1) OS image, several of our customers have experienced the following Sysprep error:

System Preparation Tool 3.14
A fatal error occurred while trying to Sysprep the machine


Essentially, the error occurs when applications associated with user accounts are out-of-synch with the provisioning information for the master machine. A detailed explanation with three use cases can be found in the following Microsoft Support article: http://support.microsoft.com/kb/2769827

Also, in certain cases, if Windows Updates have not been checked in a set period of time, Sysprep may present errors as well. In our experience, simply allowing the machine to check (knowing it will fail as it has no Internet access) will subsequently allow Sysprep to execute without error.

Lessons learned?


1.  When possible, create no additional users on the master 
    machine.  Only login as the user account from which you intend 
    to execute Sysprep.

2.  When possible, do not install any Windows Store applications
    (Appx)

3.  When possible, remove (Uninstall and Un-provision) all
    unnecessary Windows Store applications (Appx) – This will need
    to be done for every user account created on the machine…

4.  Disconnect the master machine from the Internet

5.  Turn off Windows Updates on the Master Machine

6.  Optional & universally recommended- Lock down the ability for
    users to install applications


Additionally, if you're implementing Windows 8.1, also consider that a known issue exists when Sysprep is executed on the master machine more than 1 hour after the first user has logged in. There is a disk cleanup service that is executed via Scheduled Tasks which causes interference with Sysprep and a resultant error. The following command will disable the task:

Schtasks.exe /change /disable /tn "\Microsoft\Windows\AppxDeploymentClient\Pre-staged app cleanup"

http://technet.microsoft.com/en-us/library/dn303413.aspx



Comments are closed.
Showing 2 Comments
Avatar  Jorge 10 years ago

Since you tell me that you can connect to the ntework, verify that in the Bootstrap.ini file you put the right account that has the right permissions on that share. Test with a domain admin account, if you can, just to see that it works.

Avatar  Kemal 10 years ago

in the article, you may not have the prpeor network drivers in the boot image, meaning you don't have an IP so you can't connect to the Deployment Share. Verify that you have an IP address, if not put the driver in the boot image. Let me know how it works out.



Archives

  • 2019
  • 2018
  • 2017
  • 2015
  • 2014
  • 2013
  • 2012