How to upgrade to GPOADmin 5.20 latest release (4376484)

This Knowledge Base article outlines how to upgrade to GPOADmin 5.20

Follow the below steps to upgrade GPOADmin to version 5.20

1. Download GPOADmin 5.20 from https://support.quest.com/gpoadmin/5.20/download-new-releases
2. Login to the server that hosts the GPOADmin, as the service account
3. Install GPOADmin 5.20 on top of the existing version (5.18 or 5.19)
4. Launch the GPOADmin client and reconnect to the configuration store (AD, AD LDS or SQL)
5. Install GPOADmin 5.20 on any other server that hosts a component of GPOADmin (Client, Watcher Service, etc)

Note the following when upgrading GPOADmin:

• All registered objects should be in the available state before any upgrade.
• If you are running GPMC during an upgrade, you must close and re-open it before the GPO Management tab will display. 
• If you set a custom report folder path in a previous version, you must change the reports folder path in the User Preferences to point to the existing folder.
• Due to an upgraded encryption algorithm, the service account cannot decrypt previously encrypted passwords. If you are upgrading and using SQL as your configuration store, accessed with SQL authentication, you must re-enter the password for the connection account the first time you connect to the service.
The following pre-configured passwords will also need to be re-entered: the SQL Server Backup Store account, the SMTP notifications account, and the Exchange notifications account.
• In a minimum permissions environment, Group Policy Objects with a version of 0.x may fail to deploy correctly. To solve this, make a copy of the GPO and deploy the copy. Once this has been verified as successful, delete the original.
• After upgrading ensure the “Ensure service account has access before deployment” service option is checked in the Options dialog.
• When you upgrade the Server, you must also upgrade the Client, GPMC Extension, and Watcher Service.
• GPOADmin runs under the security context of a privileged service account that must have full access to GPOs in the managed forest. If you plan to change this account, you must unlock all GPOs before making the change.
• The supported upgrade paths are from versions 5.16 and later.
• The live environment will only be visible for GPOADmin Administrators and users who have been explicitly granted access.
As a GPOADmin administrator, however, you may want to allow users to see the live environment from within the GPOAdmin console. This will, for example, enable you to delegate GPO, OU, or SOM object registration (and recursive registration) to specific users in your organization.Note the following when upgrading GPOADmin:
• All registered objects should be in the available state prior to any upgrade.
• If you are running GPMC during an upgrade, you must close and re-open it before the GPO Management tab will display. 
• If you set a custom report folder path in a previous version, you must change the reports folder path in the User Preferences to point to the existing folder.
• Due to an upgraded encryption algorithm, the service account cannot decrypt previously encrypted passwords. If you are upgrading and using SQL as your configuration store, accessed with SQL authentication, you must re-enter the password for the connection account the first time you connect to the service.
The following pre-configured passwords will also need to be re-entered: the SQL Server Backup Store account, the SMTP notifications account, and the Exchange notifications account.
•In a minimum permissions environment, Group Policy Objects with a version of 0.x may fail to deploy correctly. To solve this, make a copy of the GPO and deploy the copy. Once this has been verified as successful, delete the original.
•After upgrading ensure the “Ensure service account has access before deployment” service option is checked in the Options dialog.
•When you upgrade the Server, you must also upgrade the Client, GPMC Extension, and Watcher Service.
•GPOADmin runs under the security context of a privileged service account that must have full access to GPOs in the managed forest. If you plan to change this account, you must unlock all GPOs before making the change.
•The supported upgrade paths are from versions 5.17 and later.
•The live environment will only be visible for GPOADmin Administrators and users who have been explicitly granted access.

As a GPOADmin administrator, however, you may want to allow users to see the live environment from within the GPOAdmin console. This will, for example, enable you to delegate GPO, OU, or SOM object registration (and recursive registration) to specific users in your organization.

To permit a user to see the live environment:
1 Login to GPOADmin as a GPOADmin administrator.
2 Right-click the Live Environment node and select Properties.
3 On the Security tab, add one or more users who require access to the live environment.
4 Click OK.