You are here


Microsoft “kills” Software Asset Management?

Software giant Microsoft has announced that they are to retire 12 partner competencies over the next 18 months, including Software Asset Management. The move has caused something of a stir in the SAM world, with some commenting that Microsoft no longer cares about Software Asset Management and that it sees Cloud as the answer to all licensing ills. 

Taking a new view on Software Asset Management

At Snow, we believe that the entire organization should be empowered to contribute towards effective Software Asset Management. We call this concept 4th Generation SAM and a key to achieving it is making the right SAM intelligence available to everyone that needs it, and then giving all IT stakeholders (including the end users themselves) the tools to take charge of their own software needs within the organization’s overall SAM function.


In part III of this III part series, I will embark on a negotiation process with SAP that is not necessarily the most fun experience you can imagine when contemplating your working week. The goal is to shift the relationship from one in which it might feel like SAP is dictating the compliance terms to a discussion where both sides of the table can achieve a decent outcome that meets their long-term objectives. 

Why centralize license management?

Having a centralized license management function plays a large part in ensuring total visibility of the software licensing landscape. In this blog, I will look at the challenges encountered with a decentralized license management structure, and the arguments for moving the management of software licenses to a central solution.

Why your SAM program needs a PR makeover

The same basic principles apply to Software Asset Management. We’re not talking about the “Why you should buy Snow over SAM solution x,” kind of scenario, but how good marketing is critical to your SAM program. This may be something you hadn't thought of until now, so here are some basic steps towards the successful adoption of SAM across your organization.  

The SAP® Indirect Usage Time Bomb - PT II

In my first blog post of this three part series, I explained the concept of Indirect Usage. Why it is a significant financial risk to organizations and provided an overview of how to gain control of it. Here I explore Indirect Usage in further detail and provide practical steps to ascertain a full picture ready for contract re-negotiation and license audits.

What is your App doing?

We all know that nothing in life is free. This phrase is particularly apt when downloading so-called ‘free’ apps on mobile devices. I admit I’ve done it. In fact, I bet we’d all be hard-pushed to find someone who has a smart phone that doesn’t have free apps installed on it.

No-one said SAM would be easy…

As anyone embarking on a Software Asset Management (SAM) program for the first time quickly learns, there’s really no such thing as “push-button SAM”. Sure, you can pay a services provider to take away some of the pain, especially if you opt for a hosted SAM platform, but if your organization takes the on-premise route and doesn’t have millions of dollars to throw at professional services, then you need to sit down, buckle up and get ready for a bit of a roller-coaster ride.

The SAP® Indirect Usage Time Bomb

Are you using software that can query or write to an SAP database? For example, does your CRM access data in your ERP solution? Are you aware that you could be liable for something called “Indirect Usage” and that in all likelihood you will be under-licensed for SAP? 

SAM & IT Security – PT II

The past few years has seen support end for a number of globally used products. The likes of Windows XP and Windows Server 2003 are now unsupported by Microsoft, which means that there will no longer be updates or patches for these products.



some content goes here