Sep 11, - Microsoft released the updating licensing details for WS R2 If you have Windows Server R2 Standard edition, you will have the. Feb 17, - The Windows Server licensing is simpler than in the past. The Windows Server Standard Edition will allow a limited number of 2 VMs to. Nov 12, - Microsoft Windows Server R2 comes with the availability of two primary editions – Standard and Datacenter. The versions are identical.
August 19, Tags: See notes in italics below. Although some volume licensing contracts may delay the change, customers might need to plan ahead to exploit current pricing. Also, starting in Jan. Windows Server R2 licenses will be generally available for sale in Nov. Customers who have SA on existing Windows Server licenses will be entitled to Windows Server R2 upgrades if SA is active the month the version becomes available for download. Licensing for Windows Server Largely Unchanged The transition from Windows Server R2 to Windows Server involved substantial changes to the product's licensing model, edition lineup, and pricing.
August 19, Tags: See notes in italics below. Although some volume licensing contracts may delay the change, customers might need to plan ahead to exploit current pricing. Also, starting in Jan. Windows Server R2 licenses will be generally available for sale in Nov. Customers who have SA on existing Windows Server licenses will be entitled to Windows Server R2 upgrades if SA is active the month the version becomes available for download.
Licensing for Windows Server Largely Unchanged The transition from Windows Server R2 to Windows Server involved substantial changes to the product's licensing model, edition lineup, and pricing. In contrast, with the exception of some pricing changes, licensing for Windows Server R2 remains almost identical to Windows Server Windows Server continues to use a two-tiered licensing model.
Server-side licenses provide the right to run one or more instances of Windows Server on server hardware, and three different types of CALs provide the right for users or end-user devices to access resources on the server.
Server-Side Licensing As with its predecessor, Windows Server R2 continues to be offered in two general purpose server editions for midsize and large organizations: Standard and Datacenter.
Both server editions use the same paired-processor licensing model. Regardless of edition, each license covers up to two physical processors on a single server the number of cores inside each processor is immaterial and each license can be assigned to one server only.
Licensing two servers, each with a single processor, requires a total of two licenses, and licensing a server that contains four processors requires two licenses. Both server editions include the same technical features and capabilities and differ only with respect to virtualization use rights.
The Datacenter edition license provides the right to run an unlimited number of virtual machines VMs on the licensed server, while each Standard edition license allows up to two Windows Server-based VMs.
Multiple Standard edition licenses can be assigned to a single server "stacking" to increase the number of simultaneous VMs allowed. While this has been the least expensive licensing approach for scenarios involving 10 or fewer simultaneous VMs, it can be more expensive overall when the administrative overhead associated with software license compliance checks is factored in.
During a compliance check, customers planning to assert that a server's virtualized Windows Server workloads are covered by stacking Standard edition licenses will likely be asked to demonstrate how the claim is supported. For example, the customer could show that technical constraints in place make it impossible for more than the licensed number of VMs to run simultaneously or that logs from the previous 90 days prove that the maximum number of licensed VMs was never exceeded.
Commonly used to prevent casual or inadvertent disclosure of Office documents and e-mail, RMS protection travels with content and thus can work even if the content is moved to a computer outside an organization's control. This will encourage some customers to accelerate license purchases. However, the options and timetable for obtaining the current lower prices depends on what type of volume licensing program the customer uses for purchases and the length of time remaining on the current contract.
Datacenter edition license. Prices, quoted in U. However, the first time SA is renewed after Nov. Prices for the following offerings will also go up with Datacenter: Starting Nov. For customers using Select and Open, accelerating Datacenter purchases could make sense in two scenarios. Customer intends to use Windows Server or earlier. Thus, customers with no plans to deploy Windows Server R2 could save by purchasing licenses sooner rather than later.
Customer wants SA coverage. A customer considering whether to buy a Datacenter license with SA just before Nov. However, if a customer is choosing between buying a license with SA today to get rights to Windows Server R2 and buying the license-only that is, without SA later under the new price, the license-only option is more cost-effective.
The timing of some actions is driven by the Windows Server R2 Nov. Before Nov. Unlike customers who use the Select and Open programs, customers who have EAs have the ability to lock in a price for the duration of an enrollment term. For example, the first time a customer purchases a Windows Server Datacenter license as an Additional Product under any of these enrollments, that license type is added to the customer's EA price sheet at the then-current price, even if the customer purchases only a single unit.
The price thereafter remains unchanged for subsequent purchases through the end of the EA enrollment. Before the end of the current EA enrollment term. When an EA enrollment is renewed, the customer's price sheet is updated to reflect the products available and associated prices as of the date of renewal. Currently, RDS CALs may be used only for session-based remote desktops that are deployed on on-premises servers, or on dedicated servers not shared with other customers of a third-party service provider.
By early , RDS CALs with active SA will also be valid for workloads running on shared multitenant servers of service providers although the VM running the workload must be for the exclusive use of the particular customer. Existing rule. Under current rules, the only way to license session-based remote desktops deployed on third-party shared servers is through the provider's Service Provider License Agreement SPLA.
Under the SPLA, service providers account for software used by customers and remit monthly payments to Microsoft. In this specific scenario, the provider has to pay two separate monthly fees to Microsoft: New rule. These CALs will license client access to the customer's session-based remote desktops running on the provider's shared servers. The ability to run such workloads on Windows Azure is a recent development: The Jan. With VDI, each user's desktop including the OS, applications, and user data executes in its own VM, hosted on a centrally managed server.
With the session-based remote desktop architecture, in contrast, all users' Windows desktop applications and desktops run on the same shared instance of Windows Server; Windows Server mimics the "look" of the Windows client OS, but no instances of the client OS actually run on the server.
Under current rules, VDI workloads may only be run on customers' on-premises hardware or on third-party service provider equipment that is dedicated to the particular customer. Running VDI workloads on a service provider's shared multitenant hardware is prohibited, and no changes to this rule have been announced. Resources Windows Server R2 pricing and licensing information is at download. Windows Server licensing briefs are posted at download.
Windows Server R2 licensing was covered in the Nov. Rules for reassigning server-side licenses from on-premises to third-party service providers are discussed in " Enterprise Cloud Licensing Rules Clarified " on page 22 of the Aug.