Skip navigation
All Places > Snow Product Hub > General Licensing Forums > Blog > 2018 > December
2018

This article will deal with how to use Snow reporting and License Assignment for Direct License Allocation. Datacenter allocation will be covered in Part 2. This method can be used to assign licenses to a large number of hosts - speeding up the initial allocations when implementing Snow. Its also a good housekeeping task to check regularly that new unlicensed servers arent appearing in the estate. 

First report on the unlicensed servers:

1. Run the ‘License tracking per Computer’ report. Filter on ‘Windows Server’
2. Add columns for ‘Datacenter Name’ as well as ‘Compliance’ and ‘License Requirement’.
3. Filter on ‘Coverage reason’ = None. Your report should look similar to the screenshot below.

4. Save this report and schedule if desired – recommend weekly.
Now prepare the import spreadsheet:
5. Now export this report to XLS – it’s the list of all unlicensed Windows Servers we will work with in the next steps.
6. Remove any servers you don’t want to cover at this time – e.g. other Physical hosts requiring DC licenses
7. Add a column for the ‘Allocation’
8. Add a column for ‘ExternalID’ – this needs to match the ‘ExternalID’ field in the information tab of the license you want to assign (Note ExternalID is normally blank unless you have added a value when you added the license)
You can also use the ‘License ID’ value, which is the unique ID Snow assigns to each license – both fields are visible in the column selector of the ‘List All Licenses’ view from the Licenses Tab

9. In the XLS add the correct number of processors or processor cores to the allocation field, to match the License Requirement field, and the License or External ID of the license where they are to be taken from.

Now import the allocation:
10. From the ‘Home’ menu select a ‘License Assignment Import’ – select the XLSX above

11. Map 'Assign to' – ComputerName and ‘Assigned Quantity’ -Alocation – ‘Type’ is only necessary if datacenter licenses to be allocated. LicenseID or ExternalID is automatically assigned if it matches.

Click next and the preview screen shows the allocations that will be assigned

12. Proceed if no errors and perform a ‘License Recalculation’ to see the results in Snow License Manager

Caught in The Web

Tracking and metering software usage is one thing – but what about tracking web applications? This article will serve as an introduction to the world of Snow Web/Cloud App Metering. We will take a look at the two methods Snow provides – and their limitations, pros and cons.

 

Web App Metering Method

The “traditional” method of web app metering is fairly basic and still fully supported by Snow – set a web pattern in SLM:

 

 

A web.config file is then created in the Snow Agent install folder on the client machine. This method works by referencing the client machine’s DNS cache. You can view this on your own machine from a command prompt using the command ipconfig /displaydns.

Unfortunately, whilst this technique is largely robust enough to show who had accessed what, this method will not show the where and the how long. For example, it will show that a user had accessed the site, but not what features and not the length of time.

Furthermore, the DNS cache is not readable in all corporate environments – proxies can block this, for example.

 

Cloud App Metering With Inventory 6

Cloud App Metering incorporates DIS (Data Intelligence Service) rules. Within the DIS, patterns and rules are stored which can recognise which features, pages, tools, etc of a particular web app was used.

This is useful as many web apps offer different subscriptions levels which make certain parts available. With Cloud App Metering, it is possible to view which features are actually being used and which aren’t.

 

 

The task of adding web patterns into Snow License Manager is not necessary here, as the DIS rules are uploaded to the Software Recognition Service. Each web app is then assigned a unique ID and the rules are stored within the Snow Inventory database.

The Cloud App Metering rules are then downloaded by the Snow Inventory Agent and stored on the local machine.

 

Browser Extensions

 

 

The above is facilitated by the use of a browser extension – currently we support Chrome, Firefox and Internet Explorer 11. Browser extensions are installed via the agent, once Cloud App Metering has been activated within the Snow Inventory admin console.

The browser extension will capture all URLs accessed by the browser and stores the information in a \cloudmetering\extension-output directory within the %ProgramData% hidden folder in Windows – this data is obfuscated, meaning it cannot be read and interpreted in plain text. The agent will compare the contents of these results with the web app patterns received by the DIS rules and, when a match is found, will store them and delete all results from the extension.

This data is then sent with the .SNOWPACK file when the scheduled scan and send occurs. Once the Data Update Job runs, it is visible in Snow License Manager.

Cloud App Metering does not store data centrally for all web traffic – only websites that have DIS rules attached!

 

 

 

Setting It Up

Here’s how to setup the Snow Inventory to start using Cloud App Metering:

  1.       Agent .config file – the snowagent.config file must contain the following lines within the <SystemSettings> section:

    <Setting key="saas.firefox.enabled" value="true" />

    <Setting key="saas.ie11.enabled" value="true" />

    <Setting key="saas.chrome.enabled" value="true" />

  1.       Activate Cloud App Metering within Snow Inventory console:


  2.       Select the configuration you are rolling the change out to:

  3.       Once the agents receive the instruction, the browser extension will appear on the client machines: