Horizon 7 Upgrades from 7.5.1 to 7.5.2

Horizon 7 Upgrades  from  7.5.1 to 7.5.2
 
1. Please put maintenance mode in monitoring tool
2.Take snapshots of VM's. 
3. log in to a jump server and take the RDP of target servers from it.

Pre Upgrade Tasks:

4.      Download the below software before proceeding with the upgrade.
o   Connection/Security server installer filename is VMware-view-connection server-x86_64-7.5.2.exe
o   Horizon Agent installer filename is VMware-viewagent-x86_64-7.5.2.exe
o   VMware-Horizon-Extras-Bundle-7.5.2.zip
5.      The license can be Horizon 7 Enterprise Concurrent or Named.
6.      Take a snapshot of the RDS Hosts virtual machines. It can be an online snapshot, and you don't need the memory.
7.      Open Horizon Administrator and screenshot all the global settings and settings for desktops and pools: Pools section and Desktops section in the Inventory tree, and the Global Settings section in the View Configuration tree.
8.      Open Horizon Administrator and screenshot all the settings that are specific to each Connection server.
(For example, go to View Configuration > Servers > Connection Servers, select the Connection Server instance in the table, and click Edit. You can take a screenshot of each tab in the Edit Connection Server Settings dialog box).
 9.      Open Horizon Administrator and screenshot the settings for the Security server. Go to View Configuration > Servers and click the Security Servers tab.
               For example, select the security server, click Edit, and take a screenshot of the settings.
For both Connection and Security Servers, verify that Windows Firewall with Advanced Security is set to on.
Document the IP address, net mask, gateway, DNS server addresses and system name of the machine on which each Connection, Security Server and RDS Host server is installed.
On the Connection server (just one) use the vdmexport.exe utility to back up the LDAP database.
                                                     i.     You can run the vdmexport command on any Connection Server instance. If you have multiple Connection Server instances in a replicated group, you only need to export the data from one server. All replicated instances contain the same configuration data.
                                                   ii.     Locate the vdmexport.exe command executable file installed with Connection Server in the default path.
1.      C:\Program Files\VMware\VMware View\Server\tools\bin
                                                  iii.     Log in to a Connection Server instance as a user in the Administrators or Administrators (Read only) role. Best to login with the VDI service account (vdiadmin or another).
                                                  iv.     Select Start > Command Prompt.
                                                   v.     Type the following and press enter:
1.      cd C:\Program Files\VMware\VMware View\Server\tools\bin
                                                  vi.     You can export the data in plain text format (verbatim) by using the -v option. For example, type:
1.      vdmexport -f Myexport.LDF -v
                                                 vii.     The file will be put into the same Bin directory. Just in case, save the exported file on a different server.
If you have multiple Connection and Security Servers, always upgrade each Connection and Security server as a pair, then move on to the next pair. Afterwards, upgrade all RDS Hosts one at a time. For example:
                                                     i.     Upgrade Connection Server XXXX, then its paired Security Server XXXX.
                                                   ii.     Upgrade RDS Host XXXX
                                                  iii.     Upgrade RDS HostXXXXX
                                                  iv.     
Upgrading the Connection Server(s):
If you have more than 1 Connection server), disable the server that hosts the Connection Server instance that you are about to upgrade. If you have only 1 Connection Server, disable that server.
                                                     i.         Log in to Horizon Administrator.
                                                   ii.         Go to View Configuration > Servers and click the Connection Servers tab.
                                                  iii.         Select the Connection Server instance in the list and click the Disable button above the table.
                                                  iv.         Click OK to confirm disabling the server.
On the virtual machine with the Connection Server instance, download and run the installer for the new version of Connection Server.
                                                     i.     The installer filename is VMware-viewconnectionserver-x86_64-7.5.2.exe.
You do not need to stop any services before performing the upgrade. The installer stops and restarts services as necessary. In fact, the VMwareVDMDS service must be running in order to upgrade the View LDAP database.
The installer determines that an older version is already installed and performs an upgrade. The installer displays fewer installation options than during a fresh installation. The View LDAP is also upgraded.
Note: Before performing the upgrade, the installer does a replication status check to determine whether the server can communicate with the other servers in the replicated group and whether the server can fetch LDAP updates from the other servers in the group. If the status check fails, the upgrade does not proceed.
After the installer is finished, reboot the virtual machine.
After the reboot, verify that the VMware Horizon Connection Server service starts. This can take a long time — wait at least 15 min before worrying.
Log in to Horizon Administrator. This again can take an even longer time. Even if the service is started, the website might not appear— wait at least 15 min before worrying.
Enable the Connection Server instance that you just upgraded. 
                                                     i.         Go to View Configuration > Servers and click the Connection Servers tab.
                                                   ii.         Select the Connection Server instance in the list and click the Enable button above the table.
                                                  iii.         In the Version column, verify that the new version is displayed.
