Backward compatibility requirements for Security Center - Security Center 5.11.3.0

Security Center Installation and Upgrade Guide 5.11.3.0

Product
Security Center
Content type
Guides > Installation guides
Version
5.11
Release
5.11.3.0
ft:locale
en-US
Last updated
2024-06-27

Security Center 5.11.3.0 is backward-compatible with many Security Center components from the three previous major versions. A server or workstation that is three major versions behind can connect to the 5.11.3.0 Directory, but one that is four major versions behind cannot.

To retain backward compatibility when upgrading your system in stages, no part of Security Center can be more than three major versions apart. For systems that are four to six major versions behind, upgrade in two steps to maintain backward compatibility.
IMPORTANT: Adding backward-compatible connections slows down the performance of the Directory. It is only recommended as a temporary solution before you can upgrade all servers and workstations.
IMPORTANT: For client workstations, backward compatibility applies only to Security Desk. Config Tool is not backward-compatible because it must be of the same version as the Directory.
Backward compatibility in Security Center has the following requirements:
Upgrading to the latest version
When upgrading, you must always upgrade the main server that hosts the Directory role and Config Tool. Always upgrade expansion servers that host non-backward-compatible roles.
Using new features
To use the new features introduced in version 5.11.3.0, upgrade your Security Center servers.
Role assigned to multiple servers
If a role is assigned to multiple servers, such as in a failover configuration, all of its servers must run the same version of Security Center.
Directory assigned to multiple servers
All Directory servers must use the same version, meaning that all four digits of their version numbers must be the same. For example, if you upgrade to Security Center 5.11.3.0, you must upgrade all Directory servers to 5.11.3.0.

Backward compatibility between Security Center roles

Each new version of Security Center includes new role features that might be incompatible with earlier versions. The Security Center roles that are backward-compatible are outlined in the following table.
IMPORTANT: All expansion servers that host a non-backward-compatible role must be upgraded to the same version as the main server hosting the Directory.
5.11 role Backward-compatible with 5.8, 5.9 and 5.10
Yes No
Access Manager  
Active Directory ✓ (5.9 and later)  
ALPR Manager

Formerly LPR Manager (5.9.2.0 and earlier)

 
Archiver  
Authentication Service (OpenID & SAML2)  
Authentication Service (WS-Federation)

Formerly Active Directory Federation Services

 
Authentication Service (WS-Trust)

Formerly Active Directory Federation Services

 
Auxiliary Archiver  
Camera Integrity Monitor (hidden)  
Cloud Playback ✓ (5.10.0.0 and later)  
Directory Manager  
Global Cardholder Synchronizer (GCS)  
Health Monitor  
Intrusion Manager  
Map Manager  
Media Gateway  
Media Router  
Mobile Credential Manager ✓ (5.10.0.0 and later)  
Mobile Server  
Omnicast™ Federation™1  
Plugin (all instances) See Supported plugins in Security Center.
Point of sale  
Privacy Protector™ (hidden) ✓ (5.7 SR1 and later)  
Record Caching Service ✓ (5.10.0.0 and later)  
Record Fusion Service ✓ (5.10.0.0 and later)  
Report Manager  
Reverse Tunnel  
Reverse Tunnel Server  
Security Center Federation™  
Unit Assistant ✓ (5.10.1.0 and later)2  
Wearable Camera Manager  
Web Server  
Web-based SDK  
Zone Manager  

1 Since Omnicast 4.8 has reached End of Life, Omnicast Federation is not supported in Security Center 5.11.3.0 and later.

2 Unit Assistant is only backward-compatible for the unit password management feature. The unit certificate management feature has only been introduced in 5.11.0.0.

Backward compatibility with Security Center tasks

The Security Center 5.11 tasks that are backward-compatible with Security Desk 5.8, 5.9 and 5.10 are summarized in the following table:

1 Saved reports that use filters with During the next time intervals are not compatible with Security Desk 5.8 and earlier.

2 Used to be called Records in Security Center 5.11.1.0 and earlier.