System Center 2012 Licensing Overview

I thought I would cover a little bit of info on the recent System Center licensing changes, as you all know, simplifying and demystifying licensing is a big part of our changes so expect to see more connection between the product changes and product licensing as we move towards easier ways for customers to buy and get cloud ready

System Center have continued licensing simplification with the reduction of their multi SKU line-up, providing 2 clear editions aligned to hybrid cloud management.  Let’s look at some key product and licensing changes with the availability of SC 2012.

What are the key SC 2012 Server Management licensing changes?

• Reduced SKU line-Up to 2 editions, DC and STD 2012
• Both editions contain the same capabilities/workloads, only difference is the number of Operating System Environments (OSEs) that you can manage per license.
• Licenses are only required for managed “endpoints”, no additional licenses are needed for management server software or the ‘SQL Server Technology’
• Licensing model is Processor-based, where each license covers up to 2 Processors
• Standalone Components are available as part of the integrated DC and STD licenses and are not available to be sold separately*

*See caveat under SC SKU Availability

How many Server MLs will you need to buy?

• Server MLs are required for managed devices that run server OSEs.
• Licenses are processor-based, with each license covering up to two physical processors.

For Datacenter Edition: The number of Server MLs required for each managed server is determined by the number of physical processors in the server.

For Standard Edition: The number of Server MLs required is either number of physical processors in the server or number of OSEs being managed (whichever is greater).

Examples:                                                                       DC Server MLs Req		STD Server MLs Req
One 1-processor, non-virtualized server	1	1
One 4-processor, non-virtualized server	2	2
One 2-processor server with 3 virtual OSEs	1	2**
One 4-processor server with 8 virtual OSEs	2	4**

**An exception to this rule is when the physical OSE on your server is being used solely to run hardware virtualization software, provide hardware virtualization services, and run software to manage and service OSEs on that device.

In that case, you only count the number of virtual OSEs you will manage on the server, divide that number by two, and round up to the nearest whole number.

What is the SC SKU availability in Volume Licensing?

On Feb 1^st 2012 L&SA offerings for existing pre 2012 versions of individual Server MLs and individual product management Server licenses were removed from the volume licensing pricelist.

After SC 2012 General Availability customers can still purchase licenses for previous versions of System Center Products, only as shown in the table below

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

What are the SC SA Migration Paths?

Customers with SC and active SA at time of general availability, will be entitled to the migration paths below, all extended detail can be found outlined in the April Product List, couple of things to point out as I have had a few conversations with folks to bring some extra clarity…..see takeaways below

* System Center 2012 Datacenter covers up to 2 processors per license whereas SMSD only covers 1 processor per license.

Takeaways:

• SA is built into the SC 2012 MLs, L&SA Only
• SC 2012 has 2 offerings, separated by virtualization rights only, STDand DC
• SC 2012 Datacenter covers up to 2 processors per license whereas SMSD only covered 1 processor per license.
• Server MLs may not be split across multiple 1-Proc servers
• SQL Server Technology is no longer a separate offering, a runtime version is in both SC 2012 STDand DC editions
• License stacking is permitted for SC 2012 STD Edition to increase number of OSEs being managed, be aware of breakeven, its approx. 2.5 Virtual OSEs per processor.
• Step-Up from SC 2012 STD to SC 2012 DC is permitted
• Server MLs can manage applications running on a public cloud infrastructure through License Mobility for SA

System Center 2012 licensing for client management has been updated as well.

For more information on both server and client management licensing changes, there is a great Licensing FAQ posted HERE for Partner and HERE for Customers

SQL Server 2012 – Pricing and Licensing Quick Look

Well, Thursday saw the official announce of the SQL Server 2012 Edition line-Up and Pricing/Licensing Changes, and even though I am “technically” on holiday ….it’s definitely worth covering the key changes to whet the appetite, see below, very quick overview………more info on http://www.microsoft.com/sqlserver/en/us/future-editions/sql2012-editions.aspx

