Looking for a little advice...We currently have a Production Horizon View 7 environment consisting of (2) 7.2 Connection Servers and (2) 7.2 View Composers. These are running on Server 2012r2. We have been unsuccessful upgrading the Connection Servers to Horizon View 7.8 (suspect due to a STIG or ADAM instance issue), View Composers will upgrade without issue. We have a project that has the Horizon View environment getting rebuilt, using Server 2016, and folding into the new vCenter 6.7 environment we are currently building out. We will also be moving to Windows 10 1809 in the next 3-6 weeks, which is not supported with Horizon View 7.2 and is causing some issues with VMware Tools (yes the hpet0.present work-around seems to help but is not 100%). To add another fun wrinkle, the Connection Server certs are going to expire in JAN 2020. I also want to move to Global Entitlements (Cloud Pod) in this environment and our current Production Connection Servers are failing to initialize (might be part of the upgrade issues).
(2) Server 2012 based Horizon View Connection servers and View Composers.
(2) vCenters (6.5 VCSAs) that host the non persistent virtual desktop environment
I believe that I have 2 options to get the Connection Servers updated in time to support the move to Windows 10 1809 as we are working through getting the vCenter 6.7 environment up and stable.
Build (2) Server 2016 based Standard Horizon View 7.8 Connection Servers. Initialize Cloud Pod and ensure they are replicating properly. Schedule a maintenance window. Move entitlements off the pools based in one of the vCenters. Delete the desktops/pools running in that vCenter. Remove the vCenter and Composer from Horizon View. Update the View Composer to 7.8. Add the vCenter and Composer to the 7.8 Horizon View pod. Ensure that I can build out machines/pools. Add Move the entitlements back to the Global Entitlement. Repeat the process for the second vCenter and Composer. Update all my endpoints with the new Connection Server LB certificate.
I am hoping that by deleting the virtual desktops, that it keeps everything (database/inventory) clean.
Build (2) Horizon View 7.8 Connection Servers (on Server 2016) and make them replicas of the current 7.2 Production Connection Servers. Schedule a maintenance window. Update the endpoints with the new Horizon View LB certificate. Update the View Composers to Horizon View 7.8. Remove the Horizon View 7.2 Connection Servers from the replica group.This doesn't get me Cloud Pod (yes I can initialize it after the fact, but that is not how VMware says it should be done).
Since these are production assets, I probably would not get approval to take one Connection Server down, export out it's certificates, and replace it with a new (using the same name/IP/certificate) 7.8 Connection Server. Then take the other one down and repeat the process. I also have to plan to build out new View Composers (don't have a DBA atm, hence why I am not going to build them now). Once my vCenter 6.7 infrastructure is up, I can tie the new 7.8 View Composers to them and add them directly to the 7.8 Connection Servers (that will now be Production). This will allow me to keep all the inventory separate as well. Leadership is getting very leery of "in place upgrades" of the Production environments, so if I can use one of the above processes moving forward that is even better.
So which option looks better from everyone's experience...or I am missing other cleaner and easier options? Thanks in advance!
Also, another quick question. Will simply deleting the virtual desktops and pools from the View Composer-vCenter allow a "clean" rebuild of the desktops using the new 7.8 Connection Servers? Or do, or should I, just bite the bullet and build out new View Composers to attach to the existing vCenters? Either way I believe I would want to clear all out the desktop pools/virtual machines to ensure that my inventory is as clean as possible?