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.

BMC Server Automation, one of BMC's digital enterprise automation solutions, allows you to quickly and securely provision, configure, patch, and maintain physical, virtual, and cloud servers.
Release notes and notices
updated 09 Nov
This section provides information about what is new or changed in this space, including urgent issues, documentation updates, service packs, and patches.

Placing a watch on this page is a great way to stay informed of changes to this space.




July 07, 20178.6.01.02 Hotfix-1: Support for CDN channels for Red Hat PatchingAnnounces a hotfix for BMC Server Automation 8.5.01, which provides a fix for RHEL patching. 
October 15, 2016Version Patch 2 for Service Pack 1Lists the updates introduced in BMC Server Automation version 8.6 Patch 2 for Service Pack 1.
June 14, 2016Notification of Windows RSCD Agent vulnerability in BMC Server Automation CVE-2016-5063Alerts users to a security problem in the RSCD agent on Microsoft Windows platforms for all versions of BMC Server Automation, up to and including version 8.7 Patch 2, as well as in any BMC solution that includes this technology.
March 2, 2016Notification of critical security issue in BMC Server AutomationAlerts users to a security problem in the RSCD agent on UNIX and Linux platforms for all versions of BMC Server Automation, as well as in any BMC solution that includes this technology.
December 3, 2015Version Patch 1 for Service Pack 1Lists the updates introduced in BMC Server Automation version 8.6 Patch 1 for Service Pack 1.
May 18, 2015Service Pack 1: version 8.6.01Lists the updates and enhancements introduced in BMC Server Automation version 8.6 Service Pack 1.
December 17, 2014Patch 1: version the updates introduced in BMC Server Automation version 8.6 Patch 1.

December 11, 2014

8.6.00 enhancements and updates

Lists the enhancements introduced in BMC Server Automation version 8.6.


Ready-made PDFs are available on the PDFs page. You can also create a custom PDF.

 Click here to see the steps.

The BMC Documentation portal gives you the ability to generate PDF and Microsoft Word documents of single pages, and to create PDF exports of multiple pages in a space.  

Creating PDF and Word exports

You can create a PDF of a page or a set of pages. (Non-English page exports are not supported.) You can also create a Word document of the current page.

To export to PDF or Word

  1. From the Tools menu in the upper-right, select a format:
    • Export to Word to export the current page to Word format
    • Export to PDF to export the current page or a set of pages to PDF
  2. If exporting to PDF, select what you want to export:
    • Only this page to export the current page
    • This page and its children to export a set of pages
    For example, selecting This page and its children from the home page exports the entire space to PDF.




Concepts, architecture, deployment, planning, and system requirements.



Information about installing the product and migrating product data.

Configuring after installation


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.
What's new?


For information about the updates included in service packs and patches for this release, see the following pages:

The following sections describe enhancements for BMC Server Automation version 8.6.00:


For information about issues corrected in this release, see Known and corrected issues.

Installation and upgrade enhancements

BMC Server Automation version 8.6 includes the following enhancements to installation functionality:

Unified product install and upgrade

BMC Server Automation 8.6 provides a single installer for most installation and upgrade scenarios within the BMC Server Automation environment. The unified product installer simplifies and improves the installation experience by providing a centralized UI for installation and upgrade of all BMC Server Automation components. For more information about the unified product installer, see Installing using the unified product installer and Upgrading on Windows using the unified product installer. 

The unified product installer installs and configures BMC Server Automation components by grouping them into functional units called nodes. The first node that is installed by the unified product installer is called the Default Application Server node. It comprises an Application Server, PXE server, database, network shell, file server, and BMC Server Automation Console.  To meet the demands of a larger data center, you can deploy additional Application Servers. The additional Application Server is used for improving the performance of BMC Server Automation. For more information about adding an Additional Application Server after the Default Application Server node is installed, see Adding additional Application Servers.

Maintaining all configuration data on the database

With the release of BMC Server Automation 8.6, the latest copy of all configuration data is now maintained on the database. When an Application Server is started, it uses the configuration data that is stored on the database. 

Migration of the configuration data is performed automatically by the unified product installer during upgrade. For cases where the unified product installer cannot be used, BMC Server Automation provides the configurator utility, which performs the database migration and persists configuration data into the database. You run the configurator on all Application Servers and PXE servers. For more information about migrating the configuration data manually, see Migrating the database and persisting configuration data to the database.

