6.0.2

Table Of Contents
14 From the list of available datastores, select the location where all the virtual machine conguration les
and virtual disks will be stored and, optionally, enable thin provisioning by selecting Enable Thin Disk
Mode.
15 On the Set up temporary network page, set up the network seings.
The IP address or the FQDN of the appliance is used as a system name. It is recommended to use an
FQDN. However, if you want to use an IP address, use static IP address allocation for the appliance,
because IP addresses allocated by DHCP might change.
Option Action
Choose a
network
Select the network to which to connect the new appliance temporarily.
Verify that the temporary network provides connectivity between the source vCenter Server and the
target vCenter Server Appliance.
The networks displayed in the drop-down menu depend on the network seings of the target server.
If you are deploying the appliance directly on an ESXi host, non-ephemeral distributed virtual port
groups are not supported and are not displayed in the drop-down menu.
I If you want to assign a temporary IPv4 address with DHCP allocation, you must select
a network that is associated with a port group which accepts MAC address changes.
Network
type
Select how to allocate the IP address of the appliance.
n
Static
You are prompted to enter the IP address and network seings.
n
DHCP
A DHCP server is used to allocate the IP address. Select this option only if a DHCP server is
available in your environment.
If you use an IP address as a system name, you cannot change the IP address and update the DNS
seings after deployment.
16 Review the VMware Customer Experience Improvement Program (CEIP) page and choose if you want
to join the program.
For information about the CEIP, see the Conguring Customer Experience Improvement Program
section in vCenter Server and Host Management.
17 On the Ready to complete page, review the seings for the vCenter Single Sign-On migration and click
Finish to complete the process.
The source vCenter Single Sign-On is migrated from Windows to an appliance. The old vCenter Single Sign-
On on Windows is powered o and the new appliance starts.
What to do next
Verify that your migration to an appliance was successful. For verication steps, see “Verify Your vCenter
Server Appliance Migration Is Successful,” on page 51.
For the new Platform Services Controller appliance to replicate infrastructure data with other
Platform Services Controller instances, you must migrate or upgrade all joined vCenter Single Sign-On
instances within the vCenter Single Sign-On domain to the same version.
After you migrate all joined vCenter Single Sign-On instances, you can migrate the vCenter Server instances
within the vCenter Single Sign-On domain. For information on migrating vCenter Server instances to
appliances, see
vSphere Migration
46 VMware, Inc.