Enterprise Cloud Suite Licensing Guide

The objective of this article is to review the publicly available documentation available on Enterprise Cloud Suite

This will look at the publicly available information upon general availability on December 1st 2014

  • This article is not intended to replace the Product Use Rights or Product List or other binding contractual documents
  • The Use Rights or Terms of Service for each Product or Version are available within the Product Use Rights
  • Further product-specific conditions or limitations on use of products are in the Product List
  • Please be aware that any licensing information could be subject to change. This document confers no rights and is provided for information purposes only.
  • Please be aware, my own emphasis may have been added to quotations and extracts from 3rd party sources.
  • As always, If you would like to book a consultation, available under NDA, please drop me a note via email

Executive Summary

  • The Enterprise Cloud Suite combines three strategic elements for Microsoft to drive adoption of Office 365, Enterprise Mobility Suite, Windows Desktop OS under a consistent Per User subscription model for the desktop
  • Windows offers a compelling Per User licensing model, but organisations should continue to track device profiles and associated underlying Windows device licenses
  • The Enterprise Cloud Suite will enable remote home working and BYOD scenarios for organisation who opt to deliver a consistent Windows experience  via a VM-based VDI (dedicated image) or VM-based VDI (shared image) delivery model to a range of device profiles.
  • The Enterprise Cloud Suite will be offered at a  advantageous price to incentivise adoption, driving ‘strategic bets’ for Windows 10, Office 365 and Enterprise Mobility Suite.
  • The Enterprise Cloud Suite is available on the Enterprise Agreement (EA) and Enterprise Agreement Subscription (EAS). Customers should understand the impact of revised True Up reporting within November 2014 contracts.

Enterprise Cloud Suite Overview

Microsoft made Enterprise Cloud Suite generally available to  Enterprise Agreement customers December 1st 2014

The updated EA purchasing vehicle  combines three strategic elements for Microsoft to drive adoption of Office 365, Enterprise Mobility Suite, Windows Desktop OS under a consistent User Subscription Licensing Model.

The ‘Cloud Desktop Platform’ packages strategic objectives for Productivity and Cloud Services with Management across Devices

Cloud Desktop

  • Microsoft Intune provides a unified Mobile Device Management (MDM) and Mobile Application Management (MAM) across PCs and devices. This now includes management of Office Mobile Apps (Word, Excel, PowerPoint) for iOS devices and restrict actions such as copy, cut, and paste outside of the managed app ecosystem.
  • Azure Active Directory Premium (AADP) provides User Identity and Federation via Active Directory Federation Services (ADFS) to enable pass through authentication with SSO experience from on premise AD to cloud service providers like Office365 and Salesforce.com. Acting as a identity broker for SaaS Apps with support for Multi Factor Authentication (MFA).
  • Later this will include Microsoft Identity Manager (MIM) in H1 2015 as an on-prem Identity and Access Management (IAM)
  • Azure Rights Management Services enabling Information Rights Management (IRM) for  Office365 Services and On Premise SharePoint, Exchange and Windows Server File Services.

EMS

  • Microsoft Office365 Enterprise E3 is a flagship SaaS subscription offering of Exchange Online, SharePoint Online and the Lync Online, Yammer and Office365 Pro Plus

Office365

Windows Enterprise and SA

This represents a move from Microsoft to provide a consistent Per User licensing vehicle to enable a future ‘Cloud Desktop’ service offering. While Windows will be integrated with cloud services running on the Azure Platform; Whether the Windows service will be reflected in a consistent subscription based commercial model for Windows 10 remains to be seen.

Cloud Desktop


Windows SA Per User

Prior to General Availability of the Enterprise Cloud Suite and Windows SA Per User licensing Windows Client OS on any device under a per-user model was not an option.

Microsoft now provide four licensing options, a ‘full’ Windows SA Per User Subscription, a ‘full’ Windows VDA Per User Subscription and an Windows SA Per User ‘Add On’ Subscription and Windows SA Per User Migration 

Windows Per User

With the Windows SA Per User Subscription, organisations can license Windows Software Assurance on a per user basis. When the license is assigned primary user, the associated primary device must be licensed with a ‘qualifying OS’.

The Windows SA Per User ‘Add On’, provides the benefit of Windows Software Assurance per User, or Windows VDA per User, at a price point that recognizes existing ongoing investment. When the license is assigned to a primary user of a primary device that is already covered with active Software Assurance, the Windows Software Assurance per User Add-on grants the licensed user with all of the benefits of Windows Software Assurance per User. When you license the primary user of a primary device that is already covered with Windows VDA, the Windows Software Assurance per User Add-on grants the licensed user with all of the benefits of Windows VDA per User.

These Windows VDA Per User Subscription allows an organisation license Windows on a per user basis, and may be assigned to any user. Each licensed user has access to Windows Enterprise without the need to track the operating system license(s) on the user’s device(s), except for devices where the software is installed locally. This provides a user-centric licensing model, providing flexible options for organisations to deploy and access Windows across devices, and does provide improved license management for Windows.

The Windows SA Per User Migration  maintains the SA Only price point that is available to customers who own perpetual licenses with Software Assurance in an Enterprise Agreement (EA) or Select Agreement. Customers with active SA will receive special pricing for transition continuity, recognizing their equity investment in previous fully paid perpetual licenses. This is now available for existing renewal customers.

[Ref: Microsoft Price List Guide, December 2014]

Per Device vs. User Comparison

Enterprise Agreement Requirements

The Windows SA Per User Subscription for customers with an Enterprise Agreement (EA) should acquire Windows SA Per User for all “Qualified Users”

  • The “Qualified User” is defined in the Enterprise Agreement enrollment as “”‘Qualified User” means a person (e.g., employee, consultant, contingent staff) who: (1) is a user of a Qualified Device, or (2) accesses any server software requiring an Enterprise Product Client Access License or any Enterprise Online Service. It does not include a person who accesses server software or an Online Service solely under a License identified in the Qualified User exemptions in the Product List.” [Ref: Enterprise Agreement Enrollment 2014]
  • “To understand what “user of a Qualified Device” means, “Qualified Device” means any device that is used by or for the benefit of Enrolled Affiliate’s Enterprise and is: (1) a personal desktop computer, portable computer, workstation, or similar device capable of running Windows Professional locally (in a physical or virtual operating system environment), or (2) a device used to access a virtual desktop infrastructure (“VDI”).
  • Qualified Devices do not include any device that is: (1) designated as a server and not used as a personal computer, (2) an Industry Device, or (3) not managed (as defined in the Product List at the start of the applicable initial or renewal term of the Enrollment) as part of Enrolled Affiliate’s Enterprise. At its option, the Enrolled Affiliate may designate any device excluded above (e.g., Industry Device) that is used by or for the benefit of the Enrolled Affiliate’s Enterprise as a Qualified Device for all or a subset of Enterprise Products or Online Services the Enrolled Affiliate has selected.”

[Ref: Enterprise Agreement Enrollment 2014]

  • The Microsoft define a ‘Primary User’ must be assigned to a License Device
  • The “Primary User” is defined as  “the user who uses a Windows Software Assurance, Windows Embedded Industry Software Assurance, or Windows VDA Licensed Device more than 50% of the time in any 90 day period.

[Ref: Product Use Rights, January 2015, Page 75]

Product Licensing Requirements

  • The Licensed Device must be ‘already licensed’ for a ‘Qualified Operating System‘ of Windows as defined in the Product List
  • The Windows SA Per User Subscription does not require Software Assurance for an assigned to the Licensed Device
  • Microsoft clarify that Windows can be locally installed in a Physical OSE on Windows Pro and Enterprise devices and additionally on “integrated” screens with a size of 10.1″ diagonally or less
  • The Windows SA Per User Add On does require Active Software Assurance or active VDA Subscription Per Device License for the Licensed Device
  • The Windows SA Per User Add On can only be purchased for the maximum number of available SA or Windows VDA Subscription
  • The ongoing software use rights acquired through the purchase of Add-on User Subscription Licenses will expire with the the expiration of the SA coverage for the Qualifying License(s), or at the end of the subscription term for the Add-On USLs.
  • The VDA Subscription License is recommended  for User Profiles without a primary work device, or not considered a “Primary User” under the Product Use Rights 

Decision Tree Windows SA

[Ref: Product List –  January 2015, Page 33–35][Ref: Product List –  January 2015, Page 34]

This diagram below provides an overall view of the licensing options for Windows Per User. (As always, please refer directly to binding documentation for confirmation), but this diagram attempts to capture different device profiles and respected software use rights:

Windows Per User Graphic

Complexity of the Per Device Model

Please be aware that the Per User model is not completely abstracted from the device profile, or the requirement underlying licenses assigned to those devices.

  • It does comparatively offer less complexity when managing home workers accessing VDI from a personal device and the associated risk of unlicensed access to a virtual desktop or walking their personal devices onto the organisation premises, something restricted under the “Roaming Use Right”.
  • Adopting the Windows Per User Subscription Model without also adopting Office365 Pro Plus on a Per User Subscription Model could lead to commercial risk from non compliance.
  • For example, if a user is assigned with a Windows SA Per User Subscription, but continues to access Office Pro Plus 2013 off-premise, relying on the ‘Roaming Use Right’ available as part of Software Assurance, this would not impact the ‘Qualified Device’ count. However, should the user walk that personal device onto organisation premises, it may inadvertently ‘pull through’ a requirement to license an extended number of devices under the ‘Qualified Device’ definition.
  • Microsoft state “Roaming Use” can be used on ‘Qualifying Third Party Device’ defined by Microsoft as “a device that is not controlled, directly or indirectly, by you or your affiliates”. Organisations should be aware of the definition of “management of qualified devices” as defined in the Product List to include domain join, on premise authentication to use applications, or install of agents to enforce anti-virus, anti-malware, enforcement of group policies, or receives data about, and, configures, or gives instruction the OS on a device, or access to Windows in a Virtual Desktop Infrastructure (VDI) outside of the off-premise “Roaming Use Right”. [Ref: Product Use Rights, January 2015, Page 9] [Ref: Product List, January 2015, Page 84]

The complexity of managing  home working VDI and uncontrolled BYOD scenarios drives the business case for a consistent Per User licensing model. Microsoft will continue to incentivise procurement under the Per User licensing model available for solutions and services within the Office365 and Azure portfolio to drive adoption of a ‘cloud desktop’ under a subscription or relational procurement model.

Windows Per Device Graphic


The Enterprise Cloud Suite

Microsoft now provide three licensing options on the price list to purchase the Enterprise Cloud Suite  a ‘full’ Cloud Desktop Per User, a Cloud Desktop Add On and an Cloud Desktop From SA 

  • The Enterprise Cloud Suite User Subscription License (USL) or Cloud Desktop Per User includes Office 365 Plan E3, the Enterprise Mobility Suite  (EMS) and Windows Enterprise SA per User.
  • The Enterprise Cloud Suite Add-on or Cloud Desktop Add On can be added on to a Platform EA (which includes Office Pro Plus, Windows Enterprise and either the ECAL or Core CAL).
  • The Enterprise Cloud Suite From SA User Subscription License (USL)  or Cloud Desktop From SA provides the same functionality as the full priced Enterprise Cloud Suite USL, but at a beneficial price point for customers who own perpetual licenses with Software Assurance in an Enterprise Agreement (EA).  Customers with active SA will receive an better price point incentivise transition continuity, and recognize existing equity investment in previous fully paid perpetual licenses.  This is now available for existing renewal customers
  • Customers that see Lync Voice as a part of their future roadmap, may purchase the Lync Voice Add-On. While the Lync Voice Add-On is available from December 2014, Microsoft are careful to stipulate that no provisioning will take place upon procurement of the license.

Lync Voice Add On


The Impact of 2014 Contracts

In November 2014, Microsoft updated contract packs for the Enterprise Agreement (EA), Enterprise Agreement Subscription (EAS) and Server Cloud Enrollment (SCE).

Enterprise Agreement with Add Ons

  • Microsoft have aligned the Enterprise Plan E1, Enterprise Plan E3, Enterprise Plan E4, Enterprise Mobility Suite (EMS), and Enterprise Cloud Suite (ECS) Add-Ons as “Enterprise Online Services”.
  • This will enable organisations to enroll a subset of users into a Per User licensing model or transition users over the contract term without committing Enterprise-Wide at outset of contract.
  • Microsoft continue to offer a ‘Platform’ SKU to incentivise ‘front loading’ a contract.
  • The Lync Voice Add-On is currently aligned as an ‘Additional Product’ enabling ‘price lock’ and not categorizing Lync Voice as an ‘Enterprise Online Service’.

Enterprise Online Services Only EA

  • Organisations that sign an Enterprise Agremeent (EA) or Enterprise Agreement Subscription (EAS) for ‘Enterprise Online Services Only EA‘ must meet the minimum order requirements of the respective enrollment of 250 Enterprise Online Services USLs, including Enterprise Plan E1, Enterprise Plan E3, Enterprise Plan E4, Enterprise Mobility Suite (EMS), and Enterprise Cloud Suite (ECS), From SA and Full USLs  and Microsoft Intune Full USLs but no enterprise-wide commitment is required.
  • Enterprise Online Services can be reduced to a minimum of 250 USLs at Anniversary
  • Notably, All ‘Additional Products’ are eligible to be added to the contract

True Up Policy

A principle impact to organisations will be in the approach to the annual True Up. Updated wording in the contracts could significantly impact customers that have seasonal or other annual deployment fluctuations to impact the total cost of ownership (TCO) of a Microsoft Enterprise Agreement

This new approach, effective for customers signing the revised contracts is defined as follows for the Enterprise Agreement enrollment:

“True-up Requirements. Enrolled Affiliate must submit an annual true-up order that accounts for any changes since the initial order or last order. If there are no changes, then an update statement must be submitted instead of a true-up order.

(i) Enterprise Products. For Enterprise Products, Enrolled Affiliate must determine the number of Qualified Devices and Qualified Users (if ordering user-based Licenses) at the time the true-up order is placed and must order additional Licenses for all Qualified Devices and Qualified Users that are not already covered by existing Licenses, including any Enterprise Online Services.

(ii) Additional Products. For Additional Products that have been previously ordered under this Enrollment, Enrolled Affiliate must determine the maximum number of Additional Products used since the latter of the initial order, the last true-up order or the prior anniversary date and submit a true-up order that accounts for any increase.”

For the counting of Enterprise Products, the wording in the enrollment does have an apparent conflict, that accounts for “any changes” over the term or since the last anniversary, but later also under the term Enterprise Products “at the time the true-up order is placed”.

Taken in a wider context for customers renewing other enrollments, this tactical editing of the November 2014 also extends to the Server Cloud Enrollment :-

“(ii) True-up order. Enrolled Affiliate must determine the maximum number of Products used since the latter of the initial order the last true-up order, or the Enrollment’s prior anniversary and submit a true-up order that accounts for any increase.” [Ref: Server Cloud Enrollment 2014]

This approach has been reflected in other guidance, including deployment of the Microsoft Assessment and Planning Toolkit (MAP):

“The Microsoft Assessment Planning (MAP) Toolkit features an IT-based Software Usage Tracker functionality that provides usage reports for the following server products: Windows Server, Exchange Server, SQL Server, SharePoint Server, and System Center Configuration Manager. This automated software asset management–related functionality is designed to be used by Microsoft Volume Licensing customers. The Software Usage Tracker provides you with a view of your actual server usage, which can be valuable for comparing with your purchased CALs, or for True-up and agreement renewal discussions.” [Ref: EA Program Guide]

This change in written terminology may incentivise Microsoft to request metering of use over the contract term, or final year of a contract, to ascertain ‘maximum use’ therein driving revenues from final year True Up and subsequent renewal; underwriting the business case to move workloads to Azure

The application of this term may be applied inconsistently by Microsoft, I would recommend an agreed approach to True Up with your respective Licensing Solution Provider (LSP).


Final Thoughts

The Enterprise Cloud Suite, as a commercial licensing vehicle provides a consistent Per User licensing metric across the desktop environment and “pulls through” Windows onto a subscription procurement model. This combined suite provides an incentivised price point to drive adoption and enable the strategy for a ‘Cloud Desktop’ delivering user-centric services from Azure.  This is reflected by the recent announcements for Windows 10 that will extend Windows as a ‘universal’ platform across device profiles for Office365 and Azure services.

