Early platform support for upcoming OS versions

Support for upcoming Windows OS versions

TrueSight Server Automation uses a configuration-driven model that externalizes Windows operating system versions into a JSON file, accelerating compatibility with newly released Windows operating system versions. This eliminates the need for code changes or product upgrades with each new Windows operating system release, enabling faster agent deployment and patching workflows by significantly reducing time-to-support and removing the dependency on full product upgrades.

The Operating System parameters are externalized to a configurable JSON file, enabling support for newly certified Operating System versions without requiring a product upgrade. This simplifies update workflows and accelerates alignment with vendor releases.

 This video offers a step-by-step walkthrough explaining the Operating System version compatibility:

Limitation

• Core logic dependencies: If the new operating system version is not in line with the earlier version, then check with the BMC Platform matrix page to make sure that the support is available for the new operating system version.

Before you begin

• You must have administrator permissions to configure the settings.
• Make sure that the configuration file (windows_version_config.json) has adequate read permissions.

To support new Windows operating system via external configuration

Support for new Windows operating system versions can be enabled using external JSON configuration files. The certified configuration file will be provided by BMC. You must download this file and place it in the <TSSA Install Dir>\BladeLogic\NSH\share folder on each application server.

Example use cases for different operating systems

Example Scenario	Action	Result
Windows Server 2026 is released after TSSA 25.2.	BMC certifies the operating system and provides a config file. Download and apply the configuration, as mentioned in the following steps: On the Target Server:  Install the TrueSight Server Automation agent on the Windows Server 2026 server by passing bellow additional flag to the installer. BMC_SUPPORTED_PLATFORM=true. On each Application Server:  Copy the downloaded configuration file to the <TSSA Install Dir>\BladeLogic\NSH\share directory. If Application Server is Linux Make sure the file is owned by bladmin:bladmin and has 644 permissions.	Windows Server 2026 is enrolled.
Red Hat Enterprise Linux (RHEL) 11 is released with no major kernel changes.	BMC certifies the operating system and announces the support via the documentation, along with any additional configurations/dependencies (if required). Note: There is no flag dependency and configuration file for dependency for non-Windows operating systems, such as RHEL, OEL, SUSE, Solaris, Rocky Linux, Debian, Ubuntu, AIX, and so on.	RHEL 11 server is enrolled.

Support for Red Hat Enterprise Linux 10 OS versions

TrueSight Server Automation now certifies RHEL 10 for both RSCD agents and the patching workflow.

With this update, you can:

• Install and upgrade RSCD agents
• Enroll agents
• Live browse servers
• Execute patching jobs (both online and offline)

This support is enabled through the Early Platform Support framework introduced in TrueSight Server Automation 25.2, allowing faster OS adoption without requiring a full product upgrade.

Before you begin

• Ensure you are using TrueSight Server Automation version 25.2.
• Download the required support files and XML configurations before starting.

Prerequisites

• This support is available only in TrueSight Server Automation version 25.2.
• A server restart is required after replacing core files.
• Changes apply to Application Servers only, not target servers.
• Ensure all impacted components are backed up before making changes.
• Evaluate in non-production environments before rollout.

Supported Versions

• Operating System: Red Hat Enterprise Linux 10 (x86_64)
• Kernel Versions: 6.x and above (specific versions may vary)
• Supported Components:
  • Agent installation
  • Patch Management

Enabling early platform support for RHEL10 OS versions

RHEL 10 introduces vendor changes that require the following additional configuration steps before deploying agents or running patching jobs.

To install the RSCD Agent

Perform the following steps:

Step 1: Verify System Architecture

Run the uname -p command on the RHEL 10 machine.

• If the output is x86_64, proceed with the standard RSCD Agent installation.
• If the output is unknown, follow the further steps.

Step 2: Create Agent Installer Job (AIJ)

Create an Agent Installer Job (AIJ) using the Linux_64 Agent Installer bundle with the following installer command:mv /usr/bin/uname /usr/bin/uname_original; echo '#!/bin/sh' > /usr/bin/uname; echo 'if test "$1" = "-p"' >> /usr/bin/uname; echo 'then' >> /usr/bin/uname; echo 'echo x86_64' >> /usr/bin/uname; echo 'else' >> /usr/bin/uname; echo 'uname_original $@' >> /usr/bin/uname; echo 'fi' >> /usr/bin/uname; chmod 755 /usr/bin/uname; rpm -Uiv ??SOURCE??; mv /usr/bin/uname_original /usr/bin/uname

To execute patching use case

Perform the following steps:

Step 1: Download Required Files

1. Download the following files:
   1. redhat-channels.xml
   2. redhat-iso-url.xml
       
2. See the table below to download the files for the TSSA Server hosted on Windows or Linux servers, and verify their checksums.

   TSSA Server	File name	SHA256 Checksum	MD5 Checksum
   Windows	support-files-1.0.jar	3F1BB1CDB59879239AAED8567BE14162DEEA38E68B1D488AE4650624FAA656B6	F36597E4A42DE989058C63675CAC7E0F
   Linux	support-files-1.0.jar	5AE30A13E7F95E9C4D0DB77348E3E6261925D1DB57F5135352E76D043D51091D	106BBE6FED0C48FFA3A1C8CECD772D84

   Information

   Important

   Ensure the checksum results match the expected values before replacing the existing file. If the results do not match, please contact BMC Support.

Step 2: Update TrueSight Server Automation Server

1. Stop the TrueSight Server Automation Server.
2. Navigate to <Install Dir>/BladeLogic/NSH/br/stdlib.
3. Backup the existing support-files-1.0.jar.
4. Replace it with the downloaded support-files-1.0.jar.
5. Restart the TrueSight Server Automation Server.

Step 3: Upload XML Files via RCP

1. Navigate to the Configuration tab.
2. Select Patch Global Configuration.
3. Under the Red Hat tab in Basic Options:
   1. Upload redhat-channels.xml to RedHat Channel Filters List File.
   2. Upload redhat-iso-url.xml to RedHat ISO URLs File (CDN repo).
4. Click Apply and OK.