Migrate VMware View Administrator 5.1.2

[rlivermore]

Has anyone migrated VMware View Admin 5.x from one host and datastore to a new host/datastore? What were the steps involved and what was your experience like? Just wondering if I should just start over with a new install since it only has 3 VDI's on it.

[mittim12]

It all depends on the environments.   If you can add the host into the cluster and your using linked clones then it could be as simple as using a rebalance.    

[mpryor]

Are you talking about moving the VM that is hosting the View Connection Server component? If so, there is no tie to the physical host at all so assuming you just want to move the VM around without any changes there's not a lot to worry about other than potential downtime while the VM is powered off if you don't have vmotion configured.

Making changes to the VM itself: we don't support changing the hostname/domain membership of a CS after installation, and if you need to change the IP address (but keep FQHN the same) there are a couple of manual steps you need to perform if using certain features (PSG needs IP address to be correctly set in the admin UI, IPSec tunnel with security servers will need to be updated if configured).

[ThatVirtualBoy]

Changing the host/datastore for the broker shouldn't cause any problems. As long as the network requirements outlined here VMware KB: Network connectivity requirements for VMware View Manager 4.5 and later are still in place.

[rlivermore]

Outside of moving the VM from one host and datastore to another I'm not planning on making any other changes to the VM, it will keep the same name and IP address. If that is true are there any changes that will need to be made post migration?

[mpryor]

No, nothing needs to change to just move the VM itself around.

[pcwizchick]

I just did this. We got new Intel hosts to replace oler AMD hosts and I had to migrate the VM's to the new Hosts.  For the View Servers, I simply powered them off and migrated them in Vcenter, moving tthe vCenter host last. For the vCenter server , since vCenter couldn't be used, I powered it off, removed from inventory in one cluster and then added to inventory on the new cluster and powered it on.  If you use a serperate server for the vCenter database, you will be kicked off of vCenter.  Restarting the virtual server service on the vCenter server after the database server was migrated and powered back fixed that issue.  Hope this helps.