The licensing model ensures securement OEM licensing business model by limiting abstraction from the device profile, or the requirement for underlying Windows licenses assigned to those devices . Microsoft  continue to leverage volume licensing as a strategic tool to drive customer behaviors toward subscription services and this will continue in 2015.

Organisations should review their current and planned utilisation of Microsoft Solutions and Services to evaluate alignment with the strategic objectives of their Microsoft Account Team. Microsoft will align personnel and resources to support customers that move toward Azure and Office365 but are enabled by the 2014 contract structure to secure short term revenue generation through True Up or via Audit.

Microsoft Advisory Services

SoftwareONE provide independent consultancy services from within our Microsoft Advisory Services to optimise our clients Microsoft Strategy, including but not limited to the following benefits:

  • Knowledge Transfer on Microsoft Solutions and Services, and Licensing, from Principal Consultants from our Microsoft Advisory Practice and Technical Solutions Division
  • Confirmation of current License Entitlement and Maintenance Entitlement
  • Optimised Commercial Investment plan for Microsoft Solutions and Services
  • Commercial Analysis across Contracts and Global Pricelists
  • Assessment of Commercial Options versus Microsoft Strategic Objectives to ascertain opportunities for Negotiation Advantage
  • Managed closure support with Microsoft Global Account Manager

About

This website is a way to give back to the licensing community and as an information resource for all customers that work with Microsoft software and licensing. I hope you find it of value.

Tony Mackelworth is Microsoft Advisory Services – Practice Lead at SoftwareONE

As always, If you would like to reach out for a coffee or a meeting under NDA, Email or connect via Twitter or LinkedIn

Tony lives with his wife in Oxford, England.


Disclaimer

This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. This document does not provide you with any legal rights to any intellectual property in any Microsoft product.

Please be aware that nothing in this document constitutes specific technical advice. Some of the material in this document may have been prepared some time ago and therefore may have been superseded. Specialist advice from the vendor should be taken in relation to specific circumstances.

The contents of this document are for general information purposes only. Whilst the author(s) endeavour to ensure that the information on this document is correct, no warranty, express or implied, is given as to its accuracy and the primary author or it’s contributing Authors do not accept any liability for error or omission.

The contributing authors and owner of this document shall not be liable for any damage (including, without limitation, damage for loss of business or loss of profits) arising in contract, tort or otherwise from the use of, or inability to use, this website or any material contained in it, or from any action or decision taken as a result of using this website or any such material.

This Disclaimer is not intended to and does not create any contractual or other legal rights.

Advertisements

Office 2013 Downgrade Rights

image

The most popular topic on this website. Re-Visited.

  • This article will give you a brief overview of the downgrade rights for Office.
  • This article is not intended to replace the Product Use Rights or Product List
  • Please be aware that any licensing information could be subject to change. This article confers no rights and is provided for information purposes only.

Binding Documentation

Microsoft provide the software use terms for use of prior versions  via the monthly updated Product List and the Universal License Terms of the Product Use Rights. Microsoft define the extended software use right within the Universal License Terms and then subsequently amend or retract based on product, as specified in either the General License Terms or Product-Specific License Terms and Additional Terms of the Product Use Rights document.

  • The Universal License Terms. These terms apply to all products licensed through Microsoft Volume Licensing.
  • The General License Terms. These terms apply to all products that use a particular licensing model. Each licensing model section includes a list of products that use that particular model.
  • The Exceptions and Additional Terms for the product. Any additional product-specific terms are listed by product.

[See article: Hierarchy of Software Use Terms]


Downgrade Rights (Volume Licensing)

Microsoft provide the following definition in the Universal License Terms of the Product Use Rights,

“For any permitted copy or instance, you may create, store, install, run or access in place of the version licensed, a copy or instance of a prior version, different permitted language version, or different available platform version (for example, 32 bit or 64 bit). You may use different versions of components only as permitted under the Product-Specific License Terms. If you use an earlier version under these downgrade rights, Microsoft is under no obligation to provide security updates or support for the product or service beyond the end of support date listed at http://support.microsoft.com/lifecycle.”

[Ref: Product Use Rights, July 2013, Page 9 of 114]

The Product List states downgrade rights as a universal software use right of Volume Agreements, but are careful to continue to set the parameters of support for older versions: “customers can acquire the latest version in order to use an older version with downgrade rights, but are eligible for support for that product only if it is listed as supported” as maintained in the software lifecycle website.

[Ref: Product List, July 2013, Page 74 of 188]

Microsoft  offer a minimum of 10 years support for business products. This is classified as 5 years of mainstream support or for 2 years after the successor product is released (whichever is longer); and extended support provided for the 5 years following end of mainstream support; or for 2 years after the 2nd successive product is released (whichever is longer) – This is available in detail on the life policy website.

 


Volume Licensing: Legacy Deployments of Office

The September 2012 Licensing Brief states that downgrade rights “are granted with all application software licenses acquired through the Volume Licensing programs” wherein, Volume Agreements “give you the right to downgrade to any prior version of the same product”. 

As an example, the Multi Language Pack, when procured with an application license (for any of the following products) are eligible to version downgrade.

  • Office Standard 2013
  • Office Professional Plus 2013
  • Project Standard 2013
  • Project Professional 2013
  • Visio Standard 2013
  • Visio Professional 2013

“are eligible to use the English/Multilanguage version of a downgraded version of the product in place of the licensed version. Use of the downgraded version of the product is subject to the use rights for the 2013 version of the product. These rights expire when the customers’ rights to either the Office Multi-Language Pack 2013 or the above listed 2013 product expires.”

[Ref: Product List, July 2013, Page 102 of 188]

The Licensing Brief document states that an organisation  “may downgrade Microsoft Office Professional Plus 2010 to the Microsoft Office Professional Plus 2007, Office Professional Enterprise 2003, Office Professional XP” […]You may not, however, downgrade to Microsoft Office Standard Edition 2007 because it is a different product and not considered a prior version of Microsoft Office Professional Plus 2010.”

[Ref: Downgrade Rights Licensing Brief September 2012, Page 4 of 6]

The advisory document does address issues from the consolidation of editions upon general availability of Office 2010:

”In addition, Office Professional Plus 2010 users may not use earlier versions of the Microsoft Office OneNote note-taking program and Microsoft Office Groove software via downgrade rights, because these products are not part of earlier versions of the suite (for example, OneNote 2007 and Groove 2007 are not included with Office Professional Plus 2007)”

[Ref: Downgrade Rights Licensing Brief September 2012, Page 4 of 6]

(For information purposes, I have provided a diagram of the releases of Office illustrating where a component has been upgraded, added or discontinued; Please be aware this is not derived from any Microsoft binding or advisory documentation):
image

IT Asset Managers should be aware, that if attempting to maintain a legacy deployment of Office Enterprise 2007 as  part of your corporate image across your organisation,“Software Assurance (SA) customers who have deployed Office Enterprise 2007 only (i.e., are not using any other edition of Office in their organization), and need additional seats of Office Enterprise 2007, may purchase licenses for Office Professional Plus 2010 and downgrade to Office Enterprise 2007. No other downgrades from Office Professional Plus 2010 to Office Enterprise 2007 are permitted.”

[Product List, November 2012, Page 95 of 175]

[Ref: Licensing Brief September 2012, Page 5 of 6]

In terms of access to software for installation, Microsoft provides guidance via the Fulfilment Website informing customers that software is available for download via the Volume Licensing Service Center (VLSC).

VLSC provides download access only to the current (N) and the last version (N-1) of products. This again drives customer behaviour to upgrade. As of December 2012 Microsoft continued to support a limited set of N-2 and N-3 prior product versions for download on VLSC but should a release be removed, this is via the Product Activation Center.

Previous product editions available through VLSC

Microsoft provide guidance on support for legacy releases of Office on the Microsoft Office Products Support Lifecycle Website


Visio Professional 2013 Downgrade Rights

IT Asset Managers should be aware, that if attempting to maintain a legacy deployment of Visio Premium 2010; Upon release of Visio Professional 2013 Microsoft extended a downgrade right for Visio Premium 2010 users only with a standardised enterprise-wide deployment of the product.

“Software Assurance customers who have deployed Visio Premium 2010 only (i.e., are not using any other edition of Visio in their organization), and need additional seats of Visio Premium 2010, may purchase licenses for Visio Professional 2013 and downgrade to Visio Premium 2010. No other downgrades from Visio Professional 2013 to Visio Premium 2010 are permitted.”

[Ref: Product List, July 2013, Page 104 of 188]

This caveat, enshrined within the Product List requires strict software asset management controls to leverage this ‘downgrade right’ and is recommended to closely monitor deployed software in your desktop estate.

Under the Software Assurance Migration Path for Visio Premium 2010 Microsoft extended the use right to the Professional 2013 edition under the following conditions of use:

“Customers with active Software Assurance coverage for Visio Premium 2010 as of download availability date for Visio Professional 2013 are eligible to use Visio Professional 2013 in place of Visio Premium 2010.

The right to use Visio Professional 2013 under this offering expires when the right to use Visio Premium 2010 under the corresponding qualifying licenses expires. Use of Visio Professional 2013 is governed by the use rights for Visio Professional 2013 and the terms and conditions of the customer’s volume license agreement. This product condition note and the customer’s evidence of the corresponding qualifying license together evidence the right to use Visio Professional 2013 under this offer. Upon expiration of Software Assurance coverage for Visio Premium 2010, the customer may acquire Software Assurance for Visio Professional 2013 without the need to separately acquire a new license.

[Ref: Product List, July 2013, Page 105 of 188]

This logic is consistent in the advisory brief on Visio Premium 2010 that downgrade rights are version specific, and Microsoft maintain caveats for existing maintenance (SA) customers with legacy deployments:

“Downgrade rights in Volume Licensing agreements provide customers with the right to downgrade to any prior version of the same product. However, Visio Premium 2010 is a new product without a prior version, so downgrade rights do not apply.Only Software Assurance customers who licensed Visio Professional 2007 may continue to use Visio Professional 2007 under those licenses despite their Software Assurance migration rights to Visio Premium 2010.

[Ref: Licensing Brief September 2012, Page 5 of 6]


Visio Pro for Office 365 Downgrade Rights

As an express limitation for the Office 365 Pro Plus service; The Product List states that “Visio Pro for Office 365 service has no downgrade rights.”

[Ref: Product List, July 2013, Page 106 of 188]


Office 365 Pro Plus Downgrade Rights

An express limitation for the Office 365 Pro Plus service; the Product List states that the “Office 365 ProPlus service has no downgrade rights”.

[Ref: Product List, July 2013, Page 104 of 188]

Microsoft do address the issue of downgrade rights under O365 Pro Plus subscriptions in a non-binding advisory document:

“In Online Services customers have access to the latest technology with the newest features and releases. As with all Subscription Services, Microsoft generally offers only the latest version of the service at a time. Therefore, downgrade rights are not available with Office Professional Plus for Office 365 licenses

[Ref: Licensing Microsoft Office Professional Plus for Office 365, June 2011, Page 3 of 6]


Is there an exception to the rule….?

Microsoft do elaborate on the topic of on-premise use downgrade rights under the O365 Office Pro Plus Subscription:

“There is a one-time exception during the introduction of Office Professional Plus for Office 365 to Enterprise and Enterprise Subscription customers. If those customers have deployed Office Professional Plus 2010 under their Enterprise or Enterprise Subscription agreement, they may use Office Professional Plus 2010 software in place of Office Professional Plus for Office 365 user authenticated software. Although those customers may be allowed to use Office Professional Plus 2010 software, they are still required to comply with the use rights under their Office Professional Subscription license and no perpetual software rights apply.”

[Ref: Licensing Microsoft Office Professional Plus for Office 365, June 2011, Page 4 of 6]

It is understood this exception, (subject to approval from your Microsoft subsidiary), could be made available for organisations that provisioned an E3 tenant prior to Office 365 commercial availability on 27th February 2013; to support continued access to Office ProPlus 2010 installer until 8th April 2014.

Windows XP will be out of support on 8th April 2014 and may drive some organisations to upgrade Windows to enable access to the new wave of cloud productivity Office 365 applications on Windows 7.

The software use right to install Office 2010 locally under Office 365 is by exception, available under a specifically agreed contractual amendment from Microsoft;  Your procurement strategy should be principally defined by binding documentation for your organisation.

An agreed exception would be notwithstanding anything to the contrary in the Product Use Rights or other binding contractual documentation, to enable an organisation to install Office Professional plus 2010 locally;. However, this would likely be time limited; “[…] All customers will need to comply with Online Services upgrade requirements in the next release” and upgrade to the required version of Office Professional Plus.

[Ref: Licensing Microsoft Office Professional Plus for Office 365, June 2011, Page 4 of 6]

Driving Adoption of Cloud Services

The  Microsoft Office Website does suggest support for dual access rights for on-premise legacy office deployments, permitting customers to “keep older versions of Office side by side on your PCs to mitigate any potential file or add-in compatibility risks”   [last checked: 24.07.2013]. However, this was likely intended as a temporary right, and not aligned to the full term of the service.

The FAQ regarding Office ProPlus website is still active [last checked: 24.07.2013] and Microsoft do make the following statements: “If you have users who installed Office 2010 Subscription, you are required to upgrade to new version of Office 365 ProPlus by 28 February 2014” and “You will be able to install Office ProPlus 2010 until 28 February 2014.”; Microsoft will then remove the installation link on the Microsoft Online Portal and in May 2014 Office Professional Plus users will receive a notice and subsequently enter Reduced Functionality Mode with 30 days notice.

Taken directly from the FAQ regarding Office ProPlus website:

“We don’t want to upgrade to Office 365 ProPlus. Can’t we keep authenticating for Office ProPlus 2010?
No.

The Product Use Rights for Office ProPlus state: “If we provide a major upgrade to software licensed under your User SLs for the online service, you must install the upgrade on all devices using the online service to prevent an interruption of the online service.” Additionally, Office Subscription customers do not have downgrade rights.

If you cannot (or do not want to) upgrade to Office 365 ProPlus by 28 February 2014, you should purchase a Volume License for Office, utilize downgrade rights, and reinstall the perpetual version of Office 2010 on all machines with Office ProPlus 2010.”

This is an interesting statement, as downgrade rights remain enshrined within Volume Licensing. Those organisations seeking to leverage on-premise deployment rights for legacy versions of Office 2010 will need to leverage the use rights under a perpetual license procured under Volume Licensing.

“We purchased Office ProPlus 2010, but deployed the version of Office Professional Plus 2010 from the Volume Licensing Service Center (VLSC). What will happen to us on 28 February 2014?
First off, it you don’t understand this question, it almost certainly doesn’t apply to you.

If you installed Office Professional Plus 2010 via the MSI on the VLSC, you will not have users entering Reduced Functionality Mode, as this version is not cloud-authenticated. You will, however, be violating your Office Subscription license agreement.”

Ref: FAQ regarding Office ProPlus [last checked: 24.07.2013].

In terms of binding-documentation, the Microsoft Product List provides the following statement on legacy software use rights for Office 2010:

“Use of Office Professional Plus 2010 or Office for Mac Standard 2011

With the release of the updated service for Office 365 ProPlus your media eligibility right to use Office Professional Plus 2010 or Office for Mac Standard 2011 in place of Office 365 ProPlus software under active subscriptions has been discontinued. You have a year, until February 28th, 2014 to upgrade your devices to Office 365 ProPlus media.

* See February 2013 Product List for full terms of media eligibility rights for Office Professional Plus Subscription”

[Ref: Product List, July 2013, Page 103 of 192]

[Please note another useful resource: Microsoft Service Updates Website.]

The Impact of Office 365 “Add Ons”

It was recently announced that E3 and E4 SKUs under Office 365 will be available as “Add Ons”. This will support organisations to wish to retain perpetual rights to Core CAL and ECAL Suites but want to access cloud services. This was reported as effective August 1st.