Quick start page

This is the first page that is displayed when you launch the BMC Server Automation Console after a fresh installation. It provides you a centralized access to options that execute most major use cases for Infrastructure ManagementCompliance, Provisioning, Patching, and Configuration Management. For more information about using each of these options, see Quick start page.

Support for installing agents behind a SOCKS proxy server

BMC Server Automation now supports the installation of RSCD Agents on target servers that are behind a SOCKS proxy. For more information about the necessary configuration, see the list of preliminary tasks in Agent installation overview.

Compliance Content, Compliance, and SCAP enhancements

The following enhancements have been introduced in BMC Server Automation 8.6.00 for Compliance features:

New templates in Compliance Content for supporting additional policies and platforms

BMC Server Automation version 8.6 supports following Compliance Content component templates:

Operating systemVersionDISAPCIv3CIS
  Bench - mark versionBench - mark updateBench - mark versionBench - mark updateBench - mark versionBench - mark update
Microsoft Windows Server2012 R2 Domain ControllerVersion 1/Release 4July, 2014    
 2012 R2 Member ServerVersion 1/Release 4July, 2014    


7.1  3.0November, 20131.1.0September, 2013
 6.1Version 1/Release 2July, 2014    
 5.3  3.0November, 20131.1.0September, 2012
Novell SuSE Linux® Enterprise Server11  3.0November, 20131.0.0September, 2013
 10  3.0November, 20131.0.0September, 2013
Oracle™ Solaris™11 x86Version 1/Release 1April, 2014    
 11 SPARCVersion 1/Release 1April, 2014    
 10 x86Version 1/Release 5January, 2014    
 10 SPARCVersion 1/Release 5January, 2014    

For complete list of available templates, see Compliance policy standards supported by BMC Server Automation templates.

The CIS SUSE 10 template is derived from CIS SUSE 11. Following rules are unique to CIS SUSE 10 template:

  • 1.6 seccheck is active
  • 2.1.1 Disable Standard Services
  • 2.1.2 Disable Standard Services
  • 3.3 Disable remote SMTP connections
  • 3.4 Disable GUI Login If Possible
  • 3.5 Disable X Font Server If Possible
  • 3.6 Disable Standard Boot Services (not scorable)
  • 3.13 Only Enable ncpfs Script If Absolutely Necessary
  • 3.17 Only Enable SQL services If Absolutely Necessary
  • 5.1 syslog is active
  • 7.1 Remove .rhosts Support In PAM Configuration Files
  • 7.2 /etc/ftpusers (not scorable)
  • 7.6 Configure xinetd Access Control (not scorable)
  • 7.10 Restrict NFS Client Requests To Privileged Ports
  • 9.3 Create "authorized only" Banners For vsftpd, If Applicable
  • 12.1 Create Symlinks For Dangerous Files

Inclusion of commands as assets in a Compliance rule

The Rule Editor for compliance rules now has enhanced support for shell scripting commands.  A new Command asset is introduced, with various attributes for several forms of command outputs. Using this new asset type, you can create a rule condition that checks for a specific command output. This replaces the need to define such commands through a local configuration object in the component template. For more information see Defining a basic condition.

Defining variables in Compliance rules

You can now define a variable within a Compliance rule by assigning a value to a local property of the component template. You can then use your property-based variable in subsequent conditions in the same rule. The following new operators have been introduced to support this new feature:

  • The assign operator (represented by the := combination of characters) can be used to assign a transient value that is not saved to the database, but rather temporarily stored only for the duration of rule execution. Use this operator if you want to avoid unnecessary storage of data in the database and do not plan to perform remediation based on the results of the compliance rule analysis.
  • The persist operator can be used to assign a value that is persisted in the database. Use this operator if you plan to perform remediation based on the results of the compliance rule analysis.

For more information see Defining a basic condition.

New file/directory properties

The following file/directory properties have been added in BMC Server Automation. These properties can be used in a BLPackage, can be viewed in Live Browse, and can also be used in Compliance rules.

