Important

   

This space contains documentation for TrueSight Server Automation 8.9.03 and the later service packs for 8.9. For earlier releases, see BMC Server Automation 8.9.

TRUE

TrueSight Server Automation 8.9.00

TrueSight 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 19 Sep
This section provides information about what is new or changed in TrueSight Server Automation, including urgent issues, documentation updates, feature packs, and fix packs.

Date

Title

Summary

September 18, 2019Version 8.9.04.002: Patch 2 for version 8.9.04

Lists the updates in TrueSight Server Automation version 8.9 Service Pack 4 Patch 2.

August 13, 2019Rolling Update 1 for version 8.9.04.001

Lists the updates in TrueSight Server Automation version 8.9 Service Pack 4 Patch 1 Rolling Update 1.

June 21, 2019Version 8.9.04.001: Patch 1 for version 8.9.04

Lists the updates and enhancements introduced in TrueSight Server Automation version 8.9 Service Pack 4 Patch 1.

April 26, 2019Rolling Update 1 for version 8.9.04

Lists the updates in TrueSight Server Automation version 8.9 Service Pack 4 Rolling Update 1.

January 28, 2019Service Pack 4: version 8.9.04

Lists the updates and enhancements introduced in TrueSight Server Automation version 8.9 Service Pack 4.

October 5, 2018Version 8.9.03.001: Patch 1 for version 8.9.03

Lists the updates and enhancements introduced in TrueSight Server Automation version 8.9 Service Pack 3 Patch 1.

June 11, 2018Service Pack 3: version 8.9.03

Lists the updates and enhancements introduced in TrueSight Server Automation version 8.9 Service Pack 3.

March 16, 2018BSA 8.9.02 Rolling Update 1 (RU1)

Lists the updates and enhancements introduced in BMC Server Automation version 8.9 Service Pack 2 Rolling Update 1.

February 05, 2018Service Pack 2: version 8.9.02

Lists the updates and enhancements introduced in BMC Server Automation version 8.9 Service Pack 2.

January 19, 2018Version 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, 2017BSA 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, 2017Service Pack 1: version 8.9.01

Lists the updates and enhancements introduced in BMC Server Automation version 8.9 Service Pack 1.

September 23, 20168.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.

Tip

  • To stay informed of changes to this list, click the  icon on the top of this page.
  • 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 template you want to use:
      • Simple to export a lightweight PDF with no cover, table of contents, or index.
        By default, the Simple template only exports the current page.
      • Standard to export a traditional PDF with a cover, table of contents, and index.
        By default, the Standard template exports the current page and all child pages.


     

Related topics

Known and corrected issues

Getting started

Planning 

Installing 

Upgrading 


Planning

 

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

Installing

 

Information about installing the product and migrating product data.

Configuring after installation

 

Required post-installation configuration.

Upgrading

 

Upgrade process, migration, and configuration.

Troubleshooting

 

Issues resolution, error messages, logs, and contacting Support.

Using

 

Interface descriptions, using the product.

Administering

 

Security, system administration, maintenance.

Developing

 

Development interfaces and toolkits.

Integrating

 

Integrations with other products.
What's new?

This topic contains information about fixes and updates in Service Pack 3 (product version 8.9.03), and provides instructions for downloading and installing the service pack.

Tip

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

Build information

The following table lists build information for this release.

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...


Release

Build number

EPD version number

Release date

Patch 2 for Service Pack 4 for version 8.9

8.9.04.253

8.9.04.002September 18, 2019
Patch 1 for Service Pack 4 for version 8.9

8.9.04.227

8.9.04.001June 21, 2019
Service Pack 4 for version 8.9

8.9.04.200

8.9.04January 28, 2019
Patch 1 for version 8.9 Service Pack 3

8.9.03.647

8.9.03.001October 5, 2018
Service Pack 3 for version 8.9

8.9.03.162

8.9.03June 11, 2018

Notice

BMC Software is alerting users of BMC Server Automation for Windows Patching that they need to upgrade the BMC Server Automation application server and Windows target servers to the latest versions to ensure the continued functioning of Windows Patching within the product. 

Ivanti has announced the end-of-life for an underlying Shavlik SDK version that BMC Server Automation uses to get updates for Windows patches. The original end-of-life support for Shavlik 9.1 was December 31, 2018. The end-of-life support is now extended to September 30, 2019, which provides users with additional time to upgrade BMC Server Automation application server and the BMC Server Automation RSCD Agents running on Windows target servers.


Enhancements

The following topics describe the enhancements included in this service pack.

What's new

The following table lists the new features included in this service pack.

