Installing components on Microsoft Windows
As an alternative to the unified product installer, you can use the individual component installers to set up the BMC Server Automation environment. This topic includes the following sections:
Before you begin
Before installing BMC Server Automation on Windows, ensure that you have performed the following tasks:
Ensure that you have set up a database for use by BMC Server Automation, as discussed in Setting up a SQL Server database and user for BMC Server Automation or Setting up an Oracle database for BMC Server Automation.
- Ensure that your connection to Microsoft SQL database is not encrypted. BMC Server Automation does not support using an encrypted Microsoft SQL database connection at the time of installation. However, after the product is installed successfully, BMC Server Automation can be configured to use an encrypted connection to communicate with the Microsoft SQL database. For steps on enabling and disabling an encrypted connection to your SQL database server, see Encrypting your database connection.
To know the default installation location of various BMC Server Automation components, see Default installation location for components.
- The BMC Server Automation Application Server installation program needs a certificate password to generate a self-signed X.509 certificate. Communication between BMC Server Automation and servers being provisioned and between the Application Server and the process spawner 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.
- To add an exception for a BMC Server Automation installation program
- Open Control Panel.
- Double-click System.
- Select the Advanced tab.
- In the Performance pane, click Settings.
- Select the Data Execution Prevention tab.
- Click Turn on DEP for all programs and services except those I select.
- Click Add.
- Select the installation program for which you want to add an exception. Then click Open.
- Click OK two times.
- Restart the computer.
You can install all components on a single server, or on separate servers for scalability.
(For Windows 2012 only) Run each installation file as an Administrator so that the file server path can be created successfully.
To run the installation file as an administrator, right-click the installation file and click Run As Administrator. If you do not run the installation file as an Administrator, you must create the file server path manually before running it.
|Install an RSCD agent|
To install in a replicated domain controller environment, see Installing RSCD agents in a replicated domain controller environment.
|Learn how to install an RCSD agent on Windows. An agent is required on each server that BMC Server Automation manages.|
|Install BMC Server Automation Application Server and Network Shell|
To install Network Shell individually, see Installing only the Network Shell (Windows).
Use this procedure to install the BMC Server Automation Application Server and the Network Shell on Microsoft Windows platforms on which no previous versions of these components are installed. You can perform either:
|Configure the file server||Learn how to set up the file server to store the contents of files included in snapshots, Network Shell scripts, BLPackages, software packages, and other types of information that is not easily stored in the database.|
|Install the PXE server and TFTP servers||Use this task to install a PXE server and the TFTP server, which are functional components required for the BMC Server Automation provisioning solution, on Microsoft Windows.|
|Install BMC Server Automation Console||Learn how to install the BMC Server Automation Console and Network Shell on Microsoft Windows. The console is the graphical user interface to the BMC Server Automation servers. Network Shell is a required prerequisite of the console.|
Installing the Application Server and file server (video)
See a video demonstrating how to set up a standalone instance of a BMC Server Automation Application Server and file server for testing and development purposes.