For a more comprehensive look at Pricing/Licensing we are running PARTNER global Webast Series on SQL Server 2012– REGISTER your spot, begins on 7^th Nov through to 18^th Nov, 3 Topics over 4 TimeZones, with an opportunity to ask your questions directly to us……

SQL Server 2012 – Things to note:

We are simplifying the SKU Lineup

3 main SKUs – Standard, Business Intelligence (New, see below) and Enterprise = “Principal” SKU,

We still maintain the specialized and breadth SKUs (Express, Developer, Appliances, etc) 

 

 

 

 

 

 

 

 

 

 

Licensing Models offered

• Std offered in Server/CAL mode AND Per Core
• BI only Server/CAL
• EE only Per Core

New SKU – SQL Server 2012 BI Edition

Data Management and Analytics

 

 

 

 

 

 

 

 

 

SQL Server is moving from Proc to Cores

 

 

 

 

 

SQL EE in Server mode is retiring

• EE Server Licenses available until June 30th, 2012
• EA/EAP customers can purchase EE Servers through the end of term
• SQL Server 2012 EE Server licenses will have 20 core per server limit

SQL CAL Price Increase
Approx 27% dependent on VL agreement level

Next time…………SQL Server SA Migration and Virtualisation……….

Windows OS – OEM Reimaging Rights – Licensing and Techie Update

I thought it would be good to post this exchange on OEM Licensing as we have made some changes to the rules for our partners and also its a very common question that we get through the call centres, I have tried to give the complete picture, licensing and technology as they are so synergised these days its good to see the full story -

Let me start with what you can do with a Windows OEM License:
• You can work with an OEM to create an Custom Factory Image (CFI): the OEM can create an Image from their OEM toolkit and then use their Software Factory Integration service to install onto all your PCs at their factory prior to delivery. This type of reimaging service is available on most OEM business PCs and/or royalty OEMs – e.g. PCs installed with Windows 7 Professional.
• This can be done without any need for a Volume License for Windows.