This has an important impact for Office. Wherein, organisations will be able to “Add On” E3 and E4 service plans to their existing Enterprise Agreement (EA) without committing to Office 365 Pro Plus. This would support access to Lync, Exchange and SharePoint as a Microsoft hosted cloud service without committing to the software use terms and contractual commitment to Office 365 Pro Plus at outset. This is particularly advantageous to organisation’s with perpetual rights to Office Professional Plus 2013.

  • Add Ons are an “Additional Product”on the Customer Price Sheet (CPS)
  • Add Ons do not change the underlying EA. True up for Qualified Devices as normal.
  • “No minimum” for Add Ons.
  • Add Ons are for a “Primary User” for an existing qualifying underlying License. Add Ons cannot exceed underlying licenses on the Enterprise Agreement.

O365 AddOns 2

This will be reviewed later on this website, referencing available binding and non-binding advisory documentation. This is intended for information purposes only, and I am available for consultation (under NDA) as required to review your Microsoft procurement strategy.


Software Use Rights to Office Professional Plus 2013 on Remote Desktop Services

While limitation to downgrade a cloud service is logical, Microsoft do not exhaustively advise customers on ‘on-premise’ use rights of Office Professional Plus in their advisory and binding documentation.

The Product List does address that some organisations with an Office 365 Pro Plus user subscription, may require support for user profile(s) that require Office Professional Plus 2013 deployment on a network server:

“If the user to whom you have assigned an Office 365 ProPlus license uses the software on a network server with RDS role enabled, in lieu of installing a copy of the software provided with Office 365 ProPlus on one of the five permitted devices pursuant to the Product Use Rights for Office 365 ProPlus, that user may 1) install one copy of the Office Professional Plus 2013 software on a network server and 2) access the Office Professional Plus 2013 software from any device.  Upon termination of your Office 365 ProPlus subscription you must uninstall Office Professional Plus 2013 software from the network server.”

[Ref: Product List, July 2013, Page 103 of 188]


Final Thoughts

The restrictive approach to support legacy Office users was seen by some commentators as restrictive for customers who are looking to adopt cloud procurement, and see the value in signing up to cloud procurement model ‘now’, but have a longer transition roadmap for their legacy office deployed footprint that the Microsoft upgrade cycle.

Those seeking to leverage software use rights for legacy on-premise deployments of Office 2010 leveraged from the Office 365 cloud service plans that include Office 365 Pro Plus, appear to have a narrow and limited grace period (as of writing) until February 28th 2014 subject to Microsoft guidance and terms extracted above. The official date for Windows XP end of support is April 8th 2014

Organisations are responding to the User CAL Price Increase and interest in cloud hosted email and collaboration services within the E3-E4 Plans to review cloud procurement models at contract renewal. This is combined with a gradual change in the way incentives are paid to channel partners worldwide to drive cloud service adoption.

Many organisations have adopted a longer upgrade cycle than the software release cycle of a software vendor, but often choose to leverage new procurement contracts to leverage price protection, better price level, special rights of purchase, or extended software use rights, often enabled under an ‘active’ contract with Software Assurance (SA) (maintenance). This has long driven ‘net new’ volume procurement even when the technical reality in the customer would not support spend.

The role of downgrade rights has been critical for Microsoft to drive relational procurement contracts under Volume Licensing. The consistency in overall approach for common productivity applications like Office was useful, but this has since caused customer confusion with the emergence of Office as a cloud service offering within Office 365.

Those customers with existing perpetual rights to Office 2013 may seek to opt out of cloud subscription model for Office 365 Pro Plus, but may be under increasing scrutiny to prove compliance; Microsoft will continue to leverage the popularity of mobile working (and the explosion of companion devices) to incentivise adoption of the User based metric available under Office 365 Pro Plus. The up-date to the Office 365 cloud service commercial licensing model is welcomed in the support for customers who want to migrate to the cloud ‘on their terms’.

– If you would like to book an in-depth Licensing Workshop / Microsoft Strategy Workshop please drop a quick email or connect with Tony on Twitter


Resources

  1. The latest Product List (July)
  2. The latest Product Use Rights (July)
  3. The Product List Archive
  4. Microsoft Licensing Brief Downgrade Rights (September 2012)
  5. Microsoft Licensing Brief Licensing Microsoft Office Professional Plus for Office 365 (May 2013)
  6. Microsoft Lifecycle Information for Microsoft Office Products Support Website
  7. Microsoft Wiki FAQ regarding Office ProPlus
  8. Microsoft Office Website
  9. Microsoft Service Updates Website
  10. Microsoft Windows XP End of Support Website
  11. Microsoft Product Activation Center Support Website
  12. Microsoft Fulfilment Website
  13. Microsoft Support Lifecycle FAQ and Microsoft Support Lifecycle
  14. Microsoft Product Lifecycle Search
  15. Microsoft Office Products Support Lifecycle FAQ
  16. Microsoft Windows lifecycle fact sheet

All website were last checked: 24.07.2013

Other Useful Articles from this site.

Hierarchy of Software Licensing Terms

Windows Enterprise Edition – Under Review

The Multiplexing Rule – Under Review (Updated)


About

This website is a way to give back to the licensing community and as an information resource for all customers that work with Microsoft software and licensing. I hope you find it of value.

Tony Mackelworth is a Senior Licensing Specialist at SoftwareONE

If you would like to book an in-depth Licensing Workshop / Microsoft Strategy Workshop please drop me an email or connect with Tony on Twitter

Tony lives with his wife in Oxford, England.


Disclaimer

This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. This document does not provide you with any legal rights to any intellectual property in any Microsoft or other Software Vendor product.

This article is not intended to replace the Product Use Rights or Product List or other contractual documentation.

Please be aware that nothing on this website constitutes specific technical advice. Some of the material on this website may have been prepared some time ago, may have errors, and  may have been superseded. Specialist advice should be taken in relation to specific circumstances.

The contents of this website are for general information purposes only. Whilst the author(s) endeavour to ensure that the information on this website is correct, no warranty, express or implied, is given as to its accuracy and the primary author and website owner or it’s contributing Authors do not accept any liability for error or omission.

The contributing authors and owner of the website shall not be liable for any damage (including, without limitation, damage for loss of business or loss of profits) arising in contract, tort or otherwise from the use of, or inability to use, this website or any material contained in it, or from any action or decision taken as a result of using this website or any such material.

The information presented herein is intended exclusively as a guide offered by the author(s). The publishers product use rights, agreement terms and conditions and other definitions prevail over the information provided herein.

Continue reading

Office 2013 Overview

clip_image001[4]

Microsoft  communicated some incredible statistics; with over 350 Million smart phones used for work, and 50% of enterprises with technology roadmaps that include the Cloud; Microsoft’s cloud integrated approach for Office 2013 was their answer to provide a seamless user experience across different devices.

  • This article will give you a brief overview of the licensing model(s)
    [Article originally written 15th April 2013, Updated August 1st 2013]

  • This article is not intended to replace the Product Use Rights or Product List
  • Please be aware that any licensing information could be subject to change. This article confers no rights and is provided for information purposes only.

Office Features and Components

Below is a ‘snapshot’ of the components assigned to Office Professional Plus 2013 and the extended value proposition Microsoft have incorporated in Office 365 ProPlus

image

image


Office Professional Plus (On-Premise)

Microsoft originally released Office Professional Plus 2013 RTM to Volume Licensing Customers with Active Software Assurance (SA) on October 11th 2012

Microsoft announced that support for Office 2003 will end on April 8 2014 to coincide with Windows XP End of Support; encouraging organisations to upgrade to the latest release(s).

  • Users with an On-Premise technology roadmap are able to upgrade to Office Professional Plus 2013
    • This can be procured through Perpetual or Subscription Volume Agreements.
    • This is licensed on a Per Device model Organisations can adopt a Cloud procurement model, and transition Users to Office 365 Pro Plus over the contract term. It is recommended to work with a licensing expert Partner to understand the optimum approach to Product Licensing and Procurement Model(s) for your organisation.

image

  • On-premise client software will continue to be installed, managed, and licensed on a per-device basis.
  • The on-premises per-device model is based on a core assumption that the more devices a user has running the full software experience, the more value the user will derive.

image

[Ref: Ready To Go Microsoft Website] Please note: this is derived from non-binding marketing collateral. Please refer to binding documentation.


Office 365 ProPlus (Cloud Service Model)

Users with a Cloud Roadmap have the option to transition to Office 365 ProPlus

    • This was a re-engineered Office for cloud scenarios and multiple device use, consistent with the Microsoft vision of a user-centric cloud service.
    • This is deployed, authenticated, and managed on a per-user basis and is licensed on a Per User model.
    • A single user cloud service subscription will support use on a maximum of 5 Devices
    • Organisations can adopt Cloud Services procurement model, and transition current On-Premise Users to Office 365 ProPlus over the contract term when the O365 Services Refresh goes live.
    • Extended access to Office Apps natively via Android and iOS

[Ref: Microsoft Software Lifecycle Website]

This is a snapshot overview of the licensing features of Office 365 Pro Plus.

image

Please refer to the relevant Product Use Rights or Product List and your relevant Volume Agreement contract(s).


Mobile Office Clients

  • The Mobile Office client for mobile devices will be licensed as a Per User ‘add-on’ to the Office Professional Plus on-premises device license.
    • Commercial use rights to Office RT with purchase of Office Professional Plus on a Volume Agreement (Open, Select Plus, EA)
  • This will be included with Office 365 ProPlus Per User license.

image


An Exploration of Downgrade Rights

Binding Documentation

Microsoft provide the software use terms for use of prior versions  via the monthly updated Product List and the Universal License Terms of the Product Use Rights. Microsoft define the extended software use right within the Universal License Terms and then subsequently amend or retract based on product, as specified in either the General License Terms or Product-Specific License Terms and Additional Terms of the Product Use Rights document.

  • The Universal License Terms. These terms apply to all products licensed through Microsoft Volume Licensing.
  • The General License Terms. These terms apply to all products that use a particular licensing model. Each licensing model section includes a list of products that use that particular model.
  • The Exceptions and Additional Terms for the product. Any additional product-specific terms are listed by product.

[See article: Hierarchy of Software Use Terms]


Downgrade Rights (Volume Licensing)

Microsoft provide the following definition in the Universal License Terms of the Product Use Rights,

“For any permitted copy or instance, you may create, store, install, run or access in place of the version licensed, a copy or instance of a prior version, different permitted language version, or different available platform version (for example, 32 bit or 64 bit). You may use different versions of components only as permitted under the Product-Specific License Terms. If you use an earlier version under these downgrade rights, Microsoft is under no obligation to provide security updates or support for the product or service beyond the end of support date listed at http://support.microsoft.com/lifecycle.”

[Ref: Product Use Rights, July 2013, Page 9 of 114]

The Product List states downgrade rights as a universal software use right of Volume Agreements, but are careful to continue to set the parameters of support for older versions: “customers can acquire the latest version in order to use an older version with downgrade rights, but are eligible for support for that product only if it is listed as supported” as maintained in the software lifecycle website.

[Ref: Product List, July 2013, Page 74 of 188]

Microsoft  offer a minimum of 10 years support for business products. This is classified as 5 years of mainstream support or for 2 years after the successor product is released (whichever is longer); and extended support provided for the 5 years following end of mainstream support; or for 2 years after the 2nd successive product is released (whichever is longer) – This is available in detail on the life policy website.


Volume Licensing: Legacy Deployments of Office

The September 2012 Licensing Brief states that downgrade rights “are granted with all application software licenses acquired through the Volume Licensing programs” wherein, Volume Agreements “give you the right to downgrade to any prior version of the same product”.

As an example, the Multi Language Pack, when procured with an application license (for any of the following products) are eligible to version downgrade.

  • Office Standard 2013
  • Office Professional Plus 2013
  • Project Standard 2013
  • Project Professional 2013
  • Visio Standard 2013
  • Visio Professional 2013

“are eligible to use the English/Multilanguage version of a downgraded version of the product in place of the licensed version. Use of the downgraded version of the product is subject to the use rights for the 2013 version of the product. These rights expire when the customers’ rights to either the Office Multi-Language Pack 2013 or the above listed 2013 product expires.”

[Ref: Product List, July 2013, Page 102 of 188]

The Licensing Brief document states that an organisation  “may downgrade Microsoft Office Professional Plus 2010 to the Microsoft Office Professional Plus 2007, Office Professional Enterprise 2003, Office Professional XP” […]You may not, however, downgrade to Microsoft Office Standard Edition 2007 because it is a different product and not considered a prior version of Microsoft Office Professional Plus 2010.”

[Ref: Downgrade Rights Licensing Brief September 2012, Page 4 of 6]

The advisory document does address issues from the consolidation of editions upon general availability of Office 2010:

”In addition, Office Professional Plus 2010 users may not use earlier versions of the Microsoft Office OneNote note-taking program and Microsoft Office Groove software via downgrade rights, because these products are not part of earlier versions of the suite (for example, OneNote 2007 and Groove 2007 are not included with Office Professional Plus 2007)”

[Ref: Downgrade Rights Licensing Brief September 2012, Page 4 of 6]

(For information purposes, I have provided a diagram of the releases of Office illustrating where a component has been upgraded, added or discontinued; Please be aware this is not derived from any Microsoft binding or advisory documentation):
image

IT Asset Managers should be aware, that if attempting to maintain a legacy deployment of Office Enterprise 2007 as  part of your corporate image across your organisation,“Software Assurance (SA) customers who have deployed Office Enterprise 2007 only (i.e., are not using any other edition of Office in their organization), and need additional seats of Office Enterprise 2007, may purchase licenses for Office Professional Plus 2010 and downgrade to Office Enterprise 2007. No other downgrades from Office Professional Plus 2010 to Office Enterprise 2007 are permitted.”

[Product List, November 2012, Page 95 of 175]

[Ref: Licensing Brief September 2012, Page 5 of 6]

In terms of access to software for installation, Microsoft provides guidance via the Fulfilment Website informing customers that software is available for download via the Volume Licensing Service Center (VLSC).

VLSC provides download access only to the current (N) and the last version (N-1) of products. This again drives customer behaviour to upgrade. As of December 2012 Microsoft continued to support a limited set of N-2 and N-3 prior product versions for download on VLSC but should a release be removed, this is via the Product Activation Center.

Previous product editions available through VLSC

Microsoft provide guidance on support for legacy releases of Office on the Microsoft Office Products Support Lifecycle Website


Visio Professional 2013 Downgrade Rights

IT Asset Managers should be aware, that if attempting to maintain a legacy deployment of Visio Premium 2010; Upon release of Visio Professional 2013 Microsoft extended a downgrade right for Visio Premium 2010 users only with a standardised enterprise-wide deployment of the product.

“Software Assurance customers who have deployed Visio Premium 2010 only (i.e., are not using any other edition of Visio in their organization), and need additional seats of Visio Premium 2010, may purchase licenses for Visio Professional 2013 and downgrade to Visio Premium 2010. No other downgrades from Visio Professional 2013 to Visio Premium 2010 are permitted.”

[Ref: Product List, July 2013, Page 104 of 188]

This caveat, enshrined within the Product List requires strict software asset management controls to leverage this ‘downgrade right’ and is recommended to closely monitor deployed software in your desktop estate.

Under the Software Assurance Migration Path for Visio Premium 2010 Microsoft extended the use right to the Professional 2013 edition under the following conditions of use:

“Customers with active Software Assurance coverage for Visio Premium 2010 as of download availability date for Visio Professional 2013 are eligible to use Visio Professional 2013 in place of Visio Premium 2010.

The right to use Visio Professional 2013 under this offering expires when the right to use Visio Premium 2010 under the corresponding qualifying licenses expires. Use of Visio Professional 2013 is governed by the use rights for Visio Professional 2013 and the terms and conditions of the customer’s volume license agreement. This product condition note and the customer’s evidence of the corresponding qualifying license together evidence the right to use Visio Professional 2013 under this offer. Upon expiration of Software Assurance coverage for Visio Premium 2010, the customer may acquire Software Assurance for Visio Professional 2013 without the need to separately acquire a new license.

[Ref: Product List, July 2013, Page 105 of 188]

This logic is consistent in the advisory brief on Visio Premium 2010 that downgrade rights are version specific, and Microsoft maintain caveats for existing maintenance (SA) customers with legacy deployments:

