Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Installation cheat sheet for Microsoft Windows and SQL Server environments


Click here to create a PDF of this topic.

This cheat sheet topic provides a list of the steps required to install BMC Server Automation in a Microsoft Windows/SQL Server environment. Note that cheat sheet topics are targeted to experienced BMC Server Automation users, and do not include relevant planning and prerequisite information. If you are not an experienced user, see the topics in the Preparing for installation section to review the required planning information for installation.

The topic includes the following sections:

Setting up a database schema for a Microsoft SQL Server database

  1. Copy install scripts from external-files.zip to a location that you can access from the SQL Server console. For information on external-files.zip, see Downloading the installation files.
    If you extract the entire contents of external-files.zip, the relevant scripts appear in the /db_scripts/sqlserver directory.
  2. Start SQL Server Management Studio.
  3. Expand the database server.
  4. Right-click the Databases folder and select New Database.
  5. Provide a name for the database, such as bladelogic.


    • Use only Latin alphabet letters, numbers, and underscores (_) in database names. Do not begin database names with a number. Do not use hyphens (-). While database names with hyphens work in the BMC Server Automation system, they do not work in BMC Decision Support for Server Automation.
    • SQL Server database names are case-sensitive. You must use the same case when specifying the JDBC connections, or the load process for the BMC Decision Support for Server Automation data warehouse will fail.
  6. Use SQL Server Authentication to create a new user account for the database.


    Do not specify a BMC Server Automation database password for the account that begins with an equal sign (=).

  7. Set the default database to the database you created in step 4 and step 5.
  8. In the User Mappings section, grant the user database ownership on the database, as shown in the following figure.
  9. Set the default language for the database.
  10. Set the collation as case-insensitive for the default language.
    If you are setting up BMC Server Automation to support a language other than English, for Collation name, select the collation for your language that is case-insensitive, accent-sensitive, and (where appropriate) kana-sensitive. For example, if you are setting up BMC Server Automation for French, use French_Cl_AS. If you are setting up BMC Server Automation for Japanese, use Japanese_Cl_AS_KS. The new database appears under the Databases folder. You can set other options at this time too, but they are not required.
  11. To reduce the likelihood of database deadlocks, perform the following steps:
    1. Right-click the database server node and select New Query.
    2. Execute the following query:
    3. Execute the following additional query:
  12. Exit SQL Server Management Studio.
  13. Open a command prompt window.
  14. Change (cd) to /db_scripts/sqlserver.
  15. Run the master script that corresponds to the character sets for which your database is configured, using the following syntax:
    <master_script.bat> <db_server> <db_name> <bl_user> <bl_pwd>
    Replace the variables with the following values:


    sqlserver_master.bat if your database is configured for char/varchar character sets or sqlserver_nchar_master.bat if your database is configured for nchar/nvarchar character sets


    Name of the database server.
    If the server uses a nonstandard port, the server name and port number must be enclosed in quotation marks, as shown in the following example: "QLDS0002,1381"
    To use a named server instance, append the named instance, including the complete path, as shown in this example:
    sqlserver_master.bat <db_server>\<instance_name> <db_name> <db_user> <db_password>


    Name of the BMC Server Automation database that you created in step 4 and step 5.


    Logon name for the BMC Server Automation database user


    BMC  Server Automation database user password


When the master script runs, the following warnings might appear:

Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object 'rsave_cond_result_subtree'. The stored procedure will still be created.
Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object 'rsave_cr_group_result_subtree'. The stored procedure will still be created.

These warnings are expected and can be ignored.

A short video about database setup.

Use player to increase quality or switch to full screen | YouTube:  https://www.youtube.com/watch?v=91FEUDVD6sE

Install the agent on the file server

 Click here to see a list of requirements for the file server.

