GD Bloggers

This is the blog site for Microsoft Global Delivery Communities focused in sharing the technical knowledge about devices, apps and cloud.
Follow Us On Twitter! Subscribe To Our Blog! Contact Us

SYSPREP Tips and Supported Server Roles

SYSPREP Tips and Supported Server Roles

  • Comments 1
  • Likes
  • If you are trying to reproduce unique virtual machines, always check the generalize checkbox (or use SYSPREP /generalize) to make sure the machine gets a new SID, NIC GUIDs and other identifiers, if you don't, your AD DS will have the impression that you have two of the same machine (since it identifies machines by SIDs) and the situation can get messy. Nonetheless, some features like Windows Network Load Balancing can get confused since multiple NICs have the same GUID.
  • SYSPREP can only reset the Product Activation Key 3 times.
  • Use the sysprep /oobe (which refers to the Out Of the Box Experience), to allow for the customization for Windows settings after the reboot
  • Do not use SYSPREP on Upgrade versions of Windows, use it only for clean installations, the SYSPREP version of each installation of Windows could be different and this can cause trouble
  • Before you SYSPREP a virtual machine, always make sure you are NOT running the CLI for SYSPREP on the Hyper-V host rather than the virtual machine itself :) it happened to me once, but thank God it was in my own testing lab. 

Furthermore, this is a table that includes the roles that are supported for SYSPREP.  If you have to SYSPREP a machine that is intended to host a certain unsupported role, SYSPREP it before the role is installed.

Server Role Sysprep Support

Active Directory Certificate Server (AD CS)

No

Active Directory Domain Services (AD DS)

No

Active Directory Federation Services (AD FS)

No

Active Directory Lightweight Directory Services (AD LDS)

No

Active Directory Rights Management Server (AD RMS)

No

Application Server

Yes

DHCP Server

Yes

DNS Server

No

Fax Server

No

File Services

No

Network Policy and Access Services

No

Network Policy Routing and Remote Access Services

Yes

Print Services

No

Terminal Services

Yes

Not supported in scenarios where the master Windows image is joined to a domain.

UDDI Services

No

Web Server (Internet Information Services)

Yes

Does not support Sysprep with encrypted credentials in applicationhost.config.

Windows Deployment Services

No

Comments
  • I am afraid your first bullet point isn't factual. See Mark Russinovich's blog post on the topic of SIDs and how they (don't) matter for AD DS: blogs.technet.com/.../3291024.aspx

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment