System requirements for Windows

This topic summarizes the system requirements for the installer planner host, the supporting products, and databases used by BMC Cloud Lifecycle Management on Microsoft Windows operating systems.

• • Windows installer host requirements
    • Installer host operating system, hardware, and permissions
    • Installer host environment variables
    • Installer host port requirements
  • 
    Windows supporting product host requirements
    • Requirements for installing all Windows product hosts
  • Operating system requirements
  • SQL Server database requirements for Windows
    • Database requirements overview
    • Supported SQL Server database version
    • Authentication requirements for SQL server
    • Unicode and character set requirements for the SQL Server database
    • Precreate database support and requirements for Windows
    • Windows database requirements for supporting products
  • Where to go from here

Windows installer host requirements

Before you launch the BMC Cloud LifeCycle Management installer, ensure that the installer host meets the requirements described in the following sections, based on your operating system. An installer host is the physical or virtual machine host on which you run the installer.

Installer host operating system, hardware, and permissions

_{Back to top}

Installer host environment variables

Ensure that the user and system environment variables on the installer host are set with the same value (for example, TMP=C:\Support and TEMP=C:\Support). Also ensure that the values of these user and system variables match on both installer and product hosts.

Installer host port requirements

If a firewall is configured in your environment, ensure that the firewall allows communication from the BMC Cloud Lifecycle Management installer host to the target computers by using the ports listed in the following table. The installer uses these ports to run commands to check application connectivity, database connections, RSCD connectivity, remote installation status, and so on. The port numbers in the table are the default values and might change based on user input or user environment configuration. For example, the database might be installed on port 1522 instead of port 1521. In that case, you must ensure that the port is enabled in the firewall.

_{Back to top}

Windows supporting product host requirements

This section lists the hardware and software requirements, and the tasks that you must perform before you install the BMC Cloud Lifecycle Management solution on Microsoft Windows. For more information about product-specific hardware requirements per deployment type, see deployment architecture and sizing guidelines.

Requirements for installing all Windows product hosts

1. Define a local Windows administrator to perform all installations. 
   The user must be:
   1. The local Administrator of the system (not a domain user)
   2. Added to the Administrators group on the system.
2. Grant appropriate rights to the user:
   1. Open Administrative tools > Local Security Policy > Local Policies > User Rights Assignments.
   2. Add the user to the Allow log on locally property.
   3. Remove the user from the Deny log on locally property, if present.
