Novell PRIVILEGED USER MANAGER 2.2.1 - ADMINISTRATION GUIDE... User manual

Novell®
www.novell.com
novdocx (en) 16 April 2010
AUTHORIZED DOCUMENTATION
Novell Privileged User Manager 2.2.1 Getting Started Guide
Privileged User Manager
2.2.1
March 31, 2010
Getting Started Guide

novdocx (en) 16 April 2010
Legal Notices
Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.,
reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on
the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws.
You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the
Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on
exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export
approvals.
Copyright © 2009 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied,
stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc., has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or
more additional patents or pending patent applications in the U.S. and in other countries.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the latest online documentation for this and other Novell products, see
the Novell Documentation Web page (http://www.novell.com/documentation).

novdocx (en) 16 April 2010
Novell Trademarks
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/
trademarks/tmlist.html).
Third-Party Materials
All third-party trademarks are the property of their respective owners.

4Novell Privileged User Manager 2.2.1 Getting Started Guide
novdocx (en) 16 April 2010

Contents 5
Contents
novdocx (en) 16 April 2010
About This Guide 7
1 Novell Privileged User Manager Overview 9
1.1 Product Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2 Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.3 What’s New in 2.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3.1 General Installation Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3.2 Framework User Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3.3 Command Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3.4 Compliance Auditor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3.5 Reporting Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.3.6 Package Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2 Installation Requirements 13
2.1 Software Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.3 Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.4 Procedural Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3 Installing the Framework Manager 15
3.1 Installing a Framework Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1.1 AIX Framework Manager Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1.2 HP-UX Framework Manager Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.1.3 Linux Framework Manager Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.1.4 Solaris Framework Manager Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.1.5 Tru64 Framework Manager Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.1.6 Windows Framework Manager Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.2 Accessing the Framework Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.3 Installing a Novell Privileged User Manager License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.4 Setting Up a Package Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.5 Stopping and Restarting the Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.5.1 AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.5.2 HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.5.3 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.5.4 Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.5.5 Tru64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.5.6 Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.6 Removing the Framework Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.6.1 AIX Manager Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.6.2 HP-UX Manager Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.6.3 Linux Manager Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.6.4 Solaris Manager Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.6.5 Tru64 Manager Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.6.6 Windows Manager Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

6Novell Privileged User Manager 2.2.1 Getting Started Guide
novdocx (en) 16 April 2010
4 Installing the Agents 27
4.1 Agent Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.2 Creating a Host Name for Each Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.3 Opening Firewall Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.4 Installing and Registering a Framework Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.4.1 AIX Agent Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.4.2 HP-UX Agent Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.4.3 Linux Agent Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.4.4 Solaris Agent Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.4.5 Tru64 Agent Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.5 Removing the Agent Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.5.1 AIX Agent Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.5.2 HP-UX Agent Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.5.3 Linux Agent Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.5.4 Solaris Agent Uninstall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.5.5 Tru64 Agent Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5 Upgrading from 2.2 to 2.2.1 35

