Jan.christoffels

SNOW LICENSE MANAGER COVERAGE FOR  WINDOWS SESSION VIRTUALIZATION

Blog Post created by Jan.christoffels Employee on Apr 20, 2018

A connection broker connects users to the remote desktop server in the private datacenter or public Cloud. The application then executes entirely on the server and is visualized on the client via a display protocol. The user interacts with the application remotely by sending mouse-clicks and keystrokes to the server. The server then responds by sending screen updates back to the user’s device. Session virtualization allows any user on any operating system to access any windows application delivered by IT. As a result, enables Windows, Mac, Linux, iOS and Android devices to run any windows applications and or desktop using session virtualization. Furthermore, session virtualization leverages server-side processing power.

 

The applications are either published or the users log in to the remote desktop to access their applications.

 

The following session virtualization solutions are supported by Snow License Manager:

Citrix XenApp

Microsoft Remote Desktop Services

 

“THE SAM CHALLENGE”

Licensing of session virtualization can be based on, for example, server installations or accessing devices. For some applications, licensing is based on the number of users that the application has been published to, and that have the possibility to run the application. Active Directory groups are often used for granting application usage rights, and Active Directory group memberships are then used as basis for license requirement calculations.

The challenge is to obtain correct information on application access to be compliant and not overspend.

 

“THE SNOW SOLUTION”

 

INSTALLATION AND PREPARATION

To utilize the functionality for session metering and to gather usage for license optimization, the

Snow Inventory Client for Windows must be installed on the server host.

 

CALCULATION OF LICENSE REQUIREMENT

Snow Inventory Client for Windows identifies on which servers the applications are installed, and which devices and users that access the application. Actual usage of the application is metered as well to provide the possibility of license optimization.

 

APPLICATION USAGE RIGHTS

When a user has been granted application use rights it means that the user has been allowed to use a certain application. However, it does not automatically imply that the user has accessed it.

For applications that are licensed on application usage rights, follow the steps below to keep track of number of granted use rights versus actual usage:

  1. Create a Custom compare value type, named AD Access Rights.

  2. On the License settings tab in Application details, select Custom compare values from the Metric dropdown list, and select AD Access rights from the Custom compare value type dropdown list.

  3. On the Compare values tab in Application details, add Organization nodes and Quantity of users that have application usage rights.
  1. When compliance is calculated, license requirement will be based on registered Quantity.

 

REMOTE DESKTOP SERVICES APPLICATIONS

In Snow License Manager a device is a computer or object that has been connected to one or more remote desktop servers and/or virtual desktops. It may for example be a home PC, a smartphone, a thin client, or an inventoried computer.

With Snow Inventory Client for Windows installed on the remote desktop server, all devices that access the remote desktop server applications will be identified. Snow License Manager supports secondary use rights in remote desktop server environments where software is installed locally on rich clients.

EXAMPLE

Scenario for Microsoft Office 2013 Standard

Several devices are identified to access the application Microsoft Office 2013 Standard that is installed on the remote desktop server. In Snow License Manager the fictional application TS-Microsoft Office 2013 Standard is added to those devices.

If the accessing device is an inventoried computer with a local installation of the application, secondary use rights must be applied to avoid duplication.

To achieve this (note that the application must be in Edit mode):

  1. Change metric for the remote desktop server application according to agreement, for TS-Microsoft Office 2013 Standard = Based on total devices 
  1. For the application TS-Microsoft Office 2013 Standard and on the License settings tab, enable the option Suppress this locally installed application when inventoried on remote desktop servers and select to suppress the corresponding application Microsoft Office 2013 Standard.
  2. For the application TS-Microsoft Office 2013 Standard and on the License settings tab, enable the option Enable secondary use rights.

With the settings in place, correct license requirements will be automatically calculated according to the example below.

MICROSOFT OFFICE 2013 STANDARD

Server installations = 1

Computer installations = 500 + 200 = 700

Total installations: 701

Reduction = 1 (the server installation is discarded with the Suppress this locally installed… option)

Total number of installations that require a license: 701 – 1 = 700

 

TS-MICROSOFT OFFICE 2013 STANDARD

Accessing objects (devices) = 300

Accessing inventoried computers (devices) = 500

Total number of accessing devices = 800

Reduction = 500 (number of inventoried computers with local installation of MS Office 2013 Standard)

Total number of devices that require a license: 800 - 500 = 300

 

Total requirement for Microsoft Office 2013 Standard is 1000 licenses.

 

NOTE

When registering the license purchase for Microsoft Office 2013 Standard in Snow License Manager, the purchase needs to be divided in two: one license purchase for Microsoft Office 2013 Standard and one for TS-Microsoft Office 2013 Standard.

 

PRESENTATION IN SNOW LICENSE MANAGER

In Snow License Manager and Application details, a summary of license requirement and purchased licenses is presented. Excluded installations are indicated on the Compliance tab.

EXAMPLE

Metric: Devices

Inventoried computers that are Covered by secondary use rights are indicated by the remark U.

EXAMPLE

Metric: Installations

EXAMPLE

Metric: Custom compare values

 

 

Outcomes