CategoryUpdateDescription
PatchingShavlik update OR Third-party software updates

Shavlik version that is shipped with TrueSight Server Automation has been upgraded from Shavlik 9.1 to Shavlik 9.3. This requires that all Windows RSCD Agents that are used for Windows Patching are upgraded to 8.9.03. Windows Patching will not work with downlevel agents once the application server is upgraded to 8.9.03.

GeneralThird-party software updates

Java Runtime Environment (JRE) version that is shipped with TrueSight Server Automation has been updated to 1.8.0_172 (JRE 1.8 Update 172).

For more information about other third-party software versions, see Third-party software.

GeneralThird-party software updatesThe version of the SysInfo utility (from MagniComp) has been updated to 10-H82.
GeneralPatching

You can perform patching and remediation activities for Ubuntu 16.04 by using TrueSight Server Automation.

GeneralAIX build date

A new property, Build Date has been added in AIX  for Service Packs. You can view this property in the following tabs of the Service Packs:

  • Extended Properties tab
  • AIX Container Properties tab

For more information, see Examining patch properties for AIX.

GeneralSMB upgrade

Server Message Block (SMB) version has been upgraded to SMB version 2 (SMBv2) to avoid exposure to security vulnerabilities (for example,WannaCry ransomware attack). For more information, see multiple-vulnerabilities-in-microsoft-windows-smb-server in documentation.

You must ensure that SMBv2 is enabled for Microsoft Windows server for following actions:

  • Add node (Applicable only for Microsoft Windows application server)
  • Remote file server (Applicable only for Microsoft Windows application server and Microsoft Windows file server)
  • Agent Installer Job (Applicable only for Microsoft Windows target server)
  • Unified Agent Installer (Applicable only for Microsoft Windows target server)
Compliance ContentTemplate updates to newer benchmarks

The component template for the Health Insurance Portability and Accountability Act (HIPAA) policy has been updated to more recent benchmarks:

  • HIPAA on AIX 7.1

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

GeneralSHA 256 support

TrueSight Server Automation now supports Secure Hash Algorithm 256 (SHA 256). By default, the following certificates use SHA256 signing algorithm:

  • RSCD self-signed certificate (certificate.pem)

For fresh installation of RSCD Agent 8.9.03, the certificate.pem is created with SHA256 Signature Algorithm.

If secure logging is configured on RSCD agent, certificate.pem file is used in secure logging. So, in case of upgrade, by default, the existing certificate.pem file is not upgraded to SHA256. To use SHA256 in certificate.pem for upgraded RSCD Agent, perform the following steps:

    1. Back up the existing certificate.pem, RSCD log files and respective signature files. This is applicable if you want to verify older RSCD log files on the server.
    2. Delete certificate.pem file.
    3. Perform any operation against RSCD Agent (for example, restart service, agent info). The RSCD Agent automatically creates a new certificate.pem file with SHA256 Signature Algorithm.
      For more information, see Session layer security.
  • Application server self-signed certificate (bladelogic.keystore)

For fresh installation of application server 8.9.03, the bladelogic.keystore is created with SHA256 Signature Algorithm.

In case of upgrade, by default, the existing bladelogic.keystore file is not upgraded to SHA256. To use SHA256 in bladelogic.keystore for upgraded application server, perform the following steps:

    1. Back up the old bladelogic.keystore file.
    2. Recreate the bladelogic.keystore using blmkcert.
    3. Apply the same bladelogic.keystore across the MAS setups.
      For more information about blmkcert and the steps to apply bladelogic.keystore, see Using certificates to secure communication between clients and Application Servers.

What's changed

The following table lists down the features that have been modified.

CategoryUpdateDescription
PatchingShavlik upgrade