Property NameTypeDescription
User Owner Name StringThe name of the user owning the file/directory.
Group Owner NameStringThe name of the group owning the file/directory.
Unix ACLBoolean (true/false)Whether an Access Control List (ACL) is defined on the file (true or false).


These properties are not visible for a directory in Live Browse.


If you are using the following new artifacts, you will not be able to import their templates in versions prior to BMC Server Automation 8.5 SP1:

  • Command Support
  • List[String], String/Integer Enumeration  using LOOP_ATTR_FOR_COMPLIANCE_STR/ LOOP_ATTR_FOR_COMPLIANCE_INT

  • Assign Operator (:=)

Added new configuration files

BMC Server Automation includes new configuration files for following operating systems:

Operating SystemConfiguration files







Oracle™ Solaris™






























For complete list of configuration files, see Configuration files.

Examples for creation of compliance rules added in the documentation

See Examples for creating compliance rules for detailed examples of rules that use command and variable support.

New reports available for export from compliance results

Changes were introduced in the formats of reports that you can generate by exporting results of a Compliance Job. The following types of reports are now available:

  • View-friendly and print-friendly HTML report that is based on JavaScript Object Notation (JSON) data files —
    This new report format is generated from Compliance Job results using the Export Compliance Results menu option. The report summarizes the levels of rule compliance on the target servers, and enables you to drill down to details about any individual rule at any server, so that you can learn more about the deviation of the actual rule results from the expected results.

    The report provides you with two views:

    • Summary by Servers — a list of the servers, with statistics about the rules that failed or were compliant on each server
    • Summary by Rules — a list of the rules, with statistics about the servers where each rule failed or was compliant

Support for SCAP 1.2

BMC Server Automation now supports compliance analysis for the most recent Security Content Automation Protocol (SCAP) version 1.2 in addition to the existing support for SCAP 1.0. Two different import options now exist, depending on the type of SCAP object — whether an SCAP data stream collection (a single XML file) for SCAP 1.2, or an SCAP benchmark (several XML files).

The imported SCAP 1.2 content is displayed in the BMC Server Automation Console through 3 hierarchical nodes — an SCAP data stream collection, one or more data streams contained in the collection, and finally one or more benchmarks within each data stream.

As part of the support for SCAP 1.2, BMC Server Automation now also supports the import of SCAP 1.2 content that contains tailoring files, which are used to temporarily tweak benchmark rules by customizing profiles in an XCCDF file. During SCAP compliance analysis, BMC Server Automation applies the changes captured in the tailoring file to rule evaluation.

After running a SCAP Compliance Job the following new options are available for the export of SCAP compliance results:

  • During an export of an XCCDF results file (using the Export SCAP Compliance menu option), you can now choose which rules to include in the export — all rules, failed rules, or passed rules.
  • The Export Other SCAP Formatsmenu option now offers the following new report formats that are compliant with SCAP 1.2 (in addition to the formats previously provided for SCAP 1.0):
    • Asset identification (AI) version 1.1
    • Asset Reporting Format (ARF) version 1.1

Deploy functionality enhancements

New BLPackage object attributes enable you to deploy a BLPackage with the objective of manipulating the properties of Windows user accounts at the target servers. User asset attributes enable you to set user account control flags or disable the user account. For more information, see Manipulating Windows user account properties through a BLPackage.

Patch management enhancements

BMC Server Automation version 8.6 includes the following enhancements to patch management:

AIX patching support for SUMA

You can now download AIX patches from Fix Central servers using IBM Service Update Management Assistance (SUMA). You can select the SUMA download option while creating an AIX patch catalog. For more information about enabling this option, see Patch catalog - AIX Catalog.

Removal of dependency on Windows Helper Server location

For creating a Windows patch catalog in versions earlier than 8.6, you had to define a Windows Helper Server location. BMC Server Automation used the Windows Helper server to decrypt shavlik metadata files that are downloaded from the vendor site.

However, in BMC Server Automation 8.6, the shavlik metadata files are decrypted on the Application Server itself and there is no requirement of defining a separate Windows Helper Server location.

To create a patch catalog in offline mode, you must download the oemcatalog.zip file Shavlik Technologies and save it in the depot workspace. You must provide the depot location of the file while creating the Windows patch catalog, as described in the Repository Options section of Patch catalog - Windows Catalog.