A file server should meet the following requirements:

  • An RSCD agent must be installed and should be the same version as the Application Server.


    Do not limit access to the file server by pushing agent ACLs to the agent on the file server. All users must be mapped to the same user on the file server.

  • As a minimum, a file server must have 72 GB of available, nonredundant, disk space.


    BMC recommends that the file server be allotted 200 GB or more of available RAID 5 disk space.

  • Define a user name on the file server, and map all users to that user name. Without this mapping, a user may not be able to access a file that another user has stored on the file server. To accomplish the necessary mapping, create an entry like the following in the exports file on the file server:
    <appServer> rw,user= <userName>
    Where <appServer> is a comma-separated list of Application Server names or IP addresses (IPv4 or IPv6) and <userName> is the name to which all users are mapped.
  • Map the internal System:System role/user to the user name defined on the file server. To accomplish the mapping, create an entry like the following in the users.local file on the file server:
    System:System rw,map= <userName>
    Where <userName> is the name to which all users are mapped, typically bladmin or administrator.
    If the required directory structure does not already exist on the file server, the system process attempts to create it.
    For examples on configuring the file server agent ACLs, see Configuring the file server agent ACLs.
  • If your file server location is on partition or a mounted storage, you must ensure that the mount point for the storage or partition is consistent even if the file server host is restarted.
    For example, on Linux, you can ensure this by configuring the fstab file in the etc folder of your machine. The fstab file maps the Universally Unique Identifier (UUID) of a storage or partition to the directory it should be mounted on.

BMC Server Automation uses the file server to store the contents of files included in snapshots, Network Shell scripts, BLPackages, software packages, and other types of information that is not easily stored in the database. The file server must have a RSCD agent installed on it, as described in the following procedure.

    MultiExcerpt named 'install_agent_only_windows' was not found
The multiexcerpt named 'install_agent_only_windows' was not found. Please check the page name and MultiExcerpt name used in the MultiExcerpt Include macro.

Install the Application Server

 Click here to see the prerequisites for installing the Application Servers.

  • To perform this installation, you must have local administrator privileges.
  • If you are using Windows Terminal Services or Citrix Presentation Server to install or if you are installing on Windows 2003 or 2008, use one of the following methods to install:
  • You must set up your database schema. See Setting up the database.
  • On 64-bit Windows systems, confirm that the <WINDIR>\SysWOW64 directory contains a copy of the chcp.com file. The installer uses this file to set the code page of standard output (stdout). You can obtain the file from a 32-bit version of Windows.
  • If you plan to use the bljython utility, install the Application Server before installing Jython.

  1. On the computer where you plan to install the Application Server, log on as Administrator.
  2. Navigate to the directory containing the Application Server installation file, and start the installation program for your platform. Installers are provided for 32-bit and 64-bit Windows. (Installation program names follow the convention: BBSAversion-platform.)
  3. Follow the instructions in the installation script. For details about the required installation parameters, refer to Worksheets for installing BMC Server Automation on Windows.
  4. At the Setup Type window, select the type of installation:
    • Full — Installs the Application Server, the Network Shell, and documentation.
    • Custom — Installs the components you select.
  5. Complete the installation, using information from the worksheet.
  6. If an RSCD agent is running on the computer, restart the agent.

A short video about file server and Application Server setup.

Use player to increase quality or switch to full screen | YouTube:  https://www.youtube.com/watch?v=m7Y3SY23kuQ

Run the post-install configuration utility

