Walkthrough: Installing on Windows using the unified installer

This topic walks you through the process of installing BMC Server Automation (BSA) 8.7 on Microsoft Windows, using the unified product installer and component installers.

This topic includes the following sections:

Introduction

This topic is intended for system administrators preparing to install the BSA product. The goal of this topic is to demonstrate how to use the unified product installer to install all essential components of the BSA product in a Windows environment.

What is the unified product installer?

The unified product installer simplifies and improves the installation experience by providing a centralized UI for installing the default Application Server node. It installs a setup that consists of the following components:

Microsoft SQL database: The unified product installer creates a BSA schema on your database server.
Default Application Server: This is the primary server that is installed in a BSA environment. The unified product installer configures the default Application Server to connect to your database server. It also installs an RSCD agent on the default Application server. The default Application Server is also referred to as a default Application server node, because it hosts more than one component.
File server: You can choose to install the file server on the same machine as the default Application server (called as the local file server) or install it on a separate machine (called as a separate file server.) In the case of a separate file server, you can choose to manually install the RSCD agent or have it installed by the unified product installer.
Console and PXE/TFTP server: The unified product installer installs the console and the PXE/TFTP server on the default Application Server.

What does this walkthrough show?

In this walkthrough, we will:

Use the unified product installer to install a small BSA environment (Application Server, console, file server, PXE/TFTP).
Use the quick start page to import servers to the new environment and to add agents to those servers.
Use individual component installers to manually install additional components such as additional Application Servers, a separate PXE/TFTP server, and a separate console server, to complete a production-level environment.

The BSA environment will have the following characteristics:

Component	Number of components	Description
Application Server	2	This BSA environment consists of two Application Servers: A default Application server installed by the unified product installer on a Windows 2012 (x64) system. An additional Application Server installed on a Windows 2012 (x64) system to improve the performance of BSA.
Console	2	This BSA environment consists of two instances of the BSA console: The console installed by the unified product installer on the default Application Server node. A console that is manually installed on a separate machine (recommended for high performance environments)
Database	1	The default Application Server connects to an existing Microsoft SQL server database. Note: Although the BSA schema is created by the unified product installer, you must have access to an existing database that has been set up on a Microsoft SQL Server. For a description of that process, see Walkthrough: Setting up a SQL Server database .
File server	1	This BSA environment uses a separate Windows file server machine that is installed by the unified product installer.
PXE/TFTP server	2	This BSA environment consists of two PXE/TFTP servers: The PXE/TFTP server installed by the unified product installer on the default Application Server node A PXE/TFTP server that is manually installed on a separate machine (recommended for high performance environments).

What do I need to do before I get started?

Perform the following prerequisite steps before executing this walkthrough scenario:

Download the unified product installer files to a temporary location. The BBSA87-WIN64.zip and BBSA87-RSCDAgents.zip files required in the this walkthrough can be downloaded from the Electronic Product Distribution (EPD) website. For instructions on downloading the files, see Downloading the installation files .
You must be able to access an existing database that has been set up on Microsoft SQL Server. For a description of that process, see Walkthrough: Setting up a SQL Server database .
If you want the unified product installer to automatically install the RSCD agent on your Windows file server, you need to download the Microsoft Sysinternals Suite from the Microsoft tech support site and copy the PsExec file to the %PATH% variable on the default Application Server node (typically C:\Windows\System32\). By doing so, you configure the default Application Server machine as a PsExec server. Note: A PsExec server is not required if you choose to manually install RSCD agents on your Windows servers.

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 BMC Server Automation Console, select Start > Run.
2. For Open, enter tscc.msc. Then click OK. (If you are using Windows 2008 R2 or later, you must enter TSConfig.msc)
3. Navigate to Server Settings and do the following:
  - Set Delete temporary folders on exit to No.
  - Set Use temporary folders per session to No.
4. 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.

How to install the default Application Server and separate file server using the unified installer

We start the installation process by using the unified product installer to:

Install the default Application Server node
Install the separate file server
Configure the database
Install the console and the PXE/TFTP on the default Application Server

	Step	Example screen