About This Guide 7
novdocx (en) 16 April 2010
About This Guide
This Getting Started Guide explains the hardware requirements for the Privileged User Manager
components, then explains how to install the components.
Chapter 1, “Novell Privileged User Manager Overview,” on page 9
Chapter 2, “Installation Requirements,” on page 13
Chapter 3, “Installing the Framework Manager,” on page 15
Chapter 4, “Installing the Agents,” on page 27
Chapter 5, “Upgrading from 2.2 to 2.2.1,” on page 35
Audience
This guide is intended for users who install and manage the Privileged User Manager product.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation, or go to www.novell.com/documentation/feedback.html and enter your
comments there.
Documentation Updates
For the most recent version of the Getting Started Guide, visit the Privileged User Manager Web
Site (http://www.novell.com/documentation/privilegedusermanager22).
Additional Documentation
Privileged User Manager Administration Guide (http://www.novell.com/documentation/
privilegedusermanager22/npum_admin/data/bkyzr9y.html)
Documentation Conventions
In Novell®documentation, a greater-than symbol (>) is used to separate actions within a step and
items in a cross-reference path.
A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
trademark.

8Novell Privileged User Manager 2.2.1 Getting Started Guide
novdocx (en) 16 April 2010

Novell Privileged User Manager Overview
1
9
novdocx (en) 16 April 2010
1
Novell Privileged User Manager
Overview
Novell®Privileged User Manager delivers a robust and scalable architecture, intuitive management
console and reusable script and command libraries that enable administrators to reduce management
overhead and infrastructure costs in your environment.
Section 1.1, “Product Overview,” on page 9
Section 1.2, “Components,” on page 9
Section 1.3, “What’s New in 2.2.1,” on page 10
1.1 Product Overview
Many organizations needlessly expose their superuser or root account credentials to users who are
required to run commands that need elevated privileges, and passwords are often not changed when
administrative staff change jobs. This opens potential back doors into systems and increases the
likelihood of a security breach.
Novell Privileged User Manager helps IT administrators manage the identity and access for
superuser and root accounts by providing controlled superuser access to administrators, allowing
them to perform jobs without needlessly exposing root account credentials. It also provides a
centralized activity log across multiple platforms. The introduction of Novell Privileged User
Manager enriches the Novell Identity and Access Management and Compliance Management
solutions by adding auditing and tracking capabilities for privileged user activity across the
organization.
Novell Privileged User Manager limits corporate susceptibility to unauthorized transactions and
information access by helping organizations rapidly deploy superuser management and tracking
across all UNIX* and Linux* environments. It reduces management overhead and infrastructure
costs, controls and records which privileged users have access to what, and reduces costs and errors
through demonstrable compliance audits.
Novell Privileged User Manager works by delegating privileged access, which is authorized via a
centralized database. The end result is that a user is authorized to run the privileged command and
all activity is logged. The centralized database provides for easier administration. Compared to
competitive solutions in the marketplace, Novell Privileged User Manager is deployed more
quickly, provides faster response time, better logging and auditing and improved administration, and
leads to a more secure system and a fast return on investment.
1.2 Components
Privileged User Manager consists of a Framework Manager, where you manage and configure the
system, and an agent, which is installed on each machine where you want to monitor and control
superuser access.

10 Novell Privileged User Manager 2.2.1 Getting Started Guide
novdocx (en) 16 April 2010
Figure 1-1 Framework Manager
From the Home page, you have access to six administrative consoles:
Compliance Auditor: Proactive auditing tool that pulls events from the event logs for
analysis, according to predefined rules. It pulls filtered audit events at hourly, daily, weekly or
monthly intervals. This enables auditors to view prefiltered security transactions, play back
recordings of user activity, and record notes for compliance purposes. In an era of increasing
regulatory compliance requirements, the ability to supply demonstrable audit compliance at
any time provides a more secure system and reduces audit risk.
Framework User Manager: Manages users who log in to the Framework Manager through
role-based grouping.
Hosts: Centrally manages Privileged User Manager installation and updates, load-balancing,
redundancy of resources, and host alerts.
Reporting: Provides easy access and search capability for event logs and allows you review
and color-code user keystroke activity through the Command Risk Analysis Engine.
Command Control: Uses an intuitive graphical interface to manage security policies for
privilege management.
Package Manager: Lets you easily update any Privileged User Manager application.
1.3 What’s New in 2.2.1
The following new features have been added to Privileged User Manager 2.2.1.
Section 1.3.1, “General Installation Updates,” on page 11
Section 1.3.2, “Framework User Manager,” on page 11
Section 1.3.3, “Command Control,” on page 11
Section 1.3.4, “Compliance Auditor,” on page 11
Section 1.3.5, “Reporting Console,” on page 12
Section 1.3.6, “Package Manager,” on page 12

Novell Privileged User Manager Overview 11
novdocx (en) 16 April 2010
1.3.1 General Installation Updates
Framework Manager installations now include the Syslog Emitter, which allows events to be
published to a syslog server that supports TCP. For more information, see “Syslog Settings” in
the Novell Privileged User Manager 2.2.1 Administration guide.
Privileged User Manager can now be installed on Linux Mainframe zSeries 64-bit on SLES
(SUSE®Linux Enterprise Server) versions 10 SP2 and 11 and Red Hat* version 5.
For upgrades from 2.2 to 2.2.1, please see Chapter 5, “Upgrading from 2.2 to 2.2.1,” on
page 35.
A Sentinel collector is available for Privileged User Manager. To download the collector and
instructions, see Sentinel 6.1 Content (http://support.novell.com/products/sentinel/secure/
sentinel61.html).
1.3.2 Framework User Manager
Help Desk Role: You can select from a predefined set of attributes to create a help desk group
that can only manage user password problems such as forgotten passwords and locked accounts
because of too many bad login attempts. For more information, see “Configuring a Help Desk
Group” in the Novell Privileged User Manager 2.2.1 Administration guide.
LDAP Authentication: You can configure Framework Manager users so that they obtain their
authentication credentials from an LDAP server. For more information, see “Modify User:
Native Maps ” in the Novell Privileged User Manager 2.2.1 Administration guide.
1.3.3 Command Control
Backup and Restore: You can create a backup of the Command Control database and restore
the backup at a future date. For more information, see “Backing Up and Restoring” in the
Novell Privileged User Manager 2.2.1 Administration guide.
Keystroke Error Reporting: The Command Control agent now sends an appropriate message
rather than “session not terminated” when an error occurs with the keystroke file. The
following messages can now be sent to the audit manager for display:
File does not exist
Remote host does not exist
Run user does not exist
Executing binary does not exist
Run process missing
usrun -t Option: Provides a test command option that tests the specified command against the
rule structure. A yes or no is printed to the screen, indicating whether the command would be
accepted or not. For more information, see “Using usrun with a Command” in the Novell
Privileged User Manager 2.2.1 Administration guide
1.3.4 Compliance Auditor
Archive: You can archive records, store them offline, and restore them. For more information,
see “Archiving Records” in the Novell Privileged User Manager 2.2.1 Administration guide.
Export and Import: You can export and import audit rules, audit report settings, and access
control levels.

12 Novell Privileged User Manager 2.2.1 Getting Started Guide
novdocx (en) 16 April 2010
Keystroke Size: The log size of the keystroke file is now visible from the main page of the
Compliance Auditor console. For more information, see “Compliance Auditor Records ” in the
Novell Privileged User Manager 2.2.1 Administration guide.
Keystroke Session Termination: When viewing a keystroke session that was not properly
terminated, you can now terminate the session.
1.3.5 Reporting Console
Read and Update Roles for Record Viewing: You can assign roles to reports. This restricts
viewing and the updating the reports to the users who have been assigned the appropriate roles.
For more information, see “Modifying General Report Information” in the Novell Privileged
User Manager 2.2.1 Administration guide
Session End Time: When viewing Command Control reports, you can see the session end
time. You can also filter on this value. For more information, see “Filtering the Viewable
Records ” in the Novell Privileged User Manager 2.2.1 Administration guide.
Syslog Support: You can configure Privileged User Manager to send audit events as syslog
messages to a syslog server (either a SentinelTM server or newer syslog servers that support
TCP). For more information, see “Syslog Settings” in the Novell Privileged User Manager
2.2.1 Administration guide.
A Privileged User Manager collector is also available in the Sentinel Log Manager (http://
www.novell.com/products/sentinel-log-manager/) and as a Sentinel download (see Sentinel 6.1
Content (http://support.novell.com/products/sentinel/secure/sentinel61.html)).
Report Filters: You can define report filters by using drop-down menus based on audit
information that is collected by Privileged User Manager. For more information, see “Filtering
the Viewable Records ” in the Novell Privileged User Manager 2.2.1 Administration guide.
1.3.6 Package Manager
Improved Backup Checks: The distribution agent now checks the version of the current
package backup. If you try to update the current package with the same version, a warning
message is displayed and the package is not updated.

Installation Requirements
2
13
novdocx (en) 16 April 2010
2
Installation Requirements
Section 2.1, “Software Prerequisites,” on page 13
Section 2.2, “System Requirements,” on page 13
Section 2.3, “Supported Platforms,” on page 13
Section 2.4, “Procedural Overview,” on page 14
2.1 Software Prerequisites
Novell®Privileged User Manager installation software. Log in to the Novell Customer Center
(http://www.novell.com/center) and follow the link that allows you to download the software.
Adobe* Flash* Player.
Novell Privileged User Manager license. Log in to the Novell Customer Center (http://
www.novell.com/center) and download the license.
NOTE: By default, new installations are provided with a 90-day license for five agents, one of
which is the manager.
2.2 System Requirements
A PUM agent should have the following system requirements:
CPU - 300 MHz (RISC), 1GHz (CISC)
Memory - 50 MB additional memory
Hard Disk - 100 MB additional memory
A PUM manager should have the following system requirements:
CPU - 1 GHz or more (RISC), 2 GHz or more (CISC)
Memory - 250 MB additional memory
Hard Disk - 150 MB additional memory and additional memory for Audit Storage
TIP: Approximate additional memory calculation for Audit Storage = (250 KB) X (number of PUM
users) X (number of sessions per day (usually 8 sessions)).
2.3 Supported Platforms
The Framework Manager software and Framework Agent software have been tested on the
following platforms:
IBM* AIX* 32-bit and 64-bit on versions 5.3 and 6.1
HP-UX* (PA-RISC) 32-bit and 64-bit on versions 11.11 and 11.23
HP-UX (Itanium*) 64-bit on version 11.23
SUSE®Linux Enterprise Server (SLES) 32-bit and 64-bit on versions 10 SP1, SP2, SP3 and 11

14 Novell Privileged User Manager 2.2.1 Getting Started Guide
novdocx (en) 16 April 2010
Red Hat* 32-bit and 64-bit on versions 4.0 x86 and 5.0 x86
Linux Mainframe zSeries 64-bit on SLES versions 10 SP2 and 11 and Red Hat version 5
Sun* Solaris* (SPARC*) 32-bit and 64-bit on versions 8, 9, and 10
Sun Solaris (Intel*) 32-bit and 64-bit on versions 8, 9, and 10
HP Tru64* UNIX 64-bit on 5.1a and 5.1b
VMware* ESX Server 64-bit on 3.0 and 3.5
Xen* Hypervisor version 3.2 and 3.3
Open Enterprise Server 2 SP1 and SP2 (32-bit and 64-bit)
The Framework Manager can also be installed on Windows* 2003 Server 32-bit or 64-bit. There is
no agent software for the Windows platforms.
Ensure that your operating system is running the vendor's latest maintenance patches.
Third Party Tested Platforms
The agent can be installed on the following Linux platform:
Univention Corporate Server (UCS) 2.3
2.4 Procedural Overview
The following steps are required to install Privileged User Manager:
1Install a Framework Manager. See Chapter 3, “Installing the Framework Manager,” on
page 15.
2When the installation has completed, access and log in to the console. See Section 3.2,
“Accessing the Framework Console,” on page 19.
3Install the Privileged User Manager license. See Section 3.3, “Installing a Novell Privileged
User Manager License,” on page 20.
By default, new installations are provided with a 90-day license for five agents, one of which is
the manager. You need to install your license before the default license expires.
4Set up a Package Manager so you can install additional packages on the agents and push
package updates to your framework components. See Section 3.4, “Setting Up a Package
Manager,” on page 20.
5Install and register a Framework Agent on the computers that you want to manage. See
Chapter 4, “Installing the Agents,” on page 27.
When you have installed and registered the Framework agents, you have completed the
installation of the Framework.
6For configuration information, see the Novell Privileged User Manager 2.2.1 Administration
guide.

Installing the Framework Manager
3
15
novdocx (en) 16 April 2010
3
Installing the Framework Manager
Section 3.1, “Installing a Framework Manager,” on page 15
Section 3.2, “Accessing the Framework Console,” on page 19
Section 3.3, “Installing a Novell Privileged User Manager License,” on page 20
Section 3.4, “Setting Up a Package Manager,” on page 20
Section 3.5, “Stopping and Restarting the Framework,” on page 21
Section 3.6, “Removing the Framework Manager,” on page 23
3.1 Installing a Framework Manager
Currently, the Framework Manager is available for installation on the platforms listed below. Refer
to Chapter 2, “Installation Requirements,” on page 13 for more information regarding supported
versions.
For detailed installation instructions for your platform, select from the list below:
Section 3.1.1, “AIX Framework Manager Install,” on page 15
Section 3.1.2, “HP-UX Framework Manager Install,” on page 16
Section 3.1.3, “Linux Framework Manager Install,” on page 16
Section 3.1.4, “Solaris Framework Manager Install,” on page 17
Section 3.1.5, “Tru64 Framework Manager Install,” on page 18
Section 3.1.6, “Windows Framework Manager Install,” on page 18
3.1.1 AIX Framework Manager Install
The AIX installation package is compressed through gzip. In order to install the package, you must
unzip the package through gunzip.
By default, the installation program installs the software into
/opt/novell/npum . To change this,
create a directory in the required part of the file system and create a symbolic link to
/opt/novell/
npum
.
To install the AIX manager:
1Copy the installation package to a temporary location and use the following command to
extract the installation files:
gunzip <filename>
See the “Novell Privileged User Manager Readme” (http://www.novell.com/documentation/
privilegedusermanager22/readme/privilegedusermanager_readme.html) for the actual
filename.

16 Novell Privileged User Manager 2.2.1 Getting Started Guide
novdocx (en) 16 April 2010
2After the AIX installation package is uncompressed, use one of the following methods to
perform the installation.
The AIX smitty program.
The following command:
installp -acgNQqwX -d <directory of .bff file> novellnpum
3After installation is complete, check that the service is running by viewing the log file. The log
file is located in
/opt/novell/npum/logs/unifid.log , if the default install location was
used. If the manager installed correctly, services should be listening on 0.0.0.0:29120 and
0.0.0.0:443.
4If you have been supplied with a license, log in to the Framework Console and install the
license.
For information, refer to Section 3.2, “Accessing the Framework Console,” on page 19, and
then Section 3.3, “Installing a Novell Privileged User Manager License,” on page 20.
3.1.2 HP-UX Framework Manager Install
The HP-UX installation package is compressed through gzip. In order to install the package, you
must unzip the package through gunzip.
By default, the installation program installs the software into
/opt/novell/npum . To change this,
create a directory in the required part of the file system and create a symbolic link to
/opt/novell/
npum
.
To install the HP-UX manager:
1Copy the installation package to a temporary location and use the following command to
extract the installation files:
gunzip <filename>
See the “Novell Privileged User Manager Readme” (http://www.novell.com/documentation/
privilegedusermanager22/readme/privilegedusermanager_readme.html) for the actual
filename.
2After the HP-UX installation package is uncompressed, use the following command to install
the manager:
swinstall -s /<directory of .depot file>/<filename>.depot \*
3After installation is complete, check that the service is running by viewing the log file. The log
file is located in
/opt/novell/npum/logs/unifid.log, if the default install location was
used. If the manager installed correctly, services should be listening on 0.0.0.0:29120 and
0.0.0.0:443.
4If you have been supplied with a license, log in to the Framework Console and install the
license.
For information, refer to Section 3.2, “Accessing the Framework Console,” on page 19, and
then Section 3.3, “Installing a Novell Privileged User Manager License,” on page 20.
3.1.3 Linux Framework Manager Install
Linux hosts use the RPM packaging system for installation, upgrade, and removal.

Installing the Framework Manager 17
novdocx (en) 16 April 2010
By default, the installation program installs the software into /opt/novell/npum . To change this,
create a directory in the required part of the file system and create a symbolic link to
/opt/novell/
npum
.
To install the Linux manager:
1Copy the installation package to a temporary location and use the following command to install
the file:
rpm -i <filename>.rpm
See the “Novell Privileged User Manager Readme” (http://www.novell.com/documentation/
privilegedusermanager22/readme/privilegedusermanager_readme.html) for the actual
filename.
2After installation is complete, check that the service is running by viewing the log file. The log
file is located in
/opt/novell/npum/logs/unifid.log , if the default install location was
used. If the manager installed correctly, services should be listening on 0.0.0.0:29120 and
0.0.0.0:443.
3If you have been supplied with a license, log in to the Framework Console and install the
license.
For information, refer to Section 3.2, “Accessing the Framework Console,” on page 19, and
then Section 3.3, “Installing a Novell Privileged User Manager License,” on page 20.
3.1.4 Solaris Framework Manager Install
The Solaris installation package is compressed through gzip. In order to install the package, you
must unzip the package through gunzip.
By default, the installation program installs the software into
/opt/novell/npum . To change this,
create a directory in the required part of the file system and create a symbolic link to
/opt/novell/
npum
.
To install the Solaris manager:
1Copy the installation package to a temporary location and use the following command to
extract the installation files:
gunzip <filename>
See the “Novell Privileged User Manager Readme” (http://www.novell.com/documentation/
privilegedusermanager22/readme/privilegedusermanager_readme.html) for the actual
filename.
2After the Solaris installation package is uncompressed, use the following command to install
the manager:
pkgadd -d /<directory of .pkg file>/<filename>.pkg
3After installation is complete, check that the service is running by viewing the log file. The log
file is located in
/opt/novell/npum/logs/unifid.log , if the default install location was
accepted. If the manager installed correctly, services should be listening on 0.0.0.0:29120 and
0.0.0.0:443.

18 Novell Privileged User Manager 2.2.1 Getting Started Guide
novdocx (en) 16 April 2010
4If you have been supplied with a license, log in to the Framework Console and install the
license.
For information, refer to Section 3.2, “Accessing the Framework Console,” on page 19, and
then Section 3.3, “Installing a Novell Privileged User Manager License,” on page 20.
3.1.5 Tru64 Framework Manager Install
The Tru64 installation package is compressed through gzip. In order to install the package, you must
unzip the package through gunzip.
By default, the installation program installs the software into
/opt/novell/npum . To change this,
create a directory in the required part of the file system and create a symbolic link to
/opt/novell/
npum
.
To install the Tru64 manager:
1Copy the installation package to a temporary location and use the following command to
extract the installation files:
gunzip <filename>
tar –xvf <filename>
See the “Novell Privileged User Manager Readme” (http://www.novell.com/documentation/
privilegedusermanager22/readme/privilegedusermanager_readme.html) for the actual
filename.
2After the Tru64 installation package is uncompressed, use the following command to install the
manager:
setld -l NOVELLNPUM/
3After installation is complete, check that the service is running by viewing the log file. The log
file is located in
/opt/novell/npum/logs/unifid.log, if the default install location was
used. If the manager installed correctly, services should be listening on 0.0.0.0:29120 and
0.0.0.0:443.
4If you have been supplied with a license, log in to the Framework Console and install the
license.
For information, refer to Section 3.2, “Accessing the Framework Console,” on page 19, and
then Section 3.3, “Installing a Novell Privileged User Manager License,” on page 20.
3.1.6 Windows Framework Manager Install
1Run the following install executable to start the installation:
<filename>.exe
See the “Novell Privileged User Manager Readme” (http://www.novell.com/documentation/
privilegedusermanager22/readme/privilegedusermanager_readme.html) for the actual
filename.
2Follow the steps in the install wizard.
The Framework Manager service can be installed on any part of the normal file system. It
defaults to the
C:\Program Files\Novell\npum folder.

Installing the Framework Manager 19
novdocx (en) 16 April 2010
3After installation is complete, check that the service is running by viewing the log file. The log
file is located in
C:\Program Files\Novell\npum\logs\unifid.log , if the default install
location was used. If the manager installed correctly, services should be listening on
0.0.0.0:29120 and 0.0.0.0:443.
4If you have been supplied with a license, log in to the Framework Console and install the
license.
For information, refer to Section 3.2, “Accessing the Framework Console,” on page 19, and
then Section 3.3, “Installing a Novell Privileged User Manager License,” on page 20.
3.2 Accessing the Framework Console
1Open a Web browser on your chosen platform.
2In the address bar, enter the URL for the Framework Console as follows:
https://<hostname>
Replace <hostname> with one of the following:
The DNS name of the server where the Framework Manager is installed.
The DNS name of a server that has the Administration Agent package installed.
3If you are presented with a security alert, verify the details and select Yes to continue.
4If your browser is not already equipped with Adobe Flash Player, the browser attempts to
install it. Verify the details and select Install to continue.
A reboot or browser restart might be required.
5Log in to the Framework Console.
After you enter the URL for the Framework Console, the initial logon screen is displayed in the
browser window. You must authenticate to the system by using a username and password
defined on the system.
6(Conditional) If this is the first time to log in to the console, specify the username
admin and
password
novell , then click Logon.
7(Conditional) If this is the first time to log in to the Framework Console, you are prompted to
change the default password.
Your new password should be a minimum of six characters. If the new password is acceptable
to the system, you are logged in to the console.
IMPORTANT: To navigate in the Framework Console, do not use your browser’s Forward or
Back buttons; use the trail at the top of each page, such as:
Home / Compliance Auditor
Click Home to return to main console menu.
8Continue with Section 3.3, “Installing a Novell Privileged User Manager License,” on page 20.

20 Novell Privileged User Manager 2.2.1 Getting Started Guide
novdocx (en) 16 April 2010
3.3 Installing a Novell Privileged User Manager
License
Log in to the Novell Customer Center (http://www.novell.com/center) and download your license
file. Use the following steps to install it:
1Log in to the Framework Console.
2From the Task Pane, click About Framework.
3Click Register Framework.
4Copy the supplied license and paste it into the text area.
5Click Finish > Close.
Your license details can be viewed by selecting the About Framework option from the Tas k
Pane.
6Continue with one of the following:
Section 3.4, “Setting Up a Package Manager,” on page 20
Chapter 4, “Installing the Agents,” on page 27
3.4 Setting Up a Package Manager
The Package Manager allows you to push updates to hosts and to install additional packages on the
hosts for load balancing and failover. To use the Novell Update Server as the Package Manager, see
“Configuring the Package Manager ” in the Novell Privileged User Manager 2.2.1 Administration
guide.
To use a local host as a Package Manager:
1Create a directory such as
framework on the Framework Manager in the /tmp directory.
This directory is called
framework in the rest of these instructions.
2Copy the
novell-npum-packages-2.2.1.gz from the Package Manager directory on the CD
to the machine.
3Extract the file to the
framework directory.
For UNIX and Linux platforms, use the following commands:
gunzip novell-npum-packages-2.2.1.tar.gz
tar -xvf novell-npum-packages-2.2.1.tar
For Windows platforms, use WinZip to extract the file.
4Use the following command to publish the packages to the Package Manager.
Replace <admin> with the name of your admin user.
For Linux and UNIX platforms:
/opt/novell/npum/sbin/unifi -u <admin> distrib publish -d /tmp/framework
For Windows platforms:
c:\Program Files\novell\npum\bin\unifi -u <admin> distrib publish -d
c:\tmp\framework
5When prompted, enter the password for the admin user.