“Downgrade rights in Volume Licensing agreements provide customers with the right to downgrade to any prior version of the same product. However, Visio Premium 2010 is a new product without a prior version, so downgrade rights do not apply.Only Software Assurance customers who licensed Visio Professional 2007 may continue to use Visio Professional 2007under those licenses despite their Software Assurance migration rights to Visio Premium 2010.

[Ref: Licensing Brief September 2012, Page 5 of 6]


Visio Pro for Office 365 Downgrade Rights

As an express limitation for the Office 365 Pro Plus service; The Product List states that “Visio Pro for Office 365 service has no downgrade rights.”

[Ref: Product List, July 2013, Page 106 of 188]


Office 365 Pro Plus Downgrade Rights

An express limitation for the Office 365 Pro Plus service; the Product List states that the “Office 365 ProPlus service has no downgrade rights”.

[Ref: Product List, July 2013, Page 104 of 188]

Microsoft do address the issue of downgrade rights under O365 Pro Plus subscriptions in a non-binding advisory document:

“In Online Services customers have access to the latest technology with the newest features and releases. As with all Subscription Services, Microsoft generally offers only the latest version of the service at a time. Therefore, downgrade rights are not available with Office Professional Plus for Office 365 licenses

[Ref: Licensing Microsoft Office Professional Plus for Office 365, June 2011, Page 3 of 6]


Is there an exception to the rule….?

Microsoft do elaborate on the topic of on-premise use downgrade rights under the O365 Office Pro Plus Subscription:

“There is a one-time exception during the introduction of Office Professional Plus for Office 365 to Enterprise and Enterprise Subscription customers. If those customers have deployed Office Professional Plus 2010 under their Enterprise or Enterprise Subscription agreement, they may use Office Professional Plus 2010 software in place of Office Professional Plus for Office 365 user authenticated software. Although those customers may be allowed to use Office Professional Plus 2010 software, they are still required to comply with the use rights under their Office Professional Subscription license and no perpetual software rights apply.”

[Ref: Licensing Microsoft Office Professional Plus for Office 365, June 2011, Page 4 of 6]

It is understood this exception, (subject to approval from your Microsoft subsidiary), could be made available for organisations that provisioned an E3 tenant prior to Office 365 commercial availability on 27th February 2013; to support continued access to Office ProPlus 2010 installer until 8th April 2014.

Windows XP will be out of support on 8th April 2014 and may drive some organisations to upgrade Windows to enable access to the new wave of cloud productivity Office 365 applications on Windows 7.

The software use right to install Office 2010 locally under Office 365 is by exception, available under a specifically agreed contractual amendment from Microsoft;  Your procurement strategy should be principally defined by binding documentation for your organisation.

An agreed exception would be notwithstanding anything to the contrary in the Product Use Rights or other binding contractual documentation, to enable an organisation to install Office Professional plus 2010 locally;. However, this would likely be time limited; “[…] All customers will need to comply with Online Services upgrade requirements in the next release” and upgrade to the required version of Office Professional Plus.

[Ref: Licensing Microsoft Office Professional Plus for Office 365, June 2011, Page 4 of 6]

Driving Adoption of Cloud Services

The  Microsoft Office Website does suggest support for dual access rights for on-premise legacy office deployments, permitting customers to “keep older versions of Office side by side on your PCs to mitigate any potential file or add-in compatibility risks”   [last checked: 24.07.2013]. However, this was likely intended as atemporary right, and not aligned to the full term of the service.

The FAQ regarding Office ProPlus website is still active [last checked: 24.07.2013] and Microsoft do make the following statements: “If you have users who installed Office 2010 Subscription,you are required to upgrade to new version of Office 365 ProPlusby 28 February 2014” and “You will be able to install Office ProPlus 2010 until 28 February 2014.”; Microsoft will then remove the installation link on the Microsoft Online Portal and in May 2014 Office Professional Plus users will receive a notice and subsequently enter Reduced Functionality Mode with 30 days notice.

Taken directly from the FAQ regarding Office ProPlus website:

“We don’t want to upgrade to Office 365 ProPlus. Can’t we keep authenticating for Office ProPlus 2010?
No.

The Product Use Rights for Office ProPlus state: “If we provide a major upgrade to software licensed under your User SLs for the online service, you must install the upgrade on all devices using the online service to prevent an interruption of the online service.” Additionally, Office Subscription customers do not have downgrade rights.

If you cannot (or do not want to) upgrade to Office 365 ProPlus by 28 February 2014, you should purchase a Volume License for Office, utilize downgrade rights, and reinstall the perpetual version of Office 2010 on all machines with Office ProPlus 2010.”

This is an interesting statement, as downgrade rights remain enshrined within Volume Licensing. Those organisations seeking to leverage on-premise deployment rights for legacy versions of Office 2010 will need to leverage the use rights under a perpetual license procured under Volume Licensing.

“We purchased Office ProPlus 2010, but deployed the version of Office Professional Plus 2010 from the Volume Licensing Service Center (VLSC). What will happen to us on 28 February 2014?
First off, it you don’t understand this question, it almost certainly doesn’t apply to you.

If you installed Office Professional Plus 2010 via the MSI on the VLSC, you will not have users entering Reduced Functionality Mode, as this version is not cloud-authenticated. You will, however, be violating your Office Subscription license agreement.”

Ref: FAQ regarding Office ProPlus [last checked: 24.07.2013].

In terms of binding-documentation, the Microsoft Product Listprovides the following statement on legacy software use rights for Office 2010:

“Use of Office Professional Plus 2010 or Office for Mac Standard 2011

With the release of the updated service for Office 365 ProPlus your media eligibility right to use Office Professional Plus 2010 or Office for Mac Standard 2011 in place of Office 365 ProPlus software under active subscriptions has been discontinued. You have a year, until February 28th, 2014 to upgrade your devices to Office 365 ProPlus media.

* See February 2013 Product List for full terms of media eligibility rights for Office Professional Plus Subscription”

[Ref: Product List, July 2013, Page 103 of 192]

[Please note another useful resource: Microsoft Service Updates Website.]


The Impact of Office 365 “Add Ons”

It was recently announced that E3 and E4 SKUs under Office 365 will be available as “Add Ons”. This will support organisations to wish to retain perpetual rights to Core CAL and ECAL Suites but want to access cloud services. This was reported as effective August 1st 2013.

This has an important impact for Office. Wherein, organisations will be able to “Add On” E3 and E4 service plans to their existing Enterprise Agreement (EA) without committing to Office 365 Pro Plus. This would support access to Lync, Exchange and SharePoint as a Microsoft hosted cloud service without committing to the software use terms and contractual commitment to Office 365 Pro Plus at outset. This is particularly advantageous to organisation’s with perpetual rights to Office Professional Plus 2013.

  • Add Ons are an “Additional Product”on the Customer Price Sheet (CPS)

  • Add Ons do not change the underlying EA. True up for Qualified Devices as normal.
  • “No minimum” for Add Ons.
  • Add Ons are for a “Primary User” for an existing qualifying underlying License. Add Ons cannot exceed underlying licenses on the Enterprise Agreement.

O365 AddOns 2

This will be reviewed later on this website, referencing available binding and non-binding advisory documentation. This is intended for information purposes only, and I am available for consultation (under NDA) as required to review your Microsoft procurement strategy.


Final Thoughts

The restrictive approach to support legacy Office users was seen by some commentators as restrictive for customers who are looking to adopt cloud procurement, and see the value in signing up to cloud procurement model ‘now’, but have a longer transition roadmap for their legacy office deployed footprint that the Microsoft upgrade cycle.

Those seeking to leverage software use rights for legacy on-premise deployments of Office 2010 leveraged from the Office 365 cloud service plans that include Office 365 Pro Plus, appear to have a narrow and limited grace period (as of writing) until February 28th 2014subject to Microsoft guidance and terms extracted above. The official date for Windows XP end of support is April 8th 2014

Organisations are responding to the User CAL Price Increase and interest in cloud hosted email and collaboration services within the E3-E4 Plans to review cloud procurement models at contract renewal. This is combined with a gradual change in the way incentives are paid to channel partners worldwide to drive cloud service adoption.

Many organisations have adopted a longer upgrade cycle than the software release cycle of a software vendor, but often choose to leverage new procurement contracts to leverage price protection, better price level, special rights of purchase, or extended software use rights, often enabled under an ‘active’ contract with Software Assurance (SA) (maintenance). This has long driven ‘net new’ volume procurement even when the technical reality in the customer would not support spend.

The role of downgrade rights has been critical for Microsoft to drive relational procurement contracts under Volume Licensing. The consistency in overall approach for common productivity applications like Office was useful, but this has since caused customer confusion with the emergence of Office as a cloud service offering within Office 365.

Those customers with existing perpetual rights to Office 2013 may seek to opt out of cloud subscription model for Office 365 Pro Plus, but may be under increasing scrutiny to prove compliance; Microsoft will continue to leverage the popularity of mobile working (and the explosion of companion devices) to incentivise adoption of the User based metric available under Office 365 Pro Plus. The up-date to the Office 365 cloud service commercial licensing model is welcomed in the support for customers who want to migrate to the cloud ‘on their terms’.

– If you would like to book an in-depth Licensing Workshop / Microsoft Strategy Workshop please drop a quick email or connect with Tony on Twitter


About

This website is a way to give back to the licensing community and as an information resource for all customers that work with Microsoft software and licensing. I hope you find it of value.

Tony Mackelworth is a Senior Licensing Specialist at SoftwareONE

If you would like to book an in-depth Licensing Workshop / Microsoft Strategy Workshop please drop me an email or connect with Tony on Twitter

Tony lives with his wife in Oxford, England.



Disclaimer

This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. This document does not provide you with any legal rights to any intellectual property in any Microsoft product.

Please be aware that nothing on this website constitutes specific technical advice. Some of the material on this website may have been prepared some time ago and therefore may have been superseded. Specialist advice should be taken in relation to specific circumstances.

The contents of this website are for general information purposes only. Whilst the author(s) endeavour to ensure that the information on this website is correct, no warranty, express or implied, is given as to its accuracy and the primary author and website owner or it’s contributing Authors do not accept any liability for error or omission.

The contributing authors and owner of the website shall not be liable for any damage (including, without limitation, damage for loss of business or loss of profits) arising in contract, tort or otherwise from the use of, or inability to use, this website or any material contained in it, or from any action or decision taken as a result of using this website or any such material.

Licensing for iPads and Microsoft Surface (2012)

This article is an update for October 2012 and will incorporate updated licensing models for Windows 8 and the EA Qualified Device definition.

image

  • This article will examine how you address mobile slate devices in your organisation and bring Microsoft Windows OS experience to your users on any device depending on your business goals.
  • This will look at what you need from the Microsoft end.
  • This will look at what you need from the Citrix end.
  • This will look at the Microsoft licensing requirements to get this done.
  • This article will give you a brief overview of the different Virtualization scenarios so you can map your product and licensing requirements.
  • This article is not intended to look at Microsoft Application licensing.

Types of Virtualization

Whether personal virtual desktops, a virtual desktop pool or session-based desktops, or Virtual Apps, it is important to evaluate the Microsoft Virtualization Stack and Licensing Models to support your organisation’s objectives.

image


The Microsoft Virtualization Stack

The table below gives a brief overview of the Microsoft product stack to support your virtualization objectives. This will be different If you are adopting a VMware Solution but please be aware of how your environment will affect and interact with Microsoft Server products, Operating Systems and Applications and the associated Software Use Rights.

image


Licensing the iPad on your Network

The product licensing requirements for the Apple iPad will depend ultimately on the type of virtualization and access requirements that will be adopted.

Currently, there are three major usage scenarios for iPads in the enterprise that access Microsoft software and servers:

  • Running email from the Exchange server using iPad Email and Calendar in iOS
  • Accessing an HVD using Secure Access Client (Access Gateway)
  • Using server-based Microsoft applications, such as Office using Microsoft Remote Desktop Services enabled by 3rd party
    secure access clients, such as Citrix Receiver for iPad.

Microsoft Client Access Licenses (CALs) will enable access to most servers, aligned to Device or User. Accordingly, as most organisation’s have historically adopted a Device CAL model, iPads as extra devices need to be licensed. Compare the user server access requirements with the CAL model you are using to evaluate requirements.

If you are adopting Microsoft System Center 2012, managed clients are licensed via Client MLs (Client Management Licenses). This is available within the Client Management Suite and Configuration Manager Client ML

image

Users may require access to their Windows Applications that are not available natively on iOS or. To support this use scenario, an organisation can adopt Microsoft Remote Desktop Services (with or without Citrix XenApp software) to access Remote Desktop Protocol (RDP) or Citrix ICA.

Windows Companion Subscription Licence (CSL)

Microsoft have enable access to Windows OS via the Companion Subscription Licence (CSL) model for corporate or personal owned non-86 devices (iPad). The subscription will enable a user to access Windows in Virtual Desktop Infrastructure (VDI) or via USB Windows To Go in up to 4 companion devices.

  • Devices eligible for CSL include any type of personally owned device as well as corporate owned non-x86/x64 devices. This is intended to support BYOD policies, and Microsoft have incorporated this into the product licensing model.

image

The Windows Companion Subscription License (CSL) enables BYOCD (Bring Your Own Companion Device) scenarios and provides businesses with more flexibility to run Windows OS across various form factors.

Under Windows 7, Users that wanted access the corporate desktop remotely from their personal iPad could leverage Windows Roaming Rights under their organisations Volume Agreement with active Windows SA. However, should a user bring that device into the office and access Windows (VDI) from within the corporate firewall, the product licensing model would require an additional VDA Subscription. This was hard to track and not easy to explain.

Under Windows 8, Users that have a “Primary Device” licensed under a Volume Agreement with Software Assurance (SA) for Windows, can access Windows on or off premise on up to 4 devices via the “add on” Companion Subscription Licence (CSL)


Windows Surface (RT) Companion VDA Rights

Microsoft have incentivised the take-up of Windows RT devices by allowing the “Primary User of the licensed device” to access their windows desktop through a VDI from a corporate owned Windows RT device.

Technology has influenced how people stay connected not just from their work PC but also from secondary, or what Microsoft have termed “companion devices” such as tablets. Microsoft have bolstered SA for Windows to enable these companion devices with more flexibility for how employees can access their corporate desktop (VDI) from these devices.

With Windows 8, the primary user of a device licensed with Windows 8 Pro with active Software Assurance (SA) may access a corporate VDI from a company owned companion Windows RT device without having to acquire a separate Windows VDA subscription, encouraging corporate customers to move to Microsoft slate devices.

image

  • This encourages corporate owned slate devices such as iPad will need a CSL license If the user brings the device into the office to access Windows in a VDI Environment
  • If the organisation does support BYOD (Bring Your Own Device) it will encourage take-up of a corporate owned Windows RT device
    • Windows RT Companion VDA Rights strongly supports the procurement of Windows 8 Pro with Software Assurance (SA) and the renewal of active Volume Agreements with Software Assurance coverage for Windows.

image


Citrix Solutions

Citrix have a lot of guidance on their website on how to approach including the iPad on your network to provide full desktop or application access to your users.

Citrix XenDesktop enables user access to Windows desktops and applications on-demand from any device. The Citrix FlexCast delivery technology allows HD user experience of Virtual Desktops via Macs, PCs, Ultrabooks, Slates, iPads and Thin Clients for all access scenarios.

The Citrix Receiver is available as a client download to enable touch functionality over XenDesktop and XenApp based on Windows Server. XenApp features include instant access for both hosted and streamed virtual applications delivered into a virtual desktop.

  • Hosted Shared Desktops
  • Hosted VDI Desktops
  • Streamed VHD Desktops
  • Local VM Desktops
  • App Virtualization

image

Ref: You can find out more from Citrix by going to the http://www.citrixandmicrosoft.com

 

 


Conclusion

Microsoft and Citrix have enabled full productivity from a range of devices and provided options in the way your users access their data and their desktop and their applications. How you approach this in your organisation will have to be considered and hopefully the range of links and content within this article will assist you.

The theme of this article has been around the iPad– but your licensing requirements will be dependent on what you want your users to access on your network and the functionality and experience you want them to have, whether your organisation will invest in Windows RT Devices and the ownership of those devices.

