With any system that maintains a database of computers, a critical question is how each record is uniquely identified. For many organizations, identifying computers simply by Computer Name is sufficient […]
During installation of the K2 client, a “Department” field can be placed on the client. This value is then sent from KeyAccess to KeyServer, and can be used in a […]
Any organization using KeyServer has a powerful tool for learning how and where computers and software are being used. Using KeyServer, policies can be configured which specify how product usage […]
Though availability maps have been around since the 7.2 version of KeyServer, we’ve found that many K2 administrators either still aren’t aware of them, or they just aren’t sure where to start […]
Sassafras supplies an API that third party vendors use to build KeyServer support directly into their products. A vendor builds a custom license (.lic) file that includes basic details (such […]
Last year Apple announced that High Siera (10.13) would be the last version of OS X to support 32 bit applications. Furthermore, starting in 2018, beta versions of the current […]
We are often asked by new K2 administrators for our recommendations on the system that will host their KeyServer. While there is no optimal system configuration — each KeyServer has different usage patterns and […]
One of the reports we have recently added is the Product Optimizations report. This report aims to help you achieve cost savings by pointing out alternatives to expensive suite products. […]
K2 is a powerful Hardware Asset Management tool. The KeyAccess client collects many hardware properties which are saved in the Computer Database. However, Computer records also have some additional fields […]
In the 2015-02-25 image, we have added six new Login reports. Here’s a quick peek at one of them: The report above lets you easily compare computer utilization on different […]