6.0.1

Table Of Contents
10 Select IPv6 to configure the virtual machine to use IPv6 network.
Note that the virtual machine can retain the IP address allocated from the network as well as IPv6
addresses. Microsoft supports IPv6 for Windows Server 2003, Windows XP with Service Pack 1 (SP1) or
later, and Windows CE .NET 4.1 or later. However, these operating systems have limited IPv6 support
for built-in applications, system services, and are not recommended for IPv6 deployment.
a Select Prompt user for an address when the specification is used. Selecting this option prompts
you to enter either IPv4 or IPv6 address.
b Select Use the following IPv6 addresses to choose an IPv6 address from the list.
n
Click the pencil icon to enter additional IPv6 addresses. You can specify the full address or
shorten it by using zero compression and zero suppression. You should specify at least one
IPv6 address. You can edit an existing address, but should not duplicate existing IPv6
addresses.
n
Enter subnet mask prefix. The prefix length should be between 1 to 128 where the default
value is 64. Gateway is enabled by default, except when you choose Do not use IPv6.
11 Select DNS and specify DNS server address and click OK.
12 Select WINS and specify primary and secondary WINS information.
13 Select how the virtual machine will participate in the network and click Next.
Option Action
Workgroup
Type a workgroup name. For example, MSHOME.
Windows Server Domain
a Type the domain name.
b Type the user name and password for a user account that has
permission to add a computer to the specified domain.
14 Select Generate New Security ID (SID) 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.
15 Save the customized options as an .xml file.
a Select Save this customization specification for later use.
b Specify the filename for the specification and click Next.
16 Click Finish to save your changes.
You return to the Deploy Template or to the Clone Virtual Machine wizard. The customization is finished
after you complete the Deploy Template or the Clone Virtual Machine wizard.
When the new virtual machine starts for the first time, the guest operating system runs finalization scripts to
complete the customization process. The virtual machine might restart several times during this process.
If the guest operating system pauses when the new virtual machine starts, it might be waiting for you to
correct errors, such as an incorrect product key or an invalid user name. Open the virtual machine’s console
to determine whether the system is waiting for information.
What to do next
After you deploy and customize versions of Windows XP or Windows 2003 that are not volume licensed,
you might need to reactivate your operating system on the new virtual machine.
Chapter 2 Deploying Virtual Machines
VMware, Inc. 51