I have included briefly the licensing requirements for looking at the Windows OS and access to corporate Email. his does not cover Office, which will be addressed in a later article. However If you want further information please review my several articles on this blog to get clarity for your particular usage scenario. Microsoft Licensing can be complex, so always refer to as many dependable resources as possible, whether the Microsoft website, the Product Use Rights and Product List or your Large Account Reseller.

One take away from this article is that 3rd party vendor solutions for Virtualization delivery and management rarely provide you with the full licensing implications and costs to provide Microsoft products over their technologies. So it is worth doing your research and understanding the total cost of ownership.


Please be aware that I now work at a Large Account Reseller and will now be providing my licensing expertise through their Licensing Services. So please do get in contact with me directly if you would like to have a bespoke review for your organisation.

Our specialist team can assist you to purchase the correct licenses, at the best price, through the right program.  Please email my directly to arrange a meeting or call.

– Tony Mackelworth


Disclaimer

This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. This document does not provide you with any legal rights to any intellectual property in any Microsoft product.

Please be aware that nothing on this website constitutes specific technical advice. Some of the material on this website may have been prepared some time ago and therefore may have been superseded. Specialist advice should be taken in relation to specific circumstances.

The contents of this website are for general information purposes only. Whilst the author(s) endeavour to ensure that the information on this website is correct, no warranty, express or implied, is given as to its accuracy and the primary author and website owner or it’s contributing Authors do not accept any liability for error or omission.

The contributing authors and owner of the website shall not be liable for any damage (including, without limitation, damage for loss of business or loss of profits) arising in contract, tort or otherwise from the use of, or inability to use, this website or any material contained in it, or from any action or decision taken as a result of using this website or any such material.

This Disclaimer is not intended to and does not create any contractual or other legal rights. This website is not run by Microsoft or BT Engage IT and the opinions are the author’s own.


Windows 8 Licensing Update

Microsoft have now released Windows 8 to Volume Licensing and general release to the public will be on 26th October 2012.

  • This article will examine how you address normal PCs but also mobile slate devices in your organisation and bring Microsoft productivity tools and experience to your users on any device depending on your business goals.
  • This will look at what you need from the Microsoft end – whether you are looking at iPads or Windows RT Devices
  • This will look at the Microsoft licensing requirements to get this done.
  • This article will give you a brief overview of the different Virtualization scenarios or Device Types so you can work out your product and licensing requirements.
  • An overview of Downgrade Rights from Windows 8 If your organisation is not ready for the move from Windows 7

image

Windows 8 Pro will be the standard licensing mechanism for organisations who wish to adopt the latest release of Windows OS; while Extended Functionality, Extended Use Rights and associated Rights To Purchase are all aligned within the greater canon of Software Assurance benefits for Windows.

Software Assurance (SA) has been greatly expanded since its original introduction, and greater benefits have been attributed to a maintenance model, rather than the perpetual licence alone. This encourages customers to commit to procurement of maintenance (SA) to leverage the benefits that are not permitted with the licence alone.

In addition to the well known benefit of New Version Rights, Microsoft incentivise commitment to maintenance via Extended Functionality such as access to Windows 8 Enterprise Edition and impose certain limitations on Rights to Purchase of their wider technology stack – such as Microsoft Desktop Optimization Pack (MDOP).

Microsoft have incorporated Extended Use Rights within Software Assurance for Windows and this has been updated since Windows 7. Microsoft have responded to the popularity of tablet devices and are actively responding to BYOD (Bring Your Own Device) scenarios and responded to the emergent use of USBs for Portable Apps and Portable Windows by introducing Windows To Go within the Extended Functionality of Software Assurance (SA). This includes specific access rights to Windows in a Virtual Desktop Infrastructure (VDI); and there are updated specific licensing models that affect devices running Windows RT (Surface) or iOS, and should be exhaustively reviewed to understand the licensing implications for your organisation.


Windows 8 Pro Upgrades

Microsoft offer Windows 8 Pro though Volume Licensing as an Upgrade Licence. This approach recognises the existing base licence assigned to the device, whether OEM or Retail, or an existing Upgrade Licence(s) with underlying OEM or Retail licence.

image

The qualified base license will depend on both the Agreement type, and whether it is a new or existing Agreement. This does also include Mac OS (see diagram below) and is also available for reference in the Product List.

image_thumb24

[Ref: Windows 8 Licensing Guide, September 2012]

When an organisation is reviewing the implications of providing end users with the option to BYOD (Bring Your Own Device) it is recommended to confirm the existing licensed OS and whether it is on the “Qualified OS” list within the Product List

Please note: Organisations who have procured Windows 8 Pro software licenses through the OEM channel, please refer to the associated use rights are outlined in the Software License Terms that accompany the software. The license terms state use rights to run Windows locally on the licensed device in a Physical operating system environment (POSE). However, they do not provide use rights for accessing Windows running remotely in a virtual OSE (VOSE) from the licensed device and are limited when compared to the wider extended use rights incorporated in the Volume Agreement procurement model when combined with Software Assurance (SA).


Extended Functionality

Microsoft continue to promote adoption of premium SKUs. The Extended Functionality within Windows 8 Enterprise Edition is only available when Windows 8 Pro is procured with Software Assurance.

Extended Functionality will include access to a suite of technologies including Windows To Go, DirectAccess, BranchCache, AppLocker, VDI Enhancements, and corporate Windows 8 Apps deployment via Sideloading

image

A more detailed overview of the technologies are available on the Windows 7 website (last accessed 24/09/2012):

  • DirectAccess: Give mobile users seamless access to corporate networks without a need to VPN.
  • BranchCache: Decrease the time branch office users spend waiting to download files across the network.
  • Federated Search: Find information in remote repositories, including SharePoint sites, with a simple user interface.
  • AppLocker: Specify what software is allowed to run on a user’s PCs through centrally managed but flexible Group Policies.
  • Virtual Desktop Infrastructure (VDI) optimizations: Improved user experience for VDI with multi-monitor and microphone support, which have the ability to reuse virtual hard drive (VHD) images to boot a physical PC.
  • Multilingual user interface: Create a single OS image for deployment to users worldwide.

Microsoft have also responded to the emergent use of USBs for Portable Apps and Portable Windows and have introduced Windows To Go within the Extended Functionality of Windows 8 Enterprise Edition


Access to Windows 8 Enterprise Edition

The Windows 8 Enterprise Edition extended functionality is only available to devices with active Software Assurance (SA) for Windows.

  • The customer must ‘assign’ the Windows 8 Pro and Software Assurance (SA) within the Volume Agreement term
  • If Windows 8 Enterprise was not deployed prior to expiration, an organisation is now unable to deploy the upgrades after their coverage has expired.
  • If the assigned device was replaced after expiration, then Windows Enterprise cannot be re-assigned to the replacement device.

It is the personal view of the author, that deployment of Windows Enterprise is a right and not an obligation and therefore it should be the decision of the customer whether Enterprise is deployed on that device or not, and if they choose later that they want to deploy it after the Software Assurance term has expired, then they should be able to.

However, Microsoft confirm in the Product List that Software Assurance must remain ‘active’ to remain eligible for the benefit:

“[…] Customers with active Software Assurance coverage for the Windows desktop operating system are eligible for this benefit. Software Assurance coverage for the Windows desktop operating system on a licensed device gives customers the option to use Windows 8 Enterprise in place of Windows 8 Pro on that device.

Eligible Software Assurance customers have the rights to use Windows 8 Enterprise as described in the Product Use Rights. Customers may not move Windows 8 Enterprise from the licensed device to another device, except in conjunction with the permitted reassignment of their Software Assurance coverage.”

[Ref: Product List, September 2012, Page 59 of 169]

While an extended right to deploy Windows 8 Enterprise Edition after expiration (on a device correctly assigned within the agreement term) could arguably be supported by the following extract from the Product List below; One should be aware that access to enterprise functionality is not supported under “New Version Rights” as technically it is a different ‘Edition’ and not a new ‘Version’ of Windows.

New Version Rights

With Software Assurance, customers are eligible to upgrade to new versions of licensed software made available during their term of Software Assurance coverage. New Version Rights means, for any underlying licensed product for which Software Assurance coverage is ordered, the right to upgrade to, and run in place of the underlying licensed product, the latest version of that product that we make available during the covered period. For example, if a new version of Microsoft Office is made available during the term of your coverage, your licenses will automatically be upgraded to the new version. Customers that acquire perpetual licenses through Software Assurance can deploy the upgrades after their coverage has expired.

[Ref: Product List, September 2012, Page 55 of 169]

“When you license a device with Software Assurance, the SA benefits for that device are available for the term of the Software Assurance coverage only. Note, when acquired under a non-subscription license, Windows 8 Enterprise use rights are perpetual for the licensed device even after Software Assurance coverage ends as long as Windows 8 Enterprise was installed on the device at the time Software Assurance coverage ends. Perpetual use rights for Enterprise Edition are tied to the licensed device and end once the device is retired.”

[Ref: Windows 8 Licensing Guide, September 2012, Page 7 of 16]

Under this logic, a  customer licensed with Windows 7 Professional with active Software Assurance (SA) expiring 31st October 2012

  1. Can assign and deploy Windows 7 Enterprise Edition until the end of their Software Assurance (SA) coverage.
  2. Can deploy Windows 8 Pro in December (after expiration) using the benefit of “New Version Rights”.
  3. Cannot deploy Windows 8 Enterprise after expiration of Software Assurance (SA) coverage (since they no longer have rights to Enterprise Edition). Interesting Stuff.

[Ref: Thank you to the support and expertise of the folks at LicensEase]

Please be aware that this will supersede my previous information received from Microsoft US on this topic.


Enterprise Sideloading

Customers who have procured Windows 8 Pro with Software Assurance (SA) in an Enterprise Agreement, Select or Select Plus Agreement, or CASA Agreement, will be equipped to enable deployments of Windows 8 Apps through sideloading.

Sideloading via Windows 8 Enterprise is an enabled as a feature of Domain Joined PCs and customers can manage the deployment of corporate Windows 8 Apps to these devices by making an update to a group policy setting.

For Sideloading on Windows 8 Pro, Windows RT, or Windows 8 Enterprise devices that are non-domain joined; in addition to making the group policy update , customers will need a Volume Agreement (VL) Product Key that will be activated to enable the device for sideloading.

As stated in the Product List,

“Windows Enterprise Sideloading is the process of installing new Windows 8 Apps being used for the benefit of the customer directly to a device without going through the Windows Store. Domain joined devices running Windows 8 Enterprise edition are feature-enabled for Windows Enterprise Sideloading. Windows Enterprise Sideloading can also be enabled on devices running Windows 8 Enterprise that are not domain joined, and devices running Windows 8 Pro, or Windows RT through the use of a product key. In all cases, Windows Enterprise Sideloading may only be used to deploy Apps that are used for the benefit of the Volume Licensing customer. Windows Enterprise Sideloading functionality is supplemental to the Windows Desktop Operating System , and as such, the license terms applicable to the Windows Desktop Operating System, as supplemented here, apply to customers’ use of it.”

[Ref: Product List, September 2012, Page 98 of 169]

Windows via an Enterprise Agreement, Select or Select Plus Agreement, or CASA Agreement, will be granted enterprise sideloading rights and provided with the necessary product keys in the Volume License Service Center (VLSC).

Customers who are not committed to the Software Assurance (SA) model for Windows via the above mentioned agreements who want to deploy Apps on Windows RT or Windows 8 Pro devices can purchase a pack of 100 sideloading licenses with a single product key.

Further, the access to Sideloading is intrinsically linked to active Software Assurance as re-enforced by the wording in the Product List:

Windows Enterprise Sideloading may only be enabled on any permitted device prior to the expiration of the corresponding Software Assurance coverage or Subscription License

[Ref: Product List, September 2012, Page 98 of 169]


Windows 8 Downgrade Rights

An important knowledge resource upon release of a new product is understanding the Downgrade Rights (You can read previously provided the downgrade options for Windows 7). While to-date circa 580 Million licenses have been sold of Windows 7, many organisations have only recently deployed Windows 7 enterprise-wide or are still completing corporate refreshes to standardise on Windows 7 from XP.

It should be noted that End of Support for XP SP3 is now announced as April 8th, 2014 (12 Years and 6 Months since the original release date of October 2001)

  • Please be aware that Downgrade rights are included in licenses obtained through OEM or Volume Licensing and do not apply to retail copies of Windows.
  • OEM downgrade rights apply to Windows 8 Pro and allow downgrading for up to two prior versions (N-2) (to Windows 7 Professional or Windows Vista Business).
  • Software Assurance (SA) through Volume Licensing provides the greatest downgrade rights, allowing for downgrades to additional prior versions and editions, including notably, Windows 7 Enterprise

image

[Ref: Windows 8 Licensing Guide, September 2012]


Right to Purchase MDOP

Microsoft Desktop Optimization Pack (MDOP) includes App-V and Med-V and is provided as an Optional Purchase with Windows 8 Pro with Software Assurance (SA).

– This is an impressive toolkit to support virtualization and builds the business case for commitment to procure Windows 8 via a Volume Agreement with Software Assurance (SA).

Application Virtualization

Application Virtualization isolation occurs one level up in the stack from the OS and hardware. App virtualization isolates an application and all of that application’s files and resources from the operating system (OS), and any other application on the system.

Application virtualization isolates the application from the OS. While to the user, this doesn’t really differ from the traditional concept of directly installing applications directly on the OS, to IT organizations the difference can be massive.

App Virtualization (Microsoft App-V) allows multiple versions of the same application can run on one computer system at the same time. Also, apps can be automatically streamed to a desktop, on demand and as needed, without having to be installed by a local IT tech. App-V can provide centralized application management and security and easy, fast patching and upgrades. This is all available as part of Microsoft Desktop Optimization Pack (MDOP).

This technology can address a number of headaches. First, because the application is isolated from the OS, there’s no need for the application to be installed in any traditional sense of the word. (This means multiple versions of the same application can run on a single desktop) This also means that applications can be streamed out to a desktop when the user needs them, which doesn’t require a helpdesk call or a IT visit to the desk.

For the average desktop admin, this drastically reduces the time and cost implications of desktop management because it brings patch and upgrade management to one central location and will accelerate the deployment of any new applications. It also ensures the entire desktop environment is configured to be secure and consistent.

This enables the mobile end user, as the work critical apps they need to do their jobs actually follow them around the organization (Roaming Users). Interestingly, Microsoft’s application virtualization solution, App-V, can also stream only the parts of the application needed by the user and have instant click start-ups

Once the user logs off, the application can be removed, and is no longer there risking access by a non-authorised or unlicensed user.

When combined with User State Virtualization (USV), App-V allows you to have an environment that allows your users to be productive, with access to their own apps and data, anywhere they sign-on in your network.

Legacy Applications

If you are in the process of looking at Windows 7 you will likely be examining Application compatibility: Microsoft Enterprise Desktop Virtualization (MED-V) allows you to run your legacy applications, including Internet Explorer 6 based applications, inside a Windows XP compatibility workspace. This IT-managed Windows XP virtual environment remains hidden from your users. Applications running inside appear on the Windows 7 Start menu and appear to users indistinguishable from native applications.

Quick note – The Windows Steam Blog recommend checking out the new 2.0 release in the first quarter of 2011. Check out and evaluate the download at Microsoft Connect.

  • Buy Microsoft Desktop Optimization Pack (MDOP)
  • Create your Windows XP base image in Windows Virtual PC and install your legacy applications
  • Create a MED-V workspace package from your Windows XP base image
  • Deploy your MED-V workspace

Technical resources


Extended Use Rights

Virtual Desktop Infrastructure (VDI)

Virtual Desktop Infrastructure (VDI) is an alternative to the traditional desktop deployment model for Windows OS. This allows each user to get access to a personal desktop in the datacentre from any connected device. The access device could include a normal desktop environment with Windows or a Thin Client (TC) or iPad.

To obtain Virtual Desktop Access rights, the following approach must be adhered to:

  • A device is licensed with qualifying OS license(s) with ‘active’ coverage of Software Assurance (SA) for Windows.
  • If a device does not have qualifying OS license(s) (for example, a thin client or “nonx86” device) and, therefore, cannot be licensed with an Upgrade Licence should be licensed with a separate active Windows VDA Subscription

Roaming Use Rights