Go to View Configuration > Product Licensing and Usage, click Edit License, enter the license key, and click OK. If you already see a license there, it took the old license, so do not change anything.
Remove IPsec rules for the security server paired with the Connection Server instance that you just upgraded.
                                                     i.     In Horizon Administrator, click View Configuration > Servers.
                                                   ii.     In the Security Servers tab, select a Security server and click More Commands > Prepare for Upgrade or Reinstallation.
                                                  iii.     The IPsec rules are removed and the Prepare for Upgrade or Reinstallation setting becomes inactive, indicating that you can reinstall or upgrade the Security server.
Configure a security server pairing password using the latest version of Horizon Administrator.
                                                     i.     The security server pairing password is a one-time password that permits a Security server to be paired with a Connection Server instance. The password becomes invalid after you provide it to the Connection Server installation program.
1.      Note: You cannot pair an older version of the Security server with the current version of the Connection Server. If you configure a pairing password on the current version of Connection Server and try to install an older version of Security server, the pairing password will be invalid.
                                                   ii.     In Horizon Administrator, select View Configuration > Servers.
                                                  iii.     In the Connection Servers tab, select the Connection Server instance to pair with the Security server.
                                                  iv.     From the More Commands drop-down menu, select Specify Security Server Pairing Password.
                                                   v.     Type the password in the Pairing password and Confirm password text boxes and specify a password timeout value.
1.      You must use the password within the specified timeout period.
                                                  vi.     Click OK to configure the password.
Upgrading the Security Server(s):
Login to the Security Server you are upgrading as a Local Administrator. Most Security Servers are NOT joined to a domain, so you need to know the local password. If this Security Server is part of the domain, it is best to login with the VDI service account (vdiadmin or another).
On the VM of the Security server, download and run the installer for the latest version of Connection Server. 
                                                     i.     Note: The Connection server and Security server installer is the same file.
                                                   ii.     The installer filename is VMware-viewconnectionserver-x86_64-7.5.2.exe
The installer determines that an older version is already installed and performs an upgrade. The installer displays fewer installation options than during a fresh installation.
You will be prompted to supply the Security Server pairing password.
You might be prompted to dismiss a message box notifying you that the Security Server service was stopped. The installer stops the service in preparation for the upgrade.
After the installer is finished, reboot the virtual machine.
After the reboot, verify that the VMware Horizon View Security Server service is started. This can take a long time — wait at least 15 min before worrying.
Log in to Horizon Administrator, select the Security server in the Dashboard, and verify that the security server is now at the latest version. This can take an even longer time — wait at least 15 min before worrying.
Verify that the dashboard icons for the Connection server instances are also are green.
                                                     i.     If any instances have red icons, click the instance to determine the replication status.
This almost never happens — In Horizon Administrator, go to View Configuration > Servers > Security Servers tab and remove any duplicate Security servers from the list.
                                                     i.     The automated security server pairing mechanism can produce duplicate entries in the Security Servers list if the full system name does not match the name that was assigned when the security server was originally created.
Upgrading the RDS Host(s):
Preparing for the RDSH Host upgrade.
                                                     i.     Verify that the RDS host currently hosting remote desktops or applications is running Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2. 
1.      Windows Server 2008 (Terminal Services) is not a supported operating system for this release. If you do not have a supported Windows Server operating system, you must do a fresh installation rather than an upgrade. 
                                                   ii.     Verify that the RDS Host role is installed in the operating system. 
1.      Log in to the RDS host as an administrator.
2.      Start Server Manager.
3.      Select Roles in the navigation tree.
4.      Click Add Roles to start the Add Role wizard.
5.      Verify that the role Remote Desktop Services is already selected.
                                                  iii.     Verify that you have a domain user account with administrative privileges on the hosts that you will use to run the installer and perform the upgrade. Best is to use the VDI service account like vdiadmin or other.
                                                  iv.     Verify that you and the users have logged off from all remote desktops and remote applications.
                                                   v.     In Horizon Administrator, edit the desktop pool settings for each pool to disable the pool.
