Click to Rate and Give Feedback
TechNet
TechNet Library
Exchange Server
 Exchange Server 2007: Platforms, Ed...
Exchange 2007
Exchange Server 2007: Platforms, Editions, and Versions

Applies to: Exchange Server 2007, Exchange Server 2007 SP1 Topic Last Modified: 2008-07-10

Microsoft Exchange Server 2007 and Exchange 2007 Service Pack 1 (SP1) are available in two server editions: Standard Edition and Enterprise Edition. For more information about these editions including descriptions and comparisons, see Exchange Server 2007 Editions and Client Access Licenses. According to the Exchange Server 2007 Edition Offerings table on that Web page, the primary differences are:

  • Only Enterprise Edition can scale to 50 databases per server; Standard Edition is limited to 5 databases per server.
  • In a production environment, only Enterprise Edition is supported in a Microsoft Windows failover cluster; Standard Edition is not supported in a Windows failover cluster in production. Therefore, single copy clusters (SCCs) and cluster continuous replication (CCR) environments are only supported on Enterprise Edition. When you deploy Exchange 2007 in a failover cluster, an Enterprise Edition license is required for each node on which Exchange 2007 is installed.

Even though Exchange 2007 and Exchange 2007 SP1 come in two edition offerings, these are licensing editions that are defined by a product key. There is a single set of binary files for each platform (one for x64 systems and one for x86 systems), and the same binary files are used for both editions. When you enter a valid license product key, the supported edition for the server is established. See "Evaluations and Product Keys" below for other important information about product keys.

Exchange 2007 also comes in two client access license (CAL) editions, which are also called Standard Edition and Enterprise Edition. You can mix and match the server editions with the CAL editions. For example, you can use Enterprise Edition CALs against Standard Edition. Similarly, you can use Standard Edition CALs against Enterprise Edition. The Enterprise Edition CAL is an additive CAL, which means that you buy the Standard Edition CAL, and then add an Enterprise Edition CAL on top of it. An Enterprise Edition CAL provides you with the features listed in the last column of the Exchange 2007 CAL Offerings table. Note that some of the listed features can only be purchased through a volume license program, and they are not available as retail purchases. When you are ready to buy Exchange 2007, see How to Buy Exchange Server 2007.

Exchange 2007 RTM and SP1 are available in two platform versions: the 64-bit version is for live production environments and the 32-bit version is for non-production environments (such as labs, training facilities, demos, and evaluation environments). Only the 64-bit version can be purchased because you cannot run 32-bit Exchange 2007 servers in production.

There are exceptions with respect to production and non-production use of the 32-bit platform because Microsoft does allow minimal supported use of the 32-bit version in production environments:

  • You can use the 32-bit version in production to extend your Active Directory directory service schema. For detailed steps about how to prepare Active Directory for Exchange 2007, see How to Prepare Active Directory and Domains.
  • You can use the 32-bit version of the release to manufacturing (RTM) management tools in production to administer Exchange 2007 servers from Windows Server 2003 or Windows XP.
  • You can use the 32-bit version of the Service Pack 1 (SP1) management tools on Windows Server 2008 or on Windows Vista. Support for Windows Server 2008 and Windows Vista is available only with Microsoft Exchange Server 2007 SP1. However, you cannot use the SP1 management tools (32-bit or 64-bit) on Windows Vista to remotely manage a clustered mailbox server in a failover cluster. This is because:
    • Windows Server does not support cross-operating system management of failover clusters. Thus, Windows Vista cannot be used to manage a Windows Server 2003 failover cluster, and neither Windows Server 2003 nor Windows XP can be used to remotely manage a Windows Server 2008 failover cluster.
    • Remote management of a Windows Server 2008 failover cluster requires the installation of the Failover Cluster Management tools, which currently do not exist for Windows Vista. Thus, Windows Vista cannot be used to remotely manage a Windows Server 2008 failover cluster.

For more information about managing mixed versions of clustered mailbox servers, see Upgrading Clustered Mailbox Servers to Exchange 2007 SP1.

Important:
All other uses of the 32-bit version of Exchange 2007 in production environments are unsupported.

