Walkthrough: Adding multiple target servers to the environment
This topic walks you through the process of adding target servers to your TrueSight Server Automation environment and installing RSCD agents on them using the unified agent installer.
This topic includes the following sections:
This topic is intended for system administrators preparing to add target servers to the TrueSight Server Automation environment after successfully setting up the default application server node. We will add target servers in the following two phases:
- Enrolling multiple target servers to the TrueSight Server Automation environment using the Import Servers wizard
- Installing RSCD agents on the target servers using the unified agent installer
What is the Import Servers wizard?
The Import Servers wizard allows you to add multiple servers to a server hierarchy by specifying a text file that contains a list of server names and properties assigned to each server. You can import servers to the Servers node (the top node in the Servers folder) or a server group. When you import servers to the Servers node, the system adds those servers to its internal list of servers being managed.
What is the unified agent installer?
Unified agent installer performs the tasks necessary to install agents on servers. The unified agent installer is a wizard that steps you through the entire process needed to install agents on multiple agentless devices. The unified agent installer creates the following objects, which are all necessary to install agents:
- Agent bundle
- Remote host authentication (for Windows targets, non-Windows targets, or both)
- Remote host authentication rules
- Agent Installer Job
What does this walkthrough show?
In this walkthrough, we will use the quick start page to add the following two servers into the TrueSight Server Automation environment:
- clm-pun-016803 – Windows (64 bit)
- clm-pun-016809 – Linux (64 bit)
What do I need to do before I get started?
Perform the following prerequisite steps before executing this walkthrough:
Install and set up an Application Server, console, database and file server in your TrueSight Server Automation environment. If you are using the unified product installer to install TrueSight Server Automation, you must install the default Application Server node successfully.
If you want the unified agent installer to automatically install the RSCD agent on your Windows target, you need to download the Microsoft Sysinternals Suite from the Microsoft tech support site and copy the PsExec file to the %PATH% variable (typically C:\Windows\System32\) on any Windows machine that you plan to use as a PsExec server.
How to add target servers and install agents
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:
Save the text file (say Servers.txt) at any location in the default Application Server node (for example, C:\Program Files\BMC Software\BladeLogic\appserver).
For this walkthrough we will be adding two servers to the TrueSight Server Automation environment (without properties).
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:
The following example shows how to set the Customer property for each server:
If you need to include spaces in a property value, you must enclose the property value in double quotes:
Log on to the Console.
The quick start page (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.
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.|
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.
Perform the following steps:
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 Addto open the Add Remote Host Authentication (non-Windows) window.|
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.
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.
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.
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.
|15||Create property conditions to identify the two target servers we want to install the agents on.|
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.
Create a similar rule for clm-pun-016803, but this time using the Windows remote host authentication that we created.
The RSCD agents are successfully installed on the target servers.
To verify the successful installation of an RSCD agent on a target server, you can execute a custom command that provides you with agent information. Perform the following steps:
Wrapping it up
Congratulations! You have successfully added your target servers to your TrueSight Server Automation environment.
Where to go from here
For more information about the various tools, processes, and UIs that an administrator uses to manage the TrueSight Server Automation environment, see Administering.
You can also reference the Managing servers section, for additional server management tasks.