1.      Go to Catalog > Desktop Pools, select the pool, and click Edit.
RDS Host Upgrade Procedure
                                                     i.     On the RDS host, log in as an administrator. Best if you are the VDI service account used on the Horizon Connection Server (like vdiadmin or other).
                                                   ii.     Download and run the installer for the new version of Horizon Agent.
1.      The installer filename is VMware-viewagent-x86_64-7.5.2.exe
                                                  iii.     To start the Horizon Agent installation program, double-click the installer file.
                                                  iv.     Select the Internet Protocol (IP) version, IPv4.
                                                   v.     Select your custom setup options.
1.      Select:
a.      USB Redirection
b.      HTML Access
c.      3D RDSH
d.      Client Drive Redirection
e.      Virtual Printing
f.       Horizon Performance Tracker
2.      Uncheck the checkboxes for everything else (if any are checked).
                                                  vi.     In the Server text box, type the host name or IP address of a Connection Server host. This step might be skipped if it is an in-place upgrade of the agent.
1.      During installation, the installer registers the RDS host with this Connection Server instance. After registration, the specified Connection Server instance, and any additional instances in the same Connection Server group, can communicate with the RDS host.
                                                 vii.     Select an authentication method to register the RDS host with the Connection Server instance.
1.      Select "Specify administrator credentials"
2.      You must provide the username and password of a Connection Server administrator in the Username and Password text boxes. Service account used for VDI is best, like vdiadmin or another.
a.      The user account must be a domain user with access to View LDAP on the View Connection Server instance. A local user does not work.
                                               viii.     After the installer is finished, reboot the virtual machine.
                                                  ix.     After the reboot, in Horizon Administrator, edit the desktop pool settings for each pool to Enable the pool.
1.      Go to Catalog > Desktop Pools, select the pool, and click Edit.
Post-Upgrade Tasks:
Test connecting to at least one desktop or application in each pool.
Upgrade the Group Policy templates used in Active Directory.
                                                     i.     Horizon 7 provides several component-specific Group Policy Administrative ADMX and ADML template files. With each Horizon build, newer GPO templates are also released.
                                                   ii.     All ADMX/ADML files that provide group policy settings for Horizon 7 are available in VMware-Horizon-Extras-Bundle-7.5.2.zip.
                                                  iii.     Ask the client if they have a Central Store for their GPO templates (Most of our clients do NOT have one).
1.      If there is a central store, login to 1 Domain Controller as an Administrator, place all the ADMX files in the zip into “C:\Windows\sysvol\domain\policies\PolicyDefinitions”.
a.      Replace all existing files, if any are there.
2.      If there is a central store, login to the same Domain Controller as an Administrator, place all the ADML files in the zip into “C:\Windows\sysvol\domain\policies\PolicyDefinitions\en-us”.
a.      Replace all existing files, if any are there.
3.      You do NOT need to go to other Domain Controllers, as the files will automatically replicate.
                                                  iv.     If there is no Central Store for GPO templates.
1.      Login to the first Domain Controller as an Administrator, place all the ADMX files in the zip into “C:\Windows\PolicyDefinitions”.
a.      Replace all existing files, if any are there.
2.      Go to the same Domain Controller as an Administrator, place all the ADML files in the zip into “C:\Windows\PolicyDefinitions\en-us”.
a.      Replace all existing files, if any are there.
3.      You need to go to all other Domain Controllers and put the files in the same locations on each Domain Controller.
Wait 2 business days. Delete the VM snapshots of Connection Servers, Security Servers and RDS Hosts that you did.
Wait 4 business days. Delete the Myexport.LDF file you exported using vdmexport.exe utility.

Enable GingerCannot connect to Ginger Check your internet connection
or reload the browserDisable in this text fieldRephraseRephrase current sentenceEdit in Ginger×Enable GingerCannot connect to Ginger Check your internet connection
or reload the browserDisable in this text fieldRephraseRephrase current sentenceEdit in Ginger×Enable GingerCannot connect to Ginger Check your internet connection
or reload the browserDisable in this text fieldRephraseRephrase current sentenceEdit in Ginger×