Snow License Manager

We use SNOW to keep track of our users in our SAP system. It gives us an easy overview

We use SLM for license management in order to create license compliance. We also use contract management to manage our IT contracts. It is important for us that the license rules from the manufacturers are mapped in Snow. This means that we can rely on the license balance created by Snow.

We use Snow License Manager for compliancy check on software licenses. Snow License Manager is also used by the IT engineers for information about the usage of software product with the hospital. Snow License Manager give us a " live" view of al servers and clients useds within the hospital, thsi information is used in IT asset management and lifecycle of the hardware items.

Snow License Manager is used to track licenses and it's usage. I have also implemented processes to published authorised and denied software allowed to be installed on companies computers.

Aspiration is that Snow License Manager provides accurate information to enable informed decisions to be made around license usage, vendor spend and reduce risk of unlicensed or end of life software.

We use Snow License Manager to monitor and manage our software landscape. We use it to track installations and removals of software along with usage. We also use it to help monitor the active computers in our environment. We record our software purchases and licenses in SLM in order to track our software compliance position. If it relates to software, Snow License Manager is our organizations single source of truth.

We use it to managed our licenses. We check if there is any diferrence between the amount of licenties we have en the amout we use. We check if there is a posibilty to spare some money. The scope is the two hospitals and other departments in the region where we use IT. Sometimes there is a check which applications are installed on specific devices.

I use Snow License Manager to manage all computers, licenses and IT contracts. The most important thing here is to always have license compliance in view.

A way to see and inventory IT Assets globally. Be able to respond to audits and maintain software compliance. Snow data has also helped with multiple IT projects for upgrading or refreshing hardware.

Snow License Manager is used to manage over 1000 agreements and 11,000 software licenses. We also heavily use the computer and user discovery data to supplement our ITSM system and validate when the device was last used, and by whom.

So far we use Snow License Manager to monitor software usage. We are in the process of entering all contracts into Snow to gain visibility into software costs and compliance. This allows us to pass on costs to the actual users. We also want to gain insight into the actual use of licenses. In addition to the software inventory, we also want to map the hardware per department.

Snow License Manager is used to analyze and manage our broad license landscape. With Snow, we are able to gain knowledge on a more accurate license volume estimate, which saves on license cost, but also we are able to analyze trends and make a more accurate prediction of required software (by use). With the "snowboard," we have a handy dashboard that alerts us for upcoming negotiations and license saturation. With automated reports, we are able to help product owners, giving them an overview and alerts.

I use Snow License Manager for many tasks, but it's main use is what is was designed for Software Asset Management, we keep all of our Contracts, license agreements, subscriptions, license keys, etc. in Snow License Manager and then allow the tool to do it's work and report to us on our compliance position. But the data from Snow License Manager is so rich that we also complete many other tasks on a daily basis with this data, such as identifying unauthorised software installations and getting them removed, or reporting on failed services after an application update, or reporting on firmware versions installed across the network, or...

Snow License Manager is used in our organization for four main purposes: to determine which applications are run and where on 35,000+ computers running Windows, iOS or Linux, to alert responsible individuals to application license expiry and warn of impending and current compliance issues, to assist purchase planning and department software requests , and to identify and harvest unused licenses for reuse elsewhere according the the licensing terms. Before Snow License Manager was deployed in our organization, each branch managed software according to its own capability. There was no comprehensive, holistic application contributing to the awareness of licensing issues. Although each branch did its best, no one really knew the software estate's size, value or deployment. Where permissible by the licenses, there was still little sharing of licenses between international branches, which led in some cases to over-purchasing. Another issue was identifying unwanted and insecure applications. Also many varied applications doing basically the same thing had been deployed. Using Snow License Manager and carefully examining the use cases, the number of different applications used could be reduced. This simplified software asset management. The small footprint of the Snow Agent Manager permits deployment even in the most demanding computing environments.

The organization has ~35,000 networked computers and about the same number not connected to the network. The control of which software is used worldwide in over 80 branch offices throughout the world was an insurmountable problem until that organization began using Snow. It is currently used for almost all network-connected (IT-managed) computers using the Windows and iOS operating systems. Linux is beginning to be implemented. The detached (IT unmanaged) devices are not currently being scanned for software. Frequently unrecognized software appears within the usage of the organization, and the Snow DIS department offers an online Software Recognition Service which adds or amends recognition rules and/or applications to provide recognition for applications that are hitherto unknown. One deficit remains in the case of plugins that run exclusively with the application executable. Very often, these cannot be recognized out of the box, so the solution is to create a local application without recognition rules to manage the licenses. The open architecture of Snow does permit the creation of Powershell scripts that run for such cases, which now begin to be implemented within the organization. The Snow agent, which runs on each managed computer once a day, has a small footprint and does not interfere with compute-intensive applications. All-in-all, the Snow infrastructure is reliable, the service personnel is amiable, and the product is a good choice for large organizations.

We are using SLM to collect and present information regarding our IT estate, what we have installed, where it is, and who is using it. We will be reporting on airgap-separated domains, where licenses may or may not be shared.

We are using Snow to record all of our software licensing and also monitoring utilization. It is primarily managed by a software asset manager, who enters and maintains the licensing information in snow. Other departments have access to reference relevant licenses and reports as they need them. This was purchased to pull licenses out of multiple spreadsheets and help to monitor how software is actually being used.