1	Run the unified product installer on the machine on which you want to install the default Application server node. Extract the BBSA87-WIN64.zip and BBSA87-RSCDAgents.zip files that you downloaded from the EPD to obtain the rscd folder and the BBSA87-WIN64 folder. Copy the rscd folder from within the RSCDAgents extracted package to the following path in the BBSA87-WIN64 folder: `BBSA87-WIN64 /files/installer/` Run the setup.exe file that is In the BBSA87-WIN64 folder to start the unified product installer wizard. Select the language in which you want to run the installer and click OK.
2	Read through the basic information about the unified product installer and the types of nodes that are installed in the environment. Click Next.
3	Read the End User License Agreement (EULA) and select I agree to the terms of the license agreement. Click Next.
4	Read the BSA copyright information and select I agree to the terms of the license agreement. Click Next.
5	Enter the database server details. Enter the Host name or IPv4 address of the server that runs the database. Note that if your server is on an IPv6 address system you can only enter the host name of the server. Enter the Port that the database listens on. The default port is1433 for an SQL Database. Enter the Name of the database instance that you created. (See Walkthrough: Setting up a SQL Server database ) Enter the Login Name and Login Password that you created for the database. (See Walkthrough: Setting up a SQL Server database ) Click Next. Click here if you want to use a connection string to connect to the database server The Advanced option is only selected if you want to provide a custom connection string to your database. Note that all other fields are disabled when this option is selected. Type the database connection string in the field adjacent to the Advanced check box. An example of a connection string for an SQL database server is as follows: `jdbc:sqlserver://<DBSERVER>:<PORT>;DatabaseName=<DBNAME>;SelectMethod=cursor` Replace the variables in the above connection string, as follows: `<DBSERVER>` is the name or IP address of the database server `<PORT>` is the port used to communicate with the database `<DBNAME>` is the database name used to identify the SQL database
6	A summary of the database parameters, default installation location, Application Server base port, and file server parameters is displayed. The name of the local super user for RSCD Agent mapping is also listed.
7	Click Customize Configuration. The Installation Directory tab displays the path where BSA is installed. The default path is C:\Program Files\BMC Software\BladeLogic\ for Windows. You can customize the Installation Directory based on your requirements.
8	Click the File Server tab and enter the file server details. To install the file server on a separate machine, select the Install file server on a separate host option (In version 8.6 this option was called Use Remote file server). Because we have not manually installed the RSCD Agent on the file server, we must ensure that the RSCD agent is already installed option is not selected. Enter the Host name or IPv4 address of the file server. Note that if your server is on an IPv6 address system, you can only enter the host name of the server. Enter the directory on the file server where data is stored. Select Windows as the operating system that runs on the separate file server. Enter the name of a Windows user with administrator permissions. Enter the password of the Windows user with administrator permissions. Confirm the password.
9	Click the Ports tab at the top of the screen. Enter the Application Server Base port. Application Server ports are normally configured from a base port, with 9800 being the default base port. Arbitrary port assignments can be made in all cases. For more information, see Application Server ports.
10	Click the Passwords tab at the top of the screen. Enter new passwords in each for the fields based on the guidelines given below. Note: The default password for each entry is password. However, BMC does not recommend using the default passwords provided by the system. Certificate Password The BSA Application Server installation program needs a certificate password to generate a self-signed X.509 certificate. Click here for more information. Communication between BSA and servers being provisioned 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. BLAdmin Password BSA creates a built-in user called BLAdmin during the installation process. Click here for more information. The BLAdmin user is only assigned the BLAdmins role. To activate the default user, it must be assigned a password and granted access to servers in your network. You can use the RBAC Manager folder to perform these actions, but to start the console the first time, you must define a password for the BLAdmin user. For more information, see RBACAdmin and BLAdmin users. RBACAdmin Password BSA creates a built-in user called RBACAdmin during the installation process. Click here for more information. The RBACAdmin user is only assigned the RBACAdmins role. To activate the default user, it must be assigned a password and granted access to servers in your network. You can use the RBAC Manager folder to perform these actions, but to start the console the first time, you must define a password for the RBACAdmin user. For more information, see RBACAdmin and BLAdmin users.
11	Click the Agent Mapping tab. Enter the name of the local super user, that is, a local Administrator or Administrator-equivalent local user, to which the RSCD Agent should map incoming connections during the installation. The default user name is Administrator.
12	Click Update Configuration to apply all the configuration changes that you entered on the various tabs.
13	Click Install to proceed with the installation. The unified product installer performs the following setup operations: Creates a BSA schema in the database Installs the default application server Installs the console Installs a PXE/TFTP server Installs the Network Shell Connects the default Application Server machine to the database Installs the separate file server and the RSCD agent Installs out-of-the-box compliance content
14	If you encountered any errors while installing, click View Log to view a detailed report of the installation. Tip: BMC recommends that you save a copy of the log, before you contact technical support for further assistance. You can also find more information about resolving common issues in Troubleshooting the unified product installer. If all operations are completed successfully, click Done to exit the wizard.

