Windows Agents

Use the links below to download the agent installation software for Windows based endpoints.

There are three agents available for Windows endpoints:

  • Application Control Agent (ACS): This agent is responsible for monitoring processes executing the Verify Privilege ManagerApplication Control Functions on the endpoint.
  • Local Security Agent (LSS): This agent is responsible for monitoring and executing Local Security functions.
  • Thycotic Agent: The core agent is responsible for all reporting and monitoring communication on the endpoint. It can be considered the managing agent, while the Application Control and Local Security Agents are the worker agents.

Individual Agent Installers for Verify Privilege Manager

Hardened Agents

If agent hardening was applied to user endpoints, the hardened agents need to be deleted via the sc delete {agent name} commandline command. This needs to be done under the context of the domain user prior to running the msi-based agent installation commands. When the agent is deleted successfully, a success message will be returned, for example:

Copy 
C:\sc delete arelliaagent
[SC] DeleteService SUCCESS
C:\sc delete arelliaacsvc
[SC] DeleteService SUCCESS

If the hardened agents are being deleted via software delivery script, the script needs to be delivered under the context of the domain user.

64-bit Windows Operating Systems

Individual Windows agents are available in MSI format for easier bulk-rollout through software delivery tools. For installing individual agents, ensure that the Core IBM Security Agent is installed last.

Refer to the Software Downloads page for OS-specific downloads.

  • Application Control Agent (x64)
  • Local Security Solution Agent (x64)
  • Core Thycotic Agent (x64)

Installation Command Lines

The Install Code field can be left blank when using versions lower than 10.5.

If you are using the MSIs to install, standard logging flags work and can be used to specify where you want the installation log to be outputted to. For example: /l*vx C:\agent-install.log.

When installing agents, proper order of execution is crucial for proper registration of all components, as follows:

  • Application Control Agent

    Copy 
    msiexec.exe /i "IBMSecurity_ApplicationControlAgent_x64_11_3_7587.msi" /norestart REBOOT=ReallySuppress /qn
                        

  • Local Security Agent

    Copy 
    msiexec.exe /i "IBMSecurity_LocalSecurityAgent_x64_11_3_7585.msi" /norestart REBOOT=ReallySuppress /qn
                        

  • Core IBM Security Agent

    Copy 
    msiexec.exe /i "IBMSecurityAgent_x64_11_3_7587.msi" /norestart AMSURL=https://SERVERNAME/TMS/ INSTALLCODE=XXXX1234ABCD REBOOT=ReallySuppress /qn
                        

32-bit Windows Operating Systems

Individual Windows agents are available in MSI format for easier bulk-rollout through software delivery tools.

If you are using the MSIs to install, standard logging flags work and can be used to specify where you want the installation log to be outputted to. For example: /l*vx C:\agent-install.log.

When installing agents, proper order of execution is crucial for proper registration of all components, as follows:

  • Application Control Agent (x86)
  • Local Security Solution Agent (x86)
  • Core Thycotic Agent (x86)

Refer to the Software Downloads page for OS-specific downloads.

Installation Command Lines

The Install Code field can be left blank when using versions lower than 10.5

  • Application Control Agent

    Copy 
    msiexec.exe /i "IBMSecurity_ApplicationControlAgent_x86_11_3_7587.msi" /norestart REBOOT=ReallySuppress /qn
                        

  • Local Security Agent

    Copy 
    msiexec.exe /i "IBMSecurity_LocalSecurityAgent_x86_11_3_7585.msi" /norestart REBOOT=ReallySuppress /qn
                        

  • Core IBM Security Agent

    Copy 
    msiexec.exe /i "IBMSecurityAgent_x86_11_3_7587.msi" /norestart AMSURL=https://SERVERNAME/TMS/ INSTALLCODE=XXXX1234ABCD REBOOT=ReallySuppress /qn