Bulk Agent Installer

BMC BladeLogic Bulk RSCD Agent Installer 7.5.
00
User Guide
February 2009
www.bmc.com
Contacting BMC Software
You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information
about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada
Address BMC SOFTWARE INC Telephone 713 918 8800 or Fax 713 918 8000
2101 CITYWEST BLVD 800 841 2031
HOUSTON TX 77042-2827
USA
Outside United States and Canada
Telephone (01) 713 918 8800 Fax (01) 713 918 8000
If you have comments or suggestions about this documentation, contact Information Design and Development by email at
doc_feedback@bmc.com.
© Copyright 2007-2009 BladeLogic, Inc.

BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent
and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and
logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the
property of their respective owners.
UNIX is the registered trademark of The Open Group in the US and other countries.
Linux is a registered trademark of Linus Torvalds.
Solaris and Java are registered trademarks of Sun Microsystems, Inc. in the US and other countries.
BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is
subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted
rights notices included in this documentation.
Restricted Rights Legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF
THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to
restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and
DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101 CityWest Blvd., Houston, TX
77042-2827, USA. Any contract notices should be sent to this address.
Customer Support
You can obtain technical support by using the Support page on the BMC Software website or by contacting Customer
Support by telephone or email. To expedite your inquiry, please see “Before Contacting BMC Software.”
Support Website
You can obtain technical support from BMC Software 24 hours a day, 7 days a week at
http://www.bmc.com/support_home. From this website, you can:
• Read overviews about support services and programs that BMC Software offers.
• Find the most current information about BMC Software products.
• Search a database for problems similar to yours and possible solutions.
• Order or download product documentation.
• Report a problem or ask a question.
• Subscribe to receive email notices when new product versions are released.
• Find worldwide BMC Software support center locations and contact information, including email addresses, fax
numbers, and telephone numbers.
Support by Telephone or Email

In the United States and Canada, if you need technical support and do not have access to the Web, call 800 537 1813 or
send an email message to customer_support@bmc.com. (In the Subject line, enter SupID:<yourSupportContractID>, such
as SupID:12345.) Outside the United States and Canada, contact your local support center for assistance.
Before Contacting BMC Software

Have the following information available so that Customer Support can begin working on your issue immediately:
• Product information
— Product name
— Product version (release number)
— License number and password (trial or permanent)
• Operating system and environment information
— Machine type
— Operating system type, version, and service pack
— System hardware configuration
— Serial numbers
— Related software (database, application, and communication) including type, version, and service pack or
maintenance level
• Sequence of events leading to the problem
• Commands and options that you used
• Messages received (and the time and date that you received them)
— Product error messages
— Messages from the operating system, such as file system full
— Messages from related software
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Procedural Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
System Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Path Separators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installing and Uninstalling the Bulk RSCD Agent Installer . . . . . . . 10
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Network Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
PsExec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Nmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
WinPcap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Supported Copiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Supported Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Agent Installer Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Files for Silent Agent Installs or Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . 13
Upgrading the Bulk RSCD Agent Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Upgrading the Bulk RSCD Agent Installer on Windows . . . . . . . . . . . . . . . 17
Upgrading the Bulk RSCD Agent Installer on UNIX . . . . . . . . . . . . . . . . . . 17
Installing and Uninstalling the Bulk RSCD Agent Installer on Windows . . . . . . 18
Installing on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Uninstalling on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Installing and Uninstalling the Bulk RSCD Agent Installer on Solaris and Linux 21
Installing on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Uninstalling on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Modifying Properties in the bulkinstaller.properties File . . . . . . . . . . . . . . . . . . 24
Updating the Operating System List in the bi_platform_config.xml File . . . . . . 27
Property of BladeLogic, Inc. BMC BladeLogic Bulk RSCD Agent Installer User Guide
Strictly confidential and proprietary
5
Running script.sh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
bi_platform_config.xml Syntax Example . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Bulk RSCD Agent Installer Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Starting the Bulk RSCD Agent Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Using the Bulk RSCD Agent Installer Console . . . . . . . . . . . . . . . . . . . . . . . . . 32
Refreshing the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Minimizing and Maximizing Console Panes . . . . . . . . . . . . . . . . . . . . . . . . 33
Saving a Bulk RSCD Agent Installer Session . . . . . . . . . . . . . . . . . . . . . . . . . 35
Opening a Saved Bulk RSCD Agent Installer Session . . . . . . . . . . . . . . . . . . . 35
Working with Bulk RSCD Agent Installer Job Items . . . . . . . . . . . . . 37
Specifying Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Creating a Server Job Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Importing Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Specifying Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Specifying RSCD Agent Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Specifying RSC Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Specifying Copiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Specifying Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Discovering Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Modifying Job Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Deleting Job Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Enrolling Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Creating a CSV File for Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Working with Bulk RSCD Agent Installer Jobs . . . . . . . . . . . . . . . . . 56
Creating Bulk RSCD Agent Installer Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Creating Job Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Adding Job Items to a Job to Create a Job Definition . . . . . . . . . . . . . . . . 59
Removing Job Items from a Job Definition . . . . . . . . . . . . . . . . . . . . . . . . . 60
Running Bulk RSCD Agent Installer Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Viewing Job Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Renaming Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6
Deleting Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Licensing RSCD Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Uninstalling RSCD Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Introduction
To manage data center automation using BMC BladeLogic’s Configuration Manager and
Network Shell products, you must have a Remote System Call Daemon (RSCD) agent
installed and running on each remote server that BMC BladeLogic accesses. RSCD agents
are software programs that listen for and execute instructions sent to the servers. BMC
BladeLogic products use the agents to manage servers.
BMC BladeLogic’s Bulk RSCD Agent Installer streamlines the agent installation process by
enabling you to install or upgrade RSCD agents on multiple servers simultaneously.
This guide describes how to install and use the Bulk RSCD Agent Installer application.
Intended Audience
This document is intended for system administrators who manage networks of remote
servers.
Documentation Conventions
Procedural Descriptions
All step-by-step procedural descriptions are flagged with a heading in the left margin that
says Procedure. Within a procedure, bold text highlights actions that you should take. For
example, a procedural step might read, “From the File menu, select Add.”
If a procedure requires you to select a sub-option from a menu option, the description
includes a > to indicate you are choosing a sub-option. For example, a description might read
“select Main Option > Sub-option” rather than saying “select Main Option and then select
Sub-option.”
System Text
Monospace, serif fonts depict text that a user might enter at the command line or text that a
system generates in response to user input. Monospace fonts also depict file system paths.
The following is an example of system text:
ERROR: You must be "root" for pkgadd to execute properly.
Introduction 8
Path Separators
When describing paths, this guide uses UNIX-style path separators (forward slashes) except
in situations where Windows-style path separators (backslashes) are specifically required.
Icons
This guide sometimes refers to icons that appear in the console. The following list shows and
describes all icons mentioned in this guide.
Name Icon Description
Add Adds an item to a list of similar items.
Add All Job Adds all job items in the selected job item group to the
Items corresponding item group in the selected job. Used when
creating a job description.
Add Job Item Adds the selected job item(s) to the corresponding item group
in a selected job. Used when creating a job description.
Cancel Indicates a failed process, such as a component that did not

validate or a job that did not run successfully, or cancels an
action or task.
Check for BMC Performs a search; in this case, locates the RSCD agent
BladeLogic installed on the selected server.
Agent or Search
Delete Deletes the selected item.
Discover Servers Locates servers that are running on the specified network.
You can save the results to the Imported Servers job item
group.
Enroll Servers or In online mode, enrolls the servers with the application
Make CSV File server. In offline mode, adds the servers to a text file using a
to Export CSV format.
Execute Executes an action, such as running a job or saving the results

of server discovery.
Import Servers Imports the servers that are listed in a comma-separated value
format (CSV) file into the current Bulk RSCD Agent Installer
session.
License Agent Initiates the process of obtaining a permanent license for the
selected RSCD agent.
Load Saved Opens a session that you previously created and saved.
Session
Introduction 9
Name Icon Description
New Item Opens a dialog, which allows you to define additional job
items such as new servers or passwords.
Refresh Refreshes information in the current display, such as the Bulk

RSCD Agent Installer console.
Remove All Job Removes all job item (s) from the selected item group in a job
Items (removing it from the job description).
Remove Job Removes the selected job item (s) from a job (removing it
Item from the job description).
Save Saves the current state of the object that you are working on.
This could be the settings for a job item, such as a server or
password, or the current Bulk RSCD Agent Installer session.
Related Documentation
Available
Title Description
Formats
BMC BladeLogic Users Documents the functionality of Configuration PDF and HTML
Guide Manager and Provisioning Manager.
BMC BladeLogic Explains how to install all the components of PDF

Installation Guide the BMC BladeLogic system on all supported
platforms.
BMC BladeLogic Explains how to perform all the tasks necessary PDF
Administration Guide to make the components of a BMC BladeLogic
system function together smoothly.
BMC Service Automation Explains how to use and administer the BMC PDF and HTML
Reporting and Analytics Service Automation Reporting and Analytics
User Guide module.
BMC Service Automation Documents how to install theBMC Service PDF