How to add additional Application Servers

To meet the demands of a larger data center, you can deploy additional Application Servers. The additional Application Server is used for improving the performance of BMC Server Automation. The method described here for adding additional Application Servers is relevant only if you installed your default Application Server node using the unified product installer.

	Step	Example screen
1	Start the BMC Server Automation Console and log on using your BL Admin credentials that you created here.
2	Perform the following: Minimize the quick start page Right-click Servers, and click Add Server to add a PsExec server to the BSA environment. In this walkthrough we are using the default Application Server node as the PsExec Server. Enter the host name or IP address of the PsExec server Click Finish. The PsExec Server is added to the BSA environment.
3	Select the Configuration menu and then click Add BSA Application Server Machine.
4	Enter the following details. Host name or IPv4 address of the Application Server. Note that if your Application Server is on an !Pv6 address system you can only enter the host name of the server. User name of an account with Administrator privileges on the additional Application Server machine. Password of the account with Administrator privileges on the additional Application Server machine. Confirm the password of the account with Administrator privileges on the additional Application Server machine. Select a PsExec server from your environment. Note that in this walkthrough we have already configured the default Application Server node as a PsExec server and added it to the BSA environment.
5	Click the Advanced Options tab at the top and enter the following details. Path to the location where you want to install the additional Application Server. The default path used is C:\Program Files\BMC Software\BladeLogic\ Application Server ports are normally configured from a base port, with 9800 being the default base port. Arbitrary port assignments can be made in all cases. For more information, see Application Server ports. Enter the location you want to use as the temporary staging directory during the installation. Click Add node.
6	The additional Application Server is installed. Click OK.

How to add servers and install agents from the quick start page

The next step in setting up the BSA environment is to import servers and add agents to those servers. An easy way to do this is by using the quick start page.

	Step	Example screen
