Upgrading a Release 22.9 or later single-user GUI client

Introduction

This section describes how to upgrade a Release 22.9 or later NFM-P single-user GUI client in a standalone or redundant NFM-P deployment.

You must comply with the general requirements in NFM-P deployment configuration, and any specific requirements in this section, before you attempt to upgrade an NFM-P single-user GUI client.

Post-upgrade client connection to multiple NFM-P systems

You can configure a single-user client to connect to multiple NFM-P systems. For information , see To configure a GUI client login form to list multiple NFM-P systems.

Platform requirements

Single-user GUI client deployment is supported on the following platforms:

• Mac OS X

• Microsoft Windows

• RHEL

General

The following are the security requirements for single-user client upgrade:

• An upgrade requires only local user privileges.

• Only the user that deploys the client software, or a user with sufficient privileges, such as root or a local administrator, can start a single-user client.

Note: Single-user client upgrade requires a supported web browser on the client station. See the NSP Planning Guide for browser support information.

Mac OS

See the NSP Planning Guide for the Mac OS single-user client deployment requirements.

Microsoft Windows

See the NSP Planning Guide for the Microsoft Windows single-user client deployment requirements.

RHEL

A RHEL single-user GUI client station must have:

• a supported OS release and patch level, as described in the NSP Planning Guide

• the required RHEL OS configuration and packages, as described in Chapter 3, RHEL OS deployment for the NSP

Optionally, for greater system security, you can remove the world permissions from RHEL compiler executable files; see Resetting GCC-compiler file permissions for information.

Note: The Bash shell is the supported command shell for RHEL CLI operations.