Reporting and Analytics Automation Reporting and Analytics module on
Installation Guide all supported platforms.
BMC BladeLogic Provides a complete description of all Network PDF and man
Network Shell Command Shell commands and utilities. pages (English
Reference only)
BLCLI Help Documents how to use the BMC BladeLogic HTML (English
Command Line Interface. only)
Installing and Uninstalling the Bulk RSCD
Agent Installer
This section provides the system requirements for using the BMC BladeLogic Bulk RSCD
Agent Installer, describes how to install and uninstall the product, and how to modify
properties. It includes the following topics:
System Requirements
Upgrading the Bulk RSCD Agent Installer
Installing and Uninstalling the Bulk RSCD Agent Installer on Windows
Installing and Uninstalling the Bulk RSCD Agent Installer on Solaris and Linux
Modifying Properties in the bulkinstaller.properties File
Updating the Operating System List in the bi_platform_config.xml File
System Requirements
The system requirements for installing and using the Bulk RSCD Agent Installer are the
same as those required to install and use the BMC BladeLogic Configuration Manager. For a
list of the system requirements, see the BMC BladeLogic Installation Guide.
This section details the additional requirements and supported system information for the
Bulk RSCD Agent Installer. For details, refer to the following topics:
Supported Operating Systems
Network Shell
PsExec
Nmap
WinPcap
Supported Copiers
Supported Installers
Agent Installer Packages
Files for Silent Agent Installs or Upgrades.
Note: In addition to the requirements described in the BMC BladeLogic

Installation Guide, if you will be using the Bulk RSCD Agent Installer to run jobs
that include more than 50 servers, you need 2 GB of RAM and at least 20 MB of
free disk space on the client machine on which the Bulk RSCD Agent Installer is
installed.
Installing and Uninstalling the Bulk RSCD Agent Installer 11
Supported Operating Systems

You can install and run the Bulk RSCD Agent Installer on the same operating systems as
those supported by the Configuration Manager and Provisioning Manager consoles.
You can install RSCD agents on target servers running a full range of 32-bit and 64-bit
operating systems.
For a full list of the supported platforms, see the BMC BladeLogic Installation Guide.
Network Shell
You must have a BMC BladeLogic Network Shell client installed on the server or
workstation on which you will be installing the Bulk RSCD Agent Installer.
For details about installing the BMC BladeLogic Network Shell, see the BMC BladeLogic
Installation Guide.
During the Bulk RSCD Agent Installer installation, you are prompted for the Network Shell
directory and the Network Shell executable path is added to the bulkinstaller.properties file.
If you change Network Shell’s location, be sure to update the entry in the
bulkinstaller.properties file (see Modifying Properties in the bulkinstaller.properties File for
details).
PsExec
Windows remote installations of the Bulk RSCD Agent Installer use PsExec. Install PsExec
on the server or workstation on which you will be installing the Bulk RSCD Agent Installer.
You can download PsExec from

http://www.microsoft.com/technet/sysinternals/Utilities/PsTools.mspx.
During the Bulk RSCD Agent Installer installation, you are prompted for the PsExec
directory, and the PsExec executable path is added to the bulkinstaller.properties file. If you
change PsExec’s location, be sure to update the entry in the bulkinstaller.properties file (see
Modifying Properties in the bulkinstaller.properties File for details).
Nmap
The Bulk RSCD Agent Installer uses Nmap for server discovery. Install Nmap on the server
or workstation on which you will be installing the Bulk RSCD Agent Installer.
You can download Nmap from http://insecure.org/nmap/.
During the Bulk RSCD Agent Installer installation, you are prompted for the Nmap
directory, and the Nmap executable path is added to the bulkinstaller.properties file. If you
change Nmap’s location, be sure to update the entry in the bulkinstaller.properties file (see
Modifying Properties in the bulkinstaller.properties File for details).
Note: To use Nmap on Windows installations, you must also install WinPcap. See
WinPcap.
It is possible to use an alternative tool to Nmap if it provides the same output to the Bulk
RSCD Agent Installer as Nmap provides.
WinPcap
If you are installing the Bulk RSCD Agent Installer on a machine running Windows, you
must install WinPcap in addition to Nmap. Install WinPcap on the same server or
workstation on which you will be installing the Bulk RSCD Agent Installer.
You can download WinPcap from http://www.winpcap.org/.
Supported Copiers
You can use the following copy mechanisms to push the RSCD agent and its related files to
the target servers:
• SCP (secure copy)
• FTP
• SMB (Windows local copy)
Supported Installers
You can use the following installation mechanisms to connect to the target servers in order to
run an agent installer job on those servers:
• SSH
• SSH using Sudo
• TELNET (Windows or UNIX®)
• TELNET using Sudo
• PsExec (Windows local installer)
Note: Attempting to install an agent on a Windows target from a machine running a

UNIX-style operating system might fail, because TELNET and SSH are not
generally enabled on Windows systems and PsExec only works for Windows to
Windows installations. To ensure successful agent installations on Windows
targets, install them from a Windows machine.
Agent Installer Packages

When you set up the agent install or upgrade job you must specify an agent installer file to be
copied to each target server on which you will install or upgrade agents. When the job runs,
the agent installer file is copied to the target servers.
Install this file on the server on which you install the Bulk RSCD Agent Installer. You can
download agent installer files from the Support area of the BMC BladeLogic web site
http://www.bladelogic.com/support.jsp.
Files for Silent Agent Installs or Upgrades

All agent installations and upgrades on Windows systems require a response file that you
create by installing or upgrading an agent on a server and recording your responses to the
installation program’s prompts. Similarly, installations or upgrades on machines running
UNIX-style operating systems require a file that defines variables that control how a silent
install or upgrade behaves.
Copy the file, or files, if you are using the Bulk RSCD Agent Installer to install agents on
Windows and UNIX, onto the server on which you install the Bulk RSCD Agent Installer.
For information about creating the files for Windows and UNIX systems, see the following:
Creating a Response File for Windows Agents
Creating a File of UNIX Installation Defaults
Creating a Response File for Windows Agents

Use this procedure to record your responses to prompts from the installation program. Your
responses are stored in a response file.
Note: If the Microsoft XML (MSXML) 2.5 or later parser is not installed on a
server where you are installing the RSCD agent, a warning displays during the
installation process. MSXML is installed by default on Windows 2003 and XP
machines but not on Windows 2000. For BladeLogic’s patch analysis functionality
to be operable, MSXML must be installed. When creating a response file for
Windows agents, note the type of Windows operating system. If necessary, include
an appropriate response for the MSXML warning. When responding to the
warning, you can continue with the installation, but patch analysis will not be
functional on that server until MSXML 2.5 or later is installed.
Procedure 1 Copy rscd<version>.exe (the RSCD agent installation program) to

<WINDIR>\Temp, where <WINDIR> is typically C:\winnt or C:\Windows.
2 From the command line, connect to <WINDIR>\Temp.
3 From the command line, enter

rscd<version> –a –r –f1<WINDIR>\Temp\version-install_
type.iss
where version-install_type.iss is the name of response file you are creating
(for example, specify 7.4.1-install.iss as the name of the response file for initial installs
of 7.4.1 or 7.4.1-upgrade for upgrades to 7.4.1 from earlier versions of the agent).
The installation program for the RSCD agent opens. Use the program to perform an
initial install or an upgrade of the RSCD agent, selecting the options that are appropriate
for your site.
Creating a File of UNIX Installation Defaults
Use this procedure to create a file that defines variables that control how a silent installation
on UNIX behaves. To alter any of the default steps in a silent installation, include an entry in
the file that sets a variable for that step in the installation. Then include another line that
exports the variable. For example, a file of installation defaults might appear as follows:
NSH_INSTALL_SKEL=y
export NSH_INSTALL_SKEL
COMPONENT_CHECKED=1
export COMPONENT_CHECKED
Procedure 1 Using any server, create a text file called nsh-install-defaults in the /tmp
directory. The file must belong to root.
2 Create an entry in the file that sets a variable, such as INSTALL_DIR=
/export/home/nsh. The following table describes how to set each possible
variable:
Variable Explanation
INSTALL_DIR Setting this allows you to choose an installation directory

other than the default installation directory of /usr/nsh.
COMPONENT_CHECKED By default, running a silent installation installs all possible

[1-6] components in the installation. You can override that default
by setting the COMPONENT_CHECKED value. The
components you install can be any combination of numbers,
such as COMPONENT_CHECKED=12456. The numbers
have the following meanings:
1 - RSCD Agent
2 - Application Server
3 - Provisioning Server
4 - Network Shell
5 - Configuration Manager Console
6 - Provisioning Manager Console
When using the file with the Bulk RSCD Agent Installer, set
the value to 1.
IS_SECURE_AGENT_LOGS Setting this variable to 1 enables secure agent logging.

When secure agent logging is enabled for an agent, agent
logs are periodically rolled and digitally signed as they are
rolled.
IS_KEYSTROKE_LOGS Setting this variable to 1 enables keystroke (nexec) logging

on an agent. When keystroke logging is enabled on an agent,
remote commands run against the agent using nexec are
captured and logged in an encrypted manner in keystroke
logs. These logs are also periodically rolled and digitally
signed as they are rolled.
RND_CHOICE BladeLogic uses random data to encrypt communication