Roaming Use Rights allow the “primary user of any licensed device” to access Windows 8 running in the datacenter (VDI) or Windows To Go from non-corporate devices such as personally-owned or hotel or business centre PCs while outside the firewall (new Microsoft terminology: off company premises).

image

This licensing model enables employers to support remote working for employees whose primary work PC is licensed with SA to enable access to the virtual desktop when working outside of the office (whether at home or 3rd part premises).

Microsoft included Windows To Go as a benefit for a licensed device with SA, but also extended this to enable remote access to the corporate desktop  when working from a personal device at home or off-site; the “primary user” of a Windows 8 device licensed device with active Software Assurance (SA) can now access their corporate desktop through either VDI in the datacenter or Windows To Go via USB.

Ownership Device Type
3rd Party Owned: Non-x86
x86
Windows RT
Personally Owned: Non-x86
x86
Windows RT

Windows Companion Subscription Licence (CSL)

  • When a Primary device is covered with either Windows 8 Pro with SA or VDA Subscription is also licensed with the separate Windows Companion Subscription License (CSL), Virtual Desktop Access (VDA) access rights are extended for “primary user of the licensed device” for up to 4 companion devices.
    • Devices eligible for CSL include any type of personally owned device as well as corporate owned non-x86/x64 devices. This supports BYOD and Microsoft have incorporated this into the product licensing model.

image

The Windows Companion Subscription License (CSL) enables BYOCD (Bring Your Own Companion Device) scenarios and provides businesses with more flexibility to run Windows OS across various form factors.

Under Windows 7, Users that wanted access the corporate desktop remotely from their personal iPad could leverage Windows Roaming Rights under their organisations Volume Agreement with active Windows SA. However, should a user bring that device into the office and access Windows (VDI) from within the corporate firewall, the product licensing model would require an additional VDA Subscription. This was hard to track and not easy to explain.

Under Windows 8, Users that have a “Primary Device” licensed under a Volume Agreement with Windows SA can access Windows on or off premise on up to 4 devices via a Companion Subscription Licence (CSL)

The Windows CSL is an optional add-on for the primary user of an SA licensed device, and grants the rights to access a corporate desktop through VDI or Windows To Go on up to four companion devices.

Ownership Device Type
Corporate Owned: Non-x86
Personally Owned: x86
Windows RT
Non-x86

CSL could be more cost effective for users with multiple devices and would cost less than licensing a single device under Windows VDA.

It could also be viewed  as an approach to monetise the lost revenue from personal iPads and ensure 3rd Party devices are counted, tracked and recognised in Microsoft corporate volume purchasing contracts.


Windows Surface (RT) Companion VDA Rights

Microsoft have incentivised the take-up of Windows RT devices by allowing the “Primary User of the licensed device” to access their windows desktop through a VDI from a corporate owned Windows RT device.

Technology has influenced how people stay connected not just from their work PC but also from secondary, or what Microsoft have termed “companion devices” such as tablets. Microsoft have bolstered SA for Windows to enable these companion devices with more flexibility for how employees can access their corporate desktop (VDI) from these devices.

With Windows 8, the primary user of a device licensed with SA for Windows may access a corporate VDI from a company owned companion Windows RT device without having to acquire a separate Windows VDA subscription, encouraging corporate customers to move to Microsoft slate devices.

image

  • This encourages corporate owned slate devices such as iPad will need a CSL license If the user brings the device into the office to access Windows in a VDI Environment
  • If the organisation supports BYOD (Bring Your Own Device) it will encourage take-up of a corporate owned Windows RT device
    • Windows RT Companion VDA Rights strongly supports the procurement of Windows 8 Pro with Software Assurance (SA) and the renewal of active Volume Agreements with Software Assurance coverage for Windows.

Session Virtualization

This was originally Terminal Services and is used by several million users. Microsoft combined with Citrix have a pre-dominant share of the market. Microsoft have now named this Remote Desktop Services(RDS). This comes as part of Windows Server 2012

Session virtualization isolates the processing of the operating system and applications from the graphics and the Input and Output devices (keyboard and mouse). Once isolated, session virtualization sends the graphics from a central server and application out to an accessing device where the end user sees the display in real time. It is just as if the user were watching a live feed. However, session virtualization also captures the keyboard and mouse events of the remote user and replays them on the central datacenter.

Server Virtualization Graphic 3

This allows a user to instantly interact with the remote system. This design makes the user feel like the OS and application are actually running on the device in front of them, even though the application is sourced from a central datacenter.

This has real benefits in security with better security having all data stored and managed centrally. In this scenario, there is one shared copy of the software on the server, and this also has cost savings for patching and updates. Also, with data security and privacy concerns, having a central database provides a layer of security, by ensuring copies of the main database never leave the datacenter.

In Session Virtualization (Remote Desktop Services) users access a Windows Server OS hosting their application – In VDI, a Windows desktop hosts the application.

  • In Session Virtualization, only one copy of the OS is run on the hardware, and multiple users share that OS to run the application.
  • In VDI, each user is assigned their own complete OS, which is then used to host whatever apps the user needs

The VM is then copied to a server farm in a data centre, with each server in the farm running dozens of desktop VMs. Of course, a desktop OS is intended to be used with end users, so these virtual desktops are then accessed remotely by the end users using the same remote access technology we just talked about on the session virtualization (Remote Desktop Services)

This means that on average, VDI is more flexible and customizable than session virtualization. It is also less effective and could be more expensive to implement. In fact, due to the above mentioned product licensing requirements, VDI can be a lot more expensive than session virtualization for most customers.

As recommended by the Windows Steam Blog here is the approach to get started:

  1. Install the Remote Desktop session Host (RDSH) role service and configure RD Licensing role service and configure license settings.
  2. Install programs on the RD Session Host server and configure the client experience
  3. Configure users that will remotely connect to the RD Session Host server
  4. Expand deployment by configuring RDSH server farms and consider adding partner solutions such as Citrix XenApp
Technical Resources
  1. Windows Server 2008 R2 Remote Desktop Services Infrastructure Planning and Design Guide.
  2. Remote Desktop Services Deployment Guide

[Ref: TechNet]

In terms of licensing implications, because devices access a Windows Server operating system, they do not need any additional licensing for the Windows desktop operating system. However, the devices/users need to be licensed for the session technology (such as Windows Server CALs and Remote Desktop Services [RDS] CALs).


Acquiring Software Assurance for Windows

There are several ways to cover your Windows 8 Pro licenses with Software Assurance for Windows:

  • When purchasing a Windows 8 Pro Upgrade license through Volume Licensing, you may also acquire Software Assurance for that license.
  • Software Assurance is automatically included in certain Volume Licensing programs such as Enterprise Agreement (EA), Enterprise Subscription Agreement (EAS), Open Value (OV), Open Value Subscription (OVS), and Enrolment for Education Solutions (EES)
  • For new PCs with Windows 8 Pro preinstalled by the OEM, you can purchase Software Assurance for Windows through the Open License, or Select Plus programs within 90 days of the PC purchase.

image

[Ref: Windows 8 Licensing Guide, September 2012]


Conclusion

Microsoft have enabled full productivity from a range of devices and provided options in the way your users access their data and their desktop and their applications. How you approach this in your organisation will have to be considered and hopefully the range of links and content within this article will assist you.

Your licensing requirements will be dependent on what you want your users to access on your network and the functionality and experience you want them to have, Microsoft have updated and incorporated a number of access and device scenarios to support your requirements for access to Windows in a VDI.

Licensing can be complex, so always refer to as many dependable resources as possible, whether the Microsoft website, the Product Use Rights and Product List or your preferred Large Account Reseller (LAR).

One take away from this article is that 3rd party vendor solutions for Virtualization rarely provide you with the licensing implications and costs to provide Microsoft products over their technologies.

Microsoft have also strongly incentivised commitment to Subscription and Maintenance procurement models via Software Assurance (SA). So it is worth doing your research and understanding the total cost of ownership.


Please be aware that I now work at a Microsoft Partner  and will now be providing my licensing expertise through their licensing services . So please do get in contact with me directly if you would like to have a bespoke review for your organisation (available to organisations with UK operations).

Our specialist team can assist you to purchase the correct licenses, at the best price, through the right program.  Please email my directly to arrange a meeting or call.

– Tony Mackelworth


Disclaimer

This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. This document does not provide you with any legal rights to any intellectual property in any Microsoft product.

Please be aware that nothing on this website constitutes specific technical advice. Some of the material on this website may have been prepared some time ago and therefore may have been superseded. Specialist advice should be taken in relation to specific circumstances.

The contents of this website are for general information purposes only. Whilst the author(s) endeavour to ensure that the information on this website is correct, no warranty, express or implied, is given as to its accuracy and the primary author and website owner or it’s contributing Authors do not accept any liability for error or omission.

The contributing authors and owner of the website shall not be liable for any damage (including, without limitation, damage for loss of business or loss of profits) arising in contract, tort or otherwise from the use of, or inability to use, this website or any material contained in it, or from any action or decision taken as a result of using this website or any such material.

Windows Server 2012– Licensing Update

Microsoft will re-align Windows Server 2012 across two main editions, namely Datacenter and Standard Edition.

Microsoft will continue to adopt a “per server” license model, however a single licence will support a maximum of two physical processors.

Microsoft continue to provide advantageous software use rights for customers that purchase ‘premium’ SKUs. Windows Server Standard and Datacenter editions provide the same set of features; the only differentiation will be the number of Virtual Machines (VMs) that can be run on the licensed server.

  • Windows Server Standard Edition will allow a limited number of 2 VMs to run on up to two processors.
  • Windows Server Datacenter Edition will allow an Unlimited number of VMs to run on up to two processors.

Microsoft have now standardised the product features across the SKUs and have aligned the licensing model with System Center with a consolidation of Editions down to Datacenter and Standard; adoption of a Per Server licensing model aligned to a maximum of two processors.

Microsoft have maintained the CAL (Client Access License) model as a requirement for access to Windows Server 2012.


The advantage to Windows Server Standard customer is the increased level of functionality assigned to the SKU. This includes but is not limited to:

  • Windows Server Failover Clustering
  • BranchCache Hosted Cache Server
  • Active Directory Federated Services
  • Additional Active Directory Certificate Services
  • Distributed File Services (support for more than 1 DFS root)
  • DFS-R Cross-File Replication

Determining which Edition of Windows Server is Most Cost-effective

The most cost-effective edition of Windows Server for your virtualization needs depends on the specifics of your organisation’s environment. This can also be impacted by existing license and maintenance (SA) footprint and the chosen volume agreement that windows server is procured through.

  • Standard is the most cost-effective if you want to run a limited number of up to two VMs on the Server on up to two processors.
  • Datacenter is most cost-effective for running a moderately or highly virtualized environment. The flexibility gained from “unlimited” virtualization rights will limit exposure to non-compliance and provide easier license management.

image

There are several approaches to product licensing for Windows Server.

  1. Procure Windows Server Standard Edition for a limited virtual environment and then “stack” additional license(s) by assigning them to the physical server. 
  2. Microsoft incentivise procurement of the license with  Software Assurance (SA) by providing an ‘upgrade path’ to Windows Server Datacenter: Microsoft provide the “Step Up” SKU to allow migration to the ‘premium’ licensing model.
  3. It is recommended you engage with a software licensing expert to review and plan your procurement requirements to understand the optimum procurement model for your organisation.
  4. This can also be impacted by existing license and maintenance (SA) footprint and the chosen volume agreement

The optimum licensing vehicle for Windows Server will be dependent on the level of virtualization in the customer datacentre. If your organisation is looking at high availability and continuity and other benefits commonly associated with Virtualization (Whether VMware or Microsoft Hyper-V), then the ‘Premium’ Edition of Windows Server will support a higher number of Virtual OSEs.

imageA Licensing Specialist will often state that the “optimum” licensing model is always dependent on the specifics of the organisation and ultimately that specific “Tipping Point” for that customers’ environment, including but not limited to, access to the most cost-effective Volume Agreement.

It is therefore important not to make decisions about procurement ‘in silo’ without a wider review of the existing environment and vendor contract agreement framework. There will be server licensing considerations both pre and post consolidation and it should acknowledge the impact of v-Motion running across the estate.

The advantages of a holistic approach should not be disregarded. While the cost may be higher than your initial estimated costs for the project, but over a longer period it could deliver cost savings through leveraging economies of scale through procurement on the most appropriate Volume Agreement(s) and secure against unanticipated costs from non-compliance following a vendor review (Microsoft) or independent organisation (BSA or FAST).


Software Downgrade and Licensing Implications

  • Please be aware that all of the processors on a single server must be licensed with the same version and edition of Windows Server.
  • Microsoft allow a user to run previous versions and editions of Windows Server software as guest VMs, but do not allow assignment of multiple licenses of different versions or editions to the same physical server.

Microsoft will support downgrade of Windows Server software (the “bits”). A customer with Windows Server Datacenter 2012 will be able to install any prior version of edition. A customer with Windows Server Standard Edition 2012 will  be able to install any prior version of Standard and Enterprise Edition.

“The ability to run downgrade bits does not change the licensing or support terms in which you can use the product; the purchased product (Windows Server 2012) rights apply. This means that the license will continue to cover two physical processors and the virtualization rights do not change.” [Ref: Windows Server 2012 Licensing & Pricing FAQ]

image

[Diagram Ref: Windows Server 2012 Licensing & Pricing FAQ] – As always please refer to the  Product Use Rights and Product List 


Software Assurance Migration

A principle benefit of maintaining active Software Assurance (SA) on existing license footprint is that Microsoft usually adopt a considered approach to license migration and software use grants upon release of a new product. It is important that a customer seeks specialist advice to ensure they are aware of the licensing impact to their environment and are planning their procurement appropriately.

Upon release of Windows Server 2012, a customer with ‘active’ Software Assurance (SA) will receive use rights to 2012.

Please be aware that the licence will not be updated to the new release in VLSC unless Software Assurance (SA) is subsequently renewed at expiration. A customer will continue to have a perpetual right to the latest version, but this will only be evident upon review of the Software Assurance (SA) coverage period.

If a customer has committed to ‘active’ Software Assurance for Windows Server Enterprise 2008 R2 upon General Availability (GA) they will be entitled to receive two Standard edition licenses for each Enterprise edition license (1:2).

A customer with a current or planned highly virtualized or private cloud environment should consider taking advantage of the Software Assurance Step-Up* benefit to upgrade to Datacenter edition prior to the Windows Server 2012 General Availability since the Step-Ups from Enterprise edition to Datacenter edition will be removed from the price lists at that time.

A customer with an active Enterprise Agreement (EA) or aligned specialist enrolment with the Enterprise to Datacenter “Step Up” SKU enshrined within the CPS (Channel Price Sheet) will be able to leverage this SKU until the end of the contract term.

If a customer has active Software Assurance for Windows Server Datacenter 2008 R2 upon General Availability (GA) they will be entitled to Windows Server 2012 Datacenter.

Under the current licensing model, Datacenter license can be assigned to one processor. A Windows Server 2012 Datacenter license can be assigned to a physical server with up to two processors. Accordingly, Microsoft have adjusted the license grant: A customer with two current Datacenter licenses with Software Assurance (SA) will receive one Windows Server 2012 Datacenter server license (2:1).

If a customer has active Software Assurance for Windows Server Standard Edition 2008 R2 upon General Availability (GA) they will be entitled to one Windows Server Standard Edition license (1:1).

If a customer has active Software Assurance for Windows Server Web Edition 2008 R2 upon General Availability (GA); they  will receive an additional Windows Server 2012 Standard edition license that you can use while also maintaining your rights to run your current Web Server license.

The Microsoft license grant states that for two Windows 2008 R2 Web Server Edition licenses, a customer will receive one Windows Server 2012 Standard Edition license. If a customer retains an odd number of Windows 2008 R2 Web Server edition licenses, their grant will be based on rounding up to the next whole even number (2:1)

Microsoft have stated that a customer can continue to have the ability to host web content under the new Windows Server 2012 Standard edition license without needing a Windows Server CAL to access the server, but any other workloads that are run on the new server will follow the standard Windows Sever CAL model.

image

As always please refer to the Product Use Rights and Product List and your relevant Volume Agreement(s) and specific contract amendments. This is for information purposes only.


