The latest Key Manager Plus version is 5.9 If you are using an earlier version, you need to apply upgrade pack.
Instructions to apply the Upgrade Pack
IMPORTANT: Take a copy of the entire Key Manager Plus installation folder before applying the upgrade pack and keep it in some other location. If something goes wrong with the Key Manager Plus upgrade, you can rely on the copy. Also ensure that you stop the Key Manager Plus server before applying the upgrade pack. All your settings will remain intact.
- Stop the Key Manager Plus server / service and then take a copy of the entire Key Manager Plus installation directory.
- The upgrade pack is to be applied through a tool named UpdateManager bundled with Key Manager Plus. Navigate to <keymanagerplus_installation_folder>/bin directory and execute UpdateManager.bat (in Windows) or UpdateManager.sh (in Linux) to start the Update Manager.
- If you are applying multiple upgrade packs one-by-one, exit the Update Manager tool after applying one upgrade pack and make sure that the database process is not running. Then proceed with running the Update Manager tool to apply the next upgrade pack and so on.
- Also, when applying multiple upgrade packs sequentially, it is recommended that you start the Key Manager Plus service after each upgrade to ensure the corresponding build version runs successfully without any issue.
- Click Browse and select the .ppm file that you downloaded. Click Install to install the upgrade pack. Wait until the upgrade pack is fully installed. [Normally, it takes a few minutes for PPM installation]
- Click Close and then click Exit to exit the Update Manager tool. If you are applying more than one upgrade pack, apply them one-by-one and repeat this step after applying each pack.
- After applying the upgrade pack, check if the database process is running. If it is running, terminate that process.
- Start the Key Manager Plus server / service.
Failover Service (FOS) Setup
In a failover service set up with two application servers bound to an MS SQL cluster, you can upgrade only the primary server; the other secondary server must be reinstalled and the failover service setup must be reconfigured.
Summary of steps to be followed:
- Deactivate the failover service.
- Upgrade the primary application server.
- Reinstall the secondary application.
- Reconfigure the failover service.
Deactivate Failover Service
You can deactivate the failover service either from the primary or the secondary server.
To uninstall:
- Open a command prompt in any of the servers
- Navigate to <keymanagerplus_installation_folder>/bin directory
- Execute the command: UninstallFOS.bat
With this, the failover service will be deactivated. Next, you can uninstall Key Manager Plus application completely from the other servers.
Upgrade the primary application server
You can upgrade your primary installation of Key Manager Plus by following the below steps. The latest upgrade packs are available above. You can use the instructions mentioned above to apply the upgrade packs one by one to reach the latest version. If MS SQL is configured as back end, do take a backup of database present in MS SQL Server.
Note:
Before upgrading, it is advisable to take a backup of the entire Key Manager Plus directory. This way, even if something goes wrong, you can immediately revert to the existing version by deleting the Key Manager Plus directory and placing the backup in same location to get your Key Manager Plus instance up and running again.
Upgrade steps
- Stop the Key Manager Plus service and exit the tray icon.
- Navigate to <Key Manager Plus_Installation_Folder>/bin directory from CMD and execute UpdateManager.bat
- During MS SQL server configuration for Key Manager Plus database, if you have opted for 'Windows Authentication,' you have to start the command prompt using the service account with which the Key Manager Plus service has been configured to connect to the SQL server (i.e. instead of running as administrator, run as the service account).
- To identify whether a service account is used or a SQL account is used, navigate to <Key Manager Plus_Installation_Folder>/conf directory and opendatabase_params.conf file. If you do not find a username and password in the file, then Key Manager Plus is using Windows Authentication and therefore you need to run the command prompt with service account privilege.
- Click Browse, select the .ppm file that you downloaded and install.
- If you are applying multiple upgrade packs, do the following for each upgrade; exit the Update Manager, start & stop the Key Manager Plus service once, and execute the upgrade steps.
- After applying the upgrade packs, start the Key Manager Plus service.
Reinstall on the secondary application server
After upgrading the primary server to the latest version, You can reinstall the latest version of Key Manager Plus on your secondary server. Note: Ensure the software architectures are the same i.e. 32-bit/64-bit. You can download Key Manager Plus from this link.
Reconfigure FOS service
After reinstalling the secondary server, you can perform the steps detailed in the failover service help documentation to configure failover service in the secondary application server again.
If you need any assistance or clarifications, please contact keymanagerplus-support@manageengine.com.
Note:
Key Manager Plus also allows you to schedule database backups from within the product, and provides script to restore the data to provide assistance during disaster / data loss. While it is recommended that you take a copy of Key Manager Plus installation directory before applying the upgrade pack, you can always rely on the database backups scheduled from within the product if anything goes wrong.
How do I find out my Build number?
Log in to the Key Manager Plus web interface, and click the License option in the top pane. You will find the build number mentioned below the version number. This is the build number of the currently installed Key Manager Plus version.
