Backward compatibility requirements for Security Center - Security Center

Security Center Installation and Upgrade Guide

Applies to
Security Center
Last updated
Content type
Guides > Installation guides
Security Center
Installation guides

Security Center 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 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
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.
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, you must upgrade all Directory servers to

For information on disabling and enabling backward compatibility, see Disabling backward compatibility and Enabling backward compatibility.

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.10 role Backward compatible with 5.7, 5.8 and 5.9
Yes No
Access Manager  
Active Directory ✓ (5.9 and later)  
ALPR Manager

Formerly LPR Manager ( and earlier)

Authentication Service (OpenID & SAML2)   ✓ (introduced in
Authentication Service (WS-Federation)

Formerly Active Directory Federation Services

Authentication Service (WS-Trust)

Formerly Active Directory Federation Services

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

Backward compatibility with Security Center tasks

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

Task category Task type Backward compatible with Security Desk 5.7, 5.8 and 5.9
Yes No
Operation Monitoring (live and playback video)  
Dashboards ✓ (introduced in 5.8)
Health dashboard ✓ (introduced in
Cardholder management 1  
Credential management 1  
Visitor management 1  
People counting  
Hotlist and permit editor  
Inventory management  
Mustering ✓ (introduced in
Alarm management Alarm monitoring  
Alarm report  
Investigation Incidents  
Zone activities  
Investigation > Access control Area activities  
Door activities  
Cardholder activities  
Visitor activities  
Area presence  
Time and attendance  
Credential activities  
Credential request history  
Elevator activities  
Visit details 1  
Investigation > Asset management Asset activities  
Asset inventory  
Investigation > ALPR Hits  
Hits (Mutli-region)  
Reads (Mutli-region)  
Patrol vehicle tracking  
Inventory report  
Daily usage per patrol vehicle  
Logons per patrol vehicle  
Reads/hits per day  
Reads/hits per zone  
Zone occupancy  
Parking sessions  
Parking zone activities  
Investigation > Intrusion detection Intrusion detection area activities  
Investigation > Record fusion Records   ✓ (introduced in
Investigation > Video Archives  
Camera events  
Motion search  
Video file explorer  
Forensic search  
Security video analytics ✓ (introduced in 5.7 SR2, renamed from KiwiVision intrusion detector in 5.7 SR5)
Maintenance System status  
Audit trails  
Activity trails  
Health history  
Health statistics  
Hardware inventory  
Maintenance > Access control Access control health history  
Access control unit events  
Cardholder access rights  
Door troubleshooter  
Access rule configuration  
Cardholder configuration 1  
Credential configuration  
I/O configuration  
Maintenance > Intrusion detection Intrusion detection unit events  
Maintenance > Video Camera configuration  
Archiver events  
Archiver statistics ✓ (introduced in 5.8)
Archive storage details  
Wearable camera evidence ✓ (introduced in 5.8)

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