securely. If a server on which you are performing a silent
installation does not include a hardware device for
generating random numbers, the silent installation by default
installs the the Pseudo Random Number Generator Daemon
(prngd). You can use this variable to override that choice.
Acceptable values are:
1 - prngd (default)
2 - bl_gen_rand (creates a seed file for generating
random numbers)
NSH_ROOT_HOST Set this value to identify a client on which users are granted
root privileges for this server. This option sets the root=
flag in the exports configuration file. By default no clients
are specified.
NSH_USER_FROM and NSH_ Set these values to configure a default user mapping in the
USER_TO users.local file. By default no users are mapped. The
values set with this variable create an entry in the
users.local file that says:
NSH_USER_FROM rw,map=NSH_USER_TO
For example, by defining values for these variables, you
could create an entry in users.local like the following:
betty rw,map=root
NSH_INSTALL_SKEL By default a silent installation does not include the .nsh

/etc/skel files. Set this variable to yes to install those
files.
DEFAULT_WEBBROWSER By default the silent installation tries to find a default web

browser by searching for Netscape and Mozilla in a few
specific locations. Use this variable to identify the location
of a default web browser.
3 Create the next entry in the file to export the variable you just created.
For example, if you created a variable in the previous step that said RND_CHOICE=1,
create the next entry to say export RND_CHOICE.
4 Repeat the previous two steps for every step in the silent installation that you want to
modify.
5 Save /tmp/nsh-install-defaults.
Upgrading the Bulk RSCD Agent Installer

This section describes how to upgrade the Bulk RSCD Agent Installer.
Before beginning the upgrade, be sure to back up all of your Bulk RSCD Agent Installer
files.
Note: The following user-configurable files are not replaced during the upgrade:
bulkinstaller.properties, bi_platform_config.xml, log4j.properties, and script.sh.
Refer to the upgrade instructions for your system type:

Upgrading the Bulk RSCD Agent Installer on Windows
Upgrading the Bulk RSCD Agent Installer on UNIX
Upgrading the Bulk RSCD Agent Installer on Windows

Use the following procedure to upgrade the Bulk RSCD Agent Installer.
Procedure 1 Navigate to the directory containing the installation files and invoke the Bulk RSCD
Agent Installer installation program.
The installer extracts the files needed for installation and displays the Setup Type
window.
2 Select Upgrade and click Next.
A progress bar indicates the progress of the installation. When the installation is
complete, the Upgrade Complete window appears.
3 Click Finish to complete the upgrade.
See Starting the Bulk RSCD Agent Installer for instructions on starting the Bulk RSCD
Agent Installer.
Upgrading the Bulk RSCD Agent Installer on UNIX

Use the following procedure to upgrade the Bulk RSCD Agent Installer.
Procedure 1 Log in as root.
2 Navigate to the directory containing upgrade files and invoke the upgrade script for the
Bulk RSCD Agent Installer.
A message displays informing you that a previous installation already exists and prompts
you to confirm that you want to continue.
3 Type Y to confirm the Bulk RSCD Agent Installer upgrade.
The Installer Language Selection message displays and provides you with the following
choices:
[1] English
[2] Exit the Installer
4 Type 1 for English.
A welcome message appears, followed by a message informing you that you must agree
to the terms specified by the software authors.
5 Press Enter to continue.
The first screen of the License Agreement displays.
6 Press Enter to scroll through each screen of the agreement.
At the end of the agreement, you are prompted to accept the terms of the agreement.
7 Type Y to accept the license agreement terms.
The Component Upgrade message instructs you to confirm the Bulk RSCD Agent
Installer upgrade.
8 Type Y to confirm the Bulk RSCD Agent Installer upgrade.

Several messages appear on the screen as the upgrade continues. A message informs you
when the installation is complete.
Agent Installer.
Installing and Uninstalling the Bulk RSCD Agent Installer on Windows

This section details how to install and uninstall the Bulk RSCD Agent Installer on Windows.
Installing on Windows
Uninstalling on Windows
Installing on Windows
Use the following procedure to install the Bulk RSCD Agent Installer.
Procedure 1 Navigate to the directory containing the installation files and invoke the Bulk RSCD
Agent Installer installation program.
The installer extracts the files needed for installation and displays the Welcome window.
2 Click Next.
The Acknowledgments window opens, providing license information for all third-party
software products included in BMC BladeLogic.
3 Click Next. The License Agreement window opens.
4 To print the license agreement to your default printer, click Print.
5 After reading the license agreement, click Yes if you agree with its terms.
The Customer Information window opens.
6 Enter your name and the name of your organization, and then click Next.
The Choose Destination Location window opens.
7 Specify a directory for your installation using one of the following options:
• Accept the default location (C:\Program Files\BMC BladeLogic\
Bulk RSCD Agent Installer) by clicking Next.
• Select another location by clicking Change. The Choose Folder dialog displays. Use
it to select the installation directory and click OK. Then click Next.
The Ready to Install window opens.
8 Click Install.
A progress bar indicates the progress of the installation. When it is complete, the Nmap
Install Directory window appears.
9 Specify the directory in which Nmap is installed using one of the following options:
• Accept the default location (C:\Program Files\Nmap\) by clicking Next.
• Select another location by clicking Browse. The Choose Folder dialog displays. Use
it to select the Nmap directory and click OK. Then click Next.
If you are installing on a machine running Windows, the PsExec Install Directory
window opens.
10 Specify the directory in which PsExec is installed using one of the following options:
OM\bin\) by clicking Next.
it to select the PsExec directory and click OK. Then click Next.
The NSH Install Directory window opens.
11 Specify the directory in which Network Shell is installed using one of the following
options:
OM\bin\) by clicking Next.
it to select the Network Shell directory and click OK. Then click Next.
The Windows Temporary Directory window opens.
12 Specify a location for the Windows temporary directory. This should be a valid
Windows directory (the full path) that exists on the servers on which you will be
installing the RSCD agent.
To specify the Windows temporary directory, use one of the following options:
• Accept the default location (C:\Temp) by clicking Next.
it to select the Windows temporary directory and click OK. Then click Next.
The temporary directory is used to hold temporary files that are used during RSCD agent
installations on Windows servers.
The Windows Local Temporary Directory window opens.
13 Specify the absolute path value of the SMB/FTP temporary directory (as opposed to the
corresponding relative path value of the SMB/FTP share that you specify in the next
screen) for installing RSCD agent-related files on remote Windows machines.
To specify the absolute path to the SMB/FTP directory, use one of the following options:
it to select the directory and click OK. Then click Next.
The Windows SMB/FTP Shared Temporary Directory window opens.
14 Specify the relative path of the SMB/FTP temporary directory (as opposed to the
corresponding absolute path of the SMB/FTP share that you specified in the last screen)
for installing RSCD agent-related files on remote Windows machines using one of the
following options:
it to select the directory and click OK. Then click Next.
The UNIX Temporary Directory window opens.
15 Specify a location for the UNIX temporary directory using one of the following options:
• Accept the default location (/tmp) by clicking Next.
it to select the UNIX temporary directory and click OK. Then click Next.
16 The InstallShield Wizard Complete window declares that the installation is complete.
17 Click Finish to complete the installation.
Agent Installer.
Uninstalling on Windows
Use the following procedure to uninstall the Bulk RSCD Agent Installer.
Procedure 1 Use one of the following steps to uninstall the Bulk RSCD Agent Installer.
> From the Start menu, select Programs > BMC BladeLogic > Uninstall Bulk
RSCD Agent Installer. In the next screen, choose Remove, and then click Next.
> From the Start menu, select Settings > Control Panel. Double-click Add/Remove
Programs. Select BulkInstaller and click Remove.
2 Click Yes in the Confirm Uninstall dialog.
A progress bar indicates the progress of the installation. When it is complete, the
Uninstall Complete window announces that the uninstall is complete.
3 Click Finish to complete the uninstall.
Installing and Uninstalling the Bulk RSCD Agent Installer on Solaris

and Linux
This section details how to install and uninstall the Bulk RSCD Agent Installer on Solaris™
and Linux® machines.
Note: Attempting to install an agent on a Windows target from a machine

running a UNIX-style operating system might fail, because TELNET and SSH
are not generally enabled on Windows systems and PsExec only works for
Windows to Windows installations. To ensure successful agent installations on
Windows targets, install them from a Windows machine.
Installing on UNIX
Uninstalling on UNIX
Installing on UNIX
Use the following procedure to install the Bulk RSCD Agent Installer.
2 Navigate to the directory containing installation files and invoke the installation script
for the Bulk RSCD Agent Installer.
One of the following responses occurs:
• If Network Shell is already installed on the machine on which you are installing the
Bulk RSCD Agent Installer, a message displays about files being copied to
/usr/nsh/bulkrscdagentinstaller/install_dir and verifying
package checksums.
• If Network Shell is not installed on the machine on which you are installing the Bulk
RSCD Agent Installer, you are prompted to provide the installation directory for the
Type the installation directory and press Enter.
The Installer Language Selection message displays and provides you with the following
choices:
[1] English
[2] Exit the Installer
3 Type 1 for English.
A welcome message appears, followed by a message informing you that you must agree
to the terms specified by the software authors.
4 Press Enter to continue.
The first screen of the License Agreement displays.
5 Press Enter to scroll through each screen of the agreement.