Although the 64-bit version can be Standard Edition or Enterprise Edition, the 32-bit version is only Standard Edition. SCC and CCR are only supported in production on the Enterprise Edition of Exchange 2007. However, Microsoft has made an exception in the 32-bit version code to allow SCC and CCR to be used for non-production use on the 32-bit version, even though the 32-bit version is Standard Edition. This means that you can set up a 32-bit test lab for evaluating or testing SCC and CCR. Because it is 32-bit, you can create the non-production environments in a Microsoft Virtual Server environment for your lab or demos. For a video demonstration of CCR that uses a virtual environment, see Video series - Exchange 2007 Cluster Continuous Replication (CCR). For a video demonstration of SCR that uses a virtual environment, see Video Series: Exchange 2007 SP1 Standby Continuous Replication (SCR).

Note:
You can also install Unified Messaging (UM) with the 32-bit version in a non-production environment so that you can evaluate the UM-related features. For details about using a software-based UM test phone to test or demo UM features, see Testing Unified Messaging Server Functionality.

What Is Missing from the 32-Bit Version

In addition to the missing Exchange Management Console interface for entering a product key as described in "Evaluations and Product Keys" later in this topic, two other features are not available in the 32-bit version of Exchange 2007:

  • Automatic anti-spam updates from Microsoft Update. Only a licensed 64-bit version of Exchange 2007 can get automatic anti-spam updates from Microsoft Update.
  • Large numbers of storage groups and databases. You can have a maximum of five databases per server in as many as five storage groups on the 32-bit version.

Exchange 2007 SP1 is a full re-release of Exchange 2007 with SP1 already integrated. This is similar to the service pack slipstreaming model used by Windows Server; however, it is not slipstreaming, and you do not need to perform any slipstreaming tasks for Exchange 2007 SP1.

Note:
You can download SP1 from http://go.microsoft.com/fwlink/?LinkId=104387.

SP1 can be installed on computers running the RTM version of Exchange 2007 to perform an in-place upgrade. For new installations, you do not need to install Exchange 2007 RTM and then install SP1. Because SP1 is a completely updated set of installation files, it can be used to perform a fresh installation of Exchange 2007 SP1.

Exchange 2007 SP1 includes all update rollups previously released for Exchange 2007 up to and including Update Rollup 5. You do not need to manually uninstall any released update rollup (1-5). When you install Exchange 2007 SP1 on a system that has a released update rollup, the update rollup will be automatically uninstalled by SP1 Setup.

Neither Exchange 2007 nor Exchange 2007 SP1 is supported in production in a virtual environment. However, Microsoft has several virtualization offerings that provide a good environment for training, labs, and demos, such as Windows Server 2008 Hyper-V, Microsoft Virtual Server 2005 R2, and Microsoft Virtual PC 2007. Exchange 2007 and Exchange 2007 SP1 are supported in production environments using only the 64-bit version of Exchange 2007, and currently neither Microsoft Virtual Server nor Microsoft Virtual PC supports 64-bit guest systems. Windows Server 2008 Hyper-V includes support for 64-bit guest systems; however, Exchange 2007 and Exchange 2007 SP1 are currently not supported running under Hyper-V. Within 60 days of the Hyper-V release to manufacturing (which occurred on June 26, 2008), Microsoft will release a support statement and related guidance for Exchange 2007 as a Hyper-V guest system.

Exchange 2007 and Exchange 2007 SP1 are not supported in production in a virtual environment using virtualization software that is not Microsoft software. For details about the Microsoft support policy for third-party virtualization software, see Microsoft Knowledge Base article 897615, Support policy for Microsoft software running in non-Microsoft hardware virtualization software.

For more information about Microsoft virtualization plans, visit the Microsoft Virtualization Web site.

The RTM version of Exchange 2007 cannot be installed on Windows Server 2008. However, Exchange 2007 SP1 is supported for installation on Windows Server 2008. Although you cannot install the RTM version of Exchange 2007 on Windows Server 2008, the RTM version of Exchange 2007 will be supported for use with Windows Server 2008 directory servers.

Exchange Server 2003 Service Pack 2 (SP2) is similarly supported. Exchange Server 2003 cannot be installed on a computer running Windows Server 2008, but Exchange 2003 will be supported for use with Windows Server 2008 directory servers.

Be aware of the following when combining Microsoft Exchange with Windows Server 2008:

  • Exchange 2007 RTM and all previous versions of Microsoft Exchange are not supported for installation on a computer running Windows Server 2008.
  • Exchange 2007 SP1 can be installed on a computer running Windows Server 2008.
  • Management tools for Exchange 2007 RTM and all previous versions of Microsoft Exchange are not supported for installation on a computer running Windows Server 2008 or Windows Vista.
  • Management tools for Exchange 2007 SP1 can be installed on a computer running Windows Server 2008 or Windows Vista.

Exchange Server and Windows Server 2008 Directory Servers

