Re: Move existing Vcenter, Connection Server & Security Server to new hardware

I recently performed a couple similar migrations moving all servers from 2008 R2 to 2012 R2. The View environments were 100% linked clone desktops. This is a 3 step process:

1. Upgrade View
2. Move vCenter to new host
3. Upgrade vCenter

The basic steps are:

1. Upgrade View:
   • Backup all databases and take snapshots of all VMs.
   • Disable vCenter Provisioning in View Admin
   • Build up new 2012 R2 View Composer Server
     • install SQL Express and restore Composer database from backup
     • Install View Composer software using existing Database
   • After installation change the View Composer server in View Admin
   • Verify Domain Information, Enter User/Password if needed.
   • Turn provisioning back on and verify connection to Composer
   • Power off old Composer Server
   • Upgrade an existing 2008 R2 View Connection server (don't skip this step)
   • Build up new 2012 R2 View Connection Servers
     • "During install select "Replica" and point to the existing server you upgraded.
     • Repeat for all connection servers needed
   • Build up new 2012 R2 View Security Servers
   • Test functionality
   • After all new servers are online, uninstall View Components from old servers and power down.
2. Move vCenter:
   • Backup all databases (SQL, ADAM) and take snapshots of all VMs.
   • Backup SSL Certs
     
   • Disable vCenter Provisioning in View Admin
   • Power off vCenter and delete computer account from Domain
   • Build new 2012 R2 vCenter server with same Name and IP address
     • Add to Domain
     • Install SQL Express and restore VCDB (UMDB optional)
     • Import SSL certs from backup
     • Create ODBC DSN's for SQL databases
     • Install vCenter Server software (Same version as you were running on old hardware)
     • Select "Use Existing Database" and "Keep my Data"
     • After install, Restore ADAM database
     • Reboot
   • Log into Web Client and verify functionality and no SSL errors
   • Reconnect Hosts if needed. (Might need to restart management agents)
   • Enable vCenter Provisioning in View Admin and test View Composer actions (recompose/refresh)
3. Upgrade vCenter:

• Perform documented in-place upgrade from vSphere 5.5 to 6.0

If you would like a more detailed plan, let me know!