IBM Security Access Manager for Enterprise Single Sign-On, Version 8.2.2

Installing AccessAgent through Group Policy Object

For large AccessAgent deployments, you can install AccessAgent on multiple workstations through Microsoft Active Directory Group Policy Object.

About this task

For more information about the startup script, go to the Microsoft website at http://www.microsoft.com and search for Assign computer startup scripts GPO.

Procedure

In the SetupHlp.ini response file, specify the following required parameters:
InstallTypeGPO

Verify that the value for the InstallTypeGPO parameter is 1.

ImsConfigurationPromptEnabled

Verify that the value for the ImsConfigurationPromptEnabled parameter is 0. The default value is 0.

PriceLevel

Specify the product edition that you licensed with the PriceLevel parameter. For example: Suite or Standard.

ImsServerName

Specify the IMS Server location. For example: IMSServerName = IMSServer.example.com.
Put your AccessAgent installer package in a shared folder where all target client computers can access.
Navigate to Group Policy Object > Computer Configuration > Windows Settings > Scripts > Startup

Run the following installation batch script.

echo AA installation started on %DATE% at %TIME% > %temp%\AASuiteInstall.log 
<AccessAgent installer package>\setup.exe /silent ISRootStagePath=<temp_path>
echo AA installation ended on %DATE% at %TIME% >> %temp%\AASuiteInstall.log

Customize the parameters for the installation batch script. For example, to install AccessAgent in Japanese, see the following example:

echo AA installation started on %DATE% at %TIME% > %temp%\AASuiteInstall.log 
<AccessAgent installer package>\setup.exe /silent ISRootStagePath=C:\Temp /language:1041
echo AA installation ended on %DATE% at %TIME% >> %temp%\AASuiteInstall.log

Feedback