Migrating vCenter 5.1 with Horizon View attached

We currently have a vSphere 5.1 environment and (installed separately) a Horizon View 5.2 environment. Our vCenter server is on a physical server which will be upgraded shortly to new hardware. vCenter uses and locally installed SQL Server instance that will be manually migrated to the new server. View Composer and the View Connector both use their local default SQL and ADAM databases respectively.

We don't want to have to make any changes in Horizon View if we don't have to. Currently we have some dedicated linked-clone pools that use persistent disks and some floating linked-clone pools that use persona management.

We plan to migrate the vCenter database to the new hardware and give it the same name and IP address as the old one. We will also migrate over all the SSL certs and RSA signatures.

Would this be enough to make sure Horizon View reconnects it's pools on the new server? Is there something else we need to do to make sure users can connect to their dedicated Horizon View desktops?
Who is Participating?
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
VC_CONFIG_ENTRY does contain the GUID for vCenter Server, because you can get two entries, which causes issues.

if after the vCenter rebuild, View Composer no longer functions, you would have to recompose your Linked Clones as per this KB

VMware KB: Recomposing VMware View pool fails with error
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If the same names and IP Addresses are in use with vCenter Server, there should be no issues, between View and vCenter, and the DBs are the same.
stevegoldmanAuthor Commented:
Is there no UID generated for the vcenter instance that needs to match up?
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

stevegoldmanAuthor Commented:
It appears there is a VC_CONFIG_ENTRY in the View Composer database. This entry has an ID for the vCenter instance. It is still unclear whether this would change if we migrated the DBs, SSL certs, server name and IP to new hardware. Even with all that migrated, it would technically be a new vCenter instance, wouldn't it?

I'm sorry to keep harping on this point but my timetable for this is very short, we have a maintenance window to do this work this coming weekend.
stevegoldmanAuthor Commented:
Thank you for confirming. You've been a great help.

Keep up the good work.
stevegoldmanAuthor Commented:

We completed the physical server migration of vCenter. In the process we set the IP and server name the same on the new server as on the old one. The DB and SSL certs were migrated. I used the Certificate Automation Tool to reinstall the certs from the old server. (I had saved the certs that had been generated for that server in a secure location previously.)

Refer to: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2041600
and http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2037432

Once the DB and SSL certs were in place and all services were restarted, Horizon VMware View was tested as suggested by hanccocka. The recompose was successful and everything linked back up just fine.

Hopefully this is useful for someone else in a similar situation since there are no official guidelines on how to migrate vcenter with Horizon View.

Thanks again for your advice, hanccocka.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
No problems, glad it all went well....
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.