Component installation cheat sheet for Microsoft Windows and SQL Server environments

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 and user for a Microsoft SQL Server database
Setting up a database schema for a Microsoft SQL Server database
Install the agent on the file server
Install the Application Server
Run the post-install configuration utility
Install the console on your client system
Connect to the Application Server
What if I have problems?
Related topic

Setting up a database and user for a Microsoft SQL Server database

	Step	Example screen
1	Start the Microsoft SQL Server Management Studio application and connect to the Microsoft SQL database server.Note: You can connect a Windows default Application Server node only to a Microsoft SQL Server database.
2	Expand the database server. Right-click the Databases folder and select New Database.
3	Provide a name for the database you are setting up and click OK to exit the New Database wizard. Click here to see best practices for naming. 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.
4	Create the login credentials for the database.Right-click the Security folder and select New > Login.
5	Create log in credentials for the database. Provide a Login name (typically bladelogic), select SQL Server Authentication and enter a Password for the database. Note: Do not specify a BMC Server Automation database password for the account that begins with an equal sign (=). Ensure that the User must change password at next login option is not selected. For Default Database, enter the name of the database you are creating. Select a language for Default Language. The database for this walkthrough has a default language of English. If you are setting up your database with a default language other than English, click here for collation information. If you are setting up BMC Server Automation to support a language other than English, on the Database properties > Options page, 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.
6	Assign roles to the login name. Click on User Mappings on the left. In the Users mapped to this login section, select the name of the database that you set up earlier in this procedure (in this example: test), and set the default schema to dbo. In the Database role membership section, select db_owner. Click OK.
7	Expand the Databases folder. Right-click the new database server node we created, and select New Query.
8	To reduce the likelihood of database deadlocks, execute the following steps: Execute the following query: ALTER DATABASE <db_name> SET ALLOW_SNAPSHOT_ISOLATION ON; <db_name> is the name of the database you set up earlier in this procedure. Execute the following additional query: ALTER DATABASE <db_name> SET READ_COMMITTED_SNAPSHOT ON; <db_name> is the name of the database you set up earlier in this procedure. Exit SQL Server Management Studio.

Setting up a database schema for a Microsoft SQL Server database

Copy install scripts from the db_scripts directory in the main product .zip to a location that you can access from the SQL Server console. For information on the db_scripts directory, see Downloading-the-installation-files.
The relevant scripts appear in the /files/configurations/dbscripts/sqlserver directory inside the BBSA<version>-<platform>64 installer zip package.
Open a command prompt window.
Change (cd) to /db_scripts/sqlserver.

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:

Variable	Value
<master_script.bat>	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
<db_server>	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>
<db_name>	Name of the BMC Server Automation database that you created while setting up the database
<bl_user>	Logon name for the BMC Server Automation database user
<bl_pwd>	BMC Server Automation database user password

Note

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.

_{Back to top}

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.
Note
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.
Recommendation
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.

Failed to execute the [excerpt-include] macro.

_{Back to top}

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.
The BMC Server Automation Application Server installation program needs a certificate password to generate a self-signed X.509 certificate. Communication between BMC Server Automation and servers being provisioned and between the Application Server and the process spawner uses the Transport Layer Security (TLS) protocol and X.509 certificates. The password must be at least 6 characters. For more information about certificates and the TLS protocol, see Authentication.
The Application Server installation does not install the BMC Server Automation Console. To view the console, you must install it. For information, see Installing-the-BMC-Server-Automation-Console-and-Network-Shell-Windows.
To use provisioning with the Application Server, select the option to enable provisioning.
If you are using Windows Terminal Services or Citrix Presentation Server to install or if you are installing on a Windows operating system, use one of the following methods to install:
- Install in Install mode rather than Execute mode. For information, see Using-Install-mode-instead-of-Execute-mode.
- Install using the Windows Add or Remove Programs utility.
You must set up your database schema. See Setting-up-an-Oracle-database-for-BMC-Server-Automation and Setting-up-a-SQL-Server-database-and-user-for-BMC-Server-Automation .
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 Jython utility before installing the Application Server.
If the host computer on which you are installing the Network Shell has:
- A supported version of Perl installed--The Network Shell installation automatically installs the Network Shell Perl module. (For information about the Perl versions that BMC Server Automation supports, see Perl support.)
- An unsupported version of Perl installed--The installation copies files that allow you to install the Perl module after you have installed the supported version of Perl.

	Step	Example screen
