has anyone been able to migrate horizon view 6.2 from vcenter 5.5 to 6.0?
do a brand new installation or migrastion? what do you do with the replica vm? how do you move that to vcenter 6? cannot edit the replica vm to change the dvport group
do i need to upgrade before moving to vcenter 6.0?
so process is
1. add new vcenter 6.0 to horizon view connection server
2. move view template and register with vcenter 6.0
Horizon View 6.1 is the first version of View that supports vCenter 6, so if you're at 6.0.1, you'd need to upgrade your View components. This process covers how to address both linked clone and full clone pools...at a high level.
i dont have new hosts in vcenter 6.0
so I need to disconnect the 5.5 hosts and move to vc6
but the problem now that i have is that the
replica vms were created on the dvportgroup and there is no way I can change that and move to vss before moving the host to vc6
any idea what to do here?
Yes, move one of the hosts from your 5.5 vCenter to the 6.0 vCenter. Said host should contain your parent VM's that will be used to recompose the pools.
Replicas are clones of the parent based on the specified snapshot that are created when a linked clone pool is composed, so new replicas will be created when the pools associated with the new vCenter are composed. Be sure to update the port group assignment of the parent VMs and take a new snapshot prior to composing the pool.
So I just went through this as a rough draft. I upgraded our current infrastructure from horizon 6.1 to horizon 6.2. We were on vsphere 5.5 update 1. We setup a new vcenter server for 6.0 update 1, and took a spare host out of the cluster and upgraded that one host to esxi 6.0 and created a new cluster for that one host. Than I went into our Horizon console and added the newly created vCenter 6.0 server with ease. Now I can deploy windows 10 like butter! What I did with a few machines is removed them from their current pool and than removed them from inventory in vCenter 5.5 and created a new manual pool on the vCenter 6.0 environment, added the VM to inventory on the new 6.0 vCenter and Host, than I was able to add it to the newly created manual pool.
I can start creating new pools, i've never converted a manual pool to an automated pool so I can research that or just leave the older machines in a manual pool and create a new pool for new machines.
You'd want to create the pools as automated initially, change the type to a manual pool to add the persistent desktops to your pool, and then change it back to automated. Here's a post on how to do that: Manually Add Desktop to Automated Pool | planetmattblog
Also, if you've got Enhanced Message Security Mode enabled on the Connection Server (which is enabled by default), you may have some issues with an agent prior to 6.1. Here's some info on that: VMware KB: How to change a Horizon 6 version 6.1 environment from Enhanced message security mode to ...
The Connection and Composer Servers are not required to be in the same vCenter as the desktops, but if your plan is to migrate everything from the old vCenter to the new vCenter, they'll need to be brought over at some point in the process.