3. Standardize the user and system environment variables on the target product hosts so that they are set with the same value (for example, TMP=C:\AppData and TEMP=C:\AppData). 
4. Ensure that the values of the user and system variables match on both installer and product hosts.
5. Set the same system time on the installer host and all the product hosts, for example, Pacific Standard Time. 
6. Delete any files from the C:\Windows\Temp folder. This will speed up the process of installing the RSCD agent. 
7. Verify the product host connectivity to ensure that you can successfully launch the installation on a product host:
   1. Ensure that you can contact all target hosts (on which you want to install BMC products) from the installer computer (for example: ping <host name>.
   2. Run the ipconfig command on the target host, and verify that the IP address returned in the previous step matches the the target computer's IP address returned in this step.
   3. Record the IP addresses of all the target hosts. You might need these later during installation, for example, if you need to use an IP address in the installer because the host name does not work. 
8. Ensure that the TrueSight Server Automation Remote Server Call Daemon (RSCD) Agent is not installed on any target host. 
   The installer uses NSH to execute silent installation commands, which are accepted by the RSCD agent installed on the target hosts. The RSCD agent executes the commands so that the installer can remotely install the supporting BMC products.If an existing RSCD Agent and NSH are installed, uninstall them, as described in the following procedures.
   1. To uninstall the RSCD Agent, select Start > Programs > Windows Control Panel and open the Add/Remove Programs utility.
   2. Select the component that you want to uninstall (for example, TrueSight Server Automation RSCD Agent) and click Change/Remove
   3. After the RSCD Agent is uninstalled, go to C:\Program Files\BMC Software\Bladelogic and delete the RSCD folder.
   4. Manually delete the C:\Windows\rsc folder.

   5. Restart your computer.

      Tip

      If you don't restart your computer, installing the RSCD Agent can take an extended period of time to perform, sometimes over an hour.

      For more information, see Uninstalling components on Windows in the TrueSight Server Automation documentation.

   6.  To uninstall NSH, select Start > Programs > BMC Software > BladeLogic Server Automation Suite > Uninstall Network Shell.
   7. After the NSH is uninstalled, go to C:\Program Files\BMC Software and delete the NSH folder.
   8. Manually delete the C:\Windows\rsc folder.
   9. Restart your computer.
      For more information, see Uninstalling components on Windows in the TrueSight Server Automation documentation.

1. Turn off the Windows Firewall on all product hosts:
   1. Go to Start > Control Panel.
   2. Under System and Security, click Check Firewall Status. 
   3. Click Turn Windows Firewall on or off. 
   4. Start the Windows Firewall service, if necessary.
   5. For all three network locations, select Turn off Windows Firewall (not recommended). 
   6. Click OK. 
      For more information about stopping or disabling the firewall service, see the I Need to Disable Windows Firewall topic in the Microsoft TechNet Library. 
2. To install the products successfully on all product hosts, you must have administrator privileges for actions, such as setting system environment variables and restarting services. Therefore, having only administrator privileges is not enough. You must set the User Account Control (UAC) to disable the Administrator Approval Mode, as follows:
   1. Open Administrative tools > Local Security Policy > Local Policies > Security Options.
   2. From the list of security options displayed, double-click the User Account Control: Run all administrators in Admin Approval Mode option and set it to Disabled.
3. Install Microsoft Internet Explorer or Mozilla Firefox on any host on which you want to access the mid tier. In addition, install a browser on the installer host so that you can access the online help.
   For more information about the version of web browsers to install, see http://www.bmc.com/support.
4. Configure the terminal services.
   
   1. From the Windows Start menu, click Run.
   2. Type 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. If the settings do not take affect, complete the following steps:
      1. From the Windows Start menu, click Run.
      2. Type regedit, and then click OK.
      3. Expand HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Terminal Server.
      4. Update PerSessionTempDir to 0 and DeleteTempDirsOnExit to 0.
    

5. 
   

   Stop and disable both the IP Helper and Windows HTTP Proxy web service on the target hosts before you start installation. Otherwise, the installations fail.

6. Restart the computer.
7. (Optional) Install SAP BusinessObjects XI R 3.1 SP2 for reporting purposes.
8. File system (For example: //<target_host>/C$) on all target host should be accessible from Install Planner host.

_{Back to top}

Operating system requirements

These are the supported operating systems:

• Microsoft Windows Server 2012 R2  Standard Edition 64-bit OR
• Microsoft Windows Server 2012  Standard Edition 64-bit  OR
• Microsoft Windows Server 2016  Standard Edition

These are the minimum hardware requirements to begin with. Based on the load and usage, you may have to add additional hardware as required going ahead. 

SQL Server database requirements for Windows

The following sections outline the SQL Server database requirements for Windows platforms. For SQL Server databases, you can have the installer create a database during the installation process or you can precreate a database for your products. However, the installer requires you to authenticate a pre-created database. 

Database requirements overview

Not every product in the BMC Cloud Lifecycle Management solution requires a database. Certain products can share a database with other products in the solution. You can install the database on the same host as the BMC product, or you can install a remote database. Regardless of where you install the database, you can use the pre-create database option if you meet the requirements listed in this topic.

This section explains the database requirements for the following products:

• BMC AR System Server – Cloud Portal and Database
• TrueSight Server Automation
• TrueSight Network Automation

Supported SQL Server database version

On the supported operating systems, BMC Cloud Lifecycle Management solution supports:

• Microsoft SQL Server 2012  64-bit SP1 or SP2
• Microsoft SQL Server 2014 Enterprise Edition 64-bit
• Microsoft SQL Server 2016 Enterprise Edition 64-bit  
  
  

_{Back to top}

Authentication requirements for SQL server

SQL Server Database to be used with BMC Cloud Lifecycle Management must support SQL Server based authentication for running Pre-Analyzer checks as well for performing BMC Cloud Lifecycle Management product installations. In addition to this requirement, you can optionally have SQL Server to support Windows Authentication as well.

Unicode and character set requirements for the SQL Server database

The following Unicode and character set requirements apply to the MS SQL Server database:

• You must synchronize all your databases so that their character sets and Unicode settings are correctly aligned with their <product>, for example, BMC Remedy AR System settings.
• You must run Unicode to Unicode or non-Unicode to non-Unicode. Do not mix these settings.
• For MS SQL Server, you must set the Unicode data types to nchar, nvarchar, and ntext.

Precreate database support and requirements for Windows

In the table in product-specific database requirements, the values for the pre-created database support for SQL Server are as follows:

• Yes, but optional — A pre-created database is supported. However, you can optionally choose to have the installer create the database during the installation process.
• Yes, and mandatory — You must use a pre-created database.
• No — A pre-created database is not supported. You must allow the installer to create a database and a user.

For more information about pre-created databases, see the documentation for the respective product in the documentation for related products.

_{Back to top}

Windows database requirements for supporting products

The following table lists the requirements for SQL Server databases. For specific preparatory tasks that you must perform before you complete product installation, see the Additional information column.

_{Back to top}

Where to go from here

Permissions-required-for-Windows-installations