Modifications: The following changes are done with reference to Shavlik upgrade from Shavlik 9.1 to Shavlik 9.3:

  • In global patch configuration parameters for Shavlik, OEMCatalog.zip file is replaced with OemCatalogWpd.zip file. Patch definition and contents files ( pd5.xml and hf7b.xml) are replaced with WindowsPatchData.zip. For more information, see Creating a patch catalog for Microsoft Windows.
  • The format of the product_categories.xml (Windows Filter Configuration file) is changed in TrueSight Server Automation 8.9.03. If you have previously customized the product_categories.xml file and are upgrading from a version prior to TrueSight Server Automation 8.9.03, you must manually update the changes to the new format (see sample product_categories.xml file for the format). Any manual customization in the product sub categories is overwritten and the customizations are lost. However, BMC recommends that you keep a backup of the product_categories.xml file before upgrading. For more information, see Global Configuration parameter list.
  • A new exportIvantiProductCatalog option has been added for Microsoft Windows Patch Downloader utility (offline downloader) to export the products that are available from Ivanti. The exported CSV file is generated with Vendor, Family, Version, Product information. For more information, see Additional commands for Microsoft Windows Patch Downloader utility. This option can be used as reference for customizing product_categories.xml.
  • If you want to add a new product to the filter list in the Windows Catalog tab, you must add a new product_category tag in the product_categories.xml and add a vendor node. You can also add specific information to the optional nodes (familyversionproduct, include_products, exclude_products). For information about how to add new products to the filter list, see Filters.
  • The Refresh button to refresh the Windows Filter Configuration File while configuring global patch configuration parameters for Shavlik is not available.
  • Adding a hotfix from the Depot > Patch catalog and by using Servers > Browse (Live browse) option is not available. The following options are disabled:
    • Add to Depot As → BlPackage 
    • Deploy 

      You can perform the same action by using patching job (Analyze Patch(s) action).  For information about ways to add a hotfix, see Adding a hotfix to the Depot.
  • Uninstall from Live browse does not auto-download the payload and you have to manually provide all required inputs.

Pre-requisites: Ensure that you meet the following pre-requisites:

  • Ensure that the following components must be updated to TrueSight Server Automation 8.9.03 version:

    • Application Servers/Database
    • BMC Server Automation Consoles
    • File Server RSCD Agent
    • All Windows RSCD agents which are targets of BMC Server Automation Windows Patching
  • BMC recommends that you keep a backup of the product_categories.xml file before upgrading, because any manual customization in the product sub categories is overwritten and the customizations are lost.

Post-upgrade tasks: You must perform the following tasks after upgrading the agent, because Catalogs, Patch Analysis Job, remediation prepared with Shavlik 9.1 does not work after upgrade:

    • Update all old catalogs
    • Upgrade agents
    • Re-execute existing patching jobs with updated catalogs
    • manually update the customizations to the new format of product_categories.xml
PatchingPatching support deprecationPatching support for the following products have been removed:
  • Microsoft Windows XP
  • Microsoft Office 2000
  • Microsoft Office 2003
  • Microsoft Windows Server 2003
  • Microsoft SQL Server 2000
  • Microsoft SQL Server 2005

Compliance Content

Templates deprecation

TrueSight Server Automation no longer supports the following compliance content templates:

  1. CIS - Windows Server 2003 for Domain Controllers
  2. CIS - Windows Server 2003 for Member Servers
  3. CIS - Red Hat Enterprise Linux 5
  4. CIS SuSE Linux Enterprise Server 10 
  5. DISA - Red Hat Enterprise Linux 5
  6. DISA - Windows Server 2003 DC
  7. DISA - Windows Server 2003 MS
  8. PCI Data Security Standard - Windows Server 2003
  9. PCI Data Security Standard - Solaris8-9
  10. PCI Data Security Standard v2 - Red Hat Enterprise Linux 5
  11. PCI v3 SUSE Linux Server Enterprise Server 10
  12. HIPAA - Windows Server 2003
  13. HIPAA - SUSE 9-10 Linux
  14. HIPAA - Solaris 8-9
  15. HIPAA - AIX (5.2 and 5.3)
  16. HIPAA - Red Hat Enterprise Linux 5
  17. SOX Data Security Standard - RedHat Linux (5)
  18. SOX Data Security Standard - Windows Server 2003
  19. SOX Data Security Standard - SUSE 9-10 Linux
  20. SOX Data Security Standard - Solaris8-9
  21. SOX Data Security Standard - AIX (5.2 and 5.3)

These content templates are deprecated as updates on the compliance standards as well as the platform have been stopped by their respective vendors. TrueSight Server Automation no longer supports agent for the underlying platforms. These templates are no longer bundled and tested. However, the existing templates in your environment are not modified. If you need to use the existing templates in your environment, you can still use the existing templates. However, if you face any issues on this templates ( if the rules need fix), and you need assistance, contact BMC Customer Support.

For more information about the templates supported by the product, see Compliance policy standards supported by TrueSight Server Automation templates.

GeneralOffline helpTrueSight Server Automation 8.9.03 does not support the local offline help.
Databasepermissions

You must apply both the granular and resource permissions:

  • Resource permission
    • GRANT RESOURCE permissions
  • Individual privileges
    • CREATE TRIGGER
    • CREATE SEQUENCE
    • CREATE TYPE
    • CREATE PROCEDURE
    • CREATE CLUSTER
    • CREATE OPERATOR
    • CREATE INDEXTYPE
    • CREATE TABLE