The Post-Install Configuration wizard consolidates the minimum configuration steps that must be performed to set up an Application Server. 

  1.  To start the Post-Install Configuration wizard, do one of the following:
    • Perform an installation that includes installation of the Application Server. The installation program gives you the option of launching the wizard at the end of the installation procedure.
    • From the Windows Start menu, select Programs > BMC Software > BladeLogic Server Automation Suite > Utilities > Application Server Configuration Wizard.
    • Start the wizard manually by running one of the following commands in the directory where BMC Server Automation is installed. Enter the following:
      • (Windows)

      • (UNIX)



        If you invoke the wizard without passing the -install flag, the wizard displays configuration settings that have already been entered for the Application Server and allow you to change those settings.

        The configuration wizard opens.

  2. Read the introductory page and click Next. The Database page appears.
  3. Choose a Database Type (either Oracle or SQL Server).
  4. If you are not using a custom connection string, provide the following database configuration information (and do not select the Advancedoption):
    • Database Server — Host name or IP address (IPv4 or IPv6) of the server running the database.
    • Database Port— Port the database listens on. By default a BMC Server Automation installation uses the following database ports:

      Database Type

      Port Number



      SQL Server


    • Database Name — Microsoft SQL server database name. By default, the database name is bladelogic . (This option is only available for SQL server databases.)
    • SID — System ID of the Oracle database. (This option is only available for Oracle databases.)
    • User ID — User name that the database needs to authenticate your connection.
    • Password — Password assigned to the user ID.
      If you are using a custom connection string, provide the following database configuration information:
    • User ID — User name that the database needs to authenticate your connection.
    • Password — Password assigned to the user ID.
    • Advanced — Select this option to indicate that you are providing a custom connection string.
    • Connection String — Type the custom connection string in the field below the Advanced check box.
  5. Click Next. The File Server page appears.
  6. Provide the following file server configuration information:
    • File Server Name — Host name or IP address (IPv4 or IPv6) of the server where data is stored. By default, the file server is created on the same machine as the Application Server.
    • File Server Storage Location — Directory on the file server where data is stored. By default, the directory of the file server is <appserverInstallDirectory>/storage.
  7. Click Next. The Notification Servers page appears.
  8. Provide information identifying an email server by entering the following under SMTP Options:
    • SMTP Server — Name or IP address (IPv4 or IPv6) of the host managing email. (SMTP stands for simple mail transfer protocol.)
    • E-mail From — email address from which BMC Server Automation-generated email is sent. BMC Server Automation jobs can generate email upon their completion.
  9. If you are using SNMP trap notifications, provide information identifying the SNMP server by entering the following under SNMP Options:
    • SNMP Server — Name or IP address (IPv4 or IPv6) of the host to which SNMP traps should be sent.
    • SNMP Port — The port on the SNMP server that listens for SNMP traps. By default, the port is set to the standard SNMP port of 162.
  10. Click Next. The User Passwords page appears.
  11. Under both RBACAdmin User and BLAdmin User, enter a password and then retype the password to confirm your entry. If a password is already set, you cannot enter a password.
    Passwords are used to authenticate the RBACAdmin and BLAdmin users through the SRP authentication protocol.
    The RBACAdmin user has full permission to manage roles and users in the RBAC Manager workspace in the BMC Server Automation Console, where you can assign permissions for all BMC Server Automation users. The BLAdmin user has Read access for all system objects within BMC Server Automation. For more information about the RBACAdmin and BLAdmin users, see RBACAdmin and BLAdmin users.
  12. Click Finish.


BMC recommends that you synchronize the clock on the Application Server and all client machines. Clocks should be synchronized to the minute. For example, if an Application Server is in Boston, where the time is 7:04 Eastern Time, set the clock on client machines in San Francisco to 4:04 Pacific Time.

Install the console on your client system

 Click here to see a list of prerequisites for installing the console.

    MultiExcerpt named 'windows_console_prereqs' was not found
The multiexcerpt named 'windows_console_prereqs' was not found. Please check the page name and MultiExcerpt name used in the MultiExcerpt Include macro.

    MultiExcerpt named 'windows_console_install' was not found
The multiexcerpt named 'windows_console_install' was not found. Please check the page name and MultiExcerpt name used in the MultiExcerpt Include macro.

A short video about console installation and Application Server configuration.

Use player to increase quality or switch to full screen | YouTube:  https://www.youtube.com/watch?v=uwqlj60Lvo0

Connect to the Application Server

From the Start menu, select Programs > BMC Software > BladeLogic Server Automation Suite > Server Automation ConsolereleaseNumber.