Implications of Microsoft’s acknowledgement of underlying hardware profiles (i.e. processors)

In some circumstances, moving to a new licensing metric that identifies the hardware profile (i.e. physical processors) can lead to non-compliance under the new schema. Microsoft, as the vendor, cannot apply a licensing model that retrospectively makes customers non-compliant. Accordingly, Microsoft have taken a similar approach to the release of SQL 2012 and asked customer’s to document their environment.

It is recommended that you complete your self-assessment using the Microsoft Assessment and Planning (MAP) Toolkit or another inventory tool that can accurately archive a time/date-stamped inventory of your hardware with Windows Server installations.

Upon contract expiration, the customer has the option to renew Software Assurance on all licenses granted as a result of transitioning to the Windows Server 2012 licensing model. So please be aware that while there might not be a sudden increase in maintenance costs, there might be a deferred increase that will become active upon contract renewal.

Secondly, as VLSC and other online databases of Volume Licenses available to Microsoft will not record this license grant for subsequent maintenance (SA) renewal, it is recommended to keep a solid record of the time/date stamped inventory and the specific license grant you are leveraging. (You cannot rely on your future staff or all individuals who work in the Microsoft ecosystem to have a holistic knowledge of historical license grants).

As discussed, it is recommended to take specialist advice prior to any major new release (i.e. SQL 2012, System Center 2012, Windows Server 2012, Office 2013, Windows 8).


Enrolment for Core Infrastructure

The Enrolment for Core Infrastructure (ECI) is a 3 Year Volume Agreement contract that can be used primarily for purchase of Windows Server with the full management capabilities of System Center 2012.

The Volume Agreement offers an incentivised price-point for customers who choose to use Enrolment for Core Infrastructure (ECI) as their primary procurement route for their deployed server footprint (and future requirements) for Windows Server over the contract term.

The advantage of the Enrolment for Core Infrastructure (ECI) as a procurement route is primarily the opportunity to buy the 2012 System Center and Windows Server product stack with Software Assurance (SA) within a incentivised procurement model.

The advantage of the Enrolment for Core Infrastructure (ECI) is that the overall cost of procurement is essentially ‘discounted’ by Microsoft within this program to incentivise standardised procurement through this model.

This Volume Agreement is intended to provide full Software Assurance (SA) coverage for the assigned footprint for the contract term. This provides Software Assurance Benefits (SAB) and important Software Use Rights by adding maintenance (Software Assurance) within a relational annuity agreement.

It is recommended you engage with a software licensing expert to review and plan your procurement requirements to understand the optimum procurement model for your organisation.


Recommendations

All customers should continue to do a self-inventory, documenting the number of processors in each server in use with System Center and Windows Server. This will enable customers to receive the appropriate number of server licenses mapped to physical processors.

  • Customers can approach a self-inventory using the Microsoft Assessment and Planning (MAP) Toolkit or other inventory tools and processes to accurately archive a time/date stamped inventory of hardware tied to System Center and Windows Server deployments.
  • Customer can also work with a Microsoft Partner to understand the current managed estate and plan for current and future requirements.

Please be aware that I now work at a Microsoft Partner – and will now be providing my licensing expertise through their services. So please do get in contact with me directly if you would like to have a bespoke review for your organisation (available to organisations with UK operations).

My team can assist you to purchase the correct licenses, at the best price, through the right program. Please email me directly to arrange a meeting or call.

– Tony Mackelworth


Disclaimer

This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. This document does not provide you with any legal rights to any intellectual property in any Microsoft product.

Please be aware that nothing on this website constitutes specific technical advice. Some of the material on this website may have been prepared some time ago and therefore may have been superseded. Specialist advice should be taken in relation to specific circumstances.

The contents of this website are for general information purposes only. Whilst the author(s) endeavour to ensure that the information on this website is correct, no warranty, express or implied, is given as to its accuracy and the primary author and website owner or it’s contributing Authors do not accept any liability for error or omission.

The contributing authors and owner of the website shall not be liable for any damage (including, without limitation, damage for loss of business or loss of profits) arising in contract, tort or otherwise from the use of, or inability to use, this website or any material contained in it, or from any action or decision taken as a result of using this website or any such material.

This Disclaimer is not intended to and does not create any contractual or other legal rights. This website is not run by Microsoft or my employer and the opinions are the author’s own.


SQL Server 2012–Licensing Update


On November 3rd 2011, Microsoft announced both the release and licensing changes aligned to SQL Server 2012.

Microsoft re-aligned the functionality of the SQL 2012 across three main editions, namely Enterprise, Business Intelligence and Standard Edition. Furthermore, It also aligned the licensing across those three editions.

  • Enterprise – Mission critical applications and data warehousing
  • Business Intelligence – Premium corporate and self-service Business Intelligence (BI)
  • Standard – Basic database capabilities, reporting and analytics.

As part of that realignment of functionality, Microsoft will consolidate and therefore remove the following:

  • Datacenter – features will now be available in Enterprise Edition
  • Workgroup – features will be available in Standard Edition.
  • Standard for Small Business – features will be available in Standard Edition.image

Web Edition – Available via Services Provider License Agreement (SLPA)

In addition, non-commercial releases of SQL will continue:-

  • Developer, Express and Compact Editions will also continue to be distributed without licensing or pricing changes.

Licensing Per Core

In response to evolution of the number of cores per physical processor and the future expected consolidation of the number of processors within optimised virtual server environments; Microsoft re-aligned the licensing model for SQL 2012 to remove ‘Per Processor’ as a commercial charging mechanism for their enterprise database software.image

In licensing by a per core licensing model, Microsoft have found a better way to align pricing to hardware capacity. In addition, cores provide a precise and flexible measure of capacity across both physical and virtual environment. This is intended to support both high mobility and hybrid environments.

Enterprise and Standard Editions will be available under core-based licensing. However, Microsoft will not extend the core model to the new Business Intelligence (BI) Edition.

Enterprise Edition will include the full capabilities of SQL Server 2012, so a customer who wants to license a Business Intelligence (BI) Server on a per core basis can do so by buying Enterprise Edition.

Enterprise Edition on a Per Core licensing model will be the preferred way to license advanced SQL Server BI capabilities when users are uncountable (For instance, external facing workloads) or when there is a very large number of users.


The New Core Licensing Model

Microsoft have built two licensing metrics for licensing SQL on a ‘Per Core’ model. This is intended to respond to both high mobility and highly virtualised server environments.

Licensing by Physical Hardware

The licensing requirement for licensing ‘Per Core’ will be to count the physical number of cores on the hardware. Microsoft have ensured there is a minimum requirement, with a minimum of 4 Core licenses per physical processor.

This licensing metric is only available to SQL Enterprise Edition.

Further, Microsoft have encouraged adoption of Software Assurance (SA) by allowing deployment of SQL instances in an unlimited number of VMs.

This can support customers who have a highly virtualized VMware Environment by ensuring the underlying physical hardware is licensed with SQL. Microsoft have continued to encourage the adoption of maintenance (Software Assurance) over stand-alone licenses by extending advantageous software use rights into SA.

If an organisation does not extend software use rights via procurement of SA, unlimited instances of SQL can be deployed in a limited number of VMs corresponding to the number of assigned core licenses to the physical hardware.

  • Customers who have licensed all the physical cores on the server and want to run SQL Server 2012 software
    in more VMs than are permitted, can assign additional core licenses to the licensed server.
  • Each additional core license allows deployment of SQL Server Licensing by Individual VMs

Licensing by Individual VMs

This is the alternative per core licensing metric, extended across both Standard and Enterprise Edition.

The licensing requirement for licensing Per Virtual Core will be to count the number of virtual cores per VM ( The number of threads of physical cores assigned to VM)

Additional licenses are required when:- A

  • A single hardware thread is supporting multiple virtual cores. (A core license is required for each v-core.) or;
  • Multiple hardware threads are supporting a single virtual core. (A core license allows a single v-core to be supported by a single hardware thread.)

[Ref: SQL Server 2012, Licensing Reference Guide, June Revision, Page 11]

Microsoft have stated a minimum requirement of 4 virtual Core licenses per VM.

As a further extension to the software use rights embodied within maintenance (and not the license) SQL Server licensed with Active Software Assurance (SA) will provide flexibility of License Mobility across both on-premise and cloud deployment scenarios (see below).


Cost Implications

Microsoft have modelled the price of a Core license at circa ¼ the cost of SQL Server 2008 R2 Processor License. Accordingly, Microsoft state that there would be limited impact on a physical processor with 1-4 cores. Notably, the impact going forward would be that as compute capacity increases so will the licensing requirement.

image

Please be aware that the net price impact to an individual customers will depend on both correctly licensing the existing SQL footprint and understanding current and planned capacity and functionality requirements. Working with only an excellent Microsoft Partner will support an optimum procurement model for your organisation.

image


Server and CAL Model

Server + CAL model, available with Business Intelligence (BI) and Standard Editions, is appropriate for business intelligence workloads and scenarios in which users can be counted accurately.

Server + CAL model would support a Business Intelligence (BI) solution as It would align to the number of devices using Office and SharePoint. This would have a defined number of accessing devices.

image

To access a licensed SQL Server, the SQL Server CAL should be the same version or newer.  For instance, a deployment of SQL Server 2008 R2 Server will need a SQL 2008 R2 CAL or SQL 2012 CAL.

Each SQL Server 2012 CAL can provide access to any SQL Server database, regardless of Platform or Edition. This includes all licensed SQL Servers, including the new Business Intelligence Edition as well as Standard Edition Servers and legacy Enterprise Edition Servers.

Notably, Microsoft previously announced that SQL Server 2012 CAL price will increase by about 27%. This was prior to the recent announced User CAL Price Increase.


License Mobility

License Mobility within the datacenter is supported by extended software use rights within Software Assurance (SA). This licensing model will support both private and public clouds.

VM license mobility will be a benefit of Active Software Assurance (SA).

  • All SQL Server licenses with active Software Assurance (SA) can be reassigned to another server within the server farm as often as needed.
  • However, Microsoft have imposed limitations to organisations with dispersed datacenters, so please check the time-zone definition. Further, the limitation is extended to deployment of SQL in a “non private” cloud infrastructure.
  • The 90 day minimum time limit for licence re-assignment is applicable to organisations that do not procure SQL with active Software Assurance (SA)

Without SA, licenses can be moved from one server to another only once every 90 days.

This is important distinction for customer who are using VMware v-Motion and are intending to virtualise SQL in their global datacenters. 


License Migrations – Server + CAL

Microsoft has stated that new server licenses for Enterprise Edition will only be available for purchase through 30th June 2012.

Customers on an ‘Active’ Enterprise Agreement (EA) with an Enrolment for Desktop /Enrolment for Application Platform (EAP) Enrolment  can continue to  buy server licenses until renewal of the Agreement after June 30, 2012.

SQL Server Enterprise Licenses purchased with Active Software Assurance (SA) will upgrade to SQL Server 2012 at no additional cost within the term of their Agreement.

Microsoft customers who have licensed SQL on the Server+CAL model, with Active Software Assurance (SA) will receive SQL 2012 under New Version Rights at no additional cost.

Microsoft have stated that the migration will be subject to a 20 core per server license maximum.  This applies to both net new requirement for SQL Server or existing footprint with Active Software Assurance (SA). In the event SQL Server Enterprise Edition on the Server + CAL model is running on a Server with greater than 20 physical cores, It is recommended that you work with your Microsoft Partner who will contact the  Licensing Sales Specialist within your local Microsoft subsidiary.

Moving forward, If your organisation has procured Enterprise Edition server licenses without Software Assurance can maintain existing SQL Server 2008 R2 Enterprise Edition Server licenses as legacy licensing for existing workloads.

it is strongly recommended to work with a Microsoft Licensing Expert with strong in-house SAM capabilities if you have a pending contract renewal for SQL Server.


License Migrations – Per Processor to Core Model

Customers with processor licenses under Active Software Assurance (SA) can upgrade to SQL Server 2012 at no additional cost*

At the end of the Software Assurance (SA) term, processor licenses will be exchanged for core licenses and customers can renew their Software Assurance (SA) on core licenses. This will maintain New Version Rights and License Mobility for Software Assurance to move Volume Licensing (VL) licensed applications to shared hardware clouds.

It is recommended that you review your SQL environment at the end of the Software Assurance (SA) Term. This will provide the basis for the core licenses you will own, and will confirm the requirements for renewal of Software Assurance (SA) going forward.

Microsoft will provide access to the Microsoft Assessment and Planning (MAP) Toolkit as one way to help track and document deployments. This tool can help you plan the transition from processor-based licenses to core-based licenses by counting both processors and cores across deployments. Microsoft are actively encouraging SQL customers to work with a Microsoft Licensing Expert to determine an optimal transition plan. This will include both review of existing physical and virtual deployments and mapping onto existing and planned SQL requirements going forward

Should the recommended inventory be performed, this should be recorded to demonstrate core license needs. Customers that do not maintain a record will receive a core equivalence for only the minimum number of core licenses – Important from a proof of licence perspective for future audits.

It is strongly recommended to work with a Microsoft Licensing Expert with strong in-house SAM capabilities if you have a pending contract renewal for SQL Server.


SQL Enterprise and Standard processor licenses under SA will be exchanged for a minimum of 4 core licenses per processor or for the actual number of cores in use.

  • SQL Server Datacenter processor licenses will be exchanged for a minimum of 8 Enterprise Edition core licenses per processor or for the actual number of cores in use.

image

Customers with an Active Enterprise Agreement (EA) or Active Enterprise Agreement Subscription (EAS) with a desktop Enrolment or an Active Enrolment for Application Platform (EAP) will be able to continue to purchase Enterprise Edition server and processor licenses until the end of the Agreement Term.

Customers with an Active Enterprise Agreement (EA) or Active Enterprise Agreement Subscription (EAS) with a desktop Enrolment or an Active Enrolment for Application Platform (EAP) can also add Core licenses mid-term and can engage via the Microsoft Reseller or Microsoft Account Team.

Please be aware that renewal of Software Assurance (SA)  will continue to attach pro-rated Deployment Planning Services and Technical Assistance in addition to advantageous extended software use rights and New Version Rights.

Again, It is recommend to work with Microsoft Licensing Expert to make sure these benefits are pro-actively managed and used to the benefit of your organisation. This should be quantified in terms of ‘real value’ to on-going contract(s) embedded within a defined process and SLA within your Added-Value Resellers management schema.


Final Thoughts

The most flexible approach is to license the complete physical hardware and ensure complete flexibility for running SQL in VMs in a high availability V-motion environment.

This does require a clear understanding of the overall cost implications before diving in, as the updated core licensing model could require increased investment as the number of cores if the hardware infrastructure exceed 4 cores.

While Microsoft aligned the cost of core licenses (sold in packs of 2) to align to 4 core processors (the minimum amount of licenses that can be bought); It is acknowledged that many customers have an existing investment in at least 6 cores.

Microsoft have provided appropriate license grants for existing customers who have procured SQL with maintenance (software assurance) who had multi-core servers licensed under the pre-existing “Per Processor” licensing metric. This has been provided  as a grant to ensure existing SQL footprint do not become retrospectively non-compliant. However, this does potentially increase the cost at renewal and should be reviewed.  

As discussed, Microsoft encourage the procurement of product licensing on relational contracts with maintenance (Software Assurance) and have moved beneficial software use rights away from the stand-alone perpetual licence. Accordingly, SQL virtualization strongly encourages the procurement of SQL with Software Assurance (SA) and this will enable an organisation to deploy SQL in a high mobility vMotion environment.

While not normally recommended, an organisation could potentially approach configuration of SQL to limit mobility within the virtual environment. This would require adherence to specific DRS Affinity rules to tie virtual machines to specific ESX hosts so that they cannot move from the assigned server except in the event of a host failure.

Please be aware that if there is a host failure a DB Admin would have to immediately adjust assigned rules to pin the VM the new host for a period of 90 days in order to stay in compliance (see 90 day rule above). As always, please refer closely to the authoritative documentation and your relevant procurement contracts before proceeding.  

CPU DRS Affinity rules for a virtual machine (VM) applies not only to all of the virtual CPUs associated with the VM, but also to all other threads associated with the VM; In some cases, such as intensive visual workloads, significant communication might occur between the virtual CPUs and other VM threads.

