Microsoft Windows Server 2012 - Licensing Changes

While much of the focus this year has been on Microsoft's planned release of Windows 8, Microsoft Windows Server also has a planned release this year.  Microsoft Windows Server 2012 is slated for general availability in September and has some significant licensing changes planned to accompany the release.

Even though you may have no plans to move to Windows Server 2012 at release, this will impact all Windows Server purchases made after General Release.

 

Summary of planned changes:

1. All server licensing is changing to the per Processor model (no more “per server” licensing)
2. They are eliminating the “Enterprise” edition (the only difference between the remaining editions of Standard or Datacenter will be how they license virtual OSEs…functionality between editions will be exactly the same).
3. Each license will cover 2 processors on the same device. Existing licenses with Software Assurance will convert as follows:
• Microsoft Windows Server Datacenter – 2 licenses will convert to a single Datacenter license
• Microsoft Windows Server Enterprise – 1 license will convert to two Standard licenses
• Microsoft Windows Server Standard – 1 license will convert to one Standard license
4. Standard will now include the right for 1 physical or 2 virtual OSE’s per 2 processor box

Timing of release has not yet been disclosed (I’m betting September) – I recommend you analyze your environment and determine if you want to execute a purchase prior to general release so as to minimize the impact by maximizing the conversion ratios.

 

As always, if you need help or simply want to discuss this further let me know – I know Microsoft licensing (particularly when it changes) can be confusing…I’m happy to help explain it.

 

Please note, these changes are “planned” – by the time General Release occurs there could be more changes as the licensing terms are not set until release.

Software Audits - Beware of the Unknown!

While most of our business is focused on helping companies optimize their licensing and avoid compliance risks there are times a company comes to us when they are in some stage of being audited (whether it's called an audit or not for purposes of this posting I will refer to it as an audit anytime a third party is reviewing your licensing not at your behest).  We come across a number of areas that "surprise" customers to find out it's a compliance issue.

Take a look at the following - if any of them apply to your company, take steps to resolve these:

• Own one edition but a different edition is installed.  Do you own Microsoft Office Professional but have Microsoft Office Standard installed?  If so, you are out of compliance (and no, don't count on them to look the other way). 
• Changing the hardware that you run your Oracle database on without checking to see what it does to your core factor in determining processor licenses required. Did you move to a Sparc 4 from a Sparc 3? You just doubled your core factor...Oracle US License Agreements
• Not understanding the minimum number of users that need to be licensed (contractual requirement versus actual usage). What did that (above mentioned) increase in processors just do to the number of users you're required to license?
• Server mobility in a virtual environment. For example, did you reassign your Microsoft Windows Server Standard licenses to your virtual environment? That's fine (assuming they weren't OEM licenses) as long as you are not using VMWare's V-Motion (or similar technology).  You can only reassign licenses once every 90 days in the Microsoft server operating system world - you might accidentally be drastically increasing your licensing needs by "harvesting" that Standard license versus appropriately licensing the virtual environment.
• Did you turn on enterprise functionality in your Microsoft SharePoint Server? If so, are other instances of SharePoint inheriting that enterprise functionality without your knowing it?  The enterprise functionality in Microsoft Sharepoint requires a Microsoft Sharepoint Enterprise CAL (client access license, this CAL is also contained in the Microsoft Enterprise CAL Suite).
• Do you have Mac's in your environment? Are they accessing a Microsoft Windows OS? How are you licensing that?
• Are you on an Enterprise Agreement (Adobe, Microsoft, Oracle, etc) and not including all devices in your environment? Check your agreements, unless it specifically allows you to exclude something these agreements typically require you to license all devices - read your fine print!
• Re-imaging devices using the wrong media. The quickest way to get out of compliance in a material way is to have the wrong media loaded to your image. Make sure this is in alignment and that a change control process is followed for any changes to the image including a licensing review.
• Are you assuming downgrade rights? For example, most Attachmate products do not have downgrade rights unless you have maintenance. Don't assume this right.

If you are asked (or told) that someone will be reviewing your licensing - get help before it starts. This is not the time to rely on your internal team unless they are licensing experts and stay current on all the publishers in your environment.

The ITAM Review has a great article series on the topic of "What REALLY Happens During an Audit", I recommend reading it whether you're going through one or just looking for more information.

Microsoft Enterprise Agreements - Microsoft SQL Server Strategies

In case you haven't heard it yet, Microsoft SQL Server 2012 is going to contain some major licensing changes. Customers with existing (or new prior to the release of SQL Server 2012) Enterprise Agreements (EA) or Enrollment for Application Platforms (EAP) with SQL Server included on those agreements have some great opportunities right now but should be working out a strategy to meet their current and projected needs.

If you're unaware of the changes, check out our blog on Network World to find out more details.

If you have SQL Server Enterprise on your EA or EAP before the release of the 2012 version you can continue to purchase the same licensing model until the end of your agreement. In other words, even though the SQL Server Enterprise server and Client Access License (CAL) model will disappear with the release of 2012, if you already have that model on your EA or EAP you can continue buying under that model until your agreement ends. Additionally, if you have SQL Server Enterprise processor licenses on your EA or EAP, you can continue to purchase processor licenses (rather than core licenses) through the end of your agreement.

This presents a number of opportunities for organizations to save money moving forward but having a strategy will be key! If you don't already have these products on your EA or EAP, you might want to consider if you should add them prior to the release of Microsoft SQL Server 2012 (as opposed to waiting until your next true-up which might mean you miss an opportunity). 

As always, let us know if we can help you create a Microsoft licensing strategy that is most beneficial to your organization!