Upgrading and configuring Windows proxies

The upgrade process uninstalls the existing proxy, and installs and configures a new proxy using information taken from the previous proxy.

Before you begin

Before you upgrade, make sure you review the following guidelines:

Make sure you stop your existing Windows proxies, if running. Otherwise, the install fails and you will need to reboot the computer.
Check the Windows proxy compatibility matrix to determine whether you need to upgrade Windows proxies.
If you are upgrading from versions prior to 8.3 SP2, do not use the same installation directory as the existing Windows proxy or the installation will fail. Accepting the upgrade default prevents this.
The Windows Workgroup proxy is deprecated. If you upgrade a Workgroup proxy, it is converted into an AD proxy.
For more information, see Windows proxy compatibility.
During the upgrade process you need to enter the Active Directory credentials. Note that usernames are preserved during the upgrade, but passwords are not.
Make sure that you perform the post-upgrade configurations after you upgrade the Windows proxy.

To upgrade Windows proxies

From the installer folder, double-click on the downloaded installer file and click Next.
For instructions about how to download the installer file, see download the Windows proxy installer.
Click Browse to select the installation directory, or click Next to accept the default installation directory (C:\Program Files\BMC Software\ADDM Proxy).
To create the Windows proxy application shortcuts, click Browse to select a different folder, or click Next to accept the default folder (BMC Software\ADDM Proxy).
If you choose Don't create a Start Menu Folder here, ensure that you clear all the start menu option check boxes in the next step.
On the Select Additional Tasks screen, choose options that will be available in the Start menu, and then click Next.
If an existing Active Directory proxy is found, you are asked to enter credentials. The Account field is pre-populated with the username that the proxy is using.
In the Password field, specify the corresponding password.
If the proxy is currently running as the local system user, you are prompted for an Active Directory username and password. Although the proxy service will run as the local system user, it will not be able to perform any discovery activities until it is run as an Active Directory user.
1. Select Migrate existing configuration file to migrate any custom changes to the new proxy.
Click Next.
If an existing Workgroup proxy is found, it is converted to an Active Directory proxy. You are asked to enter credentials. The Account field is pre-populated with the username that the proxy is using. Enter the corresponding password in the Password field. If the proxy is currently running as the local system user, you are prompted for an username and password. Although the proxy service will run as the local system user, it will not be able to perform any discovery activities until it is run as a Workgroup user.
1. Select Migrate existing configuration file to migrate any custom changes to the new proxy.
Click Next.
If an existing Credential proxy is found, the default is not to request credentials. We recommend that credential proxies are run as local named users with administrator privileges, not the local system user.
1. Select Migrate existing configuration file to migrate any custom changes to the new proxy.
Click Next.
Review the details in the Ready to Install window. If the details are incorrect, click Back and navigate through the installer to correct the error. If they are correct, click Install to install the selected components.
You are asked whether you want to keep the existing configuration for each proxy.
Click Yes to keep the configuration and click Finish.

Configuring Windows proxies

After you upgrade Windows proxy, you must configure the default keys and certificates.

The default keys and certificates used in very old versions of BMC Discovery expired in 2015. The transition to newer default keys started with version 9.0, meaning that, as long as the version 11.0 appliance is configured to use the legacy keys, an appliance can use a version 9.0 proxy, but it cannot use a version 8.3.x proxy that uses the default keys.

If you have a version 8.3.x proxy, by far the best approach is to upgrade the proxy to version 11.0. If that is not possible, suitable CA certificates must be installed on the proxy.

To make 8.x proxies operate with a version 11.x appliance

To make 8.x proxies operate with a version 11.x appliance you must copy the new certificate authority file to the main proxy folder and each of the runtime folders.

Ensure that the appliance is using the legacy key and certificate.
Concatenate the two files containing the public keys, /usr/tideway/etc/ca/appliance_ca.pem (new public key) and /usr/tideway/etc/ca/appliance_ca_1.pem (old public key), using the following command:
cat /usr/tideway/etc/ca/appliance_ca.pem /usr/tideway/etc/ca/appliance_ca_1.pem > /usr/tideway/etc/ca/appliance_ca.pem
Copy /usr/tideway/etc/ca/appliance_ca.pem from the appliance to the 8.x proxy folders. Put a separate copy in the main proxy folder and each of the runtime folders. For example:
- C:\Program Files (x86)\BMC Software\ADDM Proxy\etc
- C:\Program Files (x86)\BMC Software\ADDM Proxy\runtime\<proxy name1>\etc
- C:\Program Files (x86)\BMC Software\ADDM Proxy\runtime\<proxy name2>\etc
Restart all the proxies.
Move the appliance_ca.pem file out of the /usr/tideway/etc/ca/ directory, for example to the /tmp directory.

To make proxies upgraded from 8.x to 9.x operate with a version 11.x appliance

Proxies that have been upgraded from 8.x to 9.x also require a manual upgrade of their default certificates in order to operate with a version 11.x appliance.

Copy C:\Program Files (x86)\BMC Software\ADDM Proxy\etc\ca_01.pem into each of the proxy runtime folders. For example:
- C:\Program Files (x86)\BMC Software\ADDM Proxy\runtime\<proxy name1>\etc
- C:\Program Files (x86)\BMC Software\ADDM Proxy\runtime\<proxy name2>\etc
Restart all proxies.
Proxies deployed from a 9.x proxy manager, whether upgraded or newly installed, work without any manual configuration.

Baseline changes

The baseline tool tracks changes to the system configuration from a known baseline. After an upgrade, the appliance configuration will have changed significantly. You should view the baseline page after an appliance upgrade and examine the changes made to the system. When you understand the changes that have been made, you can re-baseline the appliance so that the tool can check for changes from the configuration after upgrading to the newer version of BMC Discovery.