HomeNetwork GuideReferenceServer Software Version History

4.5. Server Software Version History

Release 7.5.1, October 2016

Significant maintenance fixes:

Release 7.5.0, July 2016

Significant maintenance fixes:

Release 7.0.1, September 2014

Server Manager 7.0.1 has no significant functional changes from release 7.0.0.

Release 7.0.0, July 2015

Server Manager 7.0.0 replaces Server Manager 6.x. The new version can handle any 7.x licenses and clients, as well as 5.x/6.x licenses and clients.

Release 6.3.1, September 2014

Server Manager 6.3.1 has no significant functional changes from release 6.3.0.

Release 6.3.0, June 2014

Significant maintenance fixes:

Release 6.2.1, March 2014

Server Manager 6.2.1 has no significant functional changes from release 6.2.0.

Release 6.2.0, September 2013

Server Manager now displays the Palisade vendor daemon port in addition to the lmgrd port. Both can now be set on Server Manager's Options screen.

Server Manager and this Guide are now available in all the same languages as the end-user software.

Server Manager and the client installers are now available in MSI versions as well as EXE.

Significant maintenance fixes:

Release 6.1.2, April 2013

Server Manager 6.1.2 has no significant functional changes from previous releases.

Release 6.1.1, February 2013

Server Manager 6.1.1 has no significant functional changes from Server Manager 6.0.1.

Release 6.0.1, October 2012

This is the initial release of Server Manager. Although the underlying license scheme is similar to 5.x, the interface for server administrators and end users has been made much more convenient. The interactive Server Manager replaces LMTools and all command-line operations.

For Concurrent Networks, server administrators can easily allow or disallow borrowing and set a maximum borrowing term. If borrowing is allowed, end users can borrow a license through @RISK and the other applications, with no need for a separate borrowing utility.

For Enterprise Networks, end-user license activation is normally done silently by the client installer. But if that fails for any reason, end users can activate through @RISK and the other applications, with no need for a separate activation utility.

Last edited: 2017-12-02

This page was: Helpful | Not Helpful