Walkthrough: Adding multiple target servers to the environment

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)

Name
host1
host2
host3

Name,Customer
host1,CustomerA
host2,CustomerB
host3,CustomerC

Name,Customer
host1,"Customer A"
host2,"Customer B"
host3,"Customer C"

Log on to the BSA Console.

1. Start the BSA Console.
2. Log on to the Console using the BLAdmin username and password that you created during installation.
3. 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.
4. Click Connect.

The quick start page (BMC Welcome Page) appears.

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.

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. 

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.

Provide a prefix that is attached to the name of all objects that unified agent installer creates.

Click Next.

Perform the following steps:

1. Select the platforms on which agents can be installed.
2. Specify the depot folder where agent bundles are stored.
3. 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.

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.

1. 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.
2. Specify the SSH port number that is used by the SSH service running on the remote host. The default port is 22.
3. 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.
    
4. 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. 

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.

1. 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.
2. PsExec server — Identify a live Windows server where PsExec is installed. Multiple remote host authentication definitions can use the same PsExec server.
3. Click OK.
4. Click Next.
   
   

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.

Click Add Property Condition. A window opens.

1. 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.
2. In the next drop-down box to the right, select equals.
3. Use the next field to the right to specify the name of the target that we want to set this condition for, 
4. Click OK. The Rule Definition panel shows the condition. Click Next.

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.

Create a similar rule for clm-pun-016803, but this time using the Windows remote host authentication that we created.

Click Next.

1. 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.
2. Specify the folder to store the Agent Installer Job that is created by the unified agent installer.
3. Click Next.

1. Specify the operating system of the servers you want to select. To display servers running any operating system, select All.
2. 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.
3. Select the Execute job now option to run the Job immediately after the exiting the unified agent installer.
4. Click Next.