Quite a jump I know but here I am. This is a View 5.0.1 environment so View Composer is on my vCenter machine. I'm wondering about the vCenter upgrade. I need to maintain vCenter access to my cluster throughout this process so I was thinking about cloning the VM, isolating it on the network, and do the upgrade on the clone. When I'm all done and ready to test, isolate the existing one and drop the upgraded one onto the network again. If I'm not moving VMs or provisioning new View clients there shouldn't be any database changes. Something tells me this is FAR to easy tho...so what am I missing?
The end goal here to is move the 4 hosts to ESXi and vCenter to 5.5u2 and bring my VDI environment up to Horizon 6.
Why clone the VM? Why not just take snapshots of all the VM's before the upgrade?
thought about that doing snaps...just alittle jumpy about tinkering with the existing vCenter\Composer box. I suppose so long as I am not doing any View operations then there shouldn't be a problem...
I understand, but taking a snapshot of the VM is much easier than cloning and if there is a problem it is much easier just to revert to the snapshot.
Please mark helpful and correct answers.
Thanks
Marc