In the version, the only significant difference between the Standard and Enterprise products is the number of mailbox databases each edition allows. The Standard edition allows up to 5 mailbox databases, while the Enterprise edition allows up to Thus, you should request the Enterprise edition if your charity or organization is fairly large.
For more information, see the Licensing section below. Licensing Below are some of the major licensing requirements for Exchange Server. For each server software license you assign, you may run, at any one time, one instance of the server software in one physical or virtual operating system environment on the licensed server.
You may run or otherwise use any number of instances of the Exchange Management Tools software in physical or virtual operating system environments on any number of devices. You may use those instances only with the server software.
Use of any instance with the server software may be direct, indirect, or through other additional software. Exchange Server is a server application, not a server operating system, so it must be used along with a server operating system.
For each instance of Exchange Server, you must also have a Windows Server license. However, you do not need CALs for Up to two devices or users to access the server software only to administer those instances Any user or device that accesses your instances of the server software without being directly or indirectly authenticated by Active Directory Standard CALs For both the Standard and Enterprise editions of Exchange Server, the Standard device or user CALs authorize one user or device to access Exchange Server.
These features include integrated archiving, in-place hold, data loss prevention, and unified messaging features. For a complete list, see the Exchange Server Licensing page Enterprise CALs do not need to be requested for users or devices that do not need to access these additional features. You can use Software Assurance to upgrade Exchange Server and associated licenses to any version released during the two years your Software Assurance is in effect.
The actual upgrade does not have to take place within those two years. You can upgrade at any time in the future, as long as Microsoft still makes the new version available to users. You cannot, however, upgrade to versions that Microsoft releases after your Software Assurance expires.
Downgrading You can downgrade Exchange Server to any version that Microsoft continues to make available at its Volume Licensing Service Center website on your organization's Licensed Downloads page. Downgrading does not depend on Software Assurance; it is a benefit of Volume Licensing. CALs obtained through TechSoup will work with the downgraded version.
Customers who acquire a license for a particular product version and edition may deploy an earlier version or different edition in its place under certain circumstances. These licensing rules, called downgrade rights vary not only by sales channel where the license was purchased but also by the particular product line, including which specific version and edition was licensed.
Organizations that understand downgrade rights as well as other rules associated with product versions and editions can minimize risk by avoiding common license compliance issues and save money by averting unnecessary license purchases. How Offerings Are Categorized into Version and Edition Generally, when a customer licenses Microsoft software, the license is for a specific version and edition of the product.
Version A version is a major release of a software product, denoted by one of the following: Mistakes Can Lead to Noncompliance: Issues related to versions, editions, and downgrade rights are common sources of noncompliance.
The most common compliance problems tend to fall into three general categories: Minor updates to a particular product version—typically delivered in the form of patches, security updates, and service packs—are usually provided for free. However, the right to use new versions, regardless of whether they are acquired via perpetual or subscription licenses, involves a fee. Perpetual licenses, the most common license type, grant the purchaser the right to use a specific product version in perpetuity.
The latest version of a perpetual license can be acquired through purchase of a new license or by virtue of having active Software Assurance SA on a preexisting license as of the date a new version becomes available to volume licensing customers.
SA is an add-on to perpetual licenses that offers version-upgrade rights and other benefits in exchange for an annual fee based on the underlying license. If a new product version is licensed via a subscription rather than through a perpetual license, the subscription always includes rights to use the most recent version available, as long as the subscription is active.
Edition Microsoft commonly offers several variations of a product or product suite , called editions. Each edition offers a different collection of product features or use rights and is sold at various price points. When a new version of a product ships, all associated editions are usually released at the same time. Some editions of a product may be specific to a particular sales channel; for example, an edition might be available through volume licensing programs only.
Common names used for editions of client-side desktop applications or application suites are Standard, Professional, and Professional Plus. In the case of Office suites, the main differences between editions are which individual applications, such as Access and Outlook, are included and the presence of a few specialized server integration features, such as the ability to automatically archive Outlook data to Exchange Server.
Common names used for editions of server software are Standard, Enterprise, and Datacenter. What differentiates various editions of server products can vary widely depending on the particular product and product version, but common differences include technical features of interest to IT professionals rather than end users such as scalability, high-availability, and security capabilities , use rights associated with virtualization, and, occasionally, the licensing model.
Customers with active SA coverage on a lower-level edition license can exchange it for a higher-level edition license through the purchase of a Step-up License. The Step-up License fee is equal to the difference in edition license prices plus the difference in SA fees for the period remaining on the current, lower-edition SA term. In the absence of a step-up option, a new higher-edition license would have to be purchased in full.
Version Downgrade Rights Version downgrade rights entitle the owner of a product license to install and run an earlier version and equivalent edition of the same product in its place; for example, allowing a customer with a Windows 8 Pro license to use Windows 7 Professional instead.
By downgrading, a customer does not forfeit the right to switch to the licensed more recent version at some point in the future. Version downgrade rights are important because Microsoft typically stops selling a product version once a newer version becomes available; therefore, buying the latest license and exercising version downgrade rights is often the only option for licensing an expansion in deployment of a noncurrent version.
This is often important for maintaining standardized configurations. For example, today, a customer wanting to deploy a new server running Windows Server Standard edition would purchase Windows Server Standard edition the current version and exercise version downgrade rights.
Note that for products licensed under the CAL licensing model, if a customer downgrades the version of the server software, the CAL version need only match or exceed the running version, not the version of the server license. Volume Licensing Offers Greatest Flexibility The degree to which version downgrades are allowed depends on the distribution channel used to acquire the license.
Volume licensing. For licenses acquired through volume licensing programs, version downgrade rights generally provide the ability to substitute any previous version. OEM and retail. To remain compliant, the customer has a few options, including enhancing version downgrade rights by adding SA to new Windows 8 Pro PCs or purchasing new computers with Windows 7 Professional OEM licenses instead of Windows 8 Pro an option that should be available until at least mid Rules for other OEM licenses as well as retail licenses vary, with licenses for server software generally providing permissive version downgrade rights and licenses for client-side applications, such as Office Home and Business edition, providing no version downgrade rights at all.
However, volume licensing rules allow SA to be added to many types of OEM and retail licenses within 90 days from the date the licenses are acquired for example, to Windows Professional and Windows Server OEM licenses. Edition Downgrade Rights The edition downgrade use rights, sometimes referred to as down-edition rights or cross-edition rights, allow a customer to install and run a different generally lower-level edition than the one purchased.
They are commonly used in conjunction with version downgrade rights to allow a customer to deploy an earlier version of a different edition of the product. There are two major reasons why edition downgrade rights are occasionally provided. Edition eliminated. Since the company typically ceases sales of all editions of a product version once a newer version becomes available, buying the latest license and exercising edition downgrade rights combined with version downgrade rights is often the only option for licensing expanded use of an old edition.
For example, with the introduction of Windows Server , there is no longer an Enterprise edition; customers can run past versions of Enterprise edition such as Windows Server R2 Enterprise by acquiring Windows Server Standard or Datacenter edition licenses and exercising edition downgrade rights.
Simplify virtualization. The second major reason for providing edition downgrade rights is to simplify licensing for virtualization scenarios.
Often customers want to consolidate new as well as legacy server workloads by running multiple instances of a product on the same physical hardware, with each instance in its own virtual machine VM.
Higher-edition Windows Server and SQL Server product licenses or sets of licenses combine the right to run multiple instances of the software within VMs on the licensed hardware with edition downgrade rights so that customers do not need to be concerned with which particular edition is running within each VM.
Mistakes Can Lead to Noncompliance Issues related to versions, editions, and downgrade rights are common sources of noncompliance. Edition Mismatch The principal edition-related compliance error is to deploy a different edition than the one purchased.
The most egregious form of edition mismatch is to own a lower-level edition license but deploy a higher-level edition. Only very rarely do product use rights allow this the major exception being Windows Server Standard edition allowing customers to downgrade to the Enterprise edition of Windows Server R2 or earlier.
A common noncompliant scenario of this type involves deployment of Project Professional by a customer with licenses for Project Standard. If uncovered during an audit, the customer would have to purchase rights to Project Professional by buying licenses outright or, if the existing Project Standard edition licenses are covered under SA, by acquiring Step-Up Licenses.
The second form of edition mismatch is to own a higher-level edition license but deploy the lower-level edition. Occasionally, this is permissible under edition downgrade rights, as is the case for recent versions of Windows Server and SQL Server mentioned above , but more often it is not.
A common noncompliant scenario of this type is a customer who purchased Office Professional Plus licenses but deployed Office Standard. Although somewhat counterintuitive, Office Professional Plus licenses do not include edition downgrade rights to Office Standard. Thus, in the event of an audit, Office Professional Plus licenses generally cannot be used to cover deployments of Office Standard, and a customer would have to purchase new licenses to match the edition deployed, or if a special exception were made, to redeploy the edition originally purchased.
Version Mismatch Inadvertent version mismatch errors are less common than accidental edition mismatches for two reasons. First, most licenses purchased through volume licensing programs include version downgrade rights, so using a version older than what is licensed is generally not an issue.
Second, most customers understand that they are noncompliant if they deploy, for production purposes, a version more recent than the version they have licensed or are entitled to under SA. However, version mismatch errors related to CALs occasionally catch some customers by surprise. Expanding on the previous example, deploying an instance of Windows Server as a DNS server—a type of core network service accessible to all clients—would likely trigger an organization-wide requirement for Windows Server CALs.
Rob Horwitz, Directions on Microsoft 3. Applying the Incorrect Set of Use Rights When exercising version downgrade rights, customers are generally subject to the use rights associated with the version and edition of the license owned rather than the use rights associated with the older version or different edition deployed. This issue tends to matter most when server workloads are virtualized because the relevant use rights—license reassignment frequency and the number of running instances permitted per license—have changed substantially over time for some products.
But sometimes the opposite is true. The best product and use right for illustrating both potential outcomes is SQL Server Enterprise edition and reassignment rights; its license reassignment rules have been altered multiple times in the past few years.
Reassignment rules define how frequently and under what circumstances customers can move licenses between devices in the case of device-based licenses or users in the case of user-based licenses within their enterprise. In contrast, Enterprise edition licenses for SQL Server and R2 provide unlimited reassignment within a server farm which can contain up to two data centers, as long as the data centers are in time zones no more than four hours apart.
When SQL Server was released, the Enterprise edition license terms went back to the previous once-everydays rule, except for licenses covered by SA, in which case the license could be moved as often as necessary within a server farm. In contrast, the same workload running on a server assigned SQL Server Enterprise or R2 Enterprise licenses benefits from more liberal reassignment rights.
Similarly, reassignment rights for Exchange Server and SharePoint Server have changed between version and loosened from once every 90 days to unfettered reassignment within a server farm and again between and back to once every 90 days for licenses that lack SA coverage , so analogous scenarios can be constructed. The second virtualization-related use right, the number of instances that can run within VMs on a licensed device under the context of a license or set of licenses , has also changed for some products, meaning that it matters which set of use rights are in effect.
Here again there are examples of changes which may either favor or disadvantage customers. For example, instance rights were changed for Windows Server Standard as part of the transition from Windows Server R2 to Windows Server , going from one instance permitted per license to two. However, in the case of SQL Server Enterprise edition, rules have been made stricter over the past decade, with the number of permitted instances capped unless all SQL Server Enterprise edition licenses assigned to a server are covered by SA.
The latest PUR can be downloaded from www. The latest Product List can be downloaded from www. Please see their details in the post above.