Early platform support for upcoming OS versions

This section contains the following topics:

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.

Important

To make sure that the Smart Agent reads the correct OS version, users must run the Update Server Properties job. This step is mandatory for synchronizing the agent with the latest configuration updates.

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.

Important:

Make sure you copy the certified configuration file to all Application Servers. If the Application Server is Linux, make sure the file is owned by bladmin:bladmin and has 644 permissions.

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.