If you also have a Volume License, there is more flexibility:
• The Volume License for Windows is an Upgrade License – for use on top of the OEM License (usually Windows Professional pre-installed).
• With a VL Windows License you can customize the image yourself or ask the OEM to customize to your specification. The OEM still supplies you with a PC that has the underlying OEM License attached to the PC (this is shown by the “Certificate of Authenticity” (COA) label on the back of a desktop PC or bottom of a laptop.
• Customers can take advantage of customizing Windows Enterprise Edition if they have Software Assurance – which offers more features than Windows Professional (such as disk drive encryption – BitLocker).
• Reimaging rights are granted to all Microsoft Volume Licensing (VL) customers as part of the license agreement(s), customers may reimage OEM Operating systems by using the media provided under their VL agreement, such as EA or Select Plus/Select.

You can reimage an OEM Operating system with VL bits as long as you meet the criteria set out in the brief attached – posted – HERE

Note that there are no reimaging rights for OEM Office unless there is Software Assurance on the PC.

In addition you can find good  Windows product licensing information on this section of Microsoft.com/licensing

Plus there is also a VL Brief regarding Windows re-imaging rights HERE, and a detailed technical/licensing whitepaper on the points above on HERE

Testing and Demo of SQL – MSDN, Technet or ISV?

 James left me a GREAT question on testing/eval/non-production solution options

 

This is a very helpful thread. I have a similar question that I wonder if you can help with. I produce a software product that has a SQL Enterprise database on the back end. When deployed in customer production environments the end customer buys the appropriate per CPU SQL Enterprise licences across all the servers on which the solution is deployed.What I would like to do is to be able to put a demonstration system in our partner’s labs that uses a SQL Developer Edition license instead. This will be so they can demonstrate and hopefully sell our (and by association, Microsoft’s) software to their end customers. This will NOT be in a production or live environment and will only be used to demonstrate the product.

Does this count as ‘demo’? If not – what would you suggest as a low cost licensing option for this scenario?

 

 

 

There are a number of options, so I want to cover off a couple below

 

The first thing to do is repost the MSDN v TechNet, this is a really good table, covering what you should use each offering for

  

  

Additional option!

 

If you plan to offer SQL as a unified solution, which it would seem is the case from the info provided J you could also become part of the ISV Program, as part of agreement terms, you would be permitted to provide to the end customer, under specific conditions, example outlined below, the SQL eval/testing/demo rights as part of that program

  

 

“Customer” above is in reference to the ISV partner signing the agreement, not “end customer” recieving the service

 

 

 

SQL Server 2008 R2 – Licensing, Changes, New editions

 

 

So a few weeks back I said that SQL Server 2008 R2 would have a new edition, with a new edition comes a revamp in the overall licensing

 

Couple of basic points before we begin, as a few emails have come through on this and a little bit of confusion

 

Note 1: SQL Server Standard and Enterprise 2008 R2 can be licensed in either Server/CAL mode or Per Processor mode your choice

Note 2: SQL Server Datacenter is offered in Per Processor mode only

 

I know that sometimes its easy to confuse license rights for the different modes, so let me cover that below, by mode/edition, then next post will concentrate on migration/transition for SA customers and next steps…..

 

In a nutshell

SQL Server 2008 R2 Datacenter is licensed Per Proc only, count and license all the physical procs in box = unlimited number of running instance of SQL Datacentre in any number of OS environments = unlimited virtualization, you also have the ability to move these instances in accordance with Server Application Mobility rights – discussed in a previous blog post and you can run Standard or Enterprise in place of DC in any OSE

 

SQL Server 2008 R2 Enterprise is licensed Per Proc or Per Server/CALs, Server Application Mobility Rights exist and are outlined in the PUR, you can run an instance of Standard in place of Enteprise in any of the OSEs – Yippeeeee!!!

 

SQL Server 2008 R2 Standard is licensed Per Proc or Per Server/CALs, currently no Server Application Mobility Rights

 

 

Now to the official – Info from the PUR below

 

Datacenter

 

SQL Server 2008 R2 Datacenter– Licensed in Per Processor Mode – License ALL Physical Procs

You must count and license all of the physical processors

You may run the server software in one physical and any number of virtual operating system environments without regard to the number of physical and virtual processors used.

You may run on the licensed server instances of Enterprise or Standard in place of Datacenter in any of the operating system environments.

 

Enterprise

 

SQL Server 2008 R2 Enterprise – Licensed in Per Processor Mode – 2 choices on counting licenses

Option 1:

If you license all of the physical processors on the licensed server

You may run any number of instances in up to four operating systems environments for each Enterprise license you assign to the server.

You may run on the licensed server instances of Standard in place of Enterprise in any of these operating system environments

 

Option 2

If you don’t want to license all the physical procs in the box, you can license on procs used, as below, to provide you proc count for Enterprise edition, remember for Standard or WG or Small business your only option is “procs used”

 

Under this option, the total number of software licenses required for a server equals the sum of the software licenses required under (A) and (B) below. 

(A)          To run instances of the server software in the physical operating system environment on a server, you need a software license for each physical processor that the physical operating system environment uses.

(B)          To run instances of the server software in virtual operating system environments on a server, you need a software license for each virtual processor¹ that each of those virtual operating system environments uses.  If a virtual operating system environment uses a fraction of a virtual processor, the fraction counts as a full virtual processor.

 

I covered a long time ago the counting process for SQL, this info is now in the April PUR, as below

 

A virtual processor is a processor in a virtual (or otherwise emulated) hardware system. 

Virtual operating system environments use virtual processors. 

Solely for licensing purposes, a virtual processor is considered to have the same number of threads and cores as each physical processor on the underlying physical hardware system. So, for any given virtual operating system environment on a server on which each physical processor provides X logical processors, the number of licenses required is the sum of a) and b) below:

