Hi all,
How can I migrate my vCenter server used by View to another computer, preserving the existing desktop pools and user-to-desktop assignment?
Our Horizon View 5.2 environment is using a vCenter 4.1 server which I would like to migrate to 5.1 on a new system with a new ip address and hostname. We are using only dedicated statefull desktop pools with automatic assignment, we are not using linked clones. It is important that after the migration when users connect to View they automatically get the same dedicated View desktop as before the migration.
How can I accomplish this? I know how to migrate a vCenter to a different host (when not using View), my question is only about the Horizon View part.
KB article 1018045, "Moving View-managed desktops between vCenter Servers is not supported", doesn't look very hopefull.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101804...
Thank you,
AlfredJ.
Here is a procedure that I have come across, note that this is not tested or supported:
Migrate View VCenter 5.0 with View Composer 3.0 to new hardware:
6.
Hi Linjo,
thanks for your response, but I think this procedure describes the migration of the composer service, probably using stateless desktops. In our environment we don't use linked clones and we have statefull desktops. We really need the users to automatically connect to the same desktop before and after the migration.
Regards,
AlfredJ.
Yes, I did not miss that fact. But you should be able to skip the steps that involves View Composer and still migrate.
It should be much easier to do then with linked clones...
I would also recommend to do it in a test environment and document the steps.
// Linjo
Alfred,
Did you try Linjo's steps to migrate your stateful view desktops to a new vcenter instance??
Thanks in advance!
--wolfegang
Hi,
Is there any official documents from VMware on moving an Horizon View 5.2 environment running on Oracle to a new Oracle server?
Thanks
Jeff
Time consuming for sure, but this is the way I'd tackle what you're trying to do. If you're using persistent disks for users, I don't have a good answer and you should likely engage some migration help from professional services.
Real world experience for me says if you have to do this with linked clones, you're better off building a new environment and simply copying over the golden images and updating them, since they'll likely require a tools update anyway. Then do a slight of hand switcheroo on migration day. I know this doesn't apply to your use case, but knowing can't hurt.
Update sequence for vSphere 5.5 and its compatible VMware products (2057795)