Showing posts with label Subscription Software. Show all posts
Showing posts with label Subscription Software. Show all posts

Thursday, August 19, 2010

Walking Away From a Microsoft Licensing Agreement

When finances are tight it's not uncommon for companies to start expiring their maintenance contracts, including software maintenance. As with any maintenance agreement that is allowed to expire, it's important that an organization understand the full implications of their actions so that it is a strategic event rather than a reactionary one. 

This is a big topic so will cover several postings - check back for more updates or e-mail us with specific questions. 

Microsoft has three primary ways for an organization to acquire licensing rights - subscription licensing (Microsoft Desktop Optimization Pack aka MDOP is an example), perpetual licensing (their traditional model where once you buy it you own the rights forever), or perpetual with maintenance (Microsoft Software Assurance aka SA). 

Subscription licensing expires at the end of the subscription agreement (unless there is a buy-out option). I'm not going into details on this type for this article. 

Perpetual licensing does not expire but also does not have upgrade rights. So again will not be discussed in this article. 

Perpetual licensing with Software Assurance includes upgrade rights until the SA expires. When SA expires, your organization is entitled to the latest version of the product which has been released to volume licensing customers. Those licenses then become perpetual licenses but inherit the licensing terms from the agreement under which they were acquired. 

For example, a customer who had a full platform Microsoft Enterprise Agreement (which automatically includes SA) which they allowed to expire at the end of May 2010 would walk away with perpetual licenses for the following Microsoft products: Office Professional Plus 2010, Windows Server 2008 Client Access License (CAL), Exchange Server 2010 Standard CAL, SharePoint Server 2010 Standard CAL, System Center Configuration Manager 2007 R2 Client Management License and Windows 7 Enterprise (but be aware of any subscription components, those are not perpetual). However; those perpetual licenses will always be restricted to the licensing rights under the Enterprise Agreement (for example, no secondary use rights for Microsoft Office which means if a user has a desktop and a laptop each would require its own license). 

While a license is covered under SA, it is at it's most flexible. Consider your future plans prior to allowing SA to expire. A couple of things to think about: 1) Will you be using any of the enhanced functionality of the Microsoft Enterprise CAL Suite? 2) Will you be increasing your server virtualization efforts and will Microsoft Windows Enterprise Server or Microsoft Windows Datacenter edition provide you with a more cost effective solution? 3) Are you licensed under Device CALs when User CALs might be more effective or vice versa - these can only be changed at time of renewal and guess what...you're not renewing. 

However; now is still the time to push the envelope on this (before expiration) as there are ways of getting this changed as long as you still have active SA. The first two scenario's would be covered by "Step-up" licenses from lower versions carrying SA. This allows you to leverage the monies you've already spent on the lesser edition by paying a reduced price for the higher edition but can only be completed while you have active SA on the product. 

Watch for more to come...or if you're considering walking away from a Microsoft Licensing Agreement talk to us first, it can help you avoid future costs and headaches!

Monday, October 19, 2009

SaaS Contracts - A function of Software Asset Management?

Earlier this month I spoke at the IAITAM conference in Nevada on the topic of Licensing Implications in the Cloud (Saas), it was a lively group and an interesting subject. However; the most interesting piece was the conversation it sparked about "Should Software Asset Management (SAM) be responsible for SaaS?".

For me the not so private laugh was the fact that several audience members asked the question right when we got to my slide asking the same question...always nice to have evidence that I do think like a SAM Manager! OK, thanks for sharing my pat on the back...

This is a topic we hear more frequently at our clients. Does subscription software such as SaaS belong under the SAM umbrella or does it belong elsewhere? Certainly businesses have used subscription software for a long time, and commonly it is not handled by IT but instead handled by the business unit that is using the service (think Payroll, HR services, etc).

I don't think there is a global answer for this, but I would urge companies to think about what's at stake if that subscription is suddenly no longer available. What happens if the provider goes out of business or the server hosting the service fails? These are examples of topics that belong in the contract signed for the service...but will a business unit necessarily think to negotiate these into the contract? How is the usage being tracked to ensure that the billing is accurate? Is the business unit going to track it or are they just going to pay the bills (start thinking telecom audit if you don't think subscription billings can be inaccurate)?

While subscription software services might not fall under the traditional SAM umbrella, it needs to fall under someone's umbrella and the SAM Manager is probably the best suited to take on the challenge.

Would love to hear other's thoughts on this...