a)      one license for every X logical processors that virtual operating system environment uses

b)      one license if the number of logical processors it uses is not a whole number multiple of X

 

“X,” as used above, equals the number of cores, or where relevant, the number of threads in each physical processor.

 

 

 

SQL Server 2008 R2 Enterprise – Licensed in Server/CAL Mode

You have the following right for each server to which you assign a software license. 

You may run, at any one time, any number of instances of the server software in up to four operating system environments (physical or virtual) on that server. 

You may run on the licensed server an instance of Standard in place of Enterprise in any of these operating system environments.

 

Standard

 

SQL Server 2008 R2 Standard – Licensed in Per Proc Mode – Based on Procs used as above

You may run, at any one time, any number of instances of the server software in physical and virtual operating system environments on the licensed server. 

However, the total number of physical and virtual processors used by those operating system environments cannot exceed the number of software licenses assigned to that server

 

 

SQL Server 2008 R2 Standard or Workgroup – Licensed in Server/CAL Mode

For each server software license you assign, you may run any number of instances of the server software in one physical or virtual operating system environment on the licensed server at a time.

 

 

Don’t forget, Fail-over rights still exist and have been extended from 2000 to now include Small Business, Workgroup and Standard

Enterprise has had fail-over rights for a long time

 

For SQL Server 2008 Small Business*, SQL Server 2008 R2 Enterprise, SQL Server 2008 R2 Standard* and SQL Server 2008 R2 Workgroup*:

Fail-over Rights.  For any operating system environment in which you run instances of the server software, you may run up to the same number of passive fail-over instances in a separate operating system environment for temporary support.  You may run the passive fail-over instances on a server other than the licensed server.

 

 

Note: SQL Datacentre is only available for servers with two or more processors, Customers may not run instances of the server software on a server with less than two processors

Note: You may not enroll more than 25 instances of any version or edition of SQL Server software with the Control Point Utility in the server software at any one time

LadyLicensing is back – More Focus

 

Well guys I have finally reached my USA destination and started my new role in World Wide Licensing, this role puts me at the heart of Program/Product Licensing readiness from a global prospective so in that respect its time for me to offer a clear focus on the blog

Firstly blog posts will continue and also “up to date” & “hot off the press” info will still be posted, but, I will also focus on the comments and requests I get directly from you guys and take those comments and that feedback to the people who make the changes , then make sure we do some clear signposting so you can find the content you need and at the right time, this will also be a major consideration for me

The first query I want to cover is from Sebastien and its a common one that most people ask for clarity on……………….

Edited for general consumption!

I’m working in a IT company and we recently hired a new employee.

We talked about licensing and I have a different understanding about CAL calculations.

Would you help me to win the bet-of-my-life ?

 

Here is the context:

A user needs to access 4 different Windows 2008 R2 servers within the our domain.

1x Standard edition, let’s say for an Active Directory server

2x Enterprise edition servers, setup as a cluster

1x Datacenter Edition, for an Hyper-V.

 

Do I need to Buy?

Answer A: 1 Windows server CAL

Answer B : 3 Windows Server CALs, one per Server edition

 

The answer is….

Windows Server CALs are just Windows CALs, they are not edition specific, so you cannot buy Windows DC CALs, they are only version specific.

You can use 1x Windows CAL xxx Version, licensed per User or per Device to connect to ANY server within you or your legal affiliates domain

The CAL needs to be equal or higher in Version to the Server it is accessing, so you cannot use a Windows 2003 CAL to access a Windows 2008 Server, but you can use a Windows 2008 Server CAL to access a Windows 2003 Server

 

Were to find this info on MS.Com

This info is posted within the PUR as below under “Servers”

Servers – Operating Systems – server license + CAL + optional external connector

First Look at SQL Server 2008 R2 SKU Line-Up and Licensing

 

SQL Server continues to meet the growing demands of enterprise workloads through two new premium editions: SQL Server Datacenter & SQL Server Parallel Data Warehouse

The new and expanded product line in SQL Server 2008 R2 delivers unprecedented value and functionality enabling massive scale at low TCO, improved Developer and IT efficiency and Self Service Business Intelligence.

 

SKU Line-Up

Licensing Changes:

SQL 2008 EE R2 will now provide up to 4 Virtual Machine Licenses, a change from SQL 2008 EE and SQL 2008 DC R2 will provide Unlimited Virtual Machine Licenses,

SQL now comes more in line with Windows Server 2008 R2 licensing, so think of Std = 1, EE=4 and DC= Unlimited

 

But what if you already have SQL EE and Software Assurance?

Well, we always have a complete transition/migration path for our SA customers, more details to follow nearer launch in the Product List

Does my Product need a Key and were do I get it?

 

I am getting more and more questions come through on Product Keys, were do I get them, what products need a key etc etc

First off, we should try not to confuse Volume Licensing Product Activation <only for Windows Vista, Windows 7 and Windows 2008> with Product Keys, VA 2.0 is a new initiative in VL and more info can be found HERE, VA 1.0 is used to install the product

So to start at the beginning

If you buy your product through OEM or FPP then it comes with a Key either on the side of the unit or on the DVD/CD, this is the key you use to install the product – be aware that OEMs will pre-install and normally pre-activate, if you need to re-install the product key is provided on the Certificate of Authenticity (COA) sticker on your PC

If you buy your product via any Volume Licensing Agreement, see FAQ list for more info, the need for a Key will come down to the actual Product itself, as an example, Office Pro Plus 2007 needs a VL Key, SQL 2005 does not

 

You can find a full list of Volume Licensing Products that require a VLK on HERE

Note: Not listed, then its Pre-PID on the media and no key is required

 

What to do if your product needs a key?

The Volume Licensing Keys <VLKs> are located on either VLSC or eOpen and called VA 1.0 or VA 2.0, the link you go to will depend on the agreement you purchased the products under, only Open Agreements go to eOpen, all other agreements to VLSC, the Keys are customer and agreement specific, so the keys belong to you and your legal affiliates and should not be shared with anyone outside of your organisation, you could be liable for misuse

Volume License Product Keys – VLSC
Product	License Key	Key Type
Visio Enterprise Network Tools	XXXXX-XXXXX-XXXXX-XXXXX	VA 1.0
Office 2000		VA 1.0
Office XP Suites		VA 1.0
Office 2003 Applications		VA 1.0
Windows Server 2008		VA 2.0
Windows 7 Professional		VA 2.0
Office 2003 Suites		VA 1.0
Office XP Applications		VA 1.0

 

The keys need to be used in conjunction with the correct VL Media, you can order this via a Partner, use the Welcome Kit or download via the VLSC/eOpen websites – this is sometimes were things go wrong, if you use the wrong media with the correct key you will get an error message

 

FAQs

How Do I Get a Volume License Key?

Program-specific instructions on how to obtain your VLK or OSK are available on the following Web pages:

•	Select / Select Plus and Enterprise customers
•	Open Value Subscription (OVS) customers
•	Open License customers
•	Campus and School Agreement customers
•	Application Service Provider customers
•	Independent Software Vendor customers
•	MSDN purchased under Select or Open License
•	All other Volume Licensing programs

Program-specific instructions on how to obtain your VLK or OSK are available on the following Web pages for customers who speak Russian, Ukrainian, and Simplified Chinese:

•	Russian and Ukrainian language Open License customers
•	Simplified Chinese language Open License customers
•	Russian and Ukrainian language Select customers
•	Russian and Ukrainian language OSL customers

 

What if I Can’t Find My Volume License or Online Services Keys?

If you are unable to obtain your VLK and OSK, call the Microsoft Activation Center for your country or region. You will need to provide your Volume License agreement information and proof of purchase when you call.

•	Customers in the UK                                      0800 0188 354
•	International customers: Find the telephone number for your country or region

Note These telephone numbers are for Volume License Keys only.

 

Exceptions

Essential Business Server and Small Business Server key info HERE

Introducing VDI Standard and Premium Suites – Overview and Licensing T&Cs

 

From Oct 1st, and in the Oct 1st PUR and Pricelist, we will offer 2 brand new VDI Suites, Standard and Premium

A little info on the Suites themselves and then to the Licensing

Customers can now buy different components of the server and management infrastructure required to run VDI through a single licensing vehicle.

This licensing vehicle has two SKUs: The VDI Standard Suite and VDI Premium Suite. Both suites complement the VECD license, by following the same device-based annual subscription pricing model, they do not replace the need for VECD*

The VDI Standard Suite is a collection of technology to help organizations deploy the basic infrastructure for VDI. Hyper-V Server 2008 R2 is the virtualization platform for hosting your servers and desktops. Management of your virtual infrastructure is taken care of the various system center components, including System Center Virtual Machine Manager, System Center Operations Manager 2007 R2 and System Center Configuration Manager 2007 R2. Applications can be delivered dynamically via App-V, since MDOP is also included in the VDI standard suite. The standard suite also enables restricted use rights for Remote Desktop Services, to deliver VDI desktops to users.

The VDI premium suite is for customers who want additional flexibility from their VDI environment. Remote Desktops Services is unrestricted, thereby enabling customers to deliver both session based desktops as well as VDI desktops. The VDI Premium Suite also includes App-V for RDS, thereby allowing organizations to deliver applications dynamically to the Remote Desktop Server, effectively reducing silos for RDS applications.

In addition to being simple to purchase, both SKUs provide customers with excellent value.

The standard suite retails at $21/device/year, whereas the premium SKU retails for $53/year**

 

VDI Suite Licensing

All the T&Cs for VDI Suite licensing are in the Oct 1st PUR – some edited highlights below

Each VDI Suite license permits:

1. use and access of VDI software on or from your VDI licensed device and other devices running permitted instances of VDI software and
2. management of virtual client OSEs on your VDI hosts.

VDI Standard Suite and VDI Premium Suite provide rights to use or access any version of the following VDI software during the term of your Select or Enterprise enrolment or Open Value agreement:

• Windows Server Remote Desktop Services (“RDS”)
• System Center Virtual Machine Manager (“VMM”)
• System Center Configuration Manager (“SCCM”)
• System Center Operations Manager (‘SCOM”)

Terms for VDI Suite License

You may directly or indirectly access RDS from your VDI licensed device except as follows. You may not access Windows Server software to host a graphical user interface (using RDS functionality or other technology) either:

• directly from your VDI licensed device or
• indirectly through a virtual OSE on your VDI host.

Despite anything to the contrary in the product use rights for Windows Server, you do not need an RDS CAL for either the VDI licensed device or the VDI host to permit this access. You must, however, acquire and assign a base Windows Server CAL to both devices or to the accessing user

 

Extended Terms for VDI Premium Suite ONLY:

Remote Desktop Services. In addition to the right to access RDS functionality from any device covered by a VDI Premium Suite, you may also access Windows Server for purposes of hosting a graphical user interface. The requirement to have a separate Windows Server CAL still applies.

Application Virtualization for Remote Desktop Services. You will be deemed to have acquired one Application Virtualization for Remote Desktop Services software license if you acquire a VDI Premium Suite license. You may use the software on your VDI host and access and use it from VDI licensed devices to which you have assigned VDI Premium Suite licenses. Despite anything to the contrary in the Product Use Rights for Application Virtualization for Remote Desktop Services you do not need a Application Virtualization for Remote Desktop Services CAL to access the Application Virtualization for Remote Desktop Services software. The requirement to have a separate Windows Server CAL still applies.

Reassignment of VDI suite licenses. Despite the limitation in the product use rights, you may reassign your license, but not on a short-term basis (i.e., not within 90 days of the last assignment). You may reassign your license sooner if you retire the VDI licensed device due to permanent hardware failure.

 

Notes:

Definitions.

• “Client OSE” is an operating system environment (“OSE”) running a client operating system.
• “VDI licensed device” is a device to which you assign a VDI suite license and from which you access and remotely use virtual client OSEs.
• “VDI host” is a device on which you host virtual client OSEs running software you access and remotely use from VDI licensed devices.
• “VDI suite license” means the VDI Standard Suite license or the VDI Premium Suite license or both.
• “VDI software” is the Microsoft software for which you are granted use, access or management rights under the “VDI suite license”).

Note: You may assign VDI suite licenses only to devices. You may not assign VDI suite licenses to users.

Note: VDI suite licenses are subscription licenses. The right to use software under a subscription license expires upon expiration or termination of the enrolment or agreement under which you acquired the license.

*Note: VECD is required as well as VDI Suite Std or Premium if you want Windows XP Pro, Vista or 7 in a VDI environment you need VECD subscription per Device also

** Pricing is always a guide, contact your MS reseller

Changes to Windows Terminal Services Licensing and App V for TS – Introducing Remote Desktop Services CAL

 

With the launch of Windows Server 2008 R2 we will re-name Windows 2008 TS CAL to Windows 2008 RDS CAL

We also have a new transition plan for customers currently on App V for TS 4.5 CALs with SA to move to the new Win Server Remote Desktop Services CAL with SA

As below!

Windows Server 2008 Remote Desktop Services CAL/EC grant for Application Virtualization for Terminal Services CAL/EC customers

For every four Application Virtualization for Terminal Services CALs they have acquired with active Software Assurance coverage as of September 1^st 2009, customers will be granted one Windows Server 2008 Remote Desktop Services CAL with software assurance. Similarly, for every four Application Virtualization for Terminal Services External Connector licenses they have acquired with active Software Assurance coverage as of September 1^st 2009, customers will be granted one Windows Server 2008 Remote Desktop Services External Connector license with software assurance. Customers must choose to use the software under either the qualifying Application Virtualization for Terminal Services licenses or the complimentary Remote Desktop Services licenses. They cannot use software under both the qualifying and complimentary licenses at the same time. Use of the software under the Remote Desktop Services licenses is subject to the product use rights for the software being accessed and used. A customer’s right to use software under the Remote Desktop Services licenses granted under this offer expires when that customer’s qualifying licenses expire or otherwise end. Enterprise Subscription, Open Value Subscription and Campus and School customers receive grant rights temporarily for the duration of their current annual subscription coverage period.  The grant does not apply to subsequent annual orders.  Buy-out options are available for the granted Remote Desktop Services licenses.

Use of Microsoft Application Virtualization 4.5 is governed by its Product Use Rights as modified by these license terms.

1. Instead of a Microsoft Application Virtualization 4.5 CAL for Terminal Services, you may acquire and assign a Windows Server 2008 Remote Desktop Services CAL or Windows Server 2008 Terminal Services CAL to any device or user that accesses your instances of Applications Virtualization for Terminal Services directly or indirectly.

2. Instead of a Microsoft Application Virtualization 4.5 External Connector for Terminal Services, you may acquire and assign a Windows Server 2008 Remote Desktop Services External Connector or Windows Server 2008 Terminal Services External Connector to any server in order to permit any number of external users to access that server’s instances of Applications Virtualization for Terminal Services directly or indirectly.

Note: Customers who purchased Application Virtualization for Terminal Services CALs or ECs, with Software Assurance between September 1^st 2009 and October 31^st 2009 are also eligible for this grant.