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 should be handled – ignored, denied, observed, or actively managed. By setting up such policies, you will be able to understand usage patterns and make […]
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 when it comes to implementing them. Therefore, we’ve put together the video above to help you get going. If you’d prefer to read through the instructions, […]
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 as the enabled count for the Policy) while the KeyServer Administrator retains the ability to work with settings such as Scope, Pools, Schedules, Custom Messages, […]
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 OS (10.13.4) show a warning message when a 32 bit program launches. Sassafras has been preparing for this transition and will supply 64-bit versions of […]
Stata for Mac is frequently managed by K2. With the release of KeyAccess 7.4.0.7, the way that the Stata program is identified has been changed, to allow distinct entries for different editions of Stata. If the Product Recognition Service (PRS) is enabled within K2, standard definitions for Stata have automatically been updated. If however, PRS […]
The collection and analysis of software license entitlement data in software purchase records is essential to Software Asset Management best practices around compliance analysis and overspend reporting for cost reduction efforts. It is not possible for a software asset manager to complete the full disposition of their duties without comparing software procurement levels to deployment, consumption, […]
Best Practices for correctly configuring Policies to track and manage software usage. K2-KeyServer can conduct many activities to support your organization’s IT management goals. It handles Software Asset Management (SAM), Hardware Asset Management (HAM), Software License Management (SLM), software usage tracking and optimization of computing resources (both software and hardware). K2 also supports IT Procurement […]
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 load profiles depending on the number of clients it supports and what products are being tracked — we can give some general guidelines to follow when […]
K2 has included an availability map feature since 7.2. Some of the main functionality is explained in an earlier post about Availability Maps as well as in the Documentation on Availability Maps. With the release of K2 7.4 the basic functionality has been augmented with two new features. Heat Maps The first new feature is […]
Several Bentley products are licensed based on the maximum number of objects that can be created. For example, a WaterCAD license might limit the number of “pipes” allowable within a model. In K2 7.4 you can configure different policies to represent each “pipe” level by using the new Tags feature. This post describes how you can create policies to support […]