1	You can import multiple servers by specifying a text file that contains a list of server names and properties assigned to each server. Create a server import text file using a comma-separated values (CSV) format, use the following syntax: The first line of the file must contain the column header Name followed by optional comma-separated property names for any properties you want to set for each server. Any property name you include in this import file must already exist in the Property Dictionary. For information about how to add a property to the property dictionary, see Managing properties using the Property Dictionary. Subsequent lines of the file must contain valid host names for each server you want to add, followed by optional comma-separated property values for each server. Save the text file (say Servers.txt) at any location in the default Application Server node. For this walkthrough we will be adding two servers to the BSA environment (without properties). clm-pun-016803 – Windows (64 bit) clm-pun-016809 – Linux (64 bit) Click here to see more samples of server import files with properties for each server. The first example shows the simplest syntax — you simply list the host names of the servers you want to add: Name host1 host2 host3 The following example shows how to set the Customer property for each server: Name,Customer host1,CustomerA host2,CustomerB host3,CustomerC If you need to include spaces in a property value, you must enclose the property value in double quotes: Name,Customer host1,"Customer A" host2,"Customer B" host3,"Customer C"
2	Log on to the BSA Console. Start the BSA Console. Log on to the Console using the BLAdmin username and password that you created during installation. The system uses a default authentication profile (defaultProfile) to log you on to the Console. BSA clients use authentication profiles to facilitate single sign-on feature. For more information about why we use Authentication Profiles, see System capabilities related to security. Click Connect. The quick start page (BMC Welcome Page) appears.
3	To enroll servers, click Enroll, under Server Enrollment. Alternative step: To Import Servers wizard, right-click the Servers folder and select Import Servers. The Import Servers wizard appears.
4	Use the File selection tree to select the text file (Servers.txt) you created at the beginning. Ensure that the If agent does not exist, install using Agent installer job option is not selected. We will be installing agents on the servers later in the walkthrough. Click Finish. Note: For the purpose of this walkthrough, we do not need to add any additional ACL policies. However if you need to control server access with agent ACLs click Next. For more information about the UI elements on the Permissions screens, see Import Servers - Permissions. For more information about ACL policies, see Controlling server access with agent ACLs.
5	The servers are successfully added to your environment.
6	The next step is to install RSCD agents on the enrolled servers. From the quick start page, under Server Enrollment, click Install, on the quick start page. Alternative step: To start the unified agent installer, right-click the Servers folder and select Unified Agent Installer. The Unified Agent Installer wizard appears.
7	Provide a prefix that is attached to the name of all objects that unified agent installer creates. Click Next.
8	Perform the following steps: Select the platforms on which agents can be installed. Specify the depot folder where agent bundles are stored. Click Next. Note: The unified agent installer uses the information you provide on this panel to create an agent bundle. For detailed information about this type of object, see Creating an agent bundle.
9	Click Add to open the Add Remote Host Authentication (non-Windows) window.
10	The Remote Host Authentication (non-Windows) window lets you provide the following information, which is used for authenticating to agentless devices. If you are installing on multiple platforms, typically you define at least one set of authentication information for each platform. Select SSH (Non-Windows) to execute commands directly on an agentless host using the credentials defined in an automation principal that you specify on this panel. Specify the SSH port number that is used by the SSH service running on the remote host. The default port is 22. Select Create new automation principal. You must provide a user name and password for the automation principal. These credentials are used to execute commands on your agentless hosts. Click OK. For more information about the different authentication protocols that you can use, see Unified Agent Installer - Remote Host Authentication (non-Windows). This page also provides information about selecting an existing automation principal.
11	Click Add to open the Add Remote Host Authentication (Windows) window.
12	The Remote Host Authentication (Windows) window lets you provide the following information, which is used for authenticating to agentless devices. If you are installing on multiple platforms, typically you define at least one set of authentication information for each platform. Select or create one of the following automation principals: Select existing automation principal - Click Browse to navigate to an automation principal. Create new automation principal - Provide a user name and password for the automation principal. Optionally, you can identify a domain for the user. PsExec server — Identify a live Windows server where PsExec is installed. Multiple remote host authentication definitions can use the same PsExec server. Click OK. Click Next. For Windows 7 and Windows 2008 target servers BMC recommends that when you install agents on Windows 7 and Windows 2008 devices that are not enabled for a domain, specify a PsExec server that is not part of a domain. When you install agents on Windows 7 and Windows 2008 devices that are enabled for a domain, specify a PsExec server that belongs to the same domain. Ensure that the automation principals you are using to access the agentless devices are associated with the same domain.
13	Click Add to open the New Rule wizard. The unified agent installer uses the information you provide on this panel to create remote host authentication rules. These rules match remote host authentication definitions with agentless devices. For detailed information about this type of object, see Creating or modifying rules for remote host authentication.
14	Click Add Property Condition. A window opens.
15	Create property conditions to identify the two target servers we want to install the agents on. In the first text box at left, click . You can view a subordinate list of properties by clicking the right arrow that appears next to the TARGET* property. When defining remote host authentication rules, use any of following subordinate properties: `TARGET.FQ_HOST` — Fully qualified name of the target device `TARGET.IP_ADDRESS` — IP address (IPv4 or IPv6) of the target device `TARGET.NAME` — Name of the target device In this walkthrough we are using the `TARGET.NAME` property. In the next drop-down box to the right, select equals. Use the next field to the right to specify the name of the target that we want to set this condition for, Click OK. The Rule Definition panel shows the condition. Click Next.
16	Select the non-Windows remote host authentication (created earlier) that should be used to authenticate the clm-pun-016809 server. Click the right arrow to move your selection to the list on the right. Click Finish.
17	Create a similar rule for clm-pun-016803, but this time using the Windows remote host authentication that we created. Click Next.
18	Select the desired options for the agent installer job as described below. Update Server Properties: Update the system with properties from the target servers on which you are installing agents. Update Configuration Objects Registration: Register any configuration objects that are found on the agent and defined in the Configuration Object Dictionary. Push Agent ACLs: Push agent ACLs to the servers that this job targets. To push ACLs, the system converts the access control list defined for a server into a users configuration file and pushes that file to the agent. The access control list is derived from user permissions defined in the RBAC system. Preserve Staging Area On Failure: Information copied to a staging area on a target server during installation should be preserved if the installation fails. By default, when the system has finished installing an agent, it automatically deletes all files in the staging area. Specify the folder to store the Agent Installer Job that is created by the unified agent installer. Click Next.
19	Specify the operating system of the servers you want to select. To display servers running any operating system, select All. Select the servers that you want to run the Agent installer job on the left and click the right arrow to move your selection to the list on the right. Select the Execute job now option to run the Job immediately after the exiting the unified agent installer. Click Next.
20	Click Finish.
21	The RSCD agents are successfully installed on the target servers.

