MSDN licensing options in Snow License Manager

Document created by marc.farmen Employee on Aug 18, 2017
Version 1Show Document
  • View in full screen mode

Within Snow License Manager two approaches can be taken to handle MSDN subscriptions. Both approaches outlined below can be implemented with short services engagements from Snow. Please contract your customer success representative for more information. 

 

Option 1: Device Based Approach


Snow License Manager can be setup to have separate “Organization Units” that include all applications that can be used under each program. For instance, an OU can be setup called “MSDN Enterprise”. Any device that is placed inside this OU will then be exempt from the over 200 products Microsoft allows under the “MSDN Enterprise” subscription.


This option is typically used when MSDN users are in a lab or development environment. When testing new applications, the users are typically not logging into each device with their own user name. Developers often use service accounts and test accounts as they are in the development process.

“Auto Connect” rules can be setup by device name wild cards, IP address ranges, serial numbers, and other factors to be automatically moved into these specific MSDN OU’s. Once a device is moved into each of the MSDN OU categories all MSDN applications on the device are removed from the overall compliance position for Symantec.


Example Screenshot:


 

Option 2: User Based Approach


Snow License Manager can also be configured in a user based model. Each MSDN subscription model such as “MSDN Enterprise”, “MSDN Professional”, “MSDN OS”, etc. is created in License Manager. This is a single application that contains the bundled applications that correspond to each subscription. (see screenshot)

 

A “MSDN Enterprise” user based license can then be applied to each user ID that has a valid subscription. Any machines on which the MSDN user is the “Most Frequent User” based on time logged on to the device will be exempt from the 200 plus applications that are allowed under each subscription.

 

Example Screenshots:



9 people found this helpful

Attachments

    Outcomes