7.3  ->  7.4 Important changes

This document describes the most important changes that a 7.3 admin should understand in order to take advantage of the new features in 7.4. New features are described with 7.3 as a point of reference and features that are essentially unchanged will not be mentioned here.

When you are ready to upgrade from a 7.3 installation, read the Server Upgrade 7.3 to 7.4 document, as it will give detailed steps including what to expect once you have upgraded.

If you are upgrading from 6.2 or older, read the changes 6.x -> 7.x document for details on the many significant changes to both the UI and functionality made since the 6.x versions. You can upgrade directly from any 6.x version to 7.4 (without going through an intermediate 7.0 / 7.1 / 7.2 / 7.3 upgrade) – but be sure to read the Server Upgrade 6.x to 7.x documentation.

Admin Alerts & Journal

In K2 version 7.4, we have added a Journal of configuration changes and events occurring in KeyServer. Some of these Journal entries get written as a result of an admin taking some action. For example, the Journal could record that the admin named Joe has changed the license limit for a particular Policy. Other entries are the result of automatic processes, and these are also Alerts, to make sure that Admins are aware of them. For example, a failure to export is recorded and displayed as an Alert. For more about this topic, refer to the Admin Alerts & Journal documentation.

Core, Socket, & PVU licensing

We continue to expand the license metrics that we support. For v7.4 we have added support for Core licensing - which essentially counts the number of cores on each computer instead of simply the number of computers. This is a license metric that is being used more and more by Microsoft. Also, in we have added support for Socket licensing. For Socket licensing, the number of physical CPUs ("Sockets" or "Packages") is counted. PVU, or Processor Value Units, is a metric defined by IBM. In this metric, each different type of computer can be assigned an arbitrary weight, or number of units, which are consumed from a purchased number of units.

Improved Availability Maps

Availability Maps were first added in K2 version 7.2. Since then we have been adding functionality, such as the ability to show lab hours, show software products installed on computers, and embed links or external html. In 7.4, Availability Maps are able to distinguish between computers that are turned off and computers that are on but with no one logged in. Also we have added a public view of historical availability - i.e. an indication of which hours are busiest. Finally in the "admin view" we have added a "Heat Map" that shows which computers in each division have been logged into the most.

JavaScript API

Starting with version 7.4, KeyConfigure can be extended via JavaScript. With the embedded JavaScript engine, you can write scripts that access, read, and modify the basic objects in KeyConfigure such as computers, policies, and products. You can also access and open new windows containing these objects. For more about this topic, refer to the Extending KeyConfigure with JavaScript documentation.

Record Tagging

We have added "tags" which can be applied to Computers, Policies, Products, and Users. A tag is arbitrary text which can be associated with any object, or multiple objects. This allows additional data attributes to be attached, even when there is no appropriate place in the standard fields. Tags can then be used simply for reference, but also for flexible filtering and aggregation within reports. For more about this topic, refer to the Tags documentation.

Policy Details UI

The Policy Details window has been changed a bit in 7.4. Some of the changes are UI only - functionally there is no difference from 7.3. Others add new functionality.

For more about these options, refer to the Policy Details documentation.