Planning for client deployments
You can use the AccessAgent as a single sign-on client on Windows workstations or on Citrix/Terminal Servers
See the following topics:
- Planning for installation of AccessAgent on Terminal Service or Citrix clients
- Planning for the Windows interactive logon experience
- Session management
- Strong authentication
To install or upgrade your AccessAgent version, see the IBM Security Access Manager for Enterprise Single Sign-On Installation Guide.
Upgrading AccessAgent clients
If you have a previous version of the AccessAgent clients, you must upgrade the IMS Server hosts to the latest version. You must upgrade the IMS Server before you upgrade the AccessAgent clients. See Upgrading AccessAgent for more information about upgrading the clients.
Enterprise installation strategies
An enterprise installation strategy involves a mass deployment of the AccessAgent packages on multiple workstations in a repeatable way.
To deploy the packages on groups of workstations remotely, you can use a software provisioning solution like Tivoli® Provisioning Manager or Active Directory Group Policy Objects.
For a silent installation, you can prepare a response file with preset deployment parameters. The response file contains parameters for the IMS Server host, license information, installation path, and product settings that are specific to your deployment environment. You can also customize the packages with additional settings to provide a custom enterprise logon experience.
Installation from a shared network folder is not supported.
Planning for AccessAgent installation on Terminal Service or Citrix clients
For terminal service deployments, you must deploy both the server and client version of AccessAgent.
You deploy the server version of AccessAgent on the Terminal Server and the client version AccessAgent on the Terminal Service/Citrix client. For terminal service environments, you can deploy the AccessAgent client in lightweight mode configuration, with a lower memory footprint on terminal service clients.
See the IBM Security Access Manager for Enterprise Single Sign-On AccessAgent on Terminal Server and Citrix Server Guide for terminal service deployments with AccessAgent.
Planning for installations with strong authentication
If you are using two-factor authentication devices, install and set up the necessary drivers for your authentication devices before deploying AccessAgent. If you are combining two-factor authentication with desktop session management schemes, see Strong authentication.
Planning for installation on workstations with shared and private desktop switching schemes (session management)
See Session management for the authentication considerations with session management schemes.