Performing Remedy SSO installation in standalone mode with the Remedy installer

You can deploy Remedy SSO in one of the following ways:

  • By using the TrueSight installer for Remedy SSO - This is a consolidated installer that contains all the prerequisite software for Remedy SSO, and can be used for a unified install experience. It only supports PostgreSQL database.
  • By using the Remedy SSO installer - This contains only the Remedy SSO Server. It doesn't contain prerequisite software, such as JRE and Tomcat. It supports databases like MS SQLServer and Oracle, apart from PostgreSQL.

This topic provides instructions for performing Remedy Single Sign-On (Remedy SSO) installation using the Remedy SSO installer. You can perform a stand-alone installation following the instructions given in this topic.

To configure the Terminal Server options on Windows

If you are planning to install Remedy SSO on a host computer with Windows, configure the following Terminal Server options that pertain to temporary folders. Doing this enables you to run the installation utility through a Terminal Services connection or a remote desktop session.


  • You need to configure the Terminal Server options only once on a host computer running on Windows.
  • You do not have to configure the options if you are planning to install Remedy SSO on running on Linux or you are reinstalling a TrueSight product on the same host computer running on Windows.
  1. On the host computer, from Start, type Run and press Enter, and type gpedit.msc and press Enter.
    The Local Group Policy Editor is opened.
  2. From the Local Group Policy Editor, navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Temporary folder.
  3. Double-click the following options and set each to Enabled:
    1. Do not delete temp folder upon exit.
    2. Do not use temporary folders per session.

  4. Back up the Windows registry and avoid receiving notification about Terminal Server configuration at the time of product installation:

    1. On the host computer, from Start, type Run and press Enter, and type regedit and press Enter.
      The Registry Editor is opened.
    2. From the Registry Editor, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server.
    3. Set the value for PerSessionTempDir and DeleteDeleteTempDirsOnExit to 0.


      You can revert these changes after you complete the installation process.

  5. Restart the host computer.

Remedy SSO Cookie domain and TrueSight Presentation Server FQDN

For a successful authorization, the Presentation Server domain name and the the Remedy SSO cookie domain must belong to the same network domain or one of the parent domains.

  • Example: Correct use of cookie domain
    • is the cookie domain of Remedy SSO
    • <tspshostname> is the Presentation Server FQDN
  • Example: Wrong use of cookie domain
    • is the cookie domain of Remedy SSO 
    • <tspshostname> is the Presentation Server FQDN

To install Remedy Single Sign-On in a standalone mode


  • You must note down the cookie domain configured on the Remedy Single Sign-On server, as you need this when you configure the domain for the Presentation Server.
  • You must note down the updated Remedy SSO Admin user password, as you need to update the password from the TrueSight console after you install or upgrade the Presentation Server. For more information, see To update Remedy SSO configuration from the TrueSight console. Open link

Remedy SSO in HA mode

If you are installing the Remedy SSO server in a high-availability mode, this procedure is applicable for the first or primary node installation.

Where to go from here

To configure the Remedy SSO general settings, see Configuring the general settings in the Remedy SSO server

Was this page helpful? Yes No Submitting... Thank you