Installation and Maintenance

Windows

In this chapter, you will find valuable insights for successfully updating your anynode version on Windows. We not only consider the update process for a single anynode instance but also address the specific circumstances within a high-availability environment.

Updating a single anynode Instance

Before proceeding with an update, please check the following:

Ensure the LOD key contains sufficient Software Upgrade Service (SUS) to use the current version. You can always check the Software Upgrade Service (SUS) status in the Configuration Mode under Licenses. Navigate to Licenses installed and check the expiration date of your Software Upgrade Service (SUS) as well as its status.

anynode frontend with license details.

• Save a backup of the latest working anynode configuration. Refer to the Configuration Export / Import chapter or Backup and Restore chapter for a full backup.

• Ensure that there are no active calls and close all related applications (for example, anynode trace analyzer tool, etc.).

• Our anynode release notes are always up to date, providing you with immediate information upon the launch of a new release regarding new features, enhancements, and bug fixes.

• The latest installation file can be found in the TE-SYSTEMS Community.

With our Software Upgrade Service (SUS) and the resulting version upgrades, you will always remain on the cutting edge of technology. This will ensure you are always meeting the requirements of the IT market. During an ongoing service term, all new releases of anynode can be downloaded and installed from the TE-SYSTEMS Community. For a comprehensive overview of the release dates for Windows, it's best to use a list view. Click on the list view button in the upper right corner. Compare the release date of the anynode version with the expiration date of your Software Upgrade Service. All anynode releases are available with your license until or equal to the expiration of the Software Upgrade Service.

TE-SYSTEMS Community with list view of anynode – The Software SBC releases.

The update process for anynode on Windows is straightforward and quick. Download and execute the anynode installation file. Launch the anynode installer.

Updating a High Availability Environment

When updating anynode in a high availability (HA) environment, there are several important considerations to ensure a smooth and uninterrupted update process. Here are key factors to keep in mind:

1. Compatibility: Verify that the new version of anynode is compatible with your current HA setup. Ensure that the update is supported for the specific HA configuration you have.

2. Backup: Before initiating the update, perform a comprehensive backup of the current configuration, settings, and any critical data. This ensures that, in the event of any issues during the update, you can quickly restore the system to its previous state.

3. Hot Standby Failover: If your HA setup includes failover capabilities, plan for the possibility of hot standby failover during the update process. Ensure that failover mechanisms are in place and tested to guarantee uninterrupted service.

4. Rollback Plan: Develop a rollback plan in case the update encounters unforeseen issues. This plan should include steps to revert to the previous version while minimizing downtime and service disruption.

5. Testing: Before updating the production environment, perform the update in a test or staging environment that replicates the HA setup. This allows you to identify and address any issues or conflicts specific to your configuration before applying the update in a live environment.

Even if it is usually not needed afterward, we recommend taking a snapshot of the system if it is a virtual system. Otherwise, create a system image and store it in a secure location beforehand.

By carefully planning and executing the update process in a high availability environment, you can minimize the risk of service disruptions and ensure the continued reliability of your anynode deployment.

With the anynode Hot Standby feature, you define important rules so that a secondary anynode system can take over in an emergency or update process as part of a high availability configuration. Via the graphical user interface of this feature, all conditions for a switchover to the secondary standby system and back can be individually set. For more details on the graphical Hot Standby user interface, we recommend watching our Hot Standby video tutorial.

The typical update procedure with the anynode hot standby feature, is as follows:

• Check initial state: anynode (main) is active, anynode (standby) is inactive.

• Activate maintenance mode on the standby system.

• Perform the update on the standby system first.

• Verify that the anynode frontend displays the correct version after the update.

• Enable maintenance mode on the main system, transferring the active role to standby.

• Disable maintenance mode on the standby system.

• Perform the update on the main system as outlined in the previous steps.

• If the main system updates successfully: Disable maintenance mode on the main system.

• When convenient, switch the active role back to the main system.

This procedure ensures a controlled update process with minimal downtime and the ability to roll back to the previous version if issues arise during the update. Always perform updates during a maintenance window to minimize the impact on users.

Updating Microsoft Teams SBA

The version of Microsoft Teams SBA installed typically corresponds to the version available at the time of creating the anynode installation package.

To obtain the newer version of Microsoft Teams SBA, users may need to install a more recent version of anynode. You need to uninstall the previous anynode version. Do not check the box for "Remove the configuration and all collected data." Then, run the latest anynode installer and enable "Install Microsoft Teams Survivable Branch Appliance" in the setup options, as described in the Microsoft Windows Installation chapter.

In our anynode release notes, you will find information about which version of Microsoft Teams SBA is being installed.

Downgrades to older anynode Versions

In rare cases, it happens that the Software Upgrade Service (SUS) for the newly installed anynode version is no longer valid. In such a situation, our sales team is ready to assist you with a SUS extension, or you can perform a downgrade for your anynode version. An expired SUS will only cover the versions which were released in the time until the SUS expired. For example, an SUS that expired on January 20th, 2024 will only cover anynode 4.10.16 and lower, but not 4.10.17 and newer, as this was released after the SUS expiry.

Before downgrading to an older version, ensure that it does not contain any software bugs, which were fixed in newer versions, affecting the features you require. We recommend reviewing our anynode Release Notes before proceeding with a downgrade.

In our TE-SYSTEMS Community, you can always access older Windows versions of anynode.

You need to uninstall your anynode version first if you already use a newer version and want to downgrade to an older version. Choose the uninstallation option while retaining configuration data (unchecked box) and run the installer. Get more details about uninstallation in the Microsoft Windows Installation chapter.