Skip navigation
All Places > Snow Product Hub > Snow License Manager > Blog > 2019 > October
2019

Hi Snow Globe,

as you know, we launched a SLM usability survey in summer, to get a better understanding of the everyday usage and experience of working in Snow License Manager. The User Experience team have, with help from other departments in Snow, sent out a voluntary survey to customers who work hands-on with Snow License Manager.

 

A huge thank you to those who provided feedback!


The learning will help guide our development efforts for future improvements of Snow License Manager.

You will find the summarized results here: SLM usability survey report customer results 

 

If you didn’t participate in this survey but would like to share about your experience using Snow License Manager, feel free to reach out to experience@snowsoftware.com

 

 

SLM Survey image

Released on October 15, 2019.

Release information

Product: Snow License Manager   
New version:      9.4.1
Release date:  15 October 2019 
Distribution:   SUS package
Current status:   Released

 

About this Release

This version of Snow License Manager is released on October 15, 2019. 

Snow License Manager 9.4.1 will replace the earlier limited release of Snow License Manager 9.4.0. Snow License Manager 9.4.0 has been removed and will not be available for use. Snow recommends the users of Snow License Manager 9.4.0 to upgrade to Snow License Manager 9.4.1 immediately to be able to use all the changes mentioned in this release notes.

Note that the subsequent release of Snow License Manager 9.5, will come soon; with general availability set for November 2019. We advise you to review the preliminary release notes for Snow License Manager 9.5 to determine your most appropriate update path. The preliminary release notes for Snow License Manager 9.5 will has been available since 25 September 2019.

Enhancements in Snow License Manager 9.4.1:

  • Ability to un-assign Oracle licenses
  • Added "Is multiple metrics" column in column selector on Search for applications page
  • Custom compare value type extended to 100 chars
  • Exclude Hyper-V only hosts by default
  • Provide an ability to include hyper-v only hosts into Windows Server license requirement manually

Corrections in Snow Snow License Manager 9.4.1:

  • Data Update Job in a Service Provider installation no longer reports an error after a Customer has been removed (PRB0042521).
  • The Data Update Job has been optimized to reduce execution time when transferring Software rows (PRB0042568).
  • The Data Update Job step Refresh Alerts has been optimized (PRB0042572).
  • Empty, duplicated, or 0.0.0.0 IP addresses are not shown in the computer list anymore.(PRB0042570)
  • Quarantine management will now correctly change a computers' state from 'Quarantined' to 'Inactive' when the configured threshold is met(PRB0042541).
  • We have corrected the API to display the compliance trend tab correctly(PRB0042515)
  • When adding a maintenance date while editing a License, the "Today" button will now properly select the current date (PRB0042574)
  • Resolved an issue when a device is used to run remote applications on servers in different organizations (PRB0042463).
  • When Oracle Database 18c is inventoried as part of the customer's Oracle estate, some customers may be experiencing UI issues in the Oracle Database Product instances overview. This latest version properly shows all inventoried Oracle Database 18c instances. (PRB0042520).
  • Some Oracle background processing tasks that need more time for execution on some customer environments, will now have the possibility to be reconfigured in order to complete successfully (PRB0042577).
  • Fixed gathering Web metering information (PRB0042086).
  • Resolved a conversion issue, due to specific regional settings, that prevented scheduled reports to be sent properly (PRB0042372).
  • Optimized the API request (PRB0042504)
  • When a user has a different region configured than English (US), adding a maintenance date to a license should no longer show a warning that the data is incorrectly formatted (PRB0042602).
  • A server that has Windows Server as the operating system and hosts virtual machines which have Windows Server installed now is excluded from Windows Server license requirement by default ( PRB0042398)
  • Added "Included in Windows Server license requirement" checkbox on Computer edit page General tab, which is visible only for hosts that have Windows Server OS. When checked, the host Windows Server installation will be counted in compliance Hyper-V only hosts are excluded by default. ( PRB0042398).
  • Fixed handling restricted user access when navigating from the "Datacenters and clusters" page to a data center/cluster details page. ( PRB0041897)
  • Displaying "Extended coverage" in the "Coverage reason" column in the "License tracking per computer" report when computers are covered by extended coverage. ( PRB0041606)
  • Fixed an issue where a deactivated CustomerId could prevent the Data Update Job from finishing. (PRB0042609)
  • Improved handling of multi delete computers in Snow License Manager. Users will no longer have to wait for the transaction to complete in the graphical interface. (PRB0042254)

SLM 9.4.0 was planned to reach General Availability (GA) on October 9. During the phased rollout we identified that one of the corrections mentioned in the release notes did not end up in the final package. This has now been fixed in the patch release of Snow License Manager 9.4.1 which will replace Snow License Manager 9.4.0 that has been withdrawn.

Information will be provided through release notes, Snow Globe, Support Portal and, Partner portal.

Snow License Manager 9.4.1 will go GA and be available on SUS on October 15 from around lunchtime (CET).

 

Snow’s Phased roll out releases

Snow has recently started doing releases in a phased manner for their products, Snow License Manager and Snow Inventory Server. The first phase goes only to a selected few customers. General availability follows within two weeks. The reasons for doing a phased rollout are:

  • Customers are given the possibility to play a pivotal role in the validation of new software releases and technology components.
  • Because the release isn’t rolled out to all customers at once, eventual problems can be fixed before or closely after the release is available for the larger mass. 

  • Furthermore, information learned from the early rollout phase can be applied to guide customers so that there are fewer issues post GA. 

If a defect, found during the phased rollout, must be fixed before GA, the dot version of the release will increase.

Depending on what will be discovered during the phased rollout, the length of this phase may vary and the GA date might change. Normally we strive for a period of maximum two weeks between Release to Market (RTM) and GA.

Just like in my latest blog post "Did you know? - Exporting all your machines" you may want to export or backup your licenses, to either save your current state or to import them into your test environment.

 

This is pretty easy to do - follow these steps to export your licenses:

 

  1. Open up the report "List all licenses" and choose the license you want to export. In my example i choose the following one:
  2. Click on Column selector and drag & drop the column "legal organisation" to the report.
  3. Now click on the three dots on the right side and choose Export -> Export as Excel.
  4. Open up your Excel which we will need to modify a bit, it should look like this:
  5. In the column "Legal organisation" you will now need to change the value, fitting to the target organisation in which you want to import the license. In my example i want to import the license to My Company / Germany / IT, which looks like this in the Organisation Structure in SMACC:

  6. The fields in the Legal Organisation column in my excel sheet need to be ROOT,DE,IT.

    Be sure that the target organisation is a legal entity. This option is set in SMACC. Otherwise you will not be able to add a license to this node.

  7. If you want to, you can change the quantity, license costs, etc.
  8. In your Excel sheet add the column "Assignment Type" and enter - by default - "Organization" as shown in the Screenshot in step 4.
  9. Now to import the license, open up SLM and go to Home - import data - license import.
  10. Make sure that the following mandatory fields are matching correctly to your sheet. If you use the exporting feature i've shown in the first steps, you need to choose the column Application as Application name:
  11. Make sure to select the legal organisation and the assignment type columns (which we created earlier)
  12. In the next step you should be able to preview the license which will be imported:
  13. And finally:
  14. You have now successfully duplicated the license:

Protip: The id is the one assigned to that license which you can see when opening the page

Protip: The id shown in step 13 is the one assigned to that license which you can see in the URL when opening the license in SLM: