PAM Server inline standalone upgrade procedure

This section looks at how to inline upgrade a standalone deployment.

Prerequisites

Before starting your standalone inline upgrade make sure the following prerequisites are met:

Prerequisite	Description
Upgrade path	Review the Standalone upgrade path to ensure you are applying the correct upgrade method based on the version you are upgrading from and to.
Hardware and Software	Ensure the correct resources are available before upgrading. The following outlines the hardware and software requirements.
Software downloads	Download the latest upgrade kit click here.
Disk space	Ensure the internal disk has a minimum of 5GB free disk space.
Recent backup	We recommend that you have a recent Osirium backup as well as VM Level backup or Snapshot of the PAM Server being upgraded.
No active user connections	Ensure there are no active user connections.
Disable Task 'Regenerate Account Credentials for all devices'	Within the Admin Interface, disable all scheduled Regenerate Account Credentials for all devices tasks within profiles.
Osirium Support account	Within the Admin Interface ensure the Osirium Support account has been enabled and a password set.
.local DNS domains	If you are using .local DNS domains, ensure matching records have been entered in the DNS Search Suffixes.
No Reporter role users	The Reporter role was removed from 9.x and is no longer available, if you are upgrading from an earlier version, any associated user groups configured within this role will have to be removed before upgrading. Upgrades will be blocked if they are not removed. For further information see Managing roles.

The diagram provides a high-level overview of the process for upgrading a standalone PAM Server.

Standalone PAM Server upgrade procedure flowchart

Upgrade standalone

Open a file transfer tool of your preference and copy the upgrade kit onto the PAM Server using the osirium_support account.
Open the PAM Server Console window, then press ALT + F2. The server login prompt appears.

Note
Alternatively, you could use an SSH connection to the PAM Server.
Enter osirium_support at the login prompt and press ENTER.
When prompted, enter the password of the osirium_support account and press ENTER.
Extract the upgrade kit copied to the server using the following command:

sudo bash Osirium_PAM_Server_vA.B.C_upgrade.bin

Where A.B.C is the version you are upgrading to.
When the kit has been extracted, type the command specified on the screen and press ENTER.
Press ENTER when prompted to start the setup and configuration.
The EULA screen will be displayed. Press ENTER once you have read it.
Wait while the upgrade completes and the server is rebooted.

Once the standalone PAM Server upgrade has successfully completed, logon and check the following before allowing users to reconnect:

Post upgrade task	Description
Trigger AD audit	Before opening any device connections that use an Active Directory account, an audit needs to be manually triggered on all provisioned Active Directories. You can do this by right clicking the Active Directory on the Manage Active Directory page, and select `Trigger audit` from the menu.
Check device states	Check device status to ensure they are running successfully.
Check user connections	Check users can connect to devices.
Re-enable scheduled tasks	Re-enable scheduled Regenerate Account Credentials for all devices tasks.
Backup	Take an Osirium backup as well as VM Level backup of the upgraded PAM Server. See Backup and Recovery for further details.
Upgrade PAM UI	If you are using a standalone PAM UI Server then use the PAM Component Compatibility Matrix to check if the PAM UI Server needs updating inline with the PAM version you have upgraded to. Upgrade as appropriate.
Upgrade MAP Server	If you are using a MAP Server then use the PAM Component Compatibility Matrix to check if the MAP Server needs updating inline with the PAM version you have upgraded to. Upgrade as appropriate.