Best Practices for Upgrading Proxy
Part 1: What Component Do I Upgrade First?
In this order, upgrade the Masters first, then the Gateway (where applicable), and the Hosts last. Any newer version of Master
and Gateway will be able to connect to any older version of Host without issue. However, if the Host version is newer than
that of Master, the older Master might not be able to connect to the newer Host. By upgrading the Hosts last, we can be sure
that a Master can always connect your Hosts during the upgrade process.
Part 2: Which License Keys Do I Use?
When you receive “Upgrade” keys (5 blocks of 4 digits), they need to be used in conjunction with your original base “New
Product” keys (6 blocks of 4 digits). If you are deploying to new machines with no previous installations of Proxy, you might
need to first enter the base “New Product” key, and then add the “Upgrade” key -depending if the “New Product” key is in a
lower version than the “Upgrade Key”. If you are installing a “New Product” key in the latest version, then no other keys are
required.
Part 3: PROXY Pro Gateway Upgrade Tips
When upgrading your Proxy Gateway to a newer version, please ensure if there are any other Proxy components installed on
that machine you also upgrade them to the same version as the Gateway.. Alternatively, uninstall any components of differing
versions so that there is not a mixture of different Proxy versions on the same machine, especially if it’s the Gateway machine.
When each component is upgraded, there are no changes made to the existing settings or configuration setup. When
upgrading, there is no need to uninstall the existing version first. A newer Proxy component can be installed on top of the
existing version without issue.
In the unlikely event that your Proxy Gateway’s database file (PgSvc.mdb) becomes corrupt, it would be a good idea to
routinely save a backup copy. To determine whether or not your database has become corrupt, open PgSvc.mdb in Microsoft
Access. If you receive an “AO Index Error”, then your database has become corrupt; send the database to
[email protected] and we will repair it. The most common explanation for a corrupt database would be if the
machine running your Proxy Gateway were to be shut off unexpectedly (power failure) while Proxy was attempting to write to
the database. Remember to stop the Proxy Gateway Service when working with this file.
Part 4: Migration of the Gateway to a New Server
Step 1: If you are looking to move your Proxy Gateway to a new server, the first step would be to copy the existing
PgSvc.mdb file from the original Gateway machine (C:\Program Files\Proxy Networks\PROXY Pro Gateway\Data) and place
that into the same directory on the new machine. This contains all of the Hosts, groups of Hosts, permissions set and all other
machine details. Please stop the Proxy Gateway before copying this file so that the Gateway is not trying to read/write to it
during the process.
Step 2: Please ensure that the new machine running your Proxy Gateway will have the same IP as the old Gateway so that
the Hosts will not have to be re-configured to report to a different Gateway IP. If the new Gateway machine will indeed have a
new IP, you can either use PhSetup to tell the Hosts what the new Gateway IP is, or create a new product configuration using
the Proxy Deployment Tool to push the updated Gateway information out.
Step 3: The last step would be to ensure the Gateway service account remains the same. For example, if the original service
account was DOMAIN\RemoteControlGateway5 on the old Gateway machine, make sure the new Gateway is also using
DOMAIN\RemoteControlGateway5).
Need More Help?
If you need further technical assistance, please contact our support team via email at [email protected] or call
617-453-2718.
Proxy Networks, Inc. | 320 Congress Street | Boston, MA 02210 | 877-PROXY-US or 617-453-2700 |
1