1	On the computer where you plan to install the Application Server, log on as Administrator. From the BMC Software Electronic Product Distribution (EPD) website, download and extract the BBSA<version>-WIN64.zip installer package. For steps on downloading files from the EPD website, see Downloading-the-installation-files. Navigate to the directory containing the Application Server installation file, which is BBSA<version>-WIN64.zip/files/installers/appserver_64/. Installation program names follow the convention: BBSAversion-platform. Start the 64-bit installation program for the Windows operating system. The Choose Setup Language panel is displayed. Choose a language and click Next. The Welcome panel is displayed.
2	Click Next. The Acknowledgement panel is displayed.
3	Click Next. The License Agreement panel is displayed.
4	Click Yes. The Customer Information panel is displayed.
5	Enter a user name and password. Click Next. The Setup Type panel is displayed.
6	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. This example uses a custom installation. Click Next. The Choose Destination Location panel is displayed.
7	Click Browse to specify an installation directory, or click Next to accept the default directory, C:\Program Files\BMC Software\BladeLogic. The Select Features panel is displayed.
8	Select the components for installation (custom installation only): Application Server Network Shell Documentation components Click Next. The Application Server JVM Settings panel is displayed.
9	Specify the maximum heap size, in megabytes, to use for the Java Virtual Machine (JVM) for the Application Server Launcher. In a multiple-Application Server (MAS) environment, the Application Server Launcher configures and controls all Application Servers on the host. Specify a value above the minimum 512 megabytes. The default is 4095 MB. Best practice: If you are setting up a MAS environment, set the MaxHeapSize to 512 MB. Then when you configure each Application Server instance, set MaxHeapSize to a value appropriate for the architecture and operating system. For recommended maximum Java heap sizes, see Sizing-and-performance. Click Next. The Certificate Password panel is displayed.
10	Specify a certificate password (must be at least 6 characters). The Application Server installation program needs a certificate password to generate a self-signed X.509 certificate. Communication between BMC Server Automation and servers being provisioned and between the Application Server and the process spawner uses the Transport Layer Security (TLS) protocol and X.509 certificates. The password must be at least 6 characters. For more information about certificates and the TLS protocol, see Authentication. Click Next. The Selected Components panel is displayed.
11	Review the selected components and click Next to start the installation.
12	The status panel displays the installation progress. When installation completes, the Post-Configuration panel is displayed.
13	Do one of the following: To configure the Application Server at a later time, click Next. To configure the Application Server and set up administrator passwords using the Post-Install Configuration wizard, select the Configure the Application Server option and click Next. See Configuring-a-single-default-Application-Server-on-the-host for instructions for completing that wizard.
14	Click Finish to exit the installation program.

_{Back to top}

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.

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)
    bin\blappconf.exe
  - (UNIX)
    ./br/blappconf
    Note
    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.
Read the introductory page and click Next. The Database page appears.
Choose a Database Type (either Oracle or SQL Server).
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 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.
  or...
  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.
Click Next. The File Server page appears.
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.
Click Next. The Notification Servers page appears.
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.
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.
Click Next. The User Passwords page appears.
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.
Click Finish.

Recommendation

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.

_{Back to top}

Install the console on your client system

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

BMC recommends that you do not install the console on the same system as the Application Server.
Before you install the BMC Server Automation Console, ensure that port 12333 (TCP) is not being used. Installation of the console requires use of this port; if it is already in use, the installation fails.

Update the Windows Terminal Services Server Settings for temporary folders. (In Windows Server 2008 R2 and later versions, Terminal Services is renamed to Remote Desktop Services).
Click here for steps about updating the Windows Terminal Services
To update the Windows Terminal Services (or Remote Desktop Services) configuration perform either of the following steps:
Server settings method
1. On the computer where you are installing the BMC Server Automation Console, select Start > Run.
2. For Open, enter tscc.msc. Then click OK. (If you are using Windows 2008 R2 or later, you must enter TSConfig.msc)
3. Navigate to Server Settings and do the following:
  Set Delete temporary folders on exit to No.
  Set Use temporary folders per session to No.
4. Restart the computer.
  If the settings do not take effect, use the Registry Editor (regedit):
Registry editor method
1. Click Start > Run and enter regedit.
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server.
3. Set the DeleteTempDirsOnExit and the PerSessionTempDir values to 0.
4. Restart the computer.
Note: The installation program uses temporary folders to preserve the install log. Usually, you can perform this update only one time; you do not need to update the configuration every time you install. However, if your Server Settings are different from those needed for installation, after you finish installing the console you can change the settings back to their previous settings.

	Step	Example screen
