Requirements for installing individual components on Microsoft Windows

Agent

• Ensure that Microsoft Visual C++ 2015 Redistributable Update 3 or later is installed on the server.
  
  Microsoft Visual C++ 2015 Redistributable Update 3 or later can be installed automatically from Agent Installer Job - Options window and by using the prepackaged content in depot software. However, the depot software can be used only for upgrade scenario. For more information, see Agent-Installer-Job-Options and Upgrading-the-RSCD-Agent-using-an-Agent-Installer-Job. When you install Microsoft Visual C++ 2015 Redistributable Update 3 or later, the installer sets the Pending Reboot flag to True in the Windows registry.

  Note

  As a prerequisite to install Microsoft Visual C++ 2015 Redistributable Update 3 on Windows 2012 R2, you must have the following patches installed on your server:

  • KB2919442 (Required for 2919355)
  • KB2919355. This patch requires several other patches: clearcompressionflag.exe, KB2919355, KB2932046, KB2959977, KB2937592, KB2938439, and KB2934018. This are all available on the download page for KB2919355.

  For more information about the prerequisites for Microsoft Visual C++ 2015 Redistributable Update 3, refer to the Microsoft documentation here.

• The RSCD agent for Microsoft Windows requires that the Server service is running.
• For a server to provide information about Windows Group Policy objects, the file secedit.exe must be installed on the server, and it must be included in the server's executable path.
• If the server is a domain member or domain controller, confirm that the Net Logon service is enabled and running before installing the RSCD agent. The agent uses the Net Logon service to determine the domain and obtain information about the machine. If the server is not part of a Windows domain, the agent uses a different method for determining machine information. Additionally, the automation principal feature uses the Net Logon service to access domain user information so the automation principal can act as a domain user. Note: If you subsequently remove the agent computer from the domain, you must also remove the Net Logon dependency (via the registry) and restart the agent. Otherwise, the agent will not start.
• The patch analysis function of TrueSight Server Automation requires the Microsoft XML (MSXML) parser version 6.0 SP2 or later to be installed on the server on which the RSCD agent is installed. You can install the RSCD agent on a computer on which MSXML is not installed, but patch analysis does not function correctly until MSXML 6.0 SP2 or later is installed.
• If you are using Windows Terminal Services or Citrix Presentation Server to install or if you are installing on a Windows operating system, use one of the following methods to install:
  
  • Install in Install mode rather than Execute mode. For information, see Using-Install-mode-instead-of-Execute-mode.
  • Install using the Windows Add or Remove Programs utility.

Application Server (and NSH)

• To perform this installation, you must have local administrator privileges.
• The TrueSight Server Automation Application Server installation program needs a certificate password to generate a self-signed X.509 certificate. Communication between TrueSight Server Automation and servers being provisioned uses the Transport Layer Security (TLS) protocol and X.509 certificates. The password must be at least 6 characters. For more information about certificates and the TLS protocol, see Authentication.
• The Application Server installation does not install the TrueSight Server Automation Console. To view the console, you must install it. For information, see Installing-the-TrueSight-Server-Automation-Console-and-Network-Shell-Windows. 
• To use provisioning with the Application Server, select the option to enable provisioning.
• If you are using Windows Terminal Services or Citrix Presentation Server to install or if you are installing on a Windows operating system, use one of the following methods to install:
  • Install in Install mode rather than Execute mode. For information, see Using-Install-mode-instead-of-Execute-mode.
  • Install using the Windows Add or Remove Programs utility.
• You must set up your database schema. See Setting-up-an-Oracle-database-for-TrueSight-Server-Automation and Setting-up-a-SQL-Server-database-and-user-for-TrueSight-Server-Automation .
• On 64-bit Windows systems, confirm that the <WINDIR>\SysWOW64 directory contains a copy of the chcp.com file. The installer uses this file to set the code page of standard output (stdout). You can obtain the file from a 32-bit version of Windows.
• If you plan to use the bljython utility, install the Application Server before installing Jython.
• If the host computer on which you are installing the Network Shell has:
  • A supported version of Perl installed--The Network Shell installation automatically installs the Network Shell Perl module. (For information about the Perl versions that TrueSight Server Automation supports, see Perl support.)
  • An unsupported version of Perl installed--The installation copies files that allow you to install the Perl module after you have installed the supported version of Perl.

