On June 22th 2015, OpenDNS released the Roaming Client for Windows version 1.7.117 The upgrade was delivered Monday June 22nd 2015 for all customers on the stage track.
The upgrade is now being made available for customers on the production track. As part of a staged process, the first wave of customers will receive the upgrade on Thursday, July 9 2015. The second stages of production upgrades will occur over the next 2 to 3 weeks.
Customers running earlier versions of the Roaming Client will receive updates inclusive of other minor point versions which had been previously released. If a Roaming Client were running an earlier version (eg: 1.6.68), it will upgrade to 1.7.117 directly and will receive all of the changes included in the minor point versions in between.
It will be a single update to 1.7.117 for all customers with all older versions.
CHANGE SUMMARY (1.7.64 to 1.7.117)
- Fixed an issue where certain features can fail if a machine is renamed between the point in time of the initial registration of the machine, and the first time the features are enabled in the policy.
CHANGE SUMMARY (1.7.41 to 1.7.64)
- New certificates have been added to the Roaming Client for accessing OpenDNS cloud resources
- Fixed an issue with incorrect allocation of memory
- Fixed a bug which caused Roaming Client to "upgrade" to a previous version of the software in certain cases
- Fixed minor issues where changing the name of a Roaming Client in the Dashboard resulted in a new registration upon upgrade to a later version.
CHANGE SUMMARY (1.7.30 to 1.7.41)
- This release of the Roaming Client addresses an issue where if a computer's hostname has changed since it was originally installed the computer’s existing roaming computer entry could be orphaned and a new entry would be generated. A new entry may disassociate the Roaming Client from its previous security policy and as well as its reporting.
- This version contains some foundational changes in preparation for new features that will be released in the future. This functionality is disabled by default pending a subsequent release.
CHANGE SUMMARY (1.6.68 to 1.7.30)
- The Roaming Client now upgrades to the latest version within 15 minutes of persistent connectivity. Previously, the Roaming Client was required to be online for 2 persistent hours before the upgrade initiated.
- This version adds the tracking of state changes and health check successes and failures to the Roaming Client diagnostics. This functionality is disabled by default pending a subsequent release.
- This version contains some foundational changes in preparation for new features that will be released in the future. This functionality is disabled by default pending a subsequent release.
Comments
0 comments
Article is closed for comments.