How to complete the install for a production environment

The unified product installer installs the console and the PXE/TFTP server on the default application server node to provide you with a ready-to-use test environment. However, for high-performance production environments, BMC recommends that you install and use additional instances of the console and the PXE/TFTP server on separate machines.

The individual component installers required for installing the console and the PXE/TFTP manually can be found at the following locations in the BBSA87-WIN64 folder. If you are installing either of the components on Linux operating systems you need to download the BBSA87-LIN64.zip package from EPD and extract the required individual component installers for Linux from that package.

Operating System	Component	Path	Installer file name
Windows	Console	\BBSA87-WIN64\files\installers\rcp	BBSACONSOLE87-WIN64
Windows	PXE/TFTP	\BBSA87-WIN64\files\installers\pxe_64	PXE87-WIN32 Note: Although you have different installers for 32-bit and 64-bit Windows for most components, for installing a a PXE/TFTP server you only have a 32-bit installer that you must use in both cases.
Linux	Console	\BBSA87-LIN64\files\installers\rcp	BBSACONSOLE87-WIN64
Linux	PXE/TFTP	\BBSA87-LIN64\files\installers\appserver_64	BBSA87-LIN64.sh

In this walkthrough we will install additional instances of the console and the PXE/TFTP on Windows servers.

Manually installing an additional instance of the console

Step

Example screen

1

Navigate to the directory containing installation files and run the installation program for the console. Different installers are provided for 32-bit and 64-bit Windows.

In this example, we are running the BBSACONSOLE87-WIN64 file on the Windows machine on which you plan to install the console.

Select a language to use for the installation and click OK.

The installer extracts the installation files, and the Introduction window opens.

2

Ensure that you have closed all applications before you proceed.

Click Next.

The Review License Agreement window opens.

3

Read the End User License Agreement (EULA) and select I agree to the terms of the license agreement if you wish to proceed.

Click Next.

The Directory Selection window opens.

4

The default installation location for the console is C:\Program Files\BMC Software\BladeLogic. Click Next to use the default location.

Alternatively, you can click Browse to change the installation location.

5

A window opens in which you can select components to install. By default, all components are selected.

The Network Shell is automatically installed when you install the console.

Note: If you clear the BMC Server Automation Console Upgrade Service check box, the BMC Server Automation Console Upgrade Service is not installed. This service is required for automatically upgrading the BMC Server Automation Console when you upgrade the Application Server.

Click Next.

6

The window displays your selections.

Click Install.

The window displays installation progress, then displays a message when installation is complete.

The console and Network Shell are installed on your machine.

7

In case you encountered any errors while installing you can click View Log to view a detailed report of the installation.

Tip: BMC recommends that you save a copy of the log, before you contact technical support for further assistance. You can also find more information about resolving common issues in Troubleshooting the unified product installer.

If all operations are completed successfully, click Done to exit the wizard.

8

Start the console.

To configure the console so that it connects to the default Application Server, click Options.

9

Click on the Authentication Profiles tab and click Add.

BSA clients use authentication profiles to facilitate single sign-on feature. You must create an Authentication profile before you start using the Console. For more information about why we use Authentication Profiles, see System capabilities related to security.

10

Enter the following information.

Assign a name to the authentication profile. For example, you could assign a name such as QATeam or DevTeam.
Enter the name or IP address (IPv4 or IPv6) of the default Application Server to which the client should connect.
Enter an Authentication Port number to which the client should connect. The same port is used for all BMC Server Automation authentication mechanisms. The default Port is 9840. For more information about Console ports, see BMC Server Automation ports.
Select any one authentication mechanism for the authentication profile:
- Secure Remote Password.
- AD/Kerberos Single Sign-on.
- Domain Authentication.
- LDAP.
- RSA SecurID Authentication.
- Public Key Infrastructure Authentication.
In this walkthrough we will use the Secure Remote Password mechanism. For information about implementing the other authentication mechanisms, see Implementing authentication.
Click OK.

