Introduction
This document is specific to ICE 3.6.5 and provides instructions for upgrading an existing 3.5.1 or 3.6.0 ICE Server to the 3.6.5 release.
Important: When upgrading from 3.5 to 3.6.5, the upgrade scripts produce a new Server Group from each server in the old system. Georedundant configurations are also effected. Consult the Post Upgrade Steps for instructions.
Important Changes to Certificate Management in 3.6.5
When installing or upgrading to 3.6.5, the ICE OS Installation Wizard generates a certstore and a new set of certificates. These certificates, including the certificate authority (CA) used to generate and validate them, are entirely unique to the system being installed or upgraded.
In Tactical environments, where an ICE Server is not in use, ICE Mobile, ICE Desktop and ICE Agent components ship with a new, default, certstore.
Peering Rallypoints: When peering Rallypoints between different ICE Server systems, all Rallypoints must use the same certstores. In versions prior to 3.6.5, this was always true, unless an administrator applied their own certstore. In 3.6.5, each ICE Server system uses its own certificates. To reconfigure the system to use the correct certstore for peering, an administrator should create a new certstore and then apply this certstore to all ICE Server systems with Rallypoint connections. This only applies when peer-meshing Rallypoints. Hybrid Tactical Environments: In 3.6.5 and newer, Tactical clients cannot connect in hybrid (Enterprise/Tactical) environments. If you are in Tactical mode on a client, then the client cannot establish Enterprise Rallypoint connection to the ICE Server. Connections can only be made with other Tactical Rallypoints relying on the same RTS certstore.For additional information, refer to the ICE Admin Guide > Appendix K: ICE Private Certificate Stores.
Server Group Transition Note