1	Navigate to the directory containing installation files and run the installation program for the console. Different installers are provided for 32-bit and 64-bit Windows. In this example, we are running the BBSACONSOLE87-WIN64 file on the Windows machine on which you plan to install the console. Select a language to use for the installation and click OK. The installer extracts the installation files, and the Introduction window opens.
2	Ensure that you have closed all applications before you proceed. Click Next. The Review License Agreement window opens.
3	Read the End User License Agreement (EULA) and select I agree to the terms of the license agreement if you wish to proceed. Click Next. The Directory Selection window opens.
4	The default installation location for the console is C:\Program Files\BMC Software\BladeLogic. Click Next to use the default location. Alternatively, you can click Browse to change the installation location.
5	A window opens in which you can select components to install. By default, all components are selected. The Network Shell is automatically installed when you install the console. Note: If you clear the BMC Server Automation Console Upgrade Service check box, the BMC Server Automation Console Upgrade Service is not installed. This service is required for automatically upgrading the BMC Server Automation Console when you upgrade the Application Server. Click Next.
6	The window displays your selections. Click Install. The window displays installation progress, then displays a message when installation is complete. The console and Network Shell are installed on your machine.
7	In case you encountered any errors while installing you can click View Log to view a detailed report of the installation. Tip: BMC recommends that you save a copy of the log, before you contact technical support for further assistance. You can also find more information about resolving common issues in Troubleshooting-the-unified-product-installer. If all operations are completed successfully, click Done to exit the wizard.
8	Start the console. To configure the console so that it connects to the default Application Server, click Options.
9	Click on the Authentication Profiles tab and click Add. BSA clients use authentication profiles to facilitate single sign-on feature. You must create an Authentication profile before you start using the Console. For more information about why we use Authentication Profiles, see System-capabilities-related-to-security.
10	Enter the following information. Assign a name to the authentication profile. For example, you could assign a name such as QATeam or DevTeam. Enter the name or IP address (IPv4 or IPv6) of the default Application Server to which the client should connect. Enter an Authentication Port number to which the client should connect. The same port is used for all BMC Server Automation authentication mechanisms. The default Port is 9840. For more information about Console ports, see BMC-Server-Automation-ports. Select any one authentication mechanism for the authentication profile: Secure Remote Password. AD/Kerberos Single Sign-on. Domain Authentication. LDAP. RSA SecurID Authentication. Public Key Infrastructure Authentication. In this walkthrough we will use the Secure Remote Password mechanism. For information about implementing the other authentication mechanisms, see Implementing-authentication. Click OK.
11	You can now log on the the Console using the BLAdmin user that is created while installing the default Application Server node, see step 10. The quick start page is the first page that is displayed once you log on the the BSA Console. It introduces you to the main use cases of BMC Server Automation and allows you to execute them from a centralized UI immediately after installing the BSA set up. For information about using the quick start page, see Quick-start-page. For general information about the UI of the BSA Console, see Navigating-the-interface.

_{Back to top}

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-profile. Perform the following steps to start the console and connect to the Application Server.

Using the Authentication profile tab, select an authentication profile.
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.

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.
Language	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.

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.
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.
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.)
Click OK. The BMC Server Automation Console appears.
Note
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.

_{Back to top}

What if I have problems?

The following table provides troubleshooting information for common installation issues.

Component

Issue

Troubleshooting

Agent

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:

Open Regedit.
locate the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Control\Session Manager.
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.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\
CurrentVersion\Policies\System\
LocalAccountTokenFilterPolicy

There is a BMC BladeLogic ZipKit available that includes a package that enables the ADMIN share (c$) using registry change and restarts the Server Service. The ZipKit is available from BMC Communities at Blade ZipKit - Enable Admin Shares for Windows 2008 R2.

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 Server

Ensuring 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.

Console

Error installing on Windows 2012

When Console or Content installers are run on a Windows 2012 platform, the following error is displayed:

Installer User Interface mode is not supported.

Workaround:

To launch the installer, perform the following steps:

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

Database

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.

Migration of database data during upgrade fails

Migration of database data during the upgrade process fails if:

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

Schema changes

BMC does not recommend, nor does it support database schema changes.

PXE and TFTP server

Setting debug logging for PXE and TFTP servers

To set logging levels on the PXE server:

In a text editor, open the log4j.propertiesfile. The file is located at:
UNIX
installDirectory/NSH/br/deployments/_pxe
Windows
installDirectory/PXE/br/deployments/_pxe
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:

In a text editor, open the tftpsvr.cffile. The file is located in:
UNIX
installDirectory/NSH/br/
Windows
installDirectory/PXE/br
For each property for which you want to gather debugging information, change the value to DEBUG or INFO.

General

Repairing 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.

Component installation cheat sheet for Microsoft Windows and SQL Server environments

Setting up a database and user for a Microsoft SQL Server database

Setting up a database schema for a Microsoft SQL Server database

Install the agent on the file server

Install the Application Server

Run the post-install configuration utility

Install the console on your client system

Connect to the Application Server

What if I have problems?

Related topic

On this page