At the end of the agreement, you are prompted to accept the terms of the agreement.
6 Type Y to accept the license agreement terms.
The Select Install Components message displays. It includes the following options:
B - Bulk Installer
9 - Start the installation
A - Select all components
Select component:
7 At the Select component: prompt, type A or B to install the Bulk RSCD Agent
Installer.
The screen message updates to indicate your choice; in the following example, B was
selected:
+ B - Bulk Installer
9 - Start the installation
A - Select all components
Select component:
8 At the Select component: prompt, type 9 to begin the installation.
You are prompted to confirm that you want to continue the installation.
9 Type Y to confirm the Bulk RSCD Agent Installer installation.
The next screen prompts you to enter the Nmap location.
Please enter the path to nmap[]:
10 Type the directory in which nmap is installed and press Enter. The default directory is
/usr/bin/nmap
The next screen prompts you to enter the Network Shell location.
Please enter the path to nsh[]:
11 Type the directory in which Network Shell is installed and press Enter. The default
directory is
/usr/nsh/bin/nsh
The next screen prompts you to provide the web browser location.
Please enter the path to your default web browser. []:
12 Specify the directory in which the web browser is installed and press Enter. For
example,
/usr/bin/<web_browser>
The next screen prompts you to provide a temporary directory for a Windows host.
Please enter the path to a temporary directory for a
Windows host [c:\Temp]:
13 Specify a location for a Windows temporary directory for use on remote Windows
machines and press Enter. The default directory is
c:\Temp
The next screen prompts you to provide a temporary directory for a UNIX host.
Please enter the path to a temporary directory for a UNIX
host [/tmp]:
14 Specify a location for a UNIX temporary directory for use on remote UNIX machines
and press Enter. The default directory is
/tmp
Several install messages appear on the screen as the installation continues. A message
informs you when the installation is complete.
Agent Installer.
Uninstalling on UNIX
Use the following procedure to uninstall the Bulk RSCD Agent Installer.

2 Navigate to the directory where you installed the Bulk RSCD Agent Installer. Typically
this directory is /usr/nsh/bulkrscdagentinstaller.
3 Invoke the installation script by entering the following:
#./Uninstall
A message reminds you that the uninstall removes all files related to the Bulk RSCD
Agent Installer. If you want to save your configuration files, you must do so before
uninstalling the product.
The next message prompts you to confirm that you want to continue uninstalling the
product.
4 Type Y to continue with the uninstall.
Several messages appear on the screen as the uninstall continues. A message informs
you when it is complete.
Modifying Properties in the bulkinstaller.properties File

The bulkinstaller.properties file contains properties associated with the Bulk RSCD Agent
Installer. You can edit the file to modify the default settings. The file is located in the Bulk
RSCD Agent Installer installation directory.
The following table lists the properties included in the bulkinstaller.properties file and
provides descriptions and examples of entries.
Property Name Description
psexecLocation The absolute path of the PsExec binary (for Windows

installations only).
The default setting is
psexecLocation=C:/Program Files/
BMC BladeLogic/OM/bin/psexec.exe
localOS The operating system running on the machine on which you

are installing the Bulk RSCD Agent Installer.
The Windows setting is
localOS=Windows
The UNIX setting is
localOS=UNIX
maxWorkerThreads The number of threads that can be invoked concurrently

within the Bulk RSCD Agent Installer.
maxWorkerThreads=10
windowsTempDir The absolute path of the default temporary directory on the

Windows install target (for storing installation-related files
for the Bulk RSCD Agent Installer and bulk agents). This is
used when a specific temporary directory is not specified for
a server.
windowsTemp=C:/Temp
windowsLocalTempDir The “actual” temporary directory (as opposed to the

SMB/FTP share, for which there is a different property) for
storing agent installation-related files on remote Windows
machines.
windowsLocalTempDir=C:/Temp
windowsRemoteTempDir The absolute path of the temporary SMB/FTP share

directory, including the path, for storing agent
installation-related files on remote Windows machines.
windowsRemoteTempDir=C:/Temp
unixTempDir The absolute path of the default temporary directory on the

UNIX install target (for storing installation-related files for
the Bulk RSCD Agent Installer and bulk agents). This is used
when a specific temporary directory is not specified for a
server.
unixTemp=/tmp
nmapLocation The absolute path of the Nmap binary.

The default Windows setting is
nmapLocation=C:/Program
Files/Nmap/nmap.exe
The default UNIX setting is
nmapLocation=/usr/bin/nmap
nshLocation The absolute path of the Network Shell binary.

The default Windows setting is
nshLocation=C:/Program Files/
BMC BladeLogic/OM/bin/nsh
The default UNIX setting is
nshLocation=/usr/nsh/bin/nsh
jcifs.resolveOrder Specifies the order in which jCIFS will resolve network

names.
jcifs.resolveOrder=DNS,LMHOST,BCAST
AES_support Specifies the AES authentication status.

