Compatibility between components
We always aim to maintain compatibility between all releases of the deviceTRUST® components, however sometimes this is not practical.
The table below details our common approach to compatibility. Before any upgrade of a component, it is strongly recommended to read the release notes of every released version of the software from the currently installed version to the target version being deployed. The compatibility section of the release notes may contain important information that overrides what is detailed here.
| Component | Capability | Previous (all versions) | Current (all versions) | Future (all versions) |
|---|---|---|---|---|
| deviceTRUST Client Extension | Can send properties to deviceTRUST Agent version | ✓ | ✓ | ✓ |
| deviceTRUST Agent | Can receive properties from deviceTRUST Client Extension version | ✓ | ✓ | ✓ |
| deviceTRUST Agent | Can load configurations from deviceTRUST Console version | ✓ | ✓ | ✗ |
| deviceTRUST Console | Can load configurations from deviceTRUST Console version | ✓ | ✓ | ✗ |
Note:
- We recommend where possible that the deviceTRUST Console and Agent share the same version number.
Upgrading
As a result of the compatibility between the deviceTRUST feature releases, the following upgrade process is recommended.
- Upgrade and deploy the deviceTRUST Agent.
- Upgrade the deviceTRUST Console.
- Upgrade the deviceTRUST Policy by opening and saving the policy within the new deviceTRUST Console.
- Deploy the upgraded deviceTRUST Policy based upon your deployment technology of choice.
Note:
- We recommend that the upgrade is first performed in an isolated, non-production test environment.
Compatibility between components
In this article
Copied!
Failed!