Wading through the software licensing minefield
Sweat those assets
Requirements Checklist for Choosing a Cloud Backup and Recovery Service Provider
Desktop Efficient licence management is crucial for a number of reasons, but they boil down to two: cost containment and legality.
According to an IDC survey on software pricing and licensing, conducted in 2010, almost all the respondents believed that some of their software licence expenditure went on either under-used or unused software. From full-on graphics packages to Excel add-ons, it's often hard to tell what's actually being used and by whom.
Other surveys tell a similar story, with enterprises frequently not making use of the software they've paid for via central agreements such as Software Assurance. Given the cumulative cost of software licences for a large desktop estate, this can add up to a substantial amount of wasted money.
Then there's the issue of legality. Today's clients are often hard to manage, since many are only occasionally connected to the corporate network and consist of a diverse range of hardware platforms and operating systems.
The software may be licensed on a number of bases: per user, per core, per CPU or per client machine. In some cases, the licences may be perpetual or licensed for a particular period only. And some clients may be virtual, which can result in a different set of licensing conditions.
Ensuring licence compliance in such a wide set of circumstances will be one of the more tricky jobs for IT, yet it is incumbent on IT to ensure that all this software is properly licensed. It's also one of those issues that's easy to ignore, as doing so appears to result in no immediate consequences. Too often, licence compliance is one of those issues that's only dealt with when news of an impending software audit reaches the ears of IT.
Sweating the assets
There are plenty of software and asset management packages available at the click of a mouse. The key is to find the one that fits your scenario. To cover the basics, you need a licence management tool that's able to examine each client, scan it to discover what software is installed, understand how the software is being used, and retrieve licence keys if necessary.
It should also be able to understand the terms and condition of each licence: for example, some packages allow the right of second use, so that one user can install the software on both a laptop and a desktop, provided they're not in use concurrently.
The tool should also be able to integrate with desktop management packages such as Microsoft's System Center Configuration Manager, which will be able to add the discovered software to its asset lists. Alternatively, you might find that SCCM's asset intelligence features are enough for your needs.
Up the sandbox
Things get easier if you're using application or desktop virtualisation. With the greater controls offered by application sandboxes, and by the central distribution of desktops, understanding application installation rates and usage should be a relatively simple matter, with no need for the discovery phase.
It may then be easier to apply a form of software metering so that, for example, 50 licences might legitimately be used by 100 users, depending on the licence terms and conditions, as long as only 50 of them are using the software at any one time. It's a technique that could save you a lot in unnecessary licence fees.
Licence compliance can be a complex process but the rewards can be worth it. The key is to ensure that there is a process, and that it's continuous.
One global brewing company running over 8,000 desktops and servers in nine countries is reported to have used this approach in order to ensure software licence compliance. It rebuilt its asset management processes and in the first year saved some $740,000 in software licence costs.
And as well saving money, you'll have the satisfaction of knowing that your software assets are legal, with no surprises expected during a software audit. ®
COMMENTS
Avoiding any unused licensing fees
One approach that goes beyond user-based licensing is usage-based licensing, where the customer pays the vendor for the actual usage incurred. This can be done on a debiting approach, where the customer purchases an inventory of usage which is consumed as they work with the application, or metering, where the usage is recorded for later billing. A pure usage-based approach also eliminates any issues about how many licenses are run or whether they run on virtual systems or not, concerns on the customer's side about whether they purchased sufficient licenses and so on.
A case study of a metering implementation is at: http://agilis-sw.com/casestudy/Fair_Isaac.html
"Things get easier if you're using virtualized desktops"
Wellll... yes, maybe, but companies are failing to manage the huge trap that this can lead them into with software licensing, particularly in hot desk environments with roaming profiles.
Take Microsoft's policy, for example: "Software Licenses are needed for all devices, be they traditional PCs, thin clients, or blade PCs, etc. that are used to access virtual images of Office, Project and/or Visio."
So, we've granted a couple of copies of Visio Professional to a couple of users. But they're wandering round the whole office, using numerous PCs with their roaming profile. It's certainly *easier* to track where they've been, I guess, but the potential cost is much higher.
IT infrastructure monitoring strategies
What you need to know about cloud backup
Enabling efficient data center monitoring
Agentless Backup is Not a Myth
Top 10 SIEM implementer’s checklist