This section outlines the supported configurations for Exchange 2007 and earlier versions of Exchange with the RTM version of Windows Server 2008. For customers running pre-release versions of Microsoft Exchange or Windows Server as authorized participants in a Technology Adoption Program for Microsoft Exchange or Windows Server, current builds of Windows Server 2008 and Exchange 2007 SP1 are also supported as described in the following list:

  • Exchange 2007 SP1, Exchange 2007, and Exchange 2003 SP2 are supported in environments that either partly or entirely use writeable Windows Server 2008 directory servers.
  • Exchange 2000 Server Service Pack 3 (SP3) and all previous versions of Microsoft Exchange are not supported for use with Windows Server 2008 directory servers. The following restrictions apply with respect to Exchange 2000 SP3:
    • Exchange 2000 SP3 can exist in an Active Directory forest that contains Windows Server 2008 directory servers, but Windows Server 2008 directory servers should not be installed in Active Directory sites that contain Exchange 2000.
    • If Windows Server 2008 directory servers must be deployed in Active Directory sites that contain Exchange 2000, you must first hard code Directory Service Access (DSAccess) on the Exchange 2000 servers in the site to point to directory servers running Windows Server 2003 or Windows 2000 Server.
  • No version of Microsoft Exchange uses read-only domain controllers or read-only global catalog servers. However, Microsoft Exchange works in environments that include read-only domain controllers or read-only global catalog servers, as long as there are writeable domain controllers available. Exchange 2007 effectively ignores read-only domain controllers and read-only global catalog servers. Exchange 2003 also ignores read-only domain controllers and read-only global catalog servers in default conditions where Exchange components automatically detect available domain controllers. No changes were made to Exchange 2003 to make it read-only directory server-aware. Therefore, trying to force Exchange 2003 services and management tools to use read-only global catalog servers may result in unpredictable behavior.

Known Issues with Exchange Server and Windows Server 2008

The following are known issues when combining legacy versions of Microsoft Exchange with Windows Server 2008:

  • Setting an Exchange 2003 domain Recipient Update Service to use a read-only domain controller will succeed, but user accounts will not be updated by the service. It is also possible to force the Active Directory Connector (ADC) service to use a read-only domain controller, but this will cause the ADC to function incorrectly.
  • Exchange 2003 may not install correctly in a pure Windows Server 2008 forest if you try to install Exchange in a child domain without installing Exchange in the parent domain.

When you install Exchange 2007, it is unlicensed and referred to as a Trial Edition. Unlicensed (Trial Edition) servers appear as Standard Edition, and they are not eligible for support from Microsoft Product Support Services. The Trial Edition expires 120 days after the date of installation. When you start the Exchange Management Console, if you have any unlicensed Exchange 2007 servers in your organization, Exchange displays a list of all unlicensed Exchange 2007 servers and the number of days that are remaining until the Trial Edition expires. If you have expired unlicensed Exchange 2007 servers, you also see a separate warning for each expired server. No loss of functionality will occur when the Trial Edition expires, so you can maintain lab, demo, training, and other non-production environments beyond 120 days without having to reinstall the Trial Edition of Exchange 2007. You can even upgrade an expired Trial Edition of Exchange 2007 RTM to SP1.

Product keys can be used for the same edition key swaps and upgrades only, and they cannot be used for downgrades. You can use a valid product key to go from the evaluation version (Trial Edition) to either Standard Edition or Enterprise Edition. You can also use a valid product key to go from Standard Edition to Enterprise Edition. You can also license the server again using the same edition product key. For example, if you had two Standard Edition servers with two keys, but you accidentally used the same key on both servers, you can change the key for one of them to be the other key that you were issued. You can take these actions without having to reinstall or reconfigure anything. After you enter the product key, the edition corresponding to that product key will be reflected.

Note:
On stand-alone computers that have the Mailbox server role installed, the Microsoft Exchange Information Store service must be restarted for the product key change to take effect. In an SCC or CCR environment, the clustered mailbox server must be stopped and started for the product key change to take effect. In addition, for computers with the Edge Transport server role installed, if the license key is applied to the Edge Transport server after you perform the Edge Subscription process, the licensing information is not updated in the Exchange organization and you must re-subscribe the Edge Transport server.

You cannot use product keys to downgrade from Enterprise Edition to Standard Edition, nor can you use them to revert to the Trial Edition. These types of downgrades can only be done by uninstalling Exchange 2007, reinstalling Exchange 2007, and entering the correct product key.