Console (and NSH)

• BMC recommends that you do not install the console on the same system as the Application Server. Copy the files from the Application Server installation (for example, ..\TSSA<version>-WIN64\Disk1\files\installers\rcp) to a different system and perform the installation there.
• Before you install the TrueSight Server Automation Console, ensure that port 12333 (TCP) is not being used. Installation of the console requires use of this port; if it is already in use, the installation fails.

• Update the Windows Terminal Services Server Settings for temporary folders. (In Windows Server 2008 R2 and later versions, Terminal Services is renamed to Remote Desktop Services).

  Click here for steps about updating the Windows Terminal Services

  To update the Windows Terminal Services (or Remote Desktop Services) configuration perform either of the following steps:

  Server settings method

  1. On the computer where you are installing the TrueSight Server Automation Console, select Start > Run.
  2. For Open, enter gpedit.msc, and then click OK.
  3. Navigate to the Temporary folders policies:
     Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services >Remote Desktop Session Host > Temporary folders
     or: 
     Computer Configuration > Administrative Templates > Windows Components > Terminal Services > Terminal Server > Temporary folders
  4. Set the Properties of Do not delete temp folder upon exit to Enabled and then click OK.
  5. Set the Properties of Do not use temporary folders per session to Enabled and then click OK.
  6. Restart the computer.
      If the settings do not take effect, use the Registry Editor (regedit):

  Registry editor method

  1. Click Start > Run and enter regedit.
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server.
  3. Set the DeleteTempDirsOnExit and the PerSessionTempDir values to 0.
  4. Restart the computer.

  Note: The installation program uses temporary folders to preserve the install log. Usually, you can perform this update only one time; you do not need to update the configuration every time you install. However, if your Server Settings are different from those needed for installation, after you finish installing the console you can change the settings back to their previous settings.
  

File server

A file server should meet the following requirements:

• An RSCD agent must be installed and should be the same version as the Application Server.
• Do not limit access to the file server by pushing agent ACLs to the agent on the file server. All users must be mapped to the same user on the file server.
• As a minimum, a file server must have 72 GB of available, nonredundant, disk space. BMC recommends that the file server be allotted 200 GB or more of available RAID 5 disk space.
• Define a user name (for example, blfsro) on the file server with read only permission on the storage, and map all users to that user name. Without this mapping, a user may not be able to access a file that another user has stored on the file server. To accomplish the necessary mapping, create an entry like the following in the exports file on the file server:
  <appServer> ro,user=blfsro
  Where <appServer> is a comma-separated list of Application Server names or IP addresses (IPv4 or IPv6).
  The default location of the exports file is:
  • (Windows) C:\Windows\rsc
  • (Linux): /etc/rsc

• Map the built-in System:System role/user to the user name (for example, blfsrw) defined on the file server with full permission on the storage. To accomplish the mapping, create an entry like the following in the users.local file on the file server:
  System:System rw,map=blfsrw
  Where blfsrw is the name to which the built-in System:System role/user is mapped, typically used when Application Server accesses the file server.
  If the required directory structure does not already exist on the file server, the system process attempts to create it.
  The default location of the users.local file is:

  • (Windows) C:\Windows\rsc
  • (Linux): /etc/rsc

  For examples on configuring the file server agent ACLs, see Configuring-the-file-server-agent-ACLs.

• If your file server location is on partition or a mounted storage, you must ensure that the mount point for the storage or partition is consistent even if the file server host is restarted.
  For example, on Linux, you can ensure this by configuring the fstab file in the etc folder of your machine. The fstab file maps the Universally Unique Identifier (UUID) of a storage or partition to the directory it should be mounted on.

NSH only

• To perform the Network Shell installation, you must have local administrator privileges.
• If you are using Windows Terminal Services or Citrix Presentation Server to install or if you are installing on a Windows operating system, use one of the following methods to install:
  • Install in Install mode rather than Execute mode. For information, see Using-Install-mode-instead-of-Execute-mode.
  • Install using the Windows Add or Remove Programs utility.
• On 64-bit Windows systems, confirm that the <WINDIR>\SysWOW64 directory contains a copy of the chcp.com file. The installer uses this file to set the code page of standard output (stdout). You can obtain the file from a 32-bit version of Windows.