If set to True, enables aes128, aes 192, and aes1256 ciphers
for SSH if they are available; if unavailable, falls back to
other ciphers. Note that if you set this to True, you must
apply global security files by copying the appropriate
policy-related JAR files to the Java™ installation directory in
the Bulk RSCD Agent Installer directory, as described in
later in this section.
If set to False, SSH authentication does not use AES ciphers.
The default setting is AES_support=false.
If you set AES authentication status to True, use the
following procedure to apply global security files:
1. Set AES_support to True.
2. Backup the current files in the
<Bulk_RSCD_Agent _Installer_directory>/
JRE/lib/security directory.
3. Download Java Cryptography Extension (JCE) Unlimited
Strength Jurisdiction Policy Files 5.0 from
http://java.sun.com/javase/downloads/index_
jdk5.jsp#docs.
4. Unzip the downloaded file and extract the files to the
following location:
<Bulk_RSCD_Agent _Installer_directory>/
JRE/lib/security
The files will include local_policy.jar (Unlimited strength
policy file) and US_export_policy.jar ((Unlimited
strength US export policy file).
If you do not make these changes, you might see an
“Algorithm negotiation fail” error when using the Bulk
RSCD Agent Installer.
Consult the Java documentation for more details about
installing and using global security files.
nmap_params Specifies the parameters for invoking Nmap. Use the string
that represents the Nmap flag you want to use. Consult Nmap
documentation for details.
By default no parameters are included.
sudo_command Specifies the sudo command used with SSH and TELNET
installer mechanisms.
sudo_command=sudo -k;sudo su-;
Updating the Operating System List in the bi_platform_config.xml File

The bi_platform_config.xml file includes a list of all operating systems on which RSCD
agents are supported. When creating job items, several require that you specify the operating
system group associated with the job items by choosing the operating system from a list. The
list of available operating systems comes from the bi_platform_config.xml file.
The current list of operating systems in bi_platform_config.xml is very comprehensive;

however, as additional operating systems are supported in the future, you can modify the file
to add the new operating systems.
The bi_platform_config.xml file is located in the Bulk RSCD Agent Installer installation
directory. This directory also includes a file named script.sh. Before adding an entry to the
bi_platform_config.xml file, run the script.sh file on the target server to get the information
needed for the operating system entry in bi_platform_config.xml.
To create an operating system entry in bi_platform_config.xml, use the following procedure.
Procedure 1 Navigate to the target server (the server on which you will be installing the RSCD
agent).
2 From Network Shell, run script.sh, as shown below:
#nsh bulk_installer_directory/script.sh
where bulk_installer_directory is the directory in which you installed the
Record the information returned by the script. For a description of this information, see
Running script.sh.
3 Navigate to the Bulk RSCD Agent Installer installation directory, open the bi_platform_
config.xml file, and edit it to create a new operating system entry.
To create a new entry, copy and paste an existing entry, and update the entry with the
new operating system information, including the information returned when you ran
script.sh in the file’s scrpString value setting.
For details about modifying bi_platform_config.xml, see bi_platform_config.xml
Syntax Example.
4 Save your changes and close the file.
The next time you display an operating system group list in the Bulk RSCD Agent
Installer console, the new operating system appears in the list.
Running script.sh
The Bulk RSCD Agent Installer installation directory includes a file named script.sh. Before
you add an entry to the bi_platform_config.xml file, run the script.sh file on the target server
(the server on which you will be installing the RSCD agent) to get the information needed
for the operating system entry (specifically the scrpString value setting) in bi_
platform_config.xml.
When you run script.sh as follows:

#nsh bulk_installer_directory/script.sh
it returns the operating system details in the following format:

server1% OS_Name OS_Version Architecture Bit_Mode
as in the following example of the information returned on a Red Hat Enterprise Linux 4
machine:
server1% RedHat_Linux_ES 4 i686 32
In this example
• RedHat_Linux_ES = the operating system name
• 4 = the operating system version
• i686 = the operating system architecture
• 32 = the operating system bit mode
When adding an operating system to the bi_platform_config.xml file, use the returned
information, RedHat_Linux_ES 4 i686 32, for the scrpString value setting.
See bi_platform_config.xml Syntax Example for details.
bi_platform_config.xml Syntax Example

The following example excerpt of the bi_platform_config.xml file includes entries for
Windows 32-bit and RedHat Enterprise Linux 4 operating systems.
- <Platform-Configuration>
- <OSPlatform>
<displayname value=”Windows 32 bit” />
<ostype value=”windows” />
<scrpString value=”32” />
<icon value=”server_windows.gif” />
<installergrpname value=”windows 32 bit” />
<rscgrpname value=”windows” />
- </OSPlatform>
- <OSPlatform>
<displayname value=”REDHAT AS 4.0” />
<ostype value=”unix” />
<scrpString value=”RedHat_Linux_ES 4 i686 32” />
<icon value=”server_linux.gif” />
<installergrpname value=”REDHAT AS 4.0” />
<rscgrpname value=”Linux” />
- </OSPlatform>
- </Platform-Configuration>
An operating system entry in the bi_platform_config.xml file includes the following lines:
• displayname value = the name displayed in the operating system group list for
imported servers job items.
• ostype value = the operating system type. This value is used internally by the Bulk
RSCD Agent Installer.
• scrpString value = the string returned from running script.sh on the target platform.
This string includes operating system information.
See Running script.sh for details.
• icon value = the icon used to represent the operating system type in the Bulk RSCD
Agent Installer console.
• installergrpname value = the name displayed in the operating system group list
for agent package job items.
• rscgrpname value = the name displayed in the supported OS list for RSC files job
items.
For more information about job items, see Working with Bulk RSCD Agent Installer Job
Items.
Getting Started
This chapter details how to get started with the Bulk RSCD Agent Installer. It includes the
following sections:
Bulk RSCD Agent Installer Overview
Starting the Bulk RSCD Agent Installer
Using the Bulk RSCD Agent Installer Console
Saving a Bulk RSCD Agent Installer Session
Opening a Saved Bulk RSCD Agent Installer Session
Bulk RSCD Agent Installer Overview

Use the Bulk RSCD Agent Installer to create agent installation or upgrade jobs that you can
run to install or upgrade agents on multiple targets (servers) at the same time.
Note: Bulk RSCD Agent Installer jobs are different than jobs that you run from the
Configuration Manager console. You run Bulk RSCD Agent Installer jobs from the
Bulk RSCD Agent Installer console.
Before you can run jobs, you have to create the jobs and their definitions. A job definition is
the set of instructions that control how a job runs. You create a job definition using a set of
job items. Job items provide the specifications for installing an agent, such as the server on
which to install the agent, the operating system that runs on the server, and the server
password. Other job items specify the agent installers, copiers, and installation mechanisms
to use for the agent install job.
You can create many jobs with different definitions. You can set up Bulk RSCD Agent
Installer jobs for various types of agent installations and upgrades. For example, you can
define a job for agent installations on servers running Windows, a job for agent installations
on UNIX-style operating systems, or a job for agent installations on servers running
Windows and UNIX operating systems.
For details about starting the Bulk RSCD Agent Installer and its user interface, see the
following topics:
Getting Started 31
When the Bulk RSCD Agent Installer is running, you can

• Use the current session to set up job items and create agent installer jobs.
For details about setting up job items, see Working with Bulk RSCD Agent Installer Job
Items.
For details about creating and running jobs, see Working with Bulk RSCD Agent
Installer Jobs.
• Open a session that you previously created and saved to run existing jobs or to modify
jobs.
See Opening a Saved Bulk RSCD Agent Installer Session for details.
At any time, you can save your work, so that you can use it later. See Saving a Bulk RSCD
Agent Installer Session for details.

You can run the Bulk RSCD Agent Installer in two ways: online mode and offline mode.
Online mode uses the BMC BladeLogic Authentication Service, which is a service dedicated
to validating user identities. You can directly enroll the servers you created in the installer
with your application server. When you enroll servers you can specify that the default access
control list (ACL) be pushed to the target servers. For more details about the BMC
BladeLogic Authentication Service and the ACL, see the BMC BladeLogic Users Guide.
Offline mode runs the Bulk RSCD Agent Installer without user authentication.
Procedure 1 To start the Bulk RSCD Agent Installer, use one of the following methods:
• On Windows, use one of the following methods:
> From the Start menu, choose Programs > BMC BladeLogic > Bulk RSCD
Agent Installer.
> From the Bulk RSCD Agent Installer directory, in a command window type the
following command:
bulkinstaller
• On a UNIX-style system, from the Bulk RSCD Agent Installer directory, in a
command window type the following command:
./bulkinstaller
Getting Started 32
2 The Select Mode dialog opens.
3 Select a mode and click Ok.

If you selected Offline mode, the Bulk RSCD Agent Installer opens and you can begin to
use it. The remaining steps in this procedure do not apply.
If you selected Online mode, the BMC BladeLogic Authentication Service runs. If no
service profiles are defined, the New Profile dialog appears; if a service profile is
defined, the Login dialog appears.
4 Continue the new profile creation or login process using the instructions on getting
started in the BMC BladeLogic Users Guide.

Use the Bulk RSCD Agent Installer console to create and manage Bulk RSCD Agent
Installer jobs.
menu bar
toolbar
job item
groups jobs
job
status
Getting Started 33
The console is divided into three panes.

• The left pane includes the job items that you use to define Bulk RSCD Agent Installer
jobs.
• The upper right pane contains Bulk RSCD Agent Installer jobs.
• The lower right pane displays the status of all jobs run in the current session.
The Bulk RSCD Agent Installer console includes a menu bar and a toolbar. You can initiate
most operations in the Bulk RSCD Agent Installer using the options on these bars or by
selecting an object and right-clicking, which displays a pop-up menu with options
appropriate to your current context.
Text at the bottom of the console displays your online or offline connection status. If you
connected to the Bulk RSCD Agent Installer using online mode, the text includes your
application server connection.
Refreshing the Console

While using the Bulk RSCD Agent Installer, you might occasionally need to refresh the
information displayed in the console. Usually the console automatically refreshes
information, but there are situations in which it is good practice to refresh manually.
Procedure To refresh the Bulk RSCD Agent Installer console, click the Refresh icon (see list of icons).
Minimizing and Maximizing Console Panes

You can maximize any of the three console panes for a better view of its contents. When you
are finished viewing information in the pane, you can minimize the pane.
Getting Started 34
Procedure To maximize a console pane, click the Maximize/Minimize button.
maximize/
minimize
buttons
Procedure To minimize a console pane, click the Maximize/Minimize button.
minimize
button
Getting Started 35
Saving a Bulk RSCD Agent Installer Session

At any time while using the Bulk RSCD Agent Installer, you can save your current session to
an XML file. All job items and jobs in the session will be saved for future use.
Procedure 1 To save your Bulk RSCD Agent Installer session, use any of the following procedures:
• Click the Save Current Session icon in the toolbar (see list of icons).
• Choose File > Save Current Session.
• Exit the Bulk RSCD Agent Installer and choose Yes at the prompt asking if you
want to save the session.
The Choose Save Directory dialog opens.
2 Specify the file name and location for the session using one of the following options:
• Accept the default location for the file, type the file name in the File Name field, and
click Save.
• Navigate to the directory in which you want to store the file, type the file name in the
File Name field, and click Save.
You are prompted whether you want the passwords saved in clear text in the file.
3 Select Yes to include the passwords in the file, or Select No to exclude the passwords
from the file.
The session is saved to the specified file.
Opening a Saved Bulk RSCD Agent Installer Session

You can open a Bulk RSCD Agent Installer session that you previously created and saved.
Procedure 1 Click the Load Saved Session icon in the toolbar (see list of icons) or choose File >
Load Saved Session.
The Load Saved Session dialog appears.
2 Navigate to the file containing the session you want to open, select it, and click Open.
The session, including any existing job items and jobs, opens in the Bulk RSCD Agent
Installer.
After you open the session, you can perform any of the following tasks in the session:
• Run jobs.
• Add, remove, or modify jobs.
• Use the session as a template for another session by saving it with a different file name,
and then opening the newly named session and changing it as needed.
For details on how to run jobs, see Running Bulk RSCD Agent Installer Jobs.
For details about setting up job items, see Working with Bulk RSCD Agent Installer Job
Items.
Getting Started 36
For details about creating and modifying jobs, see Working with Bulk RSCD Agent Installer
Jobs.
For instructions on how to save a session, see Saving a Bulk RSCD Agent Installer Session.
Working with Bulk RSCD Agent Installer Job
Items
Use job items to specify the job definition of a Bulk RSCD Agent Installer job. A job
definition is the set of instructions that control how a job runs. You can create different job
items to create jobs with different definitions. You can also modify job items and change job
definitions as needed to keep up with changes in your environment.
When you begin a new Bulk RSCD Agent Installer session, you need to set up the job items
for your site’s system configurations. This involves creating some job items and selecting
others from an existing list.
Job items appear in the left panel in the Bulk RSCD Agent Installer. The following topics
describe the job items and how to set them up so that they are ready for addition to a job to
create the job definition:
Specifying Servers
Specifying Passwords
Specifying RSCD Agent Packages
Specifying RSC Files
Specifying Copiers
Specifying Installers
The following topics provide more details about working with job items and server job
items:
Discovering Servers
Modifying Job Items
Deleting Job Items
Enrolling Servers
Creating a CSV File for Export
At any time during the process of creating job items, you can save the current Bulk RSCD
Agent Installer session. For details, see Saving a Bulk RSCD Agent Installer Session.
Specifying Servers
A job definition must include server job items. The server job item specifies the target server
(the server on which you want to install the RSCD agent). Create a server job item for each
target server you want to include in the job.
Working with Bulk RSCD Agent Installer Job Items 38
You create server job items in the Imported Servers job item group. There are three ways to
add servers to the Imported Servers job item group:
• Manually add individual servers to the group.
For details about how to manually add servers, see Creating a Server Job Item.
• Import a list of servers from a text file.
Refer to Importing Servers for details.
• Save the servers found during server discovery and they are added to the group.
For details about discovering servers and saving them to the list, see Discovering
Servers.
Creating a Server Job Item

To add an individual server to the Imported Servers job item group, use the following
procedure.
Procedure 1 Click Servers in the left pane to display the Imported Servers group.
2 Select the Imported Servers node, right-click, and choose New Server from the pop-up
menu.
The Server Details window opens.
3 Provide the server details in the following fields. Required fields are marked with an
asterisk (*).
• For Hostname, type a resolvable host name or an IP address.
• For Group, choose the type of operating system running on the target server from
the list.
If you do not specify the operating system, when the job runs, the installer will
attempt to determine the operating system of the target server.
• For Agent Version, use one of the following steps:

> If you are creating an agent install job, do not enter anything in this field.
> If you are creating an agent upgrade job, include the current version of the agent
on the server. To determine the agent version and automatically insert it into the
field, click the Check for BMC BladeLogic Agent icon (see list of icons).
• For UNIX Temp, specify a temporary directory, including the path, for storing
agent installation-related files on remote UNIX machines (if you do not want to use
the default temporary directory).
• For Windows Temp (SMB Share), specify the relative path for the SMB/FTP
temporary directory that is used to upload store agent-related files on remote
Windows machines (if you do not want to use the default temporary directory).
• For Windows Temp, specify the absolute path for the SMB/FTP temporary
directory that is used to upload store agent-related files on remote Windows
machines (if you do not want to use the default temporary directory).
4 Click the Save icon.
The new job item appears in the Imported Servers job item group.
new
Imported
Server job
item
You can add this job item to a Bulk RSCD Agent Installer job. For instructions on how
to add job items to a job, see Adding Job Items to a Job to Create a Job Definition.
Importing Servers
You can import a list of servers from a text file that uses a comma-separated values (CSV)
format. You can create a server import file using one of the following methods:
• Create and edit a text file to include the server list. To create your text file, follow the
formatting instructions in Server Import File Format.
• Using the Bulk RSCD Agent Installer, create a CSV file to export. For details, see
Creating a CSV File for Export.
Importing Servers into the Imported Servers Group

To import a list of servers from a CSV-format text file into the Imported Servers job item
group, use the following procedure.
Procedure 1 Click Servers in the left pane to display the Imported Servers group.
2 Select the Imported Servers node, right-click, and choose Import Servers from the
pop-up menu.
The Open File dialog opens.
3 Browse for the text file, select it, and click Open.
The servers appear in the Imported Servers job item group.
imported
servers
You can now add these job items to a Bulk RSCD Agent Installer job. For instructions
on how to add servers to a job, see Adding Job Items to a Job to Create a Job Definition.
Server Import File Format

Create your server import text file using the following CSV format:
• The first line of the file must contain the column header:
Name
optionally followed by (and separated by a comma) the column header
Group
to specify the server’s operating system group name.
Note: Any group you include in an import file must appear in the Group list
that is available when you double-click on a Server job item and display its
details. Groups that appear in this list have a corresponding entry in the bi_
platform_config.xml file. You can edit this file to add any operating system
group on which you will be installing or upgrading agents. For details, see
Updating the Operating System List in the bi_platform_config.xml File.
• Subsequent lines of the file must contain valid host names for each server you want to
add, followed by the optional, comma-separated operating system group for each server.
Examples:
This first example shows the simplest syntax, which includes the host names of the servers
you want to add:
Name
host1
host2
host3
The following example shows how to include the operating system group for each server:
Name,Group
host1,Windows 32 bit
host2,REDHAT 7
host3,SOLARIS 10
Specifying Passwords
When creating a job definition, you need to provide a password for each target server in the
job definition or you have to specify that users be prompted for the user name and password
for each server when they run the job. To create and set up a Password job item, use the
following procedure.
Procedure 1 Click Passwords in the left pane to display the Passwords group.
2 Select the Passwords node, right-click, and choose New Password from the pop-up
menu.
The Password Details window opens.
3 Provide the password details in the following fields. Required fields are marked with an
asterisk (*). If you choose Prompt as the password type (in the last field), the other fields
are not required.
• For Password Name, type a name to identify this password job item.
• For User Name, type the user name for the target server.
• For Domain, type the Windows domain for the target server (for use with machines
running Windows).
• For Password, type a password for the target server.
• For Confirm, type the server password again.
• For Password Type, choose the type of operating system supported for the
password or choose Prompt to prompt users for the user name and password for each
server in the job when a job is executed.
The new job item appears in the Passwords job item group.
new
Password
job item
You can now add this job item to a Bulk RSCD Agent Installer job. For instructions on
how to add job items to a job, see Adding Job Items to a Job to Create a Job Definition.
Specifying RSCD Agent Packages

A job definition must include an RSCD Agent Package job item. This job item specifies the
agent installers to use for the agent installations. If you have not already copied the agent
installer files to the server on which you installed the Bulk RSCD Agent Installer, you must
do so before running an agent installer job. For more information, see Agent Installer
Packages.
To create and set up an Agent Package job item, use the following procedure.
Procedure 1 Click Agent Packages in the left pane to display the Agent Packages group.
2 Select the Agent Packages node, right-click, and choose New Installer from the pop-up
menu.
The Agent Installer Details window opens.
3 Provide the agent installer details in the following fields. Required fields are marked
with an asterisk (*).
• For RSCD Package Name, type a name to identify this agent installer package job
item.
• For RSCD Package Path, type the full path for the agent installer file or click the
browse button to browse for the file and select it.
• For Silent File Path, type the full path for the silent file or click the browse button to
browse for the file and select it.
You must specify this file for agent installations. For information about this file for
Windows or UNIX systems, see Files for Silent Agent Installs or Upgrades.
• For Silent File Path for Upgrade, type the full path for the silent file (required for
agent upgrades on Windows machines) or click the browse button to browse for the
file and select it.
You must specify this file for agent upgrades. For information about this file for
Windows or UNIX systems, see Files for Silent Agent Installs or Upgrades.
• For Group, choose the type of operating system supported for the agent installer
from the list.
• For Pre Install Script, type the full path for a script that you want to run before the
agent installations or click the browse button to browse for the file and select it.
You can use this script to call scripts that you loaded on the target server (specified
in the Scripts to Upload field).
If you are using batch files for your scripts, see the note below.
• For Post Install Script, type the full path for a script that you want to run after the
agent installations or click the browse button to browse for the file and select it.
You can use this script to call scripts that you loaded on the target server (specified
in the Scripts to Upload field).
• For Scripts to Upload, click the Add icon to browse for the files and select them.
You can call these scripts from a pre-install or post-install script that you specify in
the next fields.
You can remove scripts using the Delete icon.
Note: If you use batch files for your pre- or post-install scripts, you must add
the following line as the first line of the batch file in order for it to run properly:
@echo off

The new job item appears in the Agent Packages job item group.
new Agent
Installer job
item
Specifying RSC Files

Each Bulk RSCD Agent Installer job requires an RSC files job item. You use this job item to
specify the access control configuration files. The configuration files listed in this job item
control how communication occurs between RSCD agents and their clients and control
which clients and users have access to RSCD agents.
For details about what each configuration file does and how to set them up, see the BMC
BladeLogic Administration Guide.
To create and set up an RSC files job item, use the following procedure.
Procedure 1 Click RSC Files in the left pane to display the RSC Files group.
2 Select the RSC Files node, right-click, and choose New RSC Files from the pop-up
menu.
The RCS Files Details window opens.
3 Provide the details for the RSC files in the following fields. Required fields are marked
with an asterisk (*).
• For Name, type a name to identify this RSC files job item.
• For Exports File, type the full path for the exports configuration file that you want
want to install on the target server or click the browse button to browse for the file
and select it.
• For Secure File, type the full path for the secure configuration file that you want
and select it.
• For Users File, type the full path for the users configuration file that you want to
install on the target server or click the browse button to browse for the file and select
it.
• For Users.local File, type the full path for the users.local configuration file that you
and select it.
• For Supported OS, choose the type of operating system supported for the
configuration files from the list.
The new job item appears in the RSC Files job item group.
new RSC
Files job
item
Specifying Copiers
Use Copier job items to specify the types of copy mechanisms the job uses to push the RSCD
agent and its related files to the target servers.
Unlike several job items that you must create, when you open the Copy Actions job item
group, the job items are already available.
Procedure 1 Click Copiers in the left pane.

The Copy Actions job item group opens. It includes the available Copier job items.
Copiers
2 Select the Copier that you want to add to a job.

how to add a job item to a job, see Adding Job Items to a Job to Create a Job Definition.
Specifying Installers
Use Installer job items to specify the types of installer mechanisms the job uses to connect to
the target servers so that it can run the agent installer on those servers.
Unlike several job items that you must create, when you open the Installer Actions job item
group, the job items are already available.
Procedure 1 Click Installers in the left pane.

The Installer Actions job item group opens. It includes the available installer job items.
Installers
2 Select the Installer that you want to add to a job.

how to add a job item to a job, see Adding Job Items to a Job to Create a Job Definition.
Note: Attempting to install an agent on a Windows target from a machine running a

UNIX-style operating system might fail, because TELNET and SSH are not
generally enabled on Windows systems and PsExec only works for Windows to
Windows installations. To ensure successful agent installations on Windows
targets, install them from a Windows machine.
Discovering Servers
You can use the server discovery feature to locate available servers and add the list of servers
to the Imported Servers job item group. This can be a quick alternative to manually adding
individual servers as job items.
If the Bulk RSCD Agent Installer is installed on a machine running Windows, you must have
WinPcap installed on that machine to use server discovery. For more information, see
WinPcap.
To discover servers and add them to the Imported Servers job item group, use the following
procedure.
Procedure 1 Click the Discover Servers icon (see list of icons) or from the Action menu choose
Discover Servers.
The Discover Servers window opens.
2 Specify the search criteria using the following fields:

• For Network Designation, choose values to specify the network range to search.
Enter the IP address range for the search. Use the first three numbers of the IP
addresses in the first three fields (these three numbers are the same for both
addresses in the range). In the last two fields, use the last numbers of the first and
last IP addresses (in that order) in the network range that you want to search. For
example, to search 10.20.86.1 to 10.20.86.50, specify the following numbers in the
five fields: 10, 20, 86, 1, and 50.
• For DNS Server Name, type the host name or IP address.
3 Click the Start Search icon to begin server discovery.
As the server discover runs, the status window displays the status. The discovered
servers appear in the Discovered Servers list.
discovered
servers
4 In the server list, select the servers you want to save to the Imported Servers job item
group (use Shift-click or Ctrl-click to select multiple items) or select the Discover
Servers node to save all servers.
The servers are added to the Imported Servers job item group.
discovered
servers
added to
Imported
Servers
To update the servers details, such as the operating system group, refer to the instructions on
specifying the details in Creating a Server Job Item.
Modifying Job Items

At any time, you can edit a job item to change its specifications. When you edit a job item,
ensure that you update the job descriptions of all jobs that include the modified job item. To
do this, remove the old job item from the job and add the updated job item to the job.
For more details, see Removing Job Items from a Job Definition and Adding Job Items to a
Job to Create a Job Definition.
Deleting Job Items

You can delete the following job items from their job item groups:
• Imported Servers
• Passwords
• Agent Packages
• RSC Files
You cannot delete other job item types, but you can deselect them.
When you delete a job item, ensure that you update the job descriptions of all jobs that
include the deleted job item. To do this, remove the corresponding job item from the job and,
if necessary, add a new job item to the job (for example, if you remove the only server under
Target, you need to add a new one). For more details, see Removing Job Items from a Job
Definition and Adding Job Items to a Job to Create a Job Definition.
To delete a job item from a job item group, use the following procedure.
Procedure 1 Click the appropriate button to display the job item group from which you want to
remove a job item and then expand the group.
2 Select the job item, right-click, and choose Delete from the pop-up menu.
3 Click Yes to confirm.
The job item is removed from the group.
Enrolling Servers
If you are running the Bulk RSCD Agent Installer in online mode, you can directly enroll the
servers you created in the installer with your application server.
When you enroll servers you can specify that the default access control list (ACL) be pushed
to the target servers. The ACL specifies the roles that have access to the servers and the
actions each role is allowed to perform. For details about the ACL, see the BMC BladeLogic
Users Guide.
To enroll servers, use the following procedure.

Procedure 1 Click Servers in the left pane to display the Imported Servers group, select the Imported
Servers job node and click the Enroll Servers icon (see list of icons) or from the Action
menu choose Enroll Servers.
The Enroll Servers window opens.
2 Select Push ACL for Enrolled Servers if you want to push the ACL for the servers you
are enrolling.
3 In the server list, select the servers to enroll or select the Servers node to include all
servers in the file.
4 Click Enroll Servers.
The Enroll Servers window displays the server enrollment status.
5 Close the window when the process finishes.
Creating a CSV File for Export

If you are running the Bulk RSCD Agent Installer in offline mode, you can create a text file
that includes the server job items in your Imported Servers job item group. The file, which
uses a comma-separated values (CSV) format, includes the servers. You can import the
servers from the file into other Bulk RSCD Agent Installer sessions or into the servers
workspace using the Configuration Manager. Importing servers in this way provides a
convenient alternative to manually adding servers to the Bulk RSCD Agent Installer or
Configuration Manager, especially if you need to add a large number of servers.
To create a server export file, use the following procedure.

Procedure 1 Click Servers in the left pane to display the Imported Servers group, select the Imported
Servers job node and click the Make CSV File to Export icon (see list of icons), or
from the Action menu choose Make CSV File to Export.
The Export to CSV window opens.
2 In the server list, select the servers to include in the export file or select the Servers node
to include all servers in the file.
3 Click Export to CSV.
The Choose Save Directory window opens.
4 Provide the file name and choose the location for the export file and click Save.
The Export to CSV window displays the file creation status.
For details about using this file to import servers into the Bulk RSCD Agent Installer, see
Importing Servers.
For details about importing servers using the Configuration Manager, see the BMC
BladeLogic Users Guide.
Working with Bulk RSCD Agent Installer Jobs
Bulk RSCD Agent Installer jobs enable you to automatically install and upgrade RSCD
agents on multiple targeted servers. Using Bulk RSCD Agent Installer jobs streamlines the
installation and upgrade of RSCD agents on large numbers of servers.
Note: Bulk RSCD Agent Installer jobs are different than jobs that you run from the
Configuration Manager console. You run Bulk RSCD Agent Installer jobs from the
Bulk RSCD Agent Installer console.
A bulk installer job definition is the set of instructions that control how a job runs. You can
create many jobs with different definitions. You can also change a job’s definition to meet
changing installation requirements at your site.
You can set up Bulk RSCD Agent Installer jobs for various types of agent installations and
upgrades. You can define a job for agent installations on servers running Windows or
UNIX-style operating systems (Solaris or Linux), or a combination of both.
This section explains how to create, define, and run Bulk RSCD Agent Installer jobs. It also
describes other tasks related to Bulk RSCD Agent Installer jobs and RSCD agents. For
details, refer to the following topics:
Creating Bulk RSCD Agent Installer Jobs
Creating Job Definitions
Running Bulk RSCD Agent Installer Jobs
Viewing Job Status
Renaming Jobs
Deleting Jobs
Licensing RSCD Agents
Uninstalling RSCD Agents
Note: If you are installing or upgrading RSCD agents in a Windows environment

where replication occurs between two or more domain controllers, there are special
procedures to follow to avoid problems related to user replication. For more
information about installing agents in a replicated domain controller environment,
see the BMC BladeLogic Installation Guide.
Working with Bulk RSCD Agent Installer Jobs 57
Creating Bulk RSCD Agent Installer Jobs

Use the following procedure to create Bulk RSCD Agent Installer jobs.
Procedure In the right pane of the Bulk RSCD Agent Installer, select the Jobs icon, right-click, and
choose New Job from the pop-up menu.
The new job appears in the Jobs list.
new job
To rename the job, use the instructions in Renaming Jobs.
You can now create the job’s definition, which specifies the rules for executing the job. See
Creating Job Definitions for details.
At any time during the process of creating jobs, you can save the current Bulk RSCD Agent
Installer session. For details, see Saving a Bulk RSCD Agent Installer Session.
Creating Job Definitions

When you create a new Bulk RSCD Agent Installer job, it does not have a definition. A job
definition is the set of instructions that control how a job runs. You use job items to create
the definition. Before you can run the job, you need to set up its definition.
The following job items make up a Bulk RSCD Agent Installer job definition:
• Targets: the servers on which to install the agent.
• Passwords: the passwords for the target servers.
Note: If you include a Password job item with a Prompt password type, BMC
BladeLogic recommends that you do not include other password job items in
the job definition. See Specifying Passwords for more information.
• Agent Packages: the agent installers to use for the agent installs.
• RSC Files: the configuration files that control access to servers and specify the security
measures that apply during the connection.
• Copiers: the copy mechanism to use during the installs.
• Installers: the type of installer to use for the agent installs.
Add these job items to a job description from the Job Items list in the left pane of the Bulk
RSCD Agent Installer; however, before you can add job items to a job description, you must
set up the job items with the agent installation specifications. For more details about job
items and how you set them up, see Working with Bulk RSCD Agent Installer Job Items.
After you set up your job items, you can add them to a job to create the job definition.
To see a job’s definition, expand the job in the Jobs list in the right pane of the Bulk RSCD
Agent Installer. This displays the job item groups that make up its definition. When you
expand a newly created job, its job item groups are empty because it does not yet have a
definition.
new job without

definition
job with
definition
For more details, see the following topics:

Adding Job Items to a Job to Create a Job Definition
Removing Job Items from a Job Definition
Adding Job Items to a Job to Create a Job Definition

After you set up job items with the agent installation specifications (Working with Bulk
RSCD Agent Installer Job Items), you can add them to a job to create the job definition.
A job item group can include one or more job items. For example, the Imported Servers job
item group might contain many servers. You can copy one or more Server job items at a time
to the job or you can copy all job items at once.
Procedure 1 Select the job to which you want to add a job item.
2 In the Job Items list in the left pane, select the appropriate job item group and do one of
the following:
• To add one or multiple job items to the job, expand the job item group to display its
entries, select the items you want to add, and click the Add Job Item icon (see list of
icons).
• To add all job items in a job item group, click the Add All Job Items icon (see list of
icons).
The job items appear in the corresponding job item group in the selected job.
Removing Job Items from a Job Definition

To remove job items from a job definition, remove them from the job. You can remove one
or more job items from a job group at the same time or all items at once.
Note: If you modify a job item, be sure to remove the job item from the job (as
described in this section) and replace it with the updated job item from the job item
group.
In the Jobs list, select the job group from which you want to remove job items and do one of
the following:
• To remove one or multiple job items, expand the job group, select the job items you want
to remove, and click the Remove Job Items icon (see list of icons). Alternatively, you
can select one or more job items (use Shift-click or Ctrl-click to select multiple items),
right-click, and choose Delete Job from the pop-up menu. Click Yes to confirm.
• To remove all job items from a job group, click the Remove All Job Items icon (see list
of icons).
Running Bulk RSCD Agent Installer Jobs

After you create a job and its definition, you can run the job to install or upgrade agents.
Procedure 1 To run a job, in the Jobs list in the right pane, select the job, right-click, and choose
Execute from the pop-up menu.
If the Passwords job item specifies a Prompt password type, the Authentication
Information dialog appears, prompting for a user name and password for the server;
otherwise, the job is executed now. (See Specifying Passwords for more information.)
2 Type your user name and password, and then click OK.
You are prompted for the user name and password for each server. Repeat this step for
each prompt.
The job is executed. (Note that if you click Cancel in the Authentication Information
dialog, the job is initiated, but it will fail.)
As the job runs, its status appears in the Job Status pane. For details about viewing the status,
see Viewing Job Status.
Agents are installed in the locations specified in the silent installation files. For more
information about these files, see Files for Silent Agent Installs or Upgrades.
Agents are automatically licensed with a demonstration license that is valid for only two
weeks. For details about obtaining and installing long-term agent licenses, see Licensing
RSCD Agents.
Viewing Job Status

As you run a Bulk RSCD Agent Installer job, its status appears in the status pane. You can
drill down into the status message for more status details.
Procedure 1 In the status pane, double-click on the status message.
The Job Status Details window opens. The top pane lists the servers in the job.
2 Click on a server to see the status of the agent installation on that server.
All status messages for the job appear in the bottom pane.
Renaming Jobs
To rename a job, use the following procedure.
Procedure 1 In the Jobs list in the right pane, select the job, right-click, and choose Rename Job from
the pop-up menu.
The Rename Job dialog opens.
2 Type the new job name and click OK.

The job name changes to the new name.
Deleting Jobs
To delete jobs from the Jobs list, use the following procedure.
Procedure 1 In the Jobs list in the right pane, select one or more jobs (use Shift-click or Ctrl-click to
select multiple jobs), right-click, and choose Delete Job from the pop-up menu.
2 Click Yes to confirm.
The jobs are removed from the list.
Licensing RSCD Agents

Agents are automatically licensed with a demonstration license that is valid for two weeks.
You can set up long-term agent licenses in the Bulk RSCD Agent Installer. To obtain
long-term licenses for agents, use the following procedure.
Procedure 1 Click the License Agents icon, or from the Action menu choose License Agents.
The License Agent window opens.
2 Type your user name and password provided by the BMC BladeLogic Support group.
3 In the server list, select the servers for which you want to license agents or select the
License Servers node to license agents for all servers in the list.
4 Click License.
The License Agents window displays the licensing status.
Uninstalling RSCD Agents

For instructions on how to uninstall RSCD agents, see the instructions in the BMC
BladeLogic Installation Guide.
Index
A installing Bulk RSCD Agent Installer

agent installers on UNIX 21
supported for Bulk RSCD Agent Installer 13 on Windows 18
B J
bi_platform_config.xml file job definitions
syntax example 29 adding job items 59
updating operating system list 27 creating 57
BMC Software, contacting 2 overview 56
bulkinstaller.properties file 24 removing job items 60
job items
C adding Imported Servers 38
console adding Passwords 41
minimizing and maximizing panes 33 adding RSC Files 46
overview 32 adding RSCD Agent Packages 43
refreshing 33 adding to jobs 59
Copier job items 47 Copy Actions group 47
Copiers deleting 52
specifying job items 47 Imported Servers group 37
supported for Bulk RSCD Agent Installer 12 Installer Actions group 48
creating modifying 52
CSV files 54 overview 37
Imported Server job items 38 Passwords group 41
jobs 57 removing from jobs 60
Password job items 41 RSC Files group 46
RSC File job items 46 RSCD Agent Packages group 43
RSCD Agent Package job items 43 specifying Copiers 47
CSV files 54 specifying Installers 48
customer support 3 jobs
D adding job items 59
definitions creating 57
adding job items 59 creating definitions 57
creating for jobs 57 deleting 61
removing job items 60 overview 56
deleting removing job items 60
job items 52 renaming 61
jobs 61 running 60
discovering servers 49 viewing status 61
E L
enrolling servers 53 licensing agents 62
I M
icons 8 modifying job items 52
Imported Servers N
adding job items 37 Network Shell 11
creating job items 38 Nmap 11
importing servers 40
Installer job items 48 O
Installers opening sessions 35
specifying job items 48 operating systems
supported for Bulk RSCD Agent Installer 12 bi_platform_config.xml file 27
supported for Bulk RSCD Agent Installer 11
updating supported list 27
64
P silent install files

Passwords creating response files for Windows 13
creating job items 41 creating UNIX installation default files 14
product support 3 required for Windows installs 13
properties starting the Bulk RSCD Agent Installer 31
bulkinstaller.properties file 24 status of jobs 61
modifying 24 support, customer 3
PsExec 11 system requirements
for Bulk RSCD Agent Installer 10
R Network Shell 11
renaming jobs 61 Nmap 11
RSC Files PsExec 11
creating job items 46 silent install files 13
RSCD Agent Packages supported agent installers 13
creating job items 43 supported copiers 12
running jobs 60 supported installers 12
S supported operating systems 11
saving sessions 35 WinPcap 12
script.sh 28 T
servers technical support 3
creating CSV files 54
discovering 49 U
enrolling 53 uninstalling Bulk RSCD Agent Installer
importing 40 on UNIX 23
server import file format 41 on Windows 20
sessions upgrading Bulk RSCD Agent Installer
opening 35 on UNIX 17
saving 35 on Windows 17
W
WinPcap 12
*97501*
*97501*
*97501*
*97501*
*97501*

Bulk Agent Installer

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Bulk Agent Installer

Încărcat de

Drepturi de autor:

Formate disponibile

BMC BladeLogic Bulk RSCD Agent Installer 7.5.

© Copyright 2007-2009 BladeLogic, Inc.

Restricted Rights Legend

Support by Telephone or Email

Before Contacting BMC Software

Name Icon Description

Add Adds an item to a list of similar items.

Cancel Indicates a failed process, such as a component that did not

Delete Deletes the selected item.

Execute Executes an action, such as running a job or saving the results

Name Icon Description

Refresh Refreshes information in the current display, such as the Bulk

BMC BladeLogic Explains how to install all the components of PDF

BMC Service Automation Documents how to install theBMC Service PDF

Note: In addition to the requirements described in the BMC BladeLogic

Supported Operating Systems

You can download PsExec from

You can download Nmap from http://insecure.org/nmap/.

You can download WinPcap from http://www.winpcap.org/.

Note: Attempting to install an agent on a Windows target from a machine running a

Agent Installer Packages

Files for Silent Agent Installs or Upgrades

Creating a Response File for Windows Agents

Procedure 1 Copy rscd<version>.exe (the RSCD agent installation program) to

3 From the command line, enter

Creating a File of UNIX Installation Defaults

INSTALL_DIR Setting this allows you to choose an installation directory

COMPONENT_CHECKED By default, running a silent installation installs all possible

IS_SECURE_AGENT_LOGS Setting this variable to 1 enables secure agent logging.

IS_KEYSTROKE_LOGS Setting this variable to 1 enables keystroke (nexec) logging

RND_CHOICE BladeLogic uses random data to encrypt communication

NSH_INSTALL_SKEL By default a silent installation does not include the .nsh

DEFAULT_WEBBROWSER By default the silent installation tries to find a default web

Upgrading the Bulk RSCD Agent Installer

Refer to the upgrade instructions for your system type:

Upgrading the Bulk RSCD Agent Installer on Windows

Upgrading the Bulk RSCD Agent Installer on UNIX

8 Type Y to confirm the Bulk RSCD Agent Installer upgrade.

Installing and Uninstalling the Bulk RSCD Agent Installer on Windows

Installing and Uninstalling the Bulk RSCD Agent Installer on Solaris

Note: Attempting to install an agent on a Windows target from a machine

5 Press Enter to scroll through each screen of the agreement.

Procedure 1 Log in as root.

Modifying Properties in the bulkinstaller.properties File

Property Name Description

psexecLocation The absolute path of the PsExec binary (for Windows

localOS The operating system running on the machine on which you

maxWorkerThreads The number of threads that can be invoked concurrently

windowsTempDir The absolute path of the default temporary directory on the

windowsLocalTempDir The “actual” temporary directory (as opposed to the

windowsRemoteTempDir The absolute path of the temporary SMB/FTP share

Property Name Description

unixTempDir The absolute path of the default temporary directory on the

nmapLocation The absolute path of the Nmap binary.

nshLocation The absolute path of the Network Shell binary.

jcifs.resolveOrder Specifies the order in which jCIFS will resolve network

Property Name Description

AES_support Specifies the AES authentication status.

Updating the Operating System List in the bi_platform_config.xml File

The current list of operating systems in bi_platform_config.xml is very comprehensive;

To create an operating system entry in bi_platform_config.xml, use the following procedure.

When you run script.sh as follows: