Upgrading High Availability Instance of Passwordstate
Once your primary site has been upgraded to the latest build, follow these instructions to upgrade your High Availability instance of Passwordstate if you have purchased this additional module.
- Ensure you have established SQL replication if you have multiple databases in your High Availability environment. Your databases should be an exact mirror or each other before you attempt to upgrade your High Availability website. To confirm both databases are running the latest build, run this SQL query below:
SQL
USE Passwordstate
SELECT BuildNo
FROM SystemSettings- Download the “Passwordstate 10 (Build 10xxx)” upgrade file from the checksums page and extract the zip file to a temporary location. (The version will change depending on what build we have released)
- Run the passwordstate.exe as an Administrator (right click and Run as Administrator) on your Passwordstate web server – simply follow the on-screen instructions for the upgrade wizard
- The upgrade of the High Availability instance is complete
- If upgrading from a build of Passwordstate earlier than 9947, and only if using a load balancer in front of your Passwordstate web servers, static machinekey settings are required in IIS for seamless failover between web servers when required. To generate static machinekey value, you will need to generate new Validation and Decryption machine keys in IIS. Below are the steps for this:
- On your primary web server, open Internet Information Services (IIS) Manager
- Browse to the Passwordstate website, and click on Machine Key icon
- Click the Generate Keys button on the right-hand side of the page, and then click the Apply button
- Copy the "C:\inetpub\Passwordstate\web-machineKey.config" file across to your second Passwordstate webserver, replacing the existing file
- The upgrade of the High Availability instance is complete
_Note: When upgrading your High Availability webserver, you should never be prompted to upgrade the database. If you are prompted to upgrade your database, there is something wrong with your SQL replication, and you should investigate this before proceeding any further. Both Passwordstate installs and databases must be running the same version in order for your websites to function correctly. This guide explains how you can determine this: KB: How To Tell What Version Of Passwordstate I Am Using