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).

  The [expand] macro is a standalone macro and it cannot be used inline. Click on this message for details.
  This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
  

File server

NSH only