Accordingly, with correct controls in place, performance might degrade if the VM DRS Affinity rules setting prevent these additional threads from being scheduled concurrently with the VMs’ virtual CPUs

(For example, a Single Processor VM with affinity set to a single CPU)

As an example, VMware recommend that users include at least one additional physical CPU in the setting in order to allow at least one of the VMs’ threads to be scheduled at the same time as its virtual CPUs

(For example, a Single Processor VM with affinity to at least two CPUs)


For information purposes only, this could suffice as a potential approach to limit procurement of Software Assurance (SA) and still be able to virtualize SQL VMs (although this would really limit the main benefits of the virtualization of SQL in the first place).

As always, this website does not constitute specific advice on adherence to licensing rules, and as always It is recommended to work closely with a Licensing Expert to confirm the correct, optimised approach.

It is recommended that an organisation consider the full product licensing implications for their underlying hardware profile and any intended vMotion set-up if intending to virtualise SQL.

I am happy to arrange a meeting and set out a plan to optimise your product licensing and procurement contracts for your specific server infrastructure.

The Search for an Optimal Product Licensing Model for SQL

The overall TCO is dependent on the specific current and planned server strategy for each individual organisation.

The most comprehensive approach is licensing the physical hardware to support high virtualization across a VMware/Hyper-V Environment (Available for SQL Enterprise Edition)

  • This provides scalability and security in terms of compliance.
  • Maximum virtualization rights can be leveraged by licensing the entire physical hardware with Enterprise Edition under the “Per Core” licensing model with Software Assurance (SA)

imageThe “optimum” licensing model is always dependent on the specifics of the organisation and ultimately that specific “Tipping Point” for that customers’ environment, including but not limited to, access to the most cost-effective Volume Agreement.

It is therefore important not to make decisions about procurement ‘in silo’ without a wider review of the existing environment and vendor contract agreement framework. There will be server licensing considerations both pre and post consolidation and it should acknowledge the impact of v-Motion running across the estate.

The advantages of a holistic approach should not be disregarded. While the cost may be higher than your initial estimated costs for the project, but over a longer period it could deliver cost savings through leveraging economies of scale through procurement on the most appropriate Volume Agreement(s) and secure against unanticipated costs from non-compliance following a vendor review (Microsoft) or independent organisation (BSA or FAST) or Vendor Price Increases.

 


Please be aware that I now work at a Large Account Reseller and will now be providing my licensing expertise through their Licensing Services. So please do get in contact with me directly if you would like to have a bespoke review for your organisation.

My team can assist you to purchase the correct licenses, at the best price, through the right program. 

Please email me directly to arrange a meeting (or call) and we can have an open conversation around your plans going forward and any concerns you may have.

Tony.Mackelworth@Softwareone.com

– Tony Mackelworth


Disclaimer

This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. This document does not provide you with any legal rights to any intellectual property in any Microsoft product.

Please be aware that nothing on this website constitutes specific technical advice. Some of the material on this website may have been prepared some time ago and therefore may have been superseded. Specialist advice should be taken in relation to specific circumstances.

The contents of this website are for general information purposes only. Whilst the author(s) endeavour to ensure that the information on this website is correct, no warranty, express or implied, is given as to its accuracy and the primary author and website owner or it’s contributing Authors do not accept any liability for error or omission.

The contributing authors and owner of the website shall not be liable for any damage (including, without limitation, damage for loss of business or loss of profits) arising in contract, tort or otherwise from the use of, or inability to use, this website or any material contained in it, or from any action or decision taken as a result of using this website or any such material.

This Disclaimer is not intended to and does not create any contractual or other legal rights. This website is not run by Microsoft or my current or future employers, and the opinions are the author’s own.


System Center Management Suite, ECAL and VDI Suite – Component Overview Comparison

I recently came across some confusion out there about what is included, and what isn’t in System Center Management Suite Enterprise and Datacenter (SMSE / SMSD), so I have included a quick run down of what products are included, and what aren’t when you are looking at a end-to-end management solution.

The confusion on the Microsoft website is whether the Server licenses are included within the SMSE SMSD stack. The answer I am afraid is no, the Server Licenses for SCOM, SCCM and SCSM will need to be acquired separately. However, great news SCDPM and SCVMM Server Licenses are included.

“The reason for the confusion is because the “management server license” refers to the Server and the “server management license” refers to the Server ML”

The SMSE and SMSD stacks include the Server MLs – details from the website are below, including the direct link.

Microsoft System Center Website

Server Management Licenses

Server Management Suites Licensing

Customers increasingly require a comprehensive suite of management tools that provide end-to-end support for virtual and non-virtual server infrastructure. The server management suites provide an easy and economical way for customers to get server management licenses for the five main products of System Center—System Center Operations Manager 2007 R2, Configuration Manager 2007 R2, Data Protection Manager 2010, Virtual Machine Manager 2008 R2, and Service Manager 2010. Because the Suites include Virtual Machine Manager—Microsoft’s solution for managing a virtual environment—customers who are running or plan to run virtual infrastructure should consider acquiring one of the Suites. The current offerings are the System Center Server Management Suite Enterprise and the System Center Server Management Suite Datacenter. Both suites include the following specific components:

  • Enterprise server management licenses for:
    • System Center Operations Manager 2007 R2
    • System Center Configuration Manager 2007 R2
    • System Center Data Protection Manager 2010
    • System Center Virtual Machine Manager 2008 R2
    • System Center Service Manager 2010
  • The System Center Virtual Machine Manager 2008 and System Center Data Protection Manager Management Server licenses are included with the purchase of the Management Licenses for these products.
  • Management Server Licenses for System Center Operations Manager 2007 R2, System Center Configuration Manager 2007 R2, and System Center Service Manager 2010 must be purchased separately.
  • The Server Management Suite Enterprise (SMSE) provides rights to manage up to four (4) Virtual Operating System Environments (VOSEs) plus the Physical Operating System Environment (POSE) provided the POSE is limited to supporting the virtualization capability per license.
  • The Server Management Suite Datacenter provides rights to manage an unlimited number of operating system environments (OSEs) on a single physical server.
(Also reference the July 2010 Product List – Page 129 of 137)

Service Manager will now be a new component of both SMSE & SMSD when Service Manager is released. This will improve datacenter service availability and performance by integrating incident and problem management with operational tools. When Service Manager becomes available on general availability, customers licensed for the SMSE or SMSD will receive the Service Manager Server ML as part of their active Software Assurance (SA) coverage.

System Center 2 System Center 3

Opalis software was purchased by Microsoft at the back-end of 2009. Microsoft customers who have acquired SMSE or SMSD with active Software Assurance (SA) on or after December 10th, 2009 will receive an Opalis license grant. The corresponding licenses are as follows,

image

Price Increase

Microsoft have also announced that both the System Center SMSE and SMSD will have a price increase on August 1st 2010

[UPDATE] The SMSE price will increase by 30%, and the SMSD price will increase by 75%

Client Management Licenses

Now the second cause of confusion is once the Server MLs are looked after in the SMSE and SMSD packages, what about the Client end of the equation. The Client MLs can be bought as part of the ECAL suite on a Enterprise Desktop within an Enterprise Agreement, as below,

Microsoft Product List

Enterprise CAL Suite

clip_image001

The Microsoft CORE CAL Suite available provides rights equivalent to the following:

  • Microsoft Exchange Server 2010 Standard CAL
  • Microsoft SharePoint Server 2010 Standard CAL
  • Microsoft System Center Configuration Manager 2007 R2 Client Management Licence
  • Windows Server 2008 R2 Standard Operating System CAL

clip_image002

The Microsoft ENTERPRISE CAL Suite available provides rights equivalent to the following:

  • Microsoft Exchange Server 2010 Standard CAL
  • Microsoft Exchange Server 2010 Enterprise CAL
  • Microsoft Forefront Protection Suite Subscription Licence, which consists of the following Microsoft Online Services:-
  • Microsoft Forefront Client Security Subscription Licence
  • Microsoft Forefront Online Protection for Exchange Subscription Licence
  • Microsoft Forefront Protection 2010 for Exchange Server Subscription Licence
  • Microsoft Forefront Security for Office Communications Server Subscription Licence
  • Microsoft Forefront Threat Management Gateway Web Protection Service Subscription Licence
  • Microsoft Forefront Protection 2010 for Sharepoint Subscription Licence
  • Microsoft Forefront Unified Access Gateway 2010 CAL
  • Microsoft Office Communications Server 2007 R2 Enterprise Edition CAL
  • Microsoft Office Communications Server 2007 Standard Edition CAL
  • Microsoft Sharepoint Server 2010 Enterprise CAL
  • Microsoft Sharepoint Server 2010 Standard CAL
  • Microsoft System Center Client Management Suite Client Management Licence, which provides rights equivalent to the following:-
  • Microsoft System Center Operations Manager 2007 R2 Client Management Licence
  • Microsoft System Center Data Protection Manager 2010 Client Management Licence
  • Microsoft System Center Service Manager 2010 Client Management Licence
  • Microsoft System Center Configuration Manager 2007 R2 Client Management Licence
  • Windows Server 2008 R2 Standard CAL
  • Windows Server 2008 Rights Management Services CAL

Product List, Page 107 of 137

(highlights, links and Pictures added for emphasis)

Enterprise CAL Suite is versionless and product use rights are determined by the status of Enterprise CAL Suite Software Assurance coverage.  If coverage lapsed, access rights under perpetual licenses are determined based on the product use rights in effect prior to the lapse in coverage.  Rights associated with Online Services offerings expire upon lapse of Software Assurance coverage, whether or not the Enterprise CAL Suite is perpetual.  As of May 1, 2010, a license for the Enterprise CAL Suite with active Software Assurance coverage provides rights equivalent to the following: All of the current components of the Core CAL Suite, all of the current components of the Forefront Protection Suite*, Exchange Server 2010 Enterprise CAL, SharePoint Server 2010 Enterprise CAL, Office Communications Server 2007 R2 Standard CAL, Office Communications Server 2007 R2 Enterprise CAL, Windows Server 2008 Rights Management Services CAL, Forefront Unified Access Gateway 2010 CAL and all of the current components of the System Center Client Management Suite.  A license for the Enterprise CAL Suite is a single license that must be assigned to a single user or device.  As provided in their volume license agreement, customers cannot separate the rights under the Enterprise CAL Suite to permit two or more users or devices to access its different components at the same time.

Forefront Protection Suite

Forefront Protection Suite is versionless and product use rights are those in effect during the term of corresponding Enterprise CAL Suite Software Assurance coverage. A subscription to Forefront Protection Suite consists of the following online services: Forefront Client Security, Forefront for Office Communications Server (formerly Antigen for Instant Messaging), Forefront Online Protection for Exchange (formerly Exchange Hosted Filtering), Forefront Protection 2010 for Exchange Server, Forefront Threat Management Gateway Web Protection Service and Forefront Protection 2010 for SharePoint Server.

image

System Center Client Management Suite

System Center Client Management Suite is versionless and product use rights are those in effect during the term of corresponding Enterprise CAL Suite Software Assurance coverage. System Center Client Management Suite provides rights equivalent to the following: System Center Operations Manager Client Management License, System Center Data Protection Manager Client Management License, and System Center Service Manager Client Management License.

image

VDI Suite

This accounts for the RDS CALs and SCVMM CALs omitted from the ECAL Suite. However, this also covers the Server Management Licenses (SMLs) for SCOM and SCCM. Microsoft Desktop Optimization Pack (MDOP) can be also included in this suite, if you haven’t already acquired it with the Windows Upgrade VL on the EA.

  • Microsoft Virtual Desktop Infrastructure Standard Suite (VDI Standard Suite)

    Includes the core products and CALs required to enable and manage VDI, including:

  • Remote Desktop Services (RDS)–The RDS component of the VDI Suite is licensed solely for use in a VDI context, it does not provide a license to use session-based RDS resources.
  • Microsoft Desktop Optimization Pack (MDOP)–a collection of technologies that enable desktop virtualization and management, including App-V
  • System Center Virtual Machine Manager (SCVMM) Client Management License –provides centralized management of the Microsoft® Hyper-V™ -based virtualization components of the VDI host
  • System Center Configuration Manager (SCCM) Standard Server Management License –provides centralized configuration management of the (physical) VDI hosts of the VDI Suite. Note: Virtualization hosts with mixed VDI and server virtualization workloads cannot be licensed through the VDI Suite.
  • System Center Operations Manager (SCOM) Standard Server Management License –provides centralized monitoring and performance management of the physical VDI host of the VDI Suite. Note: Virtualization hosts with mixed VDI and server virtualization workloads cannot be licensed through the VDI Suite.
  • Microsoft Virtual Desktop Infrastructure Premium Suite (VDI Premium Suite)

    Includes all the components of the VDI Standard Suite, plus:

  • App-V for RDS–provides application-level virtualization for RDS sessions.
  • RDS–the RDS license is not use restricted to the VDI scenario only, but can also be used for session-based desktop and applications scenarios.

I hope this clears up some of the confusion on where the licensing suites fit together. Please be aware where some packages will grant perpetual rights and others are subscriptions. The Forefront Protection Suite is a subscription and co-terminates with the Enterprise Agreement (EA) the ECAL is acquired under. This can of course, be acquired independently of an Enterprise Agreement (EA). In addition, the VDI Suite is on a subscription model, so virtualization rights leveraged under the VDI Suite will end with the subscription.

In all circumstances, the best reference will be the Microsoft Agreement you have signed, the Product Use Rights and the Product List.

eAgreements for Open Value

eAgreements for Select, Select Plus, Enterprise Agreement, and Enterprise Subscription Agreement (also known as VLCM) was already launched in August 2009.

Microsoft will extend this on August 16, 2010 to include Open Value (OV) and Open Value Subscription (OVS) contracts.  The aim of this is to provide customer and partners with a uniform tool to work with Microsoft contracts.

Benefits
• One-click installation
• Intuitive user interface
• Simple way to track agreements from creation to activation
• Provides option of electronic or physical signature for customers

Business Impact
• Users may create agreements in the current eAgreements for OV/OVS (also known as eCM) until Close of Business December 31, 2010
• Customer signatures in eCM will be accepted through Close of Business February 25, 2011

Training
• Training videos on eAgreements registration and installation are available now on the Microsoft Partner Network (MPN) eAgreements page  and for internal use on the VL Portal. Additional materials, available in mid-July , will include training presentations, User Guide, and more Demonstration Videos.
o eAgreements: Registration and Installation by an Invited User (5:43 minutes)
o eAgreements: Registration and Installation by New Users in Current and New Organizations (8:43 minutes)
o eAgreements: Inviting Colleagues and Approving Access (5:23 minutes)

Hope you find this information of value

Roaming Use Rights 2010

When you are looking at Office, Visio and Project on a Terminal Services or Remote Desktop session, please be aware that the July 1st roaming use rights do not provide full roaming use inside the firewall.

  1. The single, primary user of the licensed device may at any one time,
  2. Remotely access the software running on your servers (For example, in your datacenter) from a qualifying 3rd party device , and
  3. Run the software in a virtual operating system environment on a qualifying 3rd party device party
  4. When the primary user is on your or your affiliates’ premises or working from home on a device regularly used for work, Roaming Use Rights are not applicable
  5. You may not run the software in the physical operating system environment on the qualifying 3rd party device under Roaming Use Rights

Supported

image

Not Supported

Roaming Use Not Supported

  1. Provided for information purposes only; consult July 2010 PUR for complete language
  2. A “qualifying 3rd party device” is a device that is owned and/or controlled by an entity other than you or your affiliates
  3. Roaming Use Rights require active Software Assurance
  4. Rights apply to the single, primary user of a licensed device

When the primary user is on your or your affiliates’ premises, Roaming Use Rights are not applicable.

You may not run the software in the physical operating system environment on the qualifying third party device under the Roaming Use Rights.  All use is subject to the limitation on the number of users in the General License Terms in the Desktop Operating Systems section and must be for work-related purposes.  The primary user’s right to use the software under the Roaming Use Rights terminates when the corresponding rights on the work device expire, there is a change in the primary user status or when the primary user leaves your organization.  At that time, you must ensure that that user is no longer using the software under Roaming Use Rights.