Patching support for multibos and alternate disk on AIX 

AIX has the capability of maintaining multiple instances of Base Operating Systems (BOS). The additional instance of the BOS can be maintained in the same root volume group (multibos) or on a separate disk on a separate root volume group (alternate disk). The user can boot any one instance of the BOS which is called the active instance.The instances which have not been booted remains as stand by instances.

BMC Server Automation 8.6 supports multibos  and alternate disk patching, which allows user to access, install, maintain, update, and customize the standby BOS during setup and customization operations. Installation, maintenance, or technology level updates to the standby BOS do not change system files on the active BOS. This allows concurrent update of the standby BOS, while the active BOS remains in production, thus reducing downtime while patching. For more information, see How to perform AIX patching on an alternate disk (altdisk) or on multiple boot operating system (multibos).

Patch management support for Red Hat Enterprise Linux 7

BMC Server Automation now supports patch management on Red Hat Enterprise Linux 7. However, before you create a patch catalog ensure that you performed the prerequisite procedures as described in the Before you begin section of Creating a patch catalog.

BMC Server Automation now also supports patch analysis and remediation on Red Hat Enterprise Linux 7 with native yum (instead of blyum). If yum is installed in a non-default location, ensure that you set this location at the server level in the PATCHING_TOOL_INSTALL_LOCATION server property.

Automatic support for IAVA ID attribute 

In BMC Server Automation 8.5, the value of the IAVA ID property is not populated by the catalog update job automatically. You must set it manually in the Bulletin DepotSoftware of the catalog by running an NSH script. 

 However in BMC Server Automation 8.6 the values of this IAVA ID property is populated automatically by the catalog.

Provisioning enhancements

BMC Server Automation version 8.6 supports the following new platforms:

  • RHEL 7
  • Ubuntu 12.04

For information about the provisioning process, see Implementation process for provisioning.

Virtualization enhancements

During the setup a VMware vSphere environment in BMC Server Automation, you can now choose between adding a vCenter server as an agent-based managed server or adding it as an agentless managed object (AMO) that communicates with some other agent-based Windows proxy server. A new menu option was added to server groups, Virtualization > Add VMware Virtual Center, to enable adding the vCenter server as an AMO. For more information, see Adding the vCenter server to BMC Server Automation.

Integration with BladeLogic Dashboard

Version 8.6 includes an integration with the BladeLogic Dashboard, which provides a view into your overall BMC Server Automation environment and offers tips for optimizing BladeLogic installations. The dashboard is not a monitoring tool. Instead, it is a mechanism for quickly assessing the health of all BladeLogic system components. The BladeLogic Dashboard can also show savings that your organization is experiencing by using BladeLogic. For more information about using the dashboard, see Using the Health and Value Dashboards.

BLCLI enhancements

The following BLCLI commands are new in version 8.6.00:

Automation Academy content

The Automation Academy introduces you to a key BladeLogic use case (for example, provisioning), and then provides several step by step, cookbook-style examples that walk you through a specific aspect of that use case. For example, in the case of provisioning, one walkthrough might show you how to provision a bare-metal Windows system, while another might show how to provision a VM on VMware. The content for the Automation Academy is included in the new Getting Started branch.

The initial release of Automation Academy focuses on introducing you to the concepts of automation, provisioning, and configuration management, and includes the following sections:

Related topics

Downloading the installation files
Known and corrected issues

Frequently asked questions and other information


This topic provides information that supplements the BMC Server Automation documentation. It contains the following sections:

Frequently asked questions

This section provides answers to frequently asked questions (FAQs) about BMC Server Automation.

General questions

 When is the end of support for my version of BMC Server Automation? Is my version supported? (Should I be thinking about upgrading?)

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.

 Where can I find information about the platforms currently supported for BMC Server Automation product versions?

You can find information about the supported platform for BMC Server Automation on BMC Support Central, under Product Availability and Compatibility.

 Where is the Knowledge Base?

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

 What ports and protocols does BMC Server Automation require?

See the ports and protocols list.

 Where can I find the build number for a release?

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.

 Where can I find information about the integration of BMC Server Automation with BMC ProactiveNet?

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.

 Where can I find information about the third party software versions included with BMC Server Automation?

