6.7

Table Of Contents
n
Select Prompt the user for an address when the specification is used if you want vCenter
Serve to prompt you to enter an IP address. You can enter either an IPv4 or an IPv6 address.
n
Select Use the following IPv6 addresses to choose an IPv6 address from the list. You can also
add IPv6 addresses manually.
Gateway is enabled by default, except when you choose Do not use IPv6
10 On the DNS settings page, enter DNS and domain settings information. The Primary DNS,
Secondary DNS, and Tertiary DNS fields accept both IPv4 and IPv6 addresses.
11 On the Ready to complete page, review the details and click Finish to save your changes.
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
Use the Guest Customization wizard to save Windows guest operating system settings in a specification
that you can apply when cloning virtual machines or deploying from templates.
Note The default administrator password is not preserved for Windows Server 2008 after customization.
During customization, the Windows Sysprep utility deletes and recreates the administrator account on
Windows Server 2008. You must reset the administrator password when the virtual machine starts the
first time after customization.
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 and click Next.
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.
vSphere Virtual Machine Administration
VMware, Inc. 226