6.7

Table Of Contents
The customization specification that you created is listed in the Customization Specification Manager. You
can use the specification to customize virtual machine guest operating systems.
Create a Customization Specification for Windows Using a Custom Sysprep
Answer File
A custom sysprep answer file is a file that stores various customization settings such as computer name,
licensing information, and workgroup or domain settings. You can supply a custom sysprep answer file as
an alternative to specifying many of the settings in the Guest Customization wizard.
Windows Server 2003 and Windows XP use a text file called sysprep.inf. Windows Server 2008,
Windows Vista, and Windows 7 use an XML file called sysprep.xml. You can create these files using a
text editor, or use the Microsoft Setup Manager utility to generate them. For more information about how
to create a custom sysprep answer file, see the documentation for the relevant operating system.
You can prevent Windows from assigning new virtual machines or templates with the same Security IDs
(SIDs) as the original virtual machine. Duplicate SIDs do not cause problems when the computers are
part of a domain and only domain user accounts are used. However, if the computers are part of a
Workgroup or local user accounts are used, duplicate SIDs can compromise file access controls. For
more information, see the documentation for your Microsoft Windows operating system.
Prerequisites
Ensure that all requirements for customization are met. See Guest Operating System Customization
Requirements.
Procedure
1 Select Menu > Policies and Profiles, and under Policies and Profiles, click VM Customization
Specifications.
2 Click the Create a new specification icon.
The New VM Guest Customization Spec wizard opens.
3 On the Name and target OS page, enter a name and description for the customization specification
and select Windows as a target guest OS.
4 (Optional) Select the Generate a new security identity (SID) option.
A Windows Security ID (SID) is used in some Windows operating systems to uniquely identify
systems and users. If you do not select this option, the new virtual machine has the same SID as the
virtual machine or template from which it was cloned or deployed.
Duplicate SIDs do not cause problems when the computers are part of a domain and only domain
user accounts are used. However, if the computers are part of a Workgroup or local user accounts
are used, duplicate SIDs can compromise file access controls. For more information, see the
documentation for your Microsoft Windows operating system.
5 Select Use Custom Sysprep Answer File and click Next.
vSphere Virtual Machine Administration
VMware, Inc. 229