Sysprep /generalize a domain controller. As far as I now understand from what I read about that error, sysprep does not support generalizing domain computers. Browse other questions tagged windows-server-2012-r2 sysprep or ask your own question. 3 years, 9 months ago. Windows 7 Forums is the largest help and support community, providing friendly help and advice for Microsoft Windows 7 Computers such as Dell, HP, Acer, Asus or a custom build.
This article will show you how to Sysprep a Windows Server 2012, this is a big time saver when deploying virtual machines.
To Sysprep windows server 20102, Install the server OS and make all the configuration necessary for the image, in my case I have install VMware tools, disabled the Firewall and enabled Remote desktop.
Once done and you are ready Open C:WindowsSystem32Sysprep
Click On the sysprep icon and select “Enter System Out-of-Box Experience (OOBE)”
Tick the Generalize Tick Box and Select Shutdown
You can also view my article on How to Sysprep Windows 10
Related
The use of SkipRearm leads into a discussion around best practices for building images. In the past with Windows XP/2003 most administrators followed a process similar to this
- Install Windows
- Install applications/drivers/updates
- Run sysprep
- Capture Image Version #1
- Deploy image Version #1
When it came time to update the image the process continues as follows
- Deploy Image Version #1 to a machine
- Make changes to image
- Run sysprep
- Capture Image Version #2
- Deploy image Version #2
This process may go on and on. The issue with this type of image build process is that over time it becomes very difficult to troubleshoot any issues with this image because the process for building the image has been a manual process. An example of an issue that can be attributed to this process
818171 “An Error Has Been Encountered That Prevents Setup from Continuing” Error Message When Sysprep Mini Wizard Runs
There could be many other issues that could arise out of this type of image build practice.
Some of the disadvantages of this type of process include
- Requires interaction by the user or deployment technician.
- Increases the risk of introducing configuration errors.
- Difficult if not impossible to reproduce steps on how an image was created
With the release of Microsoft Deployment Toolkit we now have a tool that allows you create a fully automated consistent method for building a reference image and it supports all operating systems including Windows XP and Windows Server 2003. With MDT the general process looks like this:
- Setup your MDT server
- Add the operating system source files(not a custom install.wim), applications, drivers, and updates
- Create task sequence called “Build reference image”
- As part of this task sequence choose the option to prepare and capture the image
- On your reference system (physical or virtual) boot into the Lite Touch image and choose the “Build reference image” task sequence.
- MDT installs Windows and all your other components and also runs sysprep and captures the image for you
- Import this image into MDT
- Create a task sequence to deploy it such as “Deploy Custom Image version #1”
- Deploy the image to your hardware using the “Deploy Custom Image Version #1” task sequence
When it comes time to update your image you do the following
- Make your changes in the MDT workbench for the image. For example
- add some new drivers
- add new updates
- add new applications
- add some new drivers
- On your reference image boot into the lite touch image and choose the “Build Reference image” task sequence. Note that through the use of customsettings.ini or custom database you can fully automate the prompts so it requires no interaction
- MDT installs Windows and all your other components and also runs sysprep and captures the image for you
- Import this new image into MDT
- Create a new task sequence to deploy it, for example “Deploy Custom Image Version #2”
- Deploy the image to your hardware using the “Deploy Custom Image Version #2” task sequence
The difference is that you rebuild your reference image from scratch each time and sysprep is only run one time. The advantages of this type of process include:
- Consistent process for building the reference image
- Requires no modification of the default install.wim
- Uses built in mechanisms of setup to add drivers and updates to the install
- Easy to add/remove components for testing
- No interaction required by the user or deployment technician.
- Decreases the risk of introducing configuration errors.
With MDT automating the process of installing the operating system, drivers, updates, applications, and the capture of the image you ensure that each time you want to update an image the image is rebuilt in a consistent automated fashion. This image is also prepared with sysprep only once which helps prevent the random issues with images that have had sysprep run on them many times.
Hope this helps with your deployments.
Scott McArthur
Senior Support Escalation Engineer
Microsoft Enterprise Platforms Support