Solved

Upgrade View 5.1.2 to Horizon 7

Posted on 2016-11-14
3
56 Views
Last Modified: 2016-12-01
We are planning on doing an upgrade from View 5.1.2 to Horizon 7 and I'm just trying to nail down the process.

I found another thread where it is mentioned to remove any VMWare signed certificates from the View 5.1 environment before upgrading. Is there a way I can check what certs View is currently using? I'm 90% sure they aren't self signed but as I didn't setup the environment I'm not 100% sure.
We are definitely utilising the VMware certificates for Vcentre, is that of concern or OK to keep as is? Based on the upgrade guide it appears to be accepted.

Finally, is there anyone who has done this upgrade that can offer any advice on things they found during the process (or things to look out for)?

Thanks.
0
Comment
Question by:William Wallace
  • 3
3 Comments
 

Author Comment

by:William Wallace
ID: 41898404
Some additional info i've managed to locate;

I can see that Composer (installed alongside my Vcentre) is using a self signed certificate generated by the composer installation. I found this by checking the registry keys for the SSL binding (HKLM\SYSTEM\ControlSet001\Services\HTTP\Paramaters\SSLbindings) and found the cert thumbprint. Correlated that back to the self signed certificate in cert manager.

The connection server is running a 3rd party certificate and our security server is also running a 3rd party cert.

I am busy setting up a second environment running 5.1.2 to mimic what we have in production and running an update to Horizon 7 to see what happens.

cheers.
0
 

Author Comment

by:William Wallace
ID: 41899963
Ok, so attempting to go from View 5.1.2 direct to 7 does not work.

The connection server breaks completely, grinding the upgrade to a halt.

Vmware suggest going to View 5.3 and then to 7, so i will be attempting that next (in case there is anyone else reading this thread).
0
 

Accepted Solution

by:
William Wallace earned 0 total points
ID: 41909806
Upgrading from view 5.1.2, to 5.3 & then on to 7.0.2 works no problems.

If you have old XP machines, you will need to enable TLS1.0 on your connection server (and / or security server).
Longest part of the upgrade was doing the ESX upgrades midway through.

Once view upgraded, update the agents on your templates and re-compose the pools.
Worked great for me.
0

Featured Post

VMware Disaster Recovery and Data Protection

In this expert guide, you’ll learn about the components of a Modern Data Center. You will use cases for the value-added capabilities of Veeam®, including combining backup and replication for VMware disaster recovery and using replication for data center migration.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When we have a dead host and we lose all connections to the ESXi, and we need to find a way to move all VMs from that dead ESXi host.
Is your company's data protection keeping pace with virtualization? Here are 7 dynamic ways to adapt to rapid breakthroughs in technology.
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…

912 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

24 Experts available now in Live!

Get 1:1 Help Now