Migrate Windows 6.0 Vcenter to 6.7 Appliance for Horizon View env

[myesko]

Hello, We need to Migrate our Windows Vcenter server (6.0) to the VCA Appliance (6.7).

Ive been reading up on the Vcenter Appliance Migration tool that seems somewhat easy to use.  But we have Horizon View 7.12 and i cant seem to find info if there is anything i should be worried about or need to do extra, or for that matter if we should not use the migration tool and go about it a different way.

The info on the Migration tool makes it sounds like VDI would not even realize its a new vcenter, but it doesnt seem to talk about VDI.  So ide like to confirm that the migration tool is compatible with Horizon View Environments

More info on what we have

Vcenter is Windows running latest version of 6.0

Esxi Hosts are also 6.0 latest version

Horizon View is version 7.12

We have a mixture of Linked Clones with dedicated assignments and floating, plus small handful of full desktops.

Internal and External Connection server, plus Security servers. 

The main reason for the migration, we are getting a new vXrail Cluster, This requires Vcenter 6.7, plus its time to upgrade vcenter.

What we would like to do is upgrade Vcenter to 6.7 Appliance which would still control the Current cluster of esxi hosts at 6.0.  Then add the new vXrail Cluster into Vcenter.

Then we can bring up new pools on the vXrail cluster and migrate users over to the new pools. 

Hopefully all that made sense. 

Thanks for any input

Mike

[vBritinUSA]

As you are moving to a VXRail im not sure your be able to upgrade the older vCenter. I maybe wrong but i've deployed a few VXRails and they always come with their own VXRail manager and vCenter and new hosts already attached.

You can then add this to the Connection servers as a new vCenter, use the VM migration fling to move Images over and update Pools. As you use Composer you will need to spin off a new server for this as it doesn't run with the virtual appliance (1 Composer at a time).

[myesko]

Ive been talking things over with Dell and they said there is no issue using the vCenter we already have for the vXrail as long as its 6.7. 

But they werent able to give me much insight on the migration tool. 

Ide be worried if we used a new vCenter then i would have issues with all my pool and entitlements   Dont want to have to recreate them by moving to a new vCenter.

Eventually when we bring in the new vXrail we will need to migrate the master images and create new pools and entitlements but we can do it slowly.

Anyone have experience using the vcenter migration tool with a VDI env?

[nburton935]

Are you also decomissioning the original 6.0 hosts after the VxRail migration is done? You can have either the internal VCSA or external VCSA (external is BYO) - VxRail will support either.

It would be much less risky and easier to just have both environments side-by-side. The beauty is that Horizon supports multiple vCenters, so you can easily just add your new vCenter, build new pools, and start migrating users over.

Now would also be a good time to switch to Instant Clones with your new pools, and get off your linked clones. If you don't have Horizon Enterprise, you can upgrade to Horizon 8 first, which includes Instant Clones in all licensing. Linked clones are now deprecated in Horizon 8.

[vBritinUSA]

I wouldn't worry about pools & entitlments as that is managed by the connection servers. As you will use the same hostname/ip of the current vCenter that shouldn't cause you mush of an issue. Assuming you are going with the self signed cert you will need to "re trust" it in the Horizon admin page under servers(This is normal for self signed)

Spin off a new Composer server before you even start the upgrade and let that settle for a few day then make sure you snapshot the vCenter once you are ready, pause all provisioning and start.