HelixNet Configuration File Compatibility
HelixNet configuration files are forward compatible.
Updating of HelixNet configuration files can only occur during HMS-4X upgrade
Downgrading HelixNet system will always reset the configuration to default
Upgrade the Link Master between 1 major version at a time (i.e from 3.x to 4.x) to ensure the configuration file upgrades
During an upgrade to a higher version the HMS will upconvert the configuration files database to the latest file format immediately following the upgrade of the systems firmware. This may take a while, depending on system and configuration size, following the upgrade and the HMS may look unresponsive during the process. Please leave the HMS to do its configuration upgrade processing of the configuration for at least 5-10 minutes.
Configuration files saved on a previous versions of HelixNet will not be compatible and will return an error when an attempt is made to restore an older file on a newer system. Configuration files can only be upgraded during an upgrade process.
HelixNet version 3 added substantial additional configuration options with the addition of the CCM and endpoint Roles. It is recommended to rebuild the configuration if a system is being upgraded from version 1 or 2 to make use of the capabilities in version 3 and higher.
This solution is written at the time of release of HelixNet version 4.1
Related content
CAN'T FIND YOUR ANSWER? CLICK HERE TO CONTACT SUPPORT
This solution was provided by Clear-Com via a question submitted to us by customers like you. If you wish to share with us a new solution or update an old one, please follow this link..
The information on this page is owned by Clear-Com and constitutes Clear-Com’s confidential and proprietary information, may be used solely for purposes related to the furtherance of Clear-Com’ business and shall not be disclosed, distributed, copied or disseminated without Clear-Com’s prior written consent. Click Here for Clear-Com's privacy statement.