You can upgrade from the Trial Edition to the retail version by purchasing the appropriate licenses and by entering the product key that you get when you make the purchase. You can find the product key on the Exchange 2007 DVD case. It is a 25-character alphanumeric string, grouped in sets of five characters separated by hyphens. Step-by-step instructions for entering your product key can be found in How to Enter the Product Key. These steps include instructions for entering the key using either the Exchange Management Console or the Exchange Management Shell. However, in the 32-bit version, there is no Exchange Management Console interface for this because you cannot purchase 32-bit licenses.

By using either the Exchange Management Console or the Exchange Management Shell, you can see what edition you are running. By using the Exchange Management Shell, you can also see how many days, hours, minutes, seconds, and milliseconds are left on the 120-day trial period. Use the Get-ExchangeServer cmdlet and look for the Edition and RemainingTrialPeriod values.

The final RTM build of Exchange 2007 is build 685.25, but in some places it is listed as 685.24. Both are correct. When you view the version information in the Exchange Management Console or examine the value of the AdminDisplayVersion property for Exchange servers in the Exchange Management Shell, it shows the version as 685.24. When you view the Exchange version information in the Windows registry, it shows 685.25. If you use Microsoft Operations Manager, it also shows version 685.25, but if you view version information in Microsoft Office Outlook, it shows 685.24.

An exception to this version mismatch problem is present on the Edge Transport server. That only displays 685.25 for the version. This makes things interesting when looking at several Exchange servers in the Exchange Management Console that include one or more synchronized Edge Transport servers because the Version column will show both 685.24 (for non-Edge Transport servers) and 685.25 (for Edge Transport servers).

Also, when you click Help, and then click About Exchange Server 2007, you will see a different version number altogether: 685.018. This happens on all Exchange 2007 servers. These versioning discrepancies are resolved in Exchange 2007 SP1.

Finally, if you use the Get-ExchangeServer cmdlet and examine the ExchangeVersion property, you will notice a different version number: 0.1 (8.0.535.0). However, this number does not refer to the version of an installed product, but rather it refers to the minimum version of the product that can read the object. In this case, any Exchange 2007 server that is version 8.0.535.0 or later can read this object because the last changes to this object's schema were made in build 8.0.535.0.

The RTM version of Exchange 2007 SP1 is build 08.01.0240.006, which is also represented as Version 8.1 (Build 240.6). This version information is consistently displayed in the Exchange Management Console, the Exchange Management Shell, and in the About Exchange Server 2007 Help dialog box. However, after applying SP1 to an Edge Transport server running the RTM version of Exchange 2007, the version information for the Edge Transport server will not be updated in the Exchange Management Console unless the Edge Transport server is re-subscribed to the Active Directory site. This is because the Edge Transport server does not directly update Active Directory with any configuration information. Instead, the version information for Edge Transport servers is recorded in Active Directory during the creation of an Edge Subscription.

You can also determine the installed version of Exchange 2007 by examining the value for each installed role in the Registry at:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\<Role>\ConfiguredVersion

ConfiguredVersion is a string value in the format of X.X.XXX.X (e.g., 8.1.240.6). 8 is the major version number. The .1 portion indicates it is SP1 (RTM would have .0). 240 is the build number, and the .0 after 240 would be .6, the minor build number.

The value of the ExchangeVersion property remains unchanged in Exchange 2007 SP1; the output of the Get-ExchangeServer cmdlet for the ExchangeVersion parameter is 0.1 (8.0.535.0).

Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
Virtualization support statement      Kwyjibo ... Scott Schnoll - MSFT   |   Edit   |  
Note: This comment has been edited from its original wording. Please use the History feature to track comment history. There is nothing contradictory about the statements made in this article versus statements made in 897615.

"Exchange 2007 and Exchange 2007 SP1 are also not supported in production in a virtual environment using virtualization software that is not Microsoft software.".
See also, http://support.microsoft.com/?kbid=897615 which states the following:

"For Microsoft Premier-level support customers running non-Microsoft hardware virtualization software from vendors with which Microsoft does not have an established support relationship that covers virtualization solutions, Microsoft will use commercially reasonable efforts to investigate potential issues with Microsoft software running together with non-Microsoft hardware virtualization software."
Tags What's this?: Add a tag
Flag as ContentBug
Visit the Exchange team blog      Lee-Tony   |   Edit   |  

For more information about installing Exchange on a computer running the Windows Server 2008 operating system, see the Exchange Server Team Blog article Exchange Server and Windows Server 2008, Part II.

Processing
© 2008 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Page view tracker