You can upgrade Privileged Account Manager in the following ways:
WARNING:Privileged Account Manager agents and framework managers on Windows reboot automatically after upgrading to 3.2. This happens as some of the Windows components required by Privileged Account Manager are updated in 3.2. Therefore, plan for a system downtime before upgrading to 3.2.
You can upgrade Privileged Account Manager by executing certain commands in the agent or the framework manager. To use these upgrade commands, you must have the unifi file in your machine at the location /netiq/npum/bin/. This file is available as part of the Privileged Account Manager ISO. For information about the upgrade commands and its usage, refer Upgrade and Rollback Packages.
NOTE:To upgrade Privileged Account Manager to version 3.2 from any older version through command line, replace the existing unifi file with the unifi file from the PAM 3.2 ISO and then execute the upgrade command.
You can upgrade Privileged Account Manager from the Host Console, only if the Allow Package Management Through Host Console is set to Yes in the Package Manager > Settings.
To upgrade from the Host Console, perform the following:
Publish the latest packages to the Package Manager.
There are multiple ways to accomplish this.
You can use the Privileged Account Manager CD and set up your Framework Manager machine to be a local Package Manager. For instructions, see Setting Up a Package Manager.
You can configure the Package Manager to use the Novell Update Server through your Novell Customer Care account. For instructions, see Configuring the Package Manager
in the NetIQ Privileged Account Manager 3.2 Administration Guide.
(Conditional) If you are using the Novell Update Server, add the packages you need:
Click Package Manager on the home page of the console, then click Add Packages.
Configure the Package Filter to display the packages you need.
Platform: Select your platforms. Make sure you select Cross Platform, which displays the console packages that run on all platforms.
Types: Select at least Console, Module, and Patch.
Components: Select all of them: Command Control, Framework, and Miscellaneous.
Select all the packages that are listed. Make sure you select the Framework Patch.
Click Next, then click Finish when the packages have been successfully downloaded.
To ensure that all packages are up-to-date, click Check for Updates.
Select any packages that are listed.
Click Next, then click Finish when the packages have been successfully downloaded.
To upgrade your Framework Manager:
Click Hosts on the home page of the console.
Select the host that is your Framework Manager.
Click Update Packages in the task pane.
The Framework Patch should be displayed. This package must be updated to 3.2 before you can update any other packages. If this package does not display, return to Step 2 and add the Framework Patch for your platform.
NOTE:Ensure that you install the myaccess console package first then upgrade the rdprelay console package.
Select the package, then click Next.
When the package is installed, click Finish.
Click Update Packages in the task pane.
Select the listed packages, then click Next.
When the packages have installed, click Finish.
Verify that all packages display a 3.2 version. If they don’t, return to Step 2 and add any missing packages.
To install new packages available in 3.2 on your Framework Manager:
Click Hosts on the home page of the console.
Select the host that is your Framework Manager, use the arrow to display the packages, then select Packages.
Click Install Packages.
Select the Syslog Emitter, then click Next.
When the package has installed, click Finish.
To upgrade your agents:
Click Hosts on the home page of the console.
Select the hosts that are agents or select the domain containing the agents.
Click Update Packages in the task pane.
Select the Framework Patch, then click Next.
Click Update Packages in the task pane.
Select the listed packages, then click Next.
When the packages have installed, click Finish.
Verify that all packages display 3.2 version.
NOTE:To upgrade the SUSE Linux Enterprise Server (SLES) version of PUM 2.3.3 to the Linux version that Privileged account Manager supports, refer the TID 7016202.
You can upgrade Privileged Account Manager Packages using the Privileged Account Manager Installer. When you execute the installer through command line, it verifies whether Privileged Account Manager is installed in the system and if it is available, the existing packages are upgraded.
NOTE:
You must have the admin privileges for the unifi module to execute this command in the local agent machine.
This method is supported only in the Windows system.
Download the Privileged Account Manager installation file from the NetIQ Downloads website.
Execute the following command and follow the onscreen prompts to upgrade:
Syntax: msiexec /i <Installer Filename> USERNAME=<"username"> PASSWORD=<"password"> REINSTALL=ALL REINSTALLMODE=VOMUS
Example: msiexec /i netiq_pam_manager_3.2.0_x64.msi USERNAME="admin" PASSWORD="novell123" REINSTALL=ALL REINSTALLMODE=VOMUS
If you have mapped your local account to a Framework Manager user (see Modify User: Native Maps ), you need not specify the user name and password.
Example: msiexec /i netiq_pam_manager_3.2.0_x64.msi REINSTALL=ALL REINSTALLMODE=VOMUS
After upgrading Privileged Account Manager to 3.2 from lower versions, you must install the console packages:
Enterprise Credential Vault (prvcrdvlt)
Access Dashboard (userreqdashboard)
These console packages are renamed in Privileged Account Manager 3.2. Hence, these packages are not upgraded by default and must be installed manually after upgrade. You can install these packages through the Host Console or the command line options. For information about installing the packages through Host Console, see Installing Packages on a Host . For information about the commands to install the packages, see Install and Uninstall Packages.