K2 v7.1 (2014-04-28 Image) 
(a yellow icon above, instead of green, indicates that this local document is not the latest -- the latest warnings are online)
Read this document for notes on bug fix or upgrade issues that warrant emphasis, explanation, or might otherwise be overlooked.
In addition to the specific warnings below, always consult the comprehensive list of all important bug fixes as documented in:
Component History (2014-04-28)
For information on the previous version, consult 7.0 Warnings & 7.0 History.
Partner Notes documents possible issues concerning any third party product which may have been purchased with pre-configured KeyServer control built in by the software publisher. [Note: the icon for a publisher supplied license certificate (.lic file) will appear in KeyConfigure's Licenses window with a green tint.]
Upgrade KeyServer to ensure that license policies created by a non-Full Administrator will manage clients correctly (2014-04-28)
When KeyConfigure is set up with multiple administrative accounts, including some that do not have Full privileges, you should upgrade KeyServer to version 7.1.0.9 ASAP. Prior versions of KeyServer have a bug that prevents policies created by an account without Full privileges from correctly conveying additions and changes to the client computers.
Upgrade KeyServer and run KSdbConsist to remove entries in the audit database for uninstalled programs (2014-03-11)
You should upgrade KeyServer to version 7.1.0.8 ASAP, and allow KSdbConsist to run as part of the upgrade. Prior versions of KeyServer have a bug that prevents deletion from the audit database so that audit reports will always claim some programs are installed even if the software has been un-installed. An initial audit followed by the normal incremental audits will not expose this bug. But when a client computer has been instructed by KeyServer to do a “Full Audit”, the bug will prevent the removal of audit records corresponding to software that has been un-installed. While full audits are not common, they may have been triggered by a re-install of KeyAccess or other operations resulting in deletion or modification of the local audit file. KeyServer 7.1.0.8 or better fixes the bug, and KSdbConsist updates the KeyServer audit database so that subsequent full audit information will be accurately recorded.
KeyAccess on Windows should be upgraded to 7.1.0.5 or better in order to distinguish between Windows 8 and 8.1 (2013-10-28)
Windows 8.1 has a bug that causes it to inaccurately report its full version to any requesting program. If you have computers running Windows 8.1 and an older version of KeyAccess, the OS version will be reported as Windows 8.0. KeyAccess 7.1.0.5 and higher contain a workaround so the OS version is accurately detected on Windows 8.1.
KeyServer and KeyConfigure on Mac OS X should be upgraded to 7.1.0.1 or better in order to run on Mavericks (2013-10-28)
Anticipated changes in Mavericks (Mac OS X 10.9) require that you upgrade to KeyServer and KeyConfigure 7.1.0.1 if those components are run on the new OS. KeyAccess and KeyReporter are not affected, so upgrading those components is not critical.
KeyServer should be upgraded to 7.1.0.2 or better for accurate tracking of offline usage (2013-08-01)
A bug in KeyServer 7.1.0.0 - 7.1.0.1 would cause some offline events to be discarded by KeyServer. If your KeyServer is managing computers that are sometimes used 'offline', you should upgrade to KeyServer 7.1.0.2 as soon as possible in order to ensure the most complete data will be available for accurate usage reporting.
KeyAccess on Mac OS X should be upgraded to version 7.0.0.7 or later ASAP (2012-05-23)
A rare bug in KeyAccess (Mac OS X only) could cause a preferences file to become corrupt, which would lead to KeyAccess improperly deny launches of some programs. This condition could be temporarily fixed by restarting the client computer, but subsequent versions of KeyAccess fix this bug.
Upgrade cautions when converting from a 7.0 installation (2013-05-15)
Read the Major Upgrade documentation!
K2 7.1 requires a new license certificate (server.lic) and new KeyConfigure. Before upgrading an older KeyServer version (6.2, 7.0, etc) you must receive a new license certificate configured for 7.1 support -- a 7.0 or earlier certificate will not enable version 7.1.
The major version of KeyConfigure version and KeyServer version must match (e.g., first two digits must match). KeyConfigure 7.0 won't connect to KeyServer 7.1, KeyConfigure 7.1 won't connect to KeyServer 7.0.
Any KeyShadow installs must be discarded whenever the KeyServer process is upgraded. The KeyShadows must be recreated with a version 7.1 shadow certificate created by the version 7.1 KeyConfigure.