Backward Compatibility
Understanding backward compatibility is crucial for planning successful upgrades and ensuring system stability during version transitions.
This guide provides comprehensive information about ServiceOps backward compatibility across different versions and components. It helps IT administrators and implementation consultants understand which components can be upgraded independently and which require coordinated updates to maintain system functionality.
Backward compatibility in ServiceOps refers to the ability of newer server versions to work with older agent and component versions. This compatibility matrix is essential for:
- Planning phased upgrades across distributed environments
- Minimizing downtime during version transitions
- Ensuring system stability when components are upgraded at different times
- Understanding upgrade dependencies between server and agent components
Current Version Compatibility Matrix
The table below shows the latest compatibility information. Click on any version to view detailed compatibility matrix.
Latest Version Compatibility (v8.7.4)
| Agent Type | Supported Versions | Status |
|---|---|---|
| Windows Discovery Agent | v8.5.x, v8.6.x, v8.7.x | ✅ Fully Supported |
| Windows RDP Agent | v8.5.x, v8.6.x, v8.7.x | ✅ Fully Supported |
| Windows Patch Agent | v8.5.x, v8.6.x, v8.7.x | ✅ Fully Supported |
| Linux/Mac Discovery/RDP Agent | v8.5.x, v8.6.x, v8.7.x | ✅ Fully Supported |
| Windows Poller | v8.7.4 | ✅ Fully Supported |
| Windows/Linux Integration Connector | v8.7.2, v8.7.3, v8.7.4 | ✅ Fully Supported |
| Windows/Linux File Server | v8.7.x | ✅ Fully Supported |
- Current Version: Always fully supported with all features
- Previous 2 Versions: Fully supported with minor limitations
- Older Versions: Limited support, upgrade recommended
Historical Version Compatibility
v8.7.3 Compatibility Matrix (Click to expand)
| Agent Type | Supported Versions |
|---|---|
| Windows Discovery Agent | v8.4.x, v8.5.x, v8.6.x, v8.7.x |
| Windows RDP Agent | v8.4.5, v8.5.x, v8.6.x, v8.7.x |
| Windows Patch Agent | v8.4.5, v8.5.x, v8.6.x, v8.7.x |
| Linux/Mac Discovery/RDP Agent | v8.4.5, v8.5.x, v8.6.x, v8.7.x |
| Windows Poller | v8.6.3, v8.6.4, v8.6.5, v8.7.x |
| Windows/Linux Integration Connector | v8.6.4, v8.6.5, v8.7.x |
| Windows/Linux File Server | v8.6.5, v8.7.x |
v8.7.2 Compatibility Matrix (Click to expand)
| Agent Type | Supported Versions |
|---|---|
| Windows Discovery Agent | v8.4.x, v8.5.x, v8.6.x, v8.7.x |
| Windows RDP Agent | v8.4.5, v8.5.x, v8.6.x, v8.7.x |
| Windows Discovery Patch Agent | v8.4.5, v8.5.x, v8.6.x, v8.7.x |
| Linux/Mac Discovery/RDP/Patch Agent | v8.4.5, v8.5.x, v8.6.x, v8.7.x |
| Windows Poller | v8.6.3, v8.6.4, v8.6.5, v8.7.x |
| Windows/Linux Integration Connector | v8.6.4, v8.6.5, v8.7.x |
| Windows/Linux File Server | v8.6.5, v8.7.x |
v8.7.1 Compatibility Matrix (Click to expand)
| Agent Type | Supported Versions |
|---|---|
| Windows Discovery Agent | v8.4.x, v8.5.x, v8.6.x, v8.7.0 |
| Windows RDP Agent | v8.4.5, v8.5.x, v8.6.x, v8.7.0 |
| Windows Discovery Patch Agent | v8.4.5, v8.5.x, v8.6.x, v8.7.0 |
| Linux/Mac Discovery/RDP/Patch Agent | v8.4.5, v8.5.x, v8.6.x |
| Windows Poller | v8.6.3, v8.6.4, v8.6.5, v8.7.0 |
| Windows/Linux Integration Connector | v8.6.4, v8.6.5, v8.7.0 |
| Windows/Linux File Server | v8.6.5, v8.7.0 |
v8.7.0 Compatibility Matrix (Click to expand)
| Agent Type | Supported Versions |
|---|---|
| Windows Discovery Agent | v8.4.x, v8.5.x, v8.6.x |
| Windows RDP Agent | v8.4.5, v8.5.x, v8.6.x |
| Windows Discovery Patch Agent | v8.4.5, v8.5.x, v8.6.x |
| Linux/Mac Discovery/RDP/Patch Agent | v8.4.5, v8.5.x, v8.6.x, v8.7.0 |
| Windows Poller | v8.6.2, v8.6.3, v8.6.4, v8.6.5 |
| Windows/Linux Integration Connector | v8.6.3, v8.6.4, v8.6.5 |
| Windows/Linux File Server | v8.6.3, v8.6.4, v8.6.5 |
v8.6.5 Compatibility Matrix (Click to expand)
| Agent Type | Supported Versions |
|---|---|
| Windows Discovery Agent | v8.4.x, v8.5.x, v8.6.x |
| Windows RDP Agent | v8.4.5, v8.5.x, v8.6.x |
| Windows Discovery Patch Agent | v8.4.5, v8.5.x, v8.6.x |
| Linux/Mac Discovery/RDP/Patch Agent | v8.4.5, v8.5.x, v8.6.x |
| Windows Poller | v8.6.2, v8.6.3, v8.6.4 |
| Windows/Linux Integration Connector | v8.6.3, v8.6.4 |
v8.6.4 Compatibility Matrix (Click to expand)
| Agent Type | Supported Versions |
|---|---|
| Windows Discovery Agent | v8.4.x, v8.5.x, v8.6.x |
| Windows RDP Agent | v8.4.5, v8.5.x, v8.6.x |
| Windows Discovery Patch Agent | v8.4.5, v8.5.x, v8.6.x |
| Linux/Mac Discovery/RDP/Patch Agent | v8.4.5, v8.5.x, v8.6.x |
| Windows Poller | v8.6.2, v8.6.3 |
| Windows/Linux Integration Connector | v8.6.2, v8.6.3 |
Integration Connector Limitation
Integration Connector Limitation: Backward compatibility is not supported for the Integration Connector in v8.6.2. Users must uninstall the existing connector and install version 8.6.2.
v8.6.1 Compatibility Matrix (Click to expand)
| Agent Type | Supported Versions |
|---|---|
| Windows Discovery Agent | v8.4.x, v8.5.x, v8.6.0 |
| Windows RDP Agent | v8.4.5, v8.5.x, v8.6.0 |
| Windows Discovery Patch Agent | v8.4.5, v8.5.x, v8.6.0 |
| Linux/Mac Discovery/RDP/Patch Agent | v8.4.5, v8.5.x, v8.6.0 |
Key Features:
- Bulk Poller Agent upgrade support via ServiceOps is available from version 8.6.1 onward
- The Integration Connector is supported from version 8.6.1 onward and is not compatible with earlier versions
v8.6.0 Compatibility Matrix (Click to expand)
| Agent Type | Supported Versions |
|---|---|
| Windows Discovery Agent | v8.4.x, v8.5.x |
| Windows RDP Agent | v8.4.5, v8.5.x |
| Windows Discovery Patch Agent | v8.4.5, v8.5.x |
| Linux/Mac Discovery/RDP/Patch Agent | v8.4.5, v8.5.x |
- Focus on Current Version: The latest version (v8.6.5) is prominently displayed for immediate reference
- Historical Reference: Older versions are available in expandable sections for specific compatibility checks
- Future-Proof: This format can easily accommodate new versions by updating the current version table and adding new expandable sections
Component-Specific Compatibility Notes
File Server Compatibility
File Server Upgrade Requirement
File Server Upgrade Requirement: From version 8.6.5, backward compatibility with older file servers has been discontinued. It is now mandatory to upgrade all existing file servers to the latest build to ensure continued functionality and integration with ServiceOps.
Poller Service Compatibility
- From version v8.6.2 onwards, the Poller Agent must be upgraded to match the ServiceOps server version, as older Poller versions are no longer supported
- Bulk Poller Agent upgrade support via ServiceOps is available from version 8.6.1 onward
Integration Connector Compatibility
- The Integration Connector is supported from version 8.6.1 onward
- Backward compatibility is not supported for the Integration Connector in v8.6.2
- Users must uninstall existing connectors and install the compatible version
Patch Management Compatibility
Ubuntu and Mint OS Patches
Ubuntu and Mint OS Patches: To sync the Ubuntu and Mint OS Patches with the Central Repository, upgrade the server to the latest ServiceOps v8.5.0. Backward compatibility is not supported.
Tenant Architecture Changes
- Starting from version 8.6.2, each tenant must have a dedicated file server. Shared file servers are no longer supported across multiple tenants.
Upgrade Planning Considerations
Phased Upgrade Strategy
When planning upgrades across distributed environments:
- Server First: Always upgrade the ServiceOps server before upgrading agents
- Agent Compatibility: Verify agent versions are compatible with the target server version
- Component Dependencies: Consider dependencies between different components (Poller, Integration Connector, File Server)
- Downtime Planning: Schedule upgrades during maintenance windows
Pre-Upgrade Checklist
Before upgrading any component:
- Verify current version compatibility with target version
- Backup all critical data and configurations
- Review release notes for breaking changes
- Test upgrade process in a non-production environment
- Plan rollback procedures if needed
Post-Upgrade Verification
After completing upgrades:
- Verify all agents are communicating with the server
- Test critical functionality (discovery, patching, reporting)
- Monitor system performance and stability
- Update documentation with new version information
Troubleshooting Compatibility Issues
Common Issues
- Agent Communication Failures: Agents may fail to communicate if version compatibility is violated
- Feature Unavailability: Some features may not work with incompatible agent versions
- Performance Degradation: Older agents may not support newer optimizations
Resolution Steps
- Check Version Compatibility: Verify agent versions against the compatibility matrix
- Upgrade Agents: Upgrade agents to compatible versions
- Restart Services: Restart affected services after version changes
- Monitor Logs: Check system logs for compatibility-related errors