Many organizations today are still getting to grips with the licensing implications of virtualized technologies such as VDI, Citrix and Terminal Services, where instead of being simplified, controlling licensing often becomes much more complex and high-risk as the licensing metrics change and potential access to software is significantly increased.

A prime example is when organizations wish to publish software within Citrix and Terminal Services and tend to lock down application access at a user-level through Group Policy. The issue with this is that vendors such as Microsoft have device-based licensing models, whereby all devices with access to specific software titles would require a license, regardless of the actual user count.

Having to purchase licenses for all devices regardless of the business need is very expensive.

The AssetStudio for Windows & Mac OS AccessCtrl module is a must-have for organizations that are heavily reliant on Thin Client technology such as Citrix and Terminal Services as it is one of the few solutions that can enforce compliance.

With device-level access control technology, it can enforce access at the device level to comply with device-based licensing metrics and provide the required evidence of control to satisfy vendors such as Microsoft.

For organizations with software such as Microsoft, the AssetStudiofor Windows & Mac OSAccessCtrlmodule can enforce device-based software license control, allowing savings to be made on the number of application licenses required by controlling which users or devices have permission to run named applications. Limits can be placed on the number of application instances and which devices or users can run an application.

The AssetStudio for Windows & Mac OS AccessCtrl module allows organizations to control which approved applications can be accessed based on where the user or device is, the device being used, or when the user is attempting to launch the application, preventing unauthorized software.

With the AssetStudio for Windows & Mac OS AccessCtrl module organizations are now in full control. Application access can be defined on factors such as user, location, device name, IP address and firewall settings, providing complete control over what can be executed, from where, and when.