Monday, June 28, 2010

Microsoft Revamps Partner Program – Costly licensing impact on Partners?

Microsoft has a very generous internal use license program for its partners. In generalities, a Microsoft Certified Partner gets 25 copies of most all desktop software (and Client Access Licenses – CALs) and 1 or 2 server licenses each for most server technology for internal use in the form of annual license grants; a Microsoft Gold Certified Partner gets 100 copies of most desktop software and 1 to 5 server licenses each for most server software. There are additional license grants based upon expertise “competency”. These amounts can be multiplied by each location that qualifies at the same level as the overall company up to a maximum (along the lines of 500 desktop and 2 to 25 servers for Microsoft Gold Partners). 

 These license grants are obviously very valuable to Microsoft Partners in helping them minimize the cost of running their organization. However; Microsoft is now changing their partner program (for the first time in a long time) which will end up reducing the number of internal use software license grants for most partners. The new Microsoft Partner Network will replace the designations of Registered, Certified and Gold Certified with Subscriber, Competency and Advanced Competency. While there are some changes at the Registered and Certified levels (Subscriber and Competency) as it pertains to licensing the real impact comes to Gold Certified Partners who will not qualify for the Advanced Competency designation. $300k Example: One of my Software Asset Management customers is a Microsoft Gold Certified Partner with 1 additional enrolled location and several competencies. This entitles them to about 200 copies of most desktop software and CALs and a number of server licenses including 10 Microsoft Windows Server Enterprise license grants and 8 Microsoft Windows Server Datacenter processor license grants. However; this company will not qualify as an Advanced Competency partner so will instead drop down to a Competency Partner (think Certified Partner). Assuming they continue to have 1 additional enrolled location this will drop their license grants to 50 copies of most desktop software and CALs and about 2 server licenses for some servers (Microsoft Windows Server Datacenter will not be included). The financial implication of this is over $300k. 

Even those partners that do not lose their current level in the program will feel some impact from licenses being excluded from the core licensing (for example, Windows Server Datacenter edition will not be part of the core licenses). One of the hardest challenges is that IT typically manages the licenses and yet the business typically manages the partnering relationships. If these impacts are not discussed between both teams internally there could be a large number of former Microsoft partners who are now out of compliance in their licensing. 

Understanding the Dates: Each year partners have to re-enroll in the program. Those partners who re-enroll prior to 10/10/2010 (now changed to end of October) will be renewing under the existing designations of Registered, Certified or Gold Certified and will have their annual license grants based upon that enrollment. At their anniversary date in 2011 their licensing grants would change. For partners who re-enroll after 10/10/2010 (now changed to end of October) they will be renewing under the new designations and the new licensing grants will take effect. There are other changes that take effect regardless of enrollment status effective 10/10/2010 (now changed to end of October) so please be aware that this information is only as it pertains to license grants. 

What to Do: Obviously it is very important for current Microsoft Partner’s to clearly understand the requirements of the new program and where their company will fit within this program. Microsoft is doing a lot to help and their Partner desk is extremely helpful so leverage these resources! Take a good look at the license calculator tool to determine what your new license grants will be and start the budgeting and communication process internally to avoid a surprise hit to your software budget next year. If things get too confusing or time consuming, consider hiring a professional to handle the transition for you.

Monday, May 17, 2010

Mergers & Acquisitions - Software Licensing in the Due Diligence Process

It's been said that 2010 is the year of M&A (LOL...again, there have been many years in the past that have also held that moniker) and having just seen a posting on LinkedIn on this topic reminded me that it's probably time to blog about it again (check out my earlier posting on this topic for additional information).



There are lots of things to be considered, but I'm going to focus on the company doing the acquiring for this posting - if you need other scenarios check out our whitepaper on the topic.



There are typically two scenarios in acquiring: (1) you don't acquire any of the IT assets, or (2) you acquire all the assets of the company, including IT assets. The first scenario is simple as you know walking in that you have to provide these assets yourself. The second scenario is where the waters get muddy.