A logon dialog box appears. To log on, you must choose an authentication profile. For more information about creating authentication profiles, see Setting up an authentication profilePerform the following steps to start the console and connect to the Application Server.

  1.  Using the Authentication profile tab, select an authentication profile.
  2. If you:
    • Possess a valid cached session credential, skip this step and go to the next step.
    • Are using Active Directory/Kerberos (ADK) or public key infrastructure (PKI) authentication, skip this step and go to the next step.
    • Are using SRP, LDAP, or SecurID authentication, enter your user name and password. For SecurID, your password consists of a PIN followed by the current token code displayed on your RSA SecurID token.
    • Are using Domain Authentication, enter your user name and domain. The domain name must always be capitalized. If you are defined as a member of the default realm, you do not have to enter a domain name. For information about how to set up the default realm for Domain Authentication, see Configuring Domain Authentication.
  3. To change the setting for caching session credentials or the display language, click Options. The logon window expands to show additional options in a tabbed format. By default the Generaltab is open.

    Save credential for this session

    Saves a session credential between sessions.

    By default, this option is not checked. The setting for this option remains in effect for future logons until you change the setting. If a session credential is already cached, this option is dimmed.


    Displays your choice of language (either your previous choice or your acceptance of the installation default). Select a new display language for the console or keep the current user preference. The selection remains in effect as your default language for future logons until you make a new choice.

  4. Click Connect.
    If the Application Server presents the BMC Server Automation Console with an X.509 certificate that is not trusted, a security alert appears. Most Application Servers use self-signed certificates, so typically you encounter this dialog box the first time you access a particular Application Server.
  5. If a security alert does not display, skip this step and go to the next step. If a security alert describes an untrusted certificate, do one of the following:
    • To return to the logon dialog box, click No. You can cancel the logon session or use a different authentication profile to log on.
    • To accept the unknown certificate and proceed with the logon, click Yes.
    • To examine details about the certificate, click View Certificate. For more information about this procedure, see Viewing an untrusted certificate. After examining the certificate, click Yes or No, as described above.
  6. If multiple roles are associated with your user name, the Assume Role dialog box appears. From this dialog box, for Select Role, choose the role you want to use. 
    If you prefer, you can switch roles later at any time during a session. (See Switching roles.)
  7. Click OK. The BMC Server Automation Console appears.


    When the console starts, by default it loads certain types of information by running a background operation. The Show background operations icon in the lower right corner of the console indicates a background process is running. For information about background processes, see Running background operations.

What if I have problems?

The following table provides troubleshooting information for common installation issues.


Error message while installing RSCD Agent with MSI installer

While trying to install RSCD Agent using the MSI installer, you receive a message to reboot the server. After rebooting, the installer does not launch, and you receive the message again.

Any application can set a pending reboot flag in the operating system through a registry key. Sometimes a reboot does not clear the flag. This is what the setup is detecting.

Use the following workaround when you receive the pending reboot requests multiple times, even though you have rebooted the server:

  1. Open Regedit.
  2. locate the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager.
  3. Rename the PendingFileRenameOperations value to PendingFileRenameOperations2.

Access denied errors occur during install on Windows targets

When installing agents on Microsoft Windows targets, the user specified in the automation principal for remote host authentication must have access to the admin shares of the target machine. For Windows Vista and later operating systems, if you are a local administrator on a server and you are not the default administrator account, then by default you do not have access to these shares. This results in Access Denied errors during the install.

To resolve this issue:

  • Use the default administrator account
  • Use a domain administrator account that has permissions for the target device
  • Create the following registry DWORD value and set it to 1.



The /etc/sudoers file cannot be configured to accept only a root password

It is possible to configure SUDO so that it requires you to give it the root password. For many SUSE Linux installations, the /etc/sudoers file is configured this way. However, agent installation does not work with this type of configuration. If the /etc/sudoers file is configured to accept only the root password, the job fails.

To resolve this issue, configure /etc/sudoers so it accepts passwords other than the root password.


