
You’ll need to provide an (or whatever name you had set up for SSO domain). Mount the VCSA 6.7 ISO and Launch Migration Assistant Mount the latest VCSA ISO > Go to a subfolder on the root called Migration-assistant > Execute the VMware-Migration-Assistant.exe. At first, connect to your vCenter server on Windows with elevated privileges. Migration of Windows-based vCenter to VCSA – The steps
Source vCenter server (and PSC, if separated) are not using DHCP. – Act as part of the operating system (if the user is a domain user) If your vCenter Server service is running in a user account other than the Local System account, verify that the user account, in which the vCenter Server service is running, has the following permissions:. If you’re using Fully qualified domain name (FQDN), make sure that the management workstation you’re using to launch and monitor the migration process and the destination ESXi or vCenter are on the same DNS server. Clock synchronization of the target machines on the vSphere network before migration starts. Source and target systems must meet specific software and hardware requirements before you can migrate a vCenter Server, vCenter Single Sign-On, or Platform Services Controller deployment to a vCenter Server Appliance or Platform Services Controller appliance. However, you might also be interested in a CLI method which uses a JSON template. In this post, we will use a graphical user interface (GUI) method for the migration process. If you have installed vSphere Update Manager (VUM) as a side product within your vCenter server on Windows or if it runs on a separate VM, both ways are supported and you can migrate to VCSA 6.7 U1 You can also have external Platform service controllers (PSC), where v6.0 and 6.5 are supported.
You can migrate from vCenter server 6.0 or 6.5 into the VCSA 6.7 U1. In case something goes wrong, you can always revert back to your existing environment. For example, you should make a full backup of your existing vCenter server. Some guidelines, however, shall be respected. You don’t need to have any Linux skills in order to migrate your vCenter server into VCSA. However, the migration is very smooth and very straightforward thanks to those assistants. The migration is semi-automatic, where you need to perform some manual tasks and follow assistants. Today we will demonstrate the migration of Windows-based vCenter server to VMware VCSA. StarWind Virtual Tape Library (VTL) OEM.