You can find information about the included software versions in the Third-party software section of the Minimum software requirements topic and in the Browsing discovered software applications topic.

Installation and upgrade questions

 What are the Supported upgrade paths for BMC Server Automation?

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

 Where can I find deployment architecture recommendations for implementing BMC Server Automation?

You can find deployment architecture recommendations in the following Planning section: Deployment use cases

 What do I do if I just upgraded and am getting errors in Jobs that reference Custom/Server Objects?
 How to debug the failures reported during psexec commands ?

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 command: blpsexec -s winserv.bmc.com -u Administrator -p TNEKNUDRFET -h cmd /c hostname

psexec command: psexec \\winserv.bmc.com -u Administrator -p password_of_Administrator_user -h cmd /c hostname

General product usage

 I'm having trouble with an RSCD agent. How do I open up the permissions temporarily?

Use the following process:

  1. 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.
  2. Remove the "nouser" line from the users file.
  3. 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.

 What do I do if my Application Server will not start up?

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.
 I have multiple Application Servers but I cannot see all Application Server status in the Infrastructure Manager window.

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.

 How do I configure NSH/ZSH command history to persist across sessions?

See the following Knowledge Article for information on this issue:
Knowledge Article ID: 000022404

 Where can I find sizing recommendations for Application Servers?

You can find recommendations for sizing Application Servers in Sizing Application Servers.

 Where can I find "how to" information for specific user scenarios?

You can find a list of user contributed tutorial information in the BMC Contributor topics topic.

In addition, the taking the reins article on Communities includes additional videos and "how to" information.

 Are videos available that help to explain how to accomplish specific user tasks?
See the PDFs and videos topic for a list of all videos.

In addition, the taking the reins article on Communities includes additional videos and "how to" information.

Patch management

 How do I make sure my catalog does not get any new patches?

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.

 How do I make sure that my patching job remediates servers on execution?

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.

 How do I make sure that I run analysis every x hours?

You can specify a schedule for any Job to ensure that it is executed every x hours.

 How do I ensure that my catalog contains only attributes that meet "my" criteria?

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.

 How do I know which filters are missing from my Windows catalog to cover all products installed on all my targets that have been added to my patching job?

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.

WarningSep 8, 2010 6:15:54 PMPatches belonging to following filters were found missing during analysis:
Skype, English
Adobe, English
Windows Media Player, English
Microsoft Office, English
Microsoft Office 2007, English
SQL Server 2005, English
Flash, English
Microsoft Office 2003, English
.Net Framework, English
Microsoft Windows XP, English
Please update your catalog with these filters to avoid any vulnerabilities
 How do I get more details about the Deploy Job that was executed when I installed patches on my targets?

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.


 How can I determine where BMC Server Automation is installed?

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:


ls -la /proc/`ps -ef | grep rscw | grep -v grep | awk '{print $2}'` | grep exe | awk '{print $11}'


pargs -l `ps -ef | grep rscd | head -1 | awk '{print $2}'`
 Where are the RSCD Agent logs located?

On Windows: INSTALL_DIR\RSCD\rscd.log

On UNIX: INSTALL_DIR/[NSH|RSCD]/log/rscd.log

 Where is the transaction or bldeploy log?


 Where is the BMC Server Automation Application Server log that contains deployment messages?

<INSTALLDIR>\br\<deployment name>.log
The default deployment name is appserver, while other common deployments have names such as job-1.

 How do I analyze the *Trace.txt* file that is generated by a Windows Patch Analysis Job?

For detailed instructions on analyzing the Trace.txt file, see How to analyze Trace.txt generated by a Windows Patch Analysis Job (user contribution).

For a list of frequently asked questions for Agent troubleshooting, see Frequently asked questions for agent troubleshooting.

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.

Available walkthroughs

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. 

 Click here to see a list of the topics in this space that are walkthroughs.
CategoryWalkthrough topics
Getting started with automation


Configuration management

Patch management

Job management



There is no content with the specified labels


Additional resources

The following BMC sites provide information outside of the BMC Server Automation documentation that you might find helpful:

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

The following table lists topics that contain videos that supplement or replace the text-based documentation.

CategoryTopics with videos
Getting started

Console management

Patch management
Deploy Jobs
Support information

There is no content with the specified labels


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