If acquiring all of the assets, the assumption is typically made that all the software installed at time of acquisition is (a) properly licensed and (b) the license will transfer to the acquiring company. Unfortunately, these are both naive assumptions and too frequently incorrect.



In the ideal situation, IT would have the opportunity to receive the licensing statement (including copies of contracts and proof of licensing) for the company being acquired in advance so it could be factored into the valuation of the company (remember software is frequently the 2nd or 3rd largest line item in the IT budget and represents significant expense).



However; reality is that acquisitions are typically completed without IT's involvement or even if IT is involved they are very limited in the information that can be shared in advance of the completion of the deal.



So, how can IT help the company avoid acquiring someone else's licensing headache? Through education and quick follow up.



A couple of basic steps:

1) Get the issue on the table in advance of M&A activity. During M&A you're going to have a hard time getting the attention of the proper parties so preempt the situation.

2) Get some allies on the topic - legal counsel, CFO, compliance officer and purchasing officer are all key allies. Obviously this means senior level IT to senior level operations discussions.

3) Create a high level IT due diligence checklist of what IT truly needs to (a) help avoid large unnecessary costs and (b) ease integration post acquisition.

4) With the aid of your allies, get the IT due diligence checklist added to the overall company due diligence checklist. Be prepared for push back and be able to quantify through hard dollar and compliance risks the reason behind each item.

5) Post acqusition, work fast. Not only do you have a mandate to get the company integrated but you also need to ensure that if there are any licensing costs associated with acquisition that you're able to identify those for proper accounting in the financial statements as part of the acquisition cost.



Get help - understanding the licensing terms for each major publisher and the transferability of those licenses can be a daunting task. Now is the time to focus on integrating your two companies, have an expert handle the acqusition licensing issues for you.



Any other suggestions? Post them!

Friday, April 30, 2010

Microsoft SQL Server 2008 R2 Licensing Changes - CALs Also!

(Updated 5/18/10 based on info from Microsoft)

I heard an ugly rumor yesterday about Microsoft SQL Server 2008 R2 from Gaby Amar at Softmart saying that in order to use SQL Server 2008 R2 in a server/CAL model you will have to have 2008 R2 CALs as well (typically for R2 releases you don't need an updated CAL). Well...checked it out with Microsoft licensing and he was absolutely correct (I should have known better than to be surprised, LOL)!

Basically, Microsoft SQL Server 2008 R2 is a major release (think in terms of a release such as Microsoft SQL Server 2000 to Microsoft SQL Server 2005) so don't let the lack of year change in the naming convention fool you.

Customers who have active Microsoft Software Assurance on their exisiting SQL Server products will have the new release rights, but those that don't will need to purchase new licenses in order to run the software (for those who run in Server/CAL mode this means both new server licenses and new CAL licenses).

CAL Requirements
  1. If you have Microsoft Software Assurance currently in effect on your SQL Server CALs, then you are entitled to SQL Server 2008 R2 CALs
  2. If you do not have Software Assurance, you must have SQL Server 2008 R2 CALs to run SQL Server 2008 R2 using the Server/CAL software licensing model (in other words...don't try to run with your older SQL Server 2008 CALs).

You may be wondering why I'm making such a big deal about this...after all it is a new release, of course new licenses are required. My point is this: it is a departure from how Microsoft has licensed Windows Server 2008 and Windows Server 2008 R2 where the Windows Server 2008 CAL can still be used on the newer version Windows Server 2008 R2.

Additionally, there are changes to the processor licensing for SQL Server 2008 R2. You might want to check out some of these resources for more information on this and other SQL Server 2008 R2 changes.

Microsoft has provided the following links for further information on licensing:


For more information on virtualization and SQL Server 2008 R2 check out Andrew Fryer's blog.

If you have any questions - let me know! This is a huge change in Microsoft's licensing trend.