The following example displays the SIDs for four local user accounts. Notice that only the last four digits are incremented as new accounts are added.
S-1-5-21-191058668-193157475-1542849698-1000 User 1a
S-1-5-21-191058668-193157475-1542849698-1001 User 2
S-1-5-21-191058668-193157475-1542849698-1002 User 3
In addition to the computer SID, many other components and features must be cleaned up, generalized, or specialized in order to be imaged. Some examples include the following:
- Event logs
- Network settings
- Windows Media player settings
- Shell settings
Note This is not a comprehensive list.
We support the following operating systems that are prepared by using the Sysprep utility and then imaged:
- Windows NT Workstation 4.0
- Windows NT Server 4.0 (stand-alone server, not primary domain controllers or backup domain controllers)
- Windows 2000 Professional
- Windows 2000 Server (must be imaged before you run DCPromo)
- Windows 2000 Advanced Server
- Windows XP Home Edition
- Windows XP Professional
- Windows Server 2003, Standard Edition
- Windows Server 2003, Datacenter Edition
- Windows Server 2003, Enterprise Edition
- Windows Server 2003, Web Edition
- All versions of Windows Vista
- All versions of Windows Server 2008
- All versions of Windows 7
- All versions of Windows Server 2008 R2
- All versions of Windows 8
- All versions of Windows Server 2012
- All versions of Windows 10
- All versions of Windows Server 2016
Note If an image was created without using Sysprep, we do not support the running of Sysprep after the image is deployed as a way to bring the computer back into compliance. Sysprep must be run before the capture of the image.
Windows 8 and Windows Server 2012 specific information
- Tile, badge, and toast notifications do not update even though Internet connectivity is available.
- Apps that rely on RAW notification do not work as expected. For example, you notice significantly reduced functionality in Mail, Calendar, and Messaging.
- It takes a long time to synchronize changes for roaming and family safety settings.
To resolve these issues, use one of the following methods:
- Configure the computers by using the Sysprep /generalize command, and then deploy the image.
- Replace the existing user account with a new account. The device identifier is stored as part of the user profile. Each new NTUser account that is added to a computer will receive a new identifier.
Windows XPWindows Server 2003Windows 7
Windows Automated Installation Kit for Windows 7 documentation (May 2010 Update)
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.