11

You can now log on the the Console using the BLAdmin user that is created while installing the default Application Server node, see step 10.

The quick start page is the first page that is displayed once you log on the the BSA Console. It introduces you to the main use cases of BMC Server Automation and allows you to execute them from a centralized UI immediately after installing the BSA set up. For information about using the quick start page, see Quick start page.

For general information about the UI of the BSA Console, see Navigating the interface.

Manually installing an additional instance of the PXE/TFTP server

	Step	Example screen
1	Install the remote PXE/TFTP server Navigate to the directory containing installation files. Run the PXE86-WIN32 installer file on the Windows machine you plan to install the PXE/TFT server. Click Run. Select the language in which you want to run the installer and click Next.
2	The PXE/TFTP installation wizard introduces you to the installation process. Click Next.
3	Read the End User License Agreement (EULA) and click Yes to proceed. The Customer Information window opens.
4	Enter your name and the name of your organization, and then click Next. The Choose Destination Location window opens.
5	The default installation location for the PXE is C:\Program Files\BMC Software\BladeLogic\PXE. Alternatively, you can click Browse to change the installation location. Click Next to use the default location. The Network Configuration window opens.
6	Confirm that the host name and IP address of the computer on which you are installing the PXE server are correct.
7	Specify where the DHCP is located. If a DHCP server is running on: The computer on which you are installing the PXE server, select Locally (On this server). Another server or network device, select Externally (On another server). If the DHCP server is located on another host computer, the installation program automatically configures this server to function as a DHCP proxy. Note: You must configure the DHCP server differently, depending on whether it is installed on the same computer as the PXE server. For more information on configuring the DHCP server, see Configuring a DHCP server on Windows and Configuring a DHCP server on Linux. BMC recommends that you install the PXE server and the DHCP server on different host computers. Click Next. The TFTP Root window opens.
8	Do one of the following: Accept the default TFTP root directory, which is C:\Program Files\BMC Software\BladeLogic\PXE\tftproot. Choose another directory, click Browse. The TFTP server must reside on the same server as the PXE server. The TFTP server downloads the boot image during the provisioning process. The TFTP root directory is the location from which the files are read. Click Next. The Selected Components window opens.
	Review the current settings to confirm that you have specified the correct installation configuration, and then click Next.
9	A progress bar indicates the progress of the installation until the Post-Configuration Options window opens. The PXE/TFTP server is installed.
10	You can configure the PXE server as part of the installation by selecting the Configure the PXE server option and clicking Next. (See Configuring the PXE and TFTP servers for more information about this option.) Alternatively, you can configure the PXE/TFTP server at a later time by using the PXE/TFTP Server configuration tool.
11	Click Finish to exit the wizard.

Manually installing an agent on the PXE/TFTP server

For successful provisioning, the RSCD agent must be installed on the same host computer as the PXE server. You can install the agent before or after you install the PXE server.

	Step	Example screen
1	Extract the BBSA87-RSCDAgents.zip file that you downloaded from the EPD website to obtain the rscd folder. Different installers are provided for 32-bit and 64-bit Windows. (Installation program names follow the convention: RSCDversion-platform.) Navigate to the windows_64 folder, which is inside the rscd folder, and run the RSCD87-WIN64 installer file. Note: if you have installed the PXE/TFTP server on a Linux machine, you need to navigate to the appropriate Linux RSCD installer file in the rscd folder. Click Run.
2	Select the Typical option for installation, to use the default installation location for the RSCD agent, log files, security preferences, and logging. The Custom installation is used when you want to change the default settings. Click Next.
3	Click Install to begin the RSCD agent installation.
4	You can select the Show the Windows Installer log option to view a detailed report of the installation process. Click Finish to exit the wizard.

Wrapping it up

Congratulations! You have successfully set up a small BSA environment.

Where to go from here

During installation, default security settings are applied to the Application Server and file server. BMC recommends that you adjust the security level on the Application Server host computer and the file server host computer after completing the installation. For more information, see Security planning.
If you wish to manually install additional components to your environment, see Installing individual components.
To add servers to your new environment, see Walkthrough: Adding a Windows managed server and Walkthrough: Adding multiple target servers to the environment.

Page tree