BMC Server Automation 8.9
Placing a watch on this page is a great way to stay informed of changes to this space.
|February 05, 2018||Service Pack 2: version 8.9.02||Lists the updates and enhancements introduced in BMC Server Automation version 8.9 Service Pack 2.|
|January 19, 2018||Version 8.9.01.001: Patch 1 for version 8.9.01||Lists the updates and enhancements introduced in BMC Server Automation version 8.9 Service Pack 1 Patch 1.|
|November 9, 2017||BSA 8.9.01 Rolling Update 3 (RU3)||Lists the updates in BMC Server Automation version 8.9 Service Pack 1 Rolling Update 3.|
|May 17, 2017||Service Pack 1: version 8.9.01||Lists the updates and enhancements introduced in BMC Server Automation version 8.9 Service Pack 1.|
|September 23, 2016||8.9.00 enhancements and updates||
Lists the enhancements introduced in BMC Server Automation version 8.9.
Note: Patching and virtual provisioning support for Windows 2016 is available in BMC Server Automation version 8.9 hotfix 1. See the blog on BMC Communities for information about obtaining and applying the hotfix.
Ready-made PDFs are available on the PDFs page. You can also create a custom PDF.
From the Tools menu in the upper-right, select:
- Export to Word to export the current page to Word format
- Export to PDF to export the current page to PDF format
- Export branch to PDF to export the current page and its child pages to PDF format
Concepts, architecture, deployment, planning, and system requirements.
Information about installing the product and migrating product data.
Required post-installation configuration.
Upgrade process, migration, and configuration.
Issues resolution, error messages, logs, and contacting Support.
Interface descriptions, using the product.
Security, system administration, maintenance.
Development interfaces and toolkits.
Integrations with other products.
The following sections describe enhancements for BMC Server Automation version 8.9.00.
- Video – What's new in version 8.9.00?
- Installation and upgrade enhancements
- Compliance Content and Compliance enhancements
- Patch management enhancements
- Support for patching using SuSE patches
- Patch remediation using a single Deploy Job
- Patching SuSE Linux Enterprise Servers based on specific security vulnerabilities and exposures
- Support for creating SuSE patch catalog using child channels
- Support for patching Red Hat Enterprise Linux running on IBM's Power Architecture-based processors
- Content Delivery Network (CDN) patching support for Red Hat
- Patch management issue with version 8.9 agents
- Live Reporting dashboard enhancements
- Job enhancements
- Administration enhancements
- New walkthrough topics added in this release
- BLCLI enhancements
- Updated statement of support for Advanced Repeaters
- Changes in OS support in BMC Server Automation version 8.9
For information about issues corrected in this release, see Known and corrected issues.
Video – What's new in version 8.9.00?
The following video (8:26) presentation provides a high-level summary of the new features and enhancements in version 8.9.00 of BMC Server Automation.
Installation and upgrade enhancements
The following enhancements have been introduced in BMC Server Automation 8.9.00 for Installation features:
Console no longer installed by default by the Unified Product Installer
The Unified Product Installer (UPI) no longer installs a BMC Server Automation Console by default on the same host computer with the primary, default BMC Server Automation Application Server. For high performance of BMC Server Automation, BMC recommends installing the Console on a separate machine after running the UPI.
You can still choose to have the UPI install the BMC Server Automation Console, using the following methods:
- In an interactive installation, a new tab now appears in the interactive wizard, with a check box that you can select for installing the Console.
- In a silent installation, include the following line in the options file:
Additional options supported by UPI in silent installation and upgrade
Several options that were already supported by the UPI in an interactive upgrade are now supported also in a silent upgrade. These include options in the following categories:
- A PXE Server option that enables you to specify a list of remote PXE servers for the upgrade.
- Agent options that authorize the installer to install an RSCD Agent on any remote server where an RSCD Agent is not yet installed at the time of the upgrade.
Backward support for earlier client version obviates need for upgrade
Version 8.9 of the BMC Server Automation Application Server supports communication with earlier clients — the BMC Server Automation Console version 8.8 and the BLCLI (command line interface) version 8.8 — and you can choose not to upgrade such clients.
To enable this backward support for any specific Application Server, you must turn off the version compatibility check that occurs whenever you access the Console. To do this, set the blasadmin command
versioncompabilitycheck to a value of
skip, instead of the standard value of
micro. Use the following blasadmin command:
set appserver versioncompabilitycheck skip
This blasadmin command takes effect immediately, and you do not need to restart the Application Server.
The blasadmin command turns off the version compatibility check for all Consoles that are associated with a specific Application Server. For Consoles that are installed on Windows, this blasadmin command also prevents the display of the Incompatible Version error message discussed in BMC Server Automation Console Automatic Upgrade: Windows only.
An upgrade will reset the value of versioncompatibiltycheck back to micro.
Note that BLCLI 8.8 connections are supported even without turning off the version compatibility check.
The backward support of version 8.8 clients has the following limitations:
Management of maintenance windows will not work properly in a console of version 8.8.
Creation, modification, or update of a Red Hat patch catalog is not possible in a console of version 8.8.
Creation, modification, or update of a SuSE patch catalog is not possible in a console of version 8.8.
Import of depot objects (such as system packages) does not work properly in a console of version 8.8.
- In an environment with a Network Shell proxy server and SOCKS proxy server, execution of custom commands through a console of version 8.8 fails on servers that are behind the SOCKS proxy due to failure in resolving the host name.
- Git version management of NSH scripts does not work in a console of version 8.8.
Compliance Content and Compliance enhancements
The following enhancements have been introduced in BMC Server Automation 8.9.00 for Compliance features:
New templates in Compliance Content for supporting additional policies and platforms
BMC Server Automation now supports the following additional Compliance Content component templates:
|Operating System||OS version||Benchmark version||Benchmark update|
|Microsoft Windows Server||2008 R2||3.0||November, 2013|
Existing templates that are updated in version 8.9 are as follows:
|Policy||Operating system||OS version||Benchmark version||Benchmark update|
|DISA||Microsoft Windows Server||2012 Domain Controller||Version 2/Release 4||April, 2016|
|2012 Member Server||Version 2/Release 4||April, 2016|
|2008 Domain Controller||Version 6/Release 1.32||April, 2016|
|2008 Member Server||Version 6/Release 1.32||April, 2016|
|Red Hat Enterprise Linux ES/AS||6.x||Version 1/Release 11||April, 2016|
|5.x||Version 1/Release 14||April, 2016|
|CIS||Microsoft Windows Server||2012 R2||Version 2.2.0||April, 2016|
For complete list of available templates, see Compliance policy standards supported by BMC Server Automation templates.
Patch management enhancements
The following enhancements have been introduced in BMC Server Automation 8.9.00 for patch management features:
Support for patching using SuSE patches
BMC Server Automation 8.9 now supports SuSE patches for SuSE Linux Enterprise Servers (SLES) 11 and later versions. You can add SuSE patches to a SuSE patch catalog from the update type of repository. After the SuSE catalog update job is run successfully, the SuSE Patches are available in the Depot.
For example, to add SuSE patch information for SLES 11 SP3, while adding a filter, select SLES-11-SP3-Updates from the Available Repos drop-down menu. For more information about creating a SuSE patch catalog, see Creating a patch catalog.
For details on creating a configuration file for an offline SuSE catalog with SuSE patch type filters, see Preparing the configuration file for SUSE Linux Enterprise.
Patch remediation using a single Deploy Job
In earlier (pre-8.9) releases, BMC Server Automation created multiple Deploy Jobs during patch remediation for deployment of multiple BLPackages on multiple target servers. Starting with version 8.9 of BMC Server Automation, a single Deploy Job is created, by default, for the deployment of multiple BLPackages on multiple target servers.
You can still choose to have multiple Deploy Jobs created during patch remediation, as was the standard behavior in earlier versions of BMC Server Automation. To switch between a single Deploy Job and multiple Deploy Jobs, use the new Use Single Deploy Job setting in the Patch Global Configuration dialog box.
If you are performing patch remediation on Solaris servers, where some of the target servers are Guest LDOMs and other target servers are Primary LDOMs, two Deploy Jobs are created instead of a single Deploy Job. One Deploy Job is created for all Guest LDOM target servers and another Deploy Job is created for Primary LDOM target servers.
A Deploy Job for patch remediation that deploys multiple BLPackages on multiple target servers has the following limitations:
- You cannot include such a job in an Execution Task.
- You cannot execute such a job against specific targets using the Execute Against option (described in Executing a job against specific targets) or the BLCLI command Job executeAgainstServers.
- You cannot export such a Deploy Job, whether through the UI or using the BLCLI command ImportExport exportObject.
After job creation, configuration of a Deploy Job that deploys multiple BLPackages to multiple targets has the following limitations:
You cannot associate a different BLPackage with the job. On the Deploy Job - Package tab, only the first detected BLPackage (of multiple BLPackages) is displayed in the Package field and you cannot choose a different BLPackage.
You cannot add target servers to the job, whether through the UI (on the job's Deploy Job - Targets tab) or using BLCLI commands (such as DeployJob - addNamedServerToJobByJobDBKey and Job - addTargetServer).
Patching SuSE Linux Enterprise Servers based on specific security vulnerabilities and exposures
The MITRE Corporation maintains a system for publicly known information security vulnerabilities and exposures. Each security vulnerability or exposure is referenced by a Common Vulnerabilities and Exposures (CVE) ID. BMC Server Automation includes the CVE ID of a patch in its properties. This allows you to create patch smart groups based on SuSE Patch CVE IDs, and apply the patches on the SuSE servers based on specific vulnerabilities and exposures.
Support for creating SuSE patch catalog using child channels
BMC Server Automation now supports patching for supplementary child channel RPMs on SuSE. To select child channels, while creating the SuSE catalog, under Filters, click . You can then select child channels from the Available Repos drop-down list, as shown in the following screenshot:
The Available Repos drop-down list contains child channels, as well as Update and Pool base channels.
Support for patching Red Hat Enterprise Linux running on IBM's Power Architecture-based processors
BMC Server Automation now supports the patching of Red Hat Enterprise Linux operating systems that run on servers with IBM's Power Architecture-based processors (ppc64 pSeries).
Content Delivery Network (CDN) patching support for Red Hat
You can now download patches from the CDN (reposync) Red Hat network. The following table lists the OS version-Architecture combination of patches that are supported by the CDN (reposync) Red Hat network
|RHEL version||Supported processor architectures||Support for child channels|
|RHEL 6 and 7||
You can also use the CDN (reposync) Red Hat network to add Update-level type of filter for all RHEL versions.
Patch management issue with version 8.9 agents
Servers on RedHat Enterprise Linux version 5 (or earlier) are not supported as patching targets if they have a BMC Server Automation agent of version 8.9 installed. For a RHEL 5 target, you must either apply a component template fix (available from Knowledge Article 000120867) to the 8.9 agent, or use an earlier version of the agent (for example, version 8.6 or 8.7, but not 8.8).
Live Reporting dashboard enhancements
The Live Reporting dashboard capability delivered in version 8.9 is a product feature that is supported using an integration with Yellowfin. BMC Server Automation (BladeLogic) does not require a license key; however, use of Yellowfin does. A limited-use license key has been enabled as part of the Yellowfin installation process.
Use of Yellowfin technology is provided in conjunction with the Live Reporting dashboard capability of BMC Server Automation. Use of Yellowfin for capabilities other than the Live Reporting dashboard or independently of the integrated BMC Product is prohibited.
In version 8.8, BMC Server Automation introduced the Live Reporting dashboard (based on Yellowfin technology), which displayed complete information about patch management in one consolidated view. In version 8.9, the scope of the dashboard has been expanded to display live data for compliance and job activities in your environment, in addition to patch management.
The expanded Live Reporting dashboard now displays three tabs, each providing real-time core data:
- Patch tab – current, historical, and cohort analysis views of patch-related data
- Compliance tab – current, historical, and cohort analysis views of compliant servers
- Job Activity tab – successful and failed jobs run on your servers
Each of these tabs includes multiple reports, which you can use to review up-to-the-minute compliance, patch, and job activity. The Patch and Compliance tabs each present three different ways to view the data: a current view, a historical view, and a cohort analysis view. The Cohort Analysis view enables you to identify the patch management or policy compliance ratio (as a percentage) for specific server groups.
For most reports, you can drill down to see additional data (for example, how many servers are actually compliant per a given policy, as shown below).
You can easily export reports, for example, in PDF format, for closer examination or for sharing with others in your organization. For more information about using the dashboard, see the following topics:
- Using the Live Reporting dashboard
- Live Reporting dashboard Patch reports
- Live Reporting dashboard Compliance reports
- Live Reporting dashboard Job Activity reports
The Live Reporting dashboard can be accessed from the Configuration menu in the console. However, before you use Live Reporting, you must install and configure the Yellowfin business intelligence tool. See Installing and configuring Yellowfin to enable Live reporting and Using the Live Reporting dashboard for more information.
If you installed and configured the Yellowfin environment in BMC Server Automation version 8.8, you must upgrade the Yellowfin environment prior to using the Live Reporting dashboard in version 8.9. See Upgrading Yellowfin for Live Reporting.
The following enhancements have been introduced in job management in BMC BladeLogic Server Automation 8.9.00:
Improved performance of NSH Script Jobs of Type 1 in large environments
The performance of NSH Script Jobs for scripts that contain the blcli_execute command has been enhanced by the introduction of a new method for handling BLCLI execution with a new BLCLI Server service. Execution of NSH scripts of Type 1 that run BLCLI commands on large numbers of target servers now involves less resources. As a result, NSH Script Jobs take less time and do not risk crashing the Application Server.
A new blasadmin parameter,
, enables you to control the use of the new BLCLI Server service by the Application Server. By default, this parameter is set to
true (that is, the BLCLI Server service is enabled), but you can disable this service if necessary for troubleshooting purposes.
Version management of NSH scripts includes script parameters
Git-based version management of NSH scripts now includes management of changes to script parameters. Whenever you commit a new version of an NSH script, parameter information is stored in the repository, along with the content of the script, in a separate json file.
The stored parameter information is displayed when you compare versions of the script. A comparison action now opens two tabs — one for the comparison of script content, and the other for the comparison of parameter information.
Note that any versions of the NSH script that were committed to the repository before upgrading to BMC Server Automation 8.9 will not have parameter information stored. For such script versions, no comparison of parameters will be available. Similarly, when reverting to such a version of the script, the parameters will not be reverted. In addition, if you select to associate such a version of the script with an NSH Script Job (see Selection of NSH script revision in an NSH Script Job), the job uses current parameter information rather than historical parameter information.
Selection of NSH script revision in an NSH Script Job
During creation of an NSH Script Job, or when modifying an existing NSH Script Job, you can now select the version of the NSH Script to associate with the job, using the new Script Version field in the Network Shell Script Job - General panel or tab. By default, the latest version of the script is used, which might include saved changes that have not yet been committed to the repository, and you can instead select any previously committed version of the script.
The option for selecting the NSH script version is available, provided that you have set up Git-based version management and have, over time, committed a history of versions of the NSH script to your repository, as described in Walkthrough: Managing versions of NSH scripts using Git.
Log package for job run of a BLPackage Deploy Job or Patch Analysis Job
You can now generate a zip package that contains comprehensive diagnostic information for a job run of a BLPackage Deploy Job or Patch Analysis Job. This zip package contains various files with log messages related to the job run, and it is especially useful for diagnostic purposes when you contact Customer Support. The new Download Log Package menu option was added to job runs in the Job Results view for BLPackage Deploy Jobs and Patch Analysis Jobs.
For more information, see Generating a log package for a BLPackage Deploy Job run or Patch Analysis Job run.
Integration with BMC Change Automation
The new BMC Change Automation solution is an integration between BMC Server Automation and BMC Remedy Change Management, with BMC Atrium Orchestrator facilitating the communication between these two applications. This solution improves overall efficiency and effectiveness of IT Operations through improved automation and coordination of Change Management activities.
Existing procedures for the setup of an integration between BMC Server Automation and the BMC Continuous Compliance for Server Automation solution have been enhanced to enable setup of the new integration with BMC Change Automation. These integration setup procedures are accessed through a new Integration Configuration menu option under the Configuration menu in the BMC Server Automation Console, as described in Enabling Change Automation for BMC Server Automation jobs.
Integration of BMC Server Automation with BMC Change Automation offers the following benefits in job management:
- Option to require BMC Remedy ITSM approval prior to job execution, to support the Operator-Initiated Change (OIC) use case of BMC Change Automation.
- Option to create an incident in BMC Remedy ITSM if the job fails.
- Option to publish a Deploy Job or an NSH Script Job as a task template in BMC Remedy ITSM, to support the Change-Initiated Job (CIJ) use case of BMC Change Automation.
Initial setup of the new integration is optional, and you can, instead, choose to continue using the integration with Remedy ITSM that existed previously for BMC Continuous Compliance. Once you perform the setup for configuration with BMC Change Automation, you cannot revert to the previous integration setup.
The following enhancements to BladeLogic administration have been introduced in BMC BladeLogic Server Automation 8.9.00:
Improved performance of secure connections with target servers behind a SOCKS proxy
behind_socks option has been introduced in the secure file for
host entries. This option enables you to indicate which target servers are running behind a SOCKS proxy. This helps improve performance when a TCP/IP connection is established with a target server that is running behind a SOCKS proxy, by avoiding undesirable hostname-IP lookups on the client node or on Application Server nodes. For more information about using this new option, see Configuring the secure file.
Enhancements in maintenance windows
When you create a maintenance window, for a server or group of servers, all commit operations of Deploy Jobs must be executed within that maintenance window. If the commit phase of a Deploy Job is run outside of this time interval, the Deploy Job fails with an error. The following enhancements have been introduced into the management and behavior of maintenance windows:
- You can now temporarily deactivate and subsequently activate a maintenance window, using the new Activate/Deactivate toggle button that appears in the Maintenance Window Management dialog box.
- If the commit phase of an Advanced Deploy Job started executing during a maintenance window but is still running when the maintenance window ends, you can now choose between two options for job behavior:
- Pause the job. When the next maintenance window begins, you can rerun the job, and it will resume from where it left off.
This behavior is available only for Advanced Deploy Jobs on Windows servers, and it is now the default behavior for this job type.
Note that for jobs created before upgrading to BMC Server Automation 8.9, the option to pause the job is not selected by default. Furthermore, this option is only available on targets that are running an RSCD Agent of version 8.9 or later.
- Allow the job to complete (because it started during the maintenance window).
This was the standard behavior in the previous version of BMC Server Automation, and it is still the standard behavior for other types of Deploy Jobs.
- Pause the job. When the next maintenance window begins, you can rerun the job, and it will resume from where it left off.
For more information, see Walkthrough: Defining a fixed time period for running deploy jobs or patching a server.
Exclusion window for periods of time with no job execution on target servers
A new type of window has been introduced for controlling the execution of BMC Server Automation jobs on target servers and avoiding over-utilization of resources on the servers. The new exclusion window defines a period of time during which no BMC Server Automation jobs (of any type) are allowed to run on specified target servers. If you run a job during an exclusion window, the job fails with a warning.
If a job started executing before the beginning of the exclusion window, job behavior depends on the job type:
- All job types except for Advanced Deploy Job on Windows servers — The job will be allowed to complete.
- Advanced Deploy Job on Windows servers — By default, the job is paused. When the exclusion window ends, you can rerun the job, and it will resume from where it left off. You can choose to allow the job to complete, instead of pausing, by adjusting the Maintenance and Exclusion Window options in the Phases and Schedules settings of the job.
Note that for jobs created before upgrading to BMC Server Automation 8.9, the option to pause the job is not selected by default. Furthermore, this option is only available on targets that are running an RSCD Agent of version 8.9 or later.
Through the new Exclusion Window Management dialog box you can define multiple exclusion windows. Each window can be associated with one or more servers or with a server smart group. For more information, see Walkthrough: Defining a time period to block all job execution.
If the time period that you define for an exclusion window on a certain server overlaps the period defined for a maintenance window on the same server, the exclusion window takes precedence. From the time that the exclusion window begins and until it ends, the maintenance window is ignored.
GUI operations are not blocked by the exclusion window. For example:
- Certain operations that are performed by BMC Server Automation jobs can be performed by alternative methods through the GUI. The exclusion window blocks job execution, but does not block you from performing the operation through the GUI. For example, an ACL Push Job will not run during the exclusion window, but you can push ACLs manually through the GUI. Similarly, you cannot run a Network Shell Script Job, but you can run NSH commands manually.
- Even GUI operations that involve communication with target servers (such as displaying server information in Live Browse or Active Node view) are allowed during an exclusion window.
Tracking server association and other definitions of maintenance windows and exclusion windows
To help you keep track of your maintenance windows and exclusion windows and to figure out which servers are associated with which window, the following new features have been introduced:
- Two new properties were added to the Server property class, EXCLUSION_WINDOW* and MAINTENANCE_WINDOW*. You can use these properties to group servers in a smart group based on the association of these servers with a specific maintenance window or exclusion window. Such a smart group is useful when you need to select servers, especially when selecting targets for a job.
- You can now export the basic definitions and properties of all defined maintenance windows and exclusion windows to CSV, using the Export Exclusion/Maintenance Windows menu option. This option is available for any server group (static group or smart group) and for the Server root node (that is, for all servers).
New walkthrough topics added in this release
Walkthrough topics introduce you to a key BMC Server Automation use case (for example, compliance), and provide step by step, cookbook-style examples that demonstrate a specific aspect of that use case. The following walkthrough topics were added in 8.9:
For a full list of available walkthrough topics, see FAQs and additional resources.
The following table lists the new BLCLI commands that support developments and enhancements in BMC BladeLogic Server Automation 8.9.00:
BLCLI commands added or updated in version 8.9.02
|Delete||cleanupHistoricalData OldVersionComponent||(New) Deletes older version of components that have no association in Snapshot, Audit, or Compliance modules.|
|Delete||cleanupHistoricalData OldVersionJob||(New) Deletes older version of jobs that have no runs associated with that version.|
|AgentInstallerJob||setAgentInstallerJobInstallVCRuntime||(New) Update the MSVC option (Install Microsoft Visual C++ 2015 Redistributable (Windows Only)) for the new Agent Installer Job.|
|PatchingJob||createRedhatPatchingJobWithTargetServer_2||(New) Creates a Patching Job that is run against an individual server, using an existing Red Hat catalog.|
|PatchingJob||createRedhatPatchingJobWithTargetServer||(Updated) Creates a Patching Job that is run against an individual server, using an existing Red hat catalog.|
|JobRun||getJobRunIdByScheduleId||(New) Returns the Job Run ID for a given Schedule ID.|
|JobRun||(New) Returns the Job Run Key for a given Schedule ID.|
|NSHScript||getNSHScriptParamValuesString||(New) Retrieves the parameters for the NSH Script Job as a string where each entry is shown as
|BlPackage||createEmptyPackageReturnDBKey||(New)This command creates an empty BLPackage and returns handle to it.|
BLCLI commands added or updated in version 8.9.01
|BlAclTemplate||listAllAclTemplates||(Updated) Provides a list of ACL templates without further details.|
|listAllAclTemplatesWithDetails||(New) Provides a list of ACL templates that includes details of template properties.|
(New) Creates a compliance exception with one rule, reference number, and expiration date and sets it on a component.
|Delete||cleanupFileServerWithEmptyDirectoryScan||(New) Cleans all the unused files from the file server and runs the empty directory scan.|
BLCLI commands added in version 8.9.00
Updated statement of support for Advanced Repeaters
Advanced repeaters are no longer supported beginning with version 8.9.
Changes in OS support in BMC Server Automation version 8.9
This section lists the changes in OS support in BMC Server Automation version 8.9. For a complete list of supported platforms for the various components, see the Supported platforms for version 8.9.
Patching and virtual provisioning support for Windows 2016 is available in BMC Server Automation version 8.9 hotfix 1. See the blog on BMC Communities for information about obtaining and applying the hotfix.
New platform support for product components
The following table lists new combinations of operating systems and components that are supported in BMC Server Automation 8.9. (A plus sign indicates support.)
Platform / Version
|Microsoft Windows version 2016||(virtual) 1||1|
|IBM AIX version 7.2|
|Red Hat Enterprise Linux versions 6 and 7 on zSeries server|
SuSE versions 11 and 12 on zSeries server
1 Patching and virtual provisioning support for Windows 2016 is available in BMC Server Automation version 8.9 hotfix 1. See the blog on BMC Communities for information about obtaining and applying the hotfix.
Deprecated platform support in version 8.9
BMC Server Automation 8.9 no longer supports the following platforms:.
- IBM AIX 5.x: This support has been deprecated for both patch management and agent support. Note that you cannot edit an AIX 5.x patch catalog in 8.9, even if the patch catalog was created in an earlier version.
- Solaris version 9: This deprecated support applies to all product components.
- SuSE Enterprise Linux version 9 and version 10: This deprecated support applies to all product components.
- Windows Server 2003: This deprecated support applies to all product components.
Support has been deprecated for the following OS versions, as they have reached end of support life:
Ubuntu 10.x and 11.x
Debian 5.x and 6.x
VMWare ESX 4.x
Frequently asked questions
This section provides answers to frequently asked questions (FAQs) about BMC Server Automation.
For supported version information, see the following BMC Support Support page:
Note that as of June 26, 2012, version 7.x releases are no longer supported.
The BMC Knowledge Base (which includes answers for common problems with BMC Server Automation) is located at https://bmcsites.force.com/casemgmt/sc_CoveoSearch#q=BMC%20Server%20Automation&t=KB&sort=relevancy
See the ports and protocols list.
You can find the build number for the various releases (base version, SPs, and patches) in Preparing for a Windows upgrade using the unified product installer or Preparing for a Linux or UNIX upgrade using the unified product installer.
See the following documentation resources:
- For information about enabling the retrieval of change information from BMC BladeLogic Server Automation for Probable Cause Analysis (PCA), see the chapter about integrating with BMC Server Automation in the BMC ProactiveNet User Guide.
- For information about transferring data to BMC PATROL and BMC ProactiveNet regarding the status, availability, and performance of hosts and servers managed by BMC Server Automation, see the online documentation for BMC PATROL for BMC Server Automation and BMC ProactiveNet Automation Server Monitoring.
Installation and upgrade questions
You can find information about the supported upgrade paths for BMC Server Automation in the Upgrading using individual component installers section of the online technical documentation (in the Preparing for a Windows upgrade using the unified product installer or Preparing for a Linux or UNIX upgrade using the unified product installer topics).
You can find deployment architecture recommendations in the following Planning section: Deployment use cases
Check the debug level rscd.log file on the Psexec server.
You can also try to convert the blpsexec command from rscd.log to native psexec command and try to execute it on psexec server from Administrative command prompt (cmd.exe started as “Run as Administrator”).
blpsexec -s winserv.bmc.com -u Administrator -p TNEKNUDRFET -h cmd /c hostname
psexec \\winserv.bmc.com -u Administrator -p password_of_Administrator_user -h cmd /c hostname
Internal version of Visual C++ 2015 and 2017 is same (i.e. 14.0). So when we try to install VC++ 2015 redistributable it detects that newer version is already installed on the server, so installation is skipped.
As Visual C++ 2017 is binary compatible with 2015, our product will still work with Visual C++ 2017 redistributable.
No. There won’t be any issue in communication between 2 components which are using different versions of redistributable.
General product usage
Use the following process:
- Start by looking at the rscd.log. Who are your requests currently mapping to? If it is someone who does not exist in your users or users.local file, consider adding a temporary definition for them.
- Remove the "nouser" line from the users file.
- Change the contents of the exports file so that it contains a single line: "* rw,user=root" or "* rw,user=Administrator" (or the name of your local admin account).
Once you have finished troubleshooting, make sure to restore the original configuration.
The following list shows some common causes for this issue:
- Review the Application Server log and look for a Java stack trace; this usually indicates the issue.
- A few common things can cause problems with the Application Server start up:
- The File Server RSCD Agent is not licensed (for pre-8.2 versions).
- ACLs were pushed to the File Server agent.
- Add a 'System:System rw,map=<root|Administrator>' to the users.local on the File Server agent.
In this case, you need to synchronize the bladelogic.keystore across all Application Servers.
See To synchronize keystore files of multiple Application Servers for more information.
See the following Knowledge Article for information on this issue:
Knowledge Article ID: 000022404
You can find recommendations for sizing Application Servers in Sizing Application Servers.
If the catalog is in Online mode, updating the catalog obtains any new patches or modifies existing patches that have changed. To prevent new patches from being downloaded, do not run the Catalog Update Job until you need new patches in the catalog.
If the catalog is in Offline mode, then to prevent new patches from being downloaded, you must ensure:
- The source location has not been updated by re-running the downloader
- The metadata file(s), if applicable, in the depot have not been changed since the last run
If you ensure the preceding items, running a Catalog Update Job does not add any new patch metadata or modify existing patch metadata.
While creating the Patching Job, from the Deploy Job options menu within the Remediation Options panel, select the Execute job now option. The same options are available while creating a remediation job from the Analysis results.
You can specify a schedule for any Job to ensure that it is executed every x hours.
You must create a custom property on an appropriate depot object. For example, to set certain criteria on a Windows Hotfix object, by selecting Property Dictionary View > Built-in Property Classes > Hotfix, you can add a new property. You can then create a new smart group using an appropriate condition to include this new property.
The job log of the Patching Job displays a warning message that indicates the filters that must be added so that all products on all targets that are part of the Patching Job are analyzed in the next run of the Patching Job. A sample warning message is shown below.
You can use the drop-down list in the Deploy Job options settings to get the desired information about the execution of that Deploy Job. For example, if you select the All Information option within Logging level, subsequent execution of the Deploy Job provides you with all information about the Deploy Job execution.
On UNIX, look in /etc/lib/rsc/HOME or /usr/lib/rsc/HOME. If that file does not exist, you are running a local or self-contained installation, and will need to derive the installation location from running processes. For example:
On Windows: INSTALL_DIR\RSCD\rscd.log
On UNIX: INSTALL_DIR/[NSH|RSCD]/log/rscd.log
The default deployment name is appserver, while other common deployments have names such as job-1.
For detailed instructions on analyzing the Trace.txt file, see How to analyze Trace.txt generated by a Windows Patch Analysis Job (user contribution).
Top Knowledge Articles from BMC Customer Support
BMC Communites maintains a list of the top 10 Knowledge Articles (KAs) as recommended by the Customer Support team for BMC BladeLogic Server Automation.
The KAs are selected by a combination of both the collective experience of the team and other quantitative factors, with the goal of sharing the most relevant and useful information in a easy to consume format.
See Top 10 Knowledge Articles for BladeLogic Server Automation on BMC Communities for the list.
Walkthrough topics introduce you to a key BMC BladeLogic Server Automation use case (for example, compliance), and provide step by step, cookbook-style examples that demonstrate a specific aspect of that use case.
|Getting started with automation||
The following BMC sites provide information outside of the BMC Server Automation documentation that you might find helpful:
- BMC Communities, Server Automation community, where you can find a series of Best Practice webinars
- BMC Support Knowledge Base, search filtered by BMC Server Automation
- BMC Educational Services, BMC Server Automation learning path
- BMC Global Services, BMC Server Automation offerings
- www.bmc.com, information about BMC Server Automation
The following table lists topics that contain videos that supplement or replace the text-based documentation. To see additional videos about BMC BladeLogic Server Automation and other BMC solutions, visit BMCtv.
|Category||Topics with videos|
|Live Reporting Dashboard||