For more information, see List of required database permissions.

Downloading the service pack

Service Pack 3 for version 8.9 includes full installers for all components. You can download the files for version 8.9.03 from the TrueSight Server Automation 8.9.03 download page at the BMC Electronic Product Distribution (EPD) website

For full download instructions, see Downloading the installation files.

For a list of installation programs by OS, see Installation programs for TrueSight Server Automation.

Installing the service pack as a fresh product installation

If you are installing this service pack as a fresh product installation, do one of the following:

Upgrading to the service pack

You can upgrade to this service pack from product versions 8.7.x, 8.8.x, 8.9.00, 8.9.01, and 8.9.02.

To upgrade, do one of the following:


Frequently asked questions and other information

 

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

Frequently asked questions

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

General questions


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

For supported version information, see the following BMC Support Support page:
http://webapps.bmc.com/support/faces/az/prodallversions.jsp?seqid=164625
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 TrueSight Server Automation product versions?

You can find information about the supported platform for TrueSight 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 TrueSight 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 TrueSight 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 TrueSight 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 TrueSight 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 TrueSight Server Automation, see the online documentation for BMC PATROL for TrueSight Server Automation and BMC ProactiveNet Automation Server Monitoring.

 Where can I find information about the third party software versions included with TrueSight 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 TrueSight Server Automation?

You can find information about the supported upgrade paths for TrueSight 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 TrueSight 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?

 Where are the Microsoft Visual C++ 2015 Redistributable installation log files located?

%temp% directory

 How do I find the description of Microsoft Visual C++ 2015 Redistributable related errors reported in log files?
 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

 What will happen if Microsoft Visual C++ 2017 redistributable is already installed on a server?

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.

 Will 8.9.2 Application server (that uses Microsoft Visual C++ 2015) have any backword compatibility issues with older Agents (which uses Microsoft Visual C++ 2005 redistributable)?

No. There won’t be any issue in communication between 2 components which are using different versions of redistributable. 

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.

Powershell execution


 How do I change the default blpowershell configuration values in blpowershell.cnf file?

Create an NSH Type 1 script with blpowershell command and use the required option as mentioned in To manage PowerShell configurations.

 How do I reset the PowerShell configurations to default values?

Create an NSH Type 1 script with blpowershell -resetoption command and execute the script against the server whose PowerShell configuration needs to be reset.

 How do I configure the blpowershell.cnf file if the PowerShell is installed in a non-default location (for example, C:\Powershell\bin\pwsh.exe) and is not present in the PATH environment variable?

You must have PS_DIR=C:\Powershell\bin and PS_CMD=pwsh.exe in the blpowershell.cnf file. Create an NSH Type 1 script with blpowershell command and use the required option as mentioned in To manage PowerShell configurations. For example,

blpowershell -setoption "PS_DIR" "C:\Powershell\bin"
blpowershell -setoption "PS_CMD" "pwsh.exe"
 I have installed PowerShell in a non-default location (for example, C:\Powershell\bin\pwsh.exe) and is not mentioned in the PATH environment variable. How do I use this PowerShell at runtime?

Additional runtime options are provided to override the configured PowerShell values in blpowershell.cnf. You need to pass the following additional runtime argument when executing the PowerShell script:

-blpsusedir "C:\Powershell\bin"
-blpsusecmd "pwsh.exe"

For more information about overriding options at runtime, see Overriding the PowerShell options at runtime.

 PowerShell script returns an error message, but TrueSight Server Automation reports it as Success. Why is this behaviour?

After the PowerShell script is executed, TrueSight Server Automation decides Success/Failure based on the exit code of PowerShell command. You can try executing the same PowerShell script manually on the target server from the command prompt and check the exit status (%errorlevel% or $?). It was observed that the PowerShell version before version 5 returns Success message even if the script execution fails.


Troubleshooting


 How can I determine where TrueSight 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:

Linux:

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

Solaris:

pargs -l `ps -ef | grep rscd | head -1 | awk '{print $2}'`

 Where are the RSCD Agent logs located?
On Windows: INSTALL_DIR\RSCD\rscd.logOn UNIX: INSTALL_DIR/[NSH|RSCD]/log/rscd.log

 Where is the transaction or bldeploy log?
<INSTALLDIR>\Transactions\log\bldeploy-xxxx.log

 Where is the TrueSight 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
Provisioning
Configuration management
Patch management
Job management
Compliance
Installing
Integrating
Database


Additional resources

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



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

Comments