Target system is in pending reboot state causing potential RSCD Agent installation problem

If the target system is in a pending reboot state (for example, from a previous patch or other software installation), you can use the PENDINGREBOOTFORCE flag to allow the MSI installer to ignore the pending reboot state and allow the installation to proceed. After you confirm that the pending reboot state on the target is not a result of a previous RSCD installation, you can set PENDINGREBOOTFORCE=1. Following is a command-line sample for the MSI installation program:

msiexec /I RSCD85-SP1-P1.WIN32.msi /qn REBOOT=ReallySuppress PENDINGREBOOTFORCE=1

Application serverEnsuring that bljython works after installing the Application Server
On Microsoft Windows platforms, if you install the Jython utility after you install the Application Server, the BMC Server Automation Jython executable (bljython.exe) does not work. 

The Application Server installation on Windows creates the bljython.cfg file. Creation of this file converts the value of the JYTHON_HOME variable to an absolute path. If the Jython utility is not installed and the JYTHON_HOME variable set before the Application Server installation, the bljython.cfg file does not contain the full path to the Jython installation.

When you launch bljython.exe or when you run a Jython script, the utility displays an exception and an error message:

java.lang.NoClassDefFoundError: org/python/util/jython
Caused by: java.lang.ClassNotFoundException: org.python.util.jython
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
[ERROR] Failed to find main class: org/python/util/jython

To resolve this issue, do one of the following:

  • Copy the jython.jar file into the stdlib directory. The location for this directory is: <installDirectory>\br\stdlib, where <installDirectory> is the BMC Server Automation installation directory
  • Edit the bljython.cfg file to specify the full path to the jython.jar file. The bljython.cfg file location is <installDirectory>\br\bljython.cfg, where <installDirectory> is the BMC Server Automation installation directory.
ConsoleError installing on Windows 2012
When Advanced Repeater, Console, or Content installers are run on a Windows 2012 platform, the following error is displayed:

Installer User Interface mode is not supported.


To launch the installer, perform the following steps:

  1. Right-click the <Installer>.exe file and select the Troubleshoot compatibility option.
  2. Click Troubleshoot program.
  3. Select the Program worked on earlier version of windows but won't install or run now check box and click Next.
  4. Select the I don't know option and click Next.
  5. Click Test the program.

Database cleanup command does not work

The first attempt to delete some BMC Server Automation objects using Delete cleanupDatabase might fail. However, subsequent runs of Delete cleanupDatabase delete the objects.

Data Migration Manager upgrades fail

When you launch upgrades from the Data Migration Manager console, the console must remain open and connected to the upgrade process until the process completes. The upgrade process fails if:

  • You close the console — Do not close the console.
  • The session times out — If you are running the upgrade using a remote console, disable session timeouts before launching the Data Migration Manager.
  • The session loses connection to the upgrade process for any reason — Check network connections.

Schema changes

    Page not found for multiexcerpt macro.
The page: Setting up an Oracle database user and schema for BMC Server Automation was not found. Please check/update the page name used in the 'multiexcerpt-include' macro.
PXE and TFTP server

Setting debug logging for PXE and TFTP servers

To set logging levels on the PXE server:

  1. In a text editor, open the log4j.propertiesfile. The file is located at:





  2. For each property for which you want to log debugging information, change the value to DEBUG or INFO.

To set logging levels on the TFTP server:

  1. In a text editor, open the tftpsvr.cffile. The file is located in:





  2. For each property for which you want to gather debugging information, change the value to DEBUG or INFO.
GeneralRepairing components
To repair a component that has been damaged by corruption or accident, run the installation program again. In some cases, the installer presents different options when you reinstall. 

User configurations are preserved in an over-the-top reinstallation, except for changes that can be made during installation.

You cannot use the Add/Remove Programs utility in the system Control Panel to modify or repair BMC Server Automation components.

Related topic

Installation cheat sheet for Linux and Oracle environments

Was this page helpful? Yes No Submitting... Thank you