Supported Processors

• Intel Pentium or compatible 800 megahertz (MHz) or faster 32-bit processor
• x64 architecture-based Intel Xeon or Intel Pentium family processor that supports Intel® Extended Memory 64 Technology (Intel® EM64T)
• x64 architecture based computer with AMD Opteron or AMD Athlon 64-bit processor that supports AMD64 platform

  Note:
  Intel Itanium IA64 processors are not supported.

Memory

• Minimum: 1 gigabyte (GB) of RAM per server plus 7 MB per mailbox.
• Recommended: 2 gigabytes (GBs) of RAM per server plus 10 MB per mailbox.
• The paging file size should be equal to the amount of RAM in the server.

Available Disk Space

• At least 1.2 GB of available disk space on the drive on which you install Exchange. An additional 500 MB of available disk space is needed for each Unified Messaging (UM) language pack that you plan to install.
• 200 MB of available disk space on the system drive
• DVD drive (local or network accessible)

• Operating System:
  • 32-bit Beta 2 Exchange Server 2007 trial   Will run on Microsoft Windows Server 2003 Service Pack (SP) 1 or Windows Server 2003 R2, Standard or Enterprise Editions. The Enterprise Edition is required to use the cluster continuous replication and single copy cluster features in Exchange 2007.

    Important:
    Installing the 32-bit version of Exchange 2007 is supported in testing or training environments, but it is not supported in production environments. In production environments, you must install the 64-bit version of Exchange 2007.

    Note:
    You can install the Exchange Management Tools (which include the Exchange Management Console, the Exchange Management Shell, and the Exchange Help file) on a computer with a 32-bit processor running Microsoft Windows Server 2003 or Windows XP.

  • 64-bit Beta 2 Exchange Server 2007 trial   Will run on Windows Server 2003 x64 or Windows Server 2003 R2 x64, Standard or Enterprise Editions. The Enterprise Edition is required to use the cluster continuous replication and single copy cluster features in Exchange 2007.
• Microsoft .NET Framework 2.0   Exchange 2007 is built on Microsoft .NET Framework 2.0. For download information, see .NET Framework Developer Center.
• Windows PowerShell   The RC0 version of Windows PowerShell must be installed because the Exchange Management Console runs inside / on top of Windows PowerShell. The Setup splash screen provides a link to download the required RC0 version of Windows PowerShell.
• Internet Information Service (IIS)   The World Wide Web Publishing service (W3SVC) is required for the Client Access server (CAS) and Mailbox server roles. In addition, the Client Access server role also requires ASP.NET.
• Microsoft Management Console (MMC) 3.0   The MMC 3.0 build must be installed. For download information, see MMC 3.0 Update.
• Exchange Organization Operation mode set to Native Mode   The Exchange Operation mode for the organization must be Native Mode.
• Active Directory Domain Functional Level set to Windows 2000 Native or greater   This domain functional level is required to support the new Exchange Servers universal group.
• Schema Master must be Microsoft Windows Server 2003 or Microsoft Windows Server 2003 Service Pack 1   The server that holds the Schema Master Flexible Single Master Operation (FSMO) role needs to have Windows Server 2003 or Windows Server 2003 with Service Pack 1 installed.
• Windows Server 2003 hotfix 904639   For more information about this hotfix that is related to 64-bit installations, see Microsoft Knowledge Base article 904639, An access violation may occur when you try to run a 64-bit program that uses the interface remoting component of MDAC 2.8 on a computer that is running Windows Server 2003. The article includes links to the hotfix.

  Important:
  Installing the 32-bit version of Exchange 2007 is supported in testing or training environments, but it is not supported in production environments. In production environments, you must install the 64-bit version of Exchange 2007.

  Note:
  You can install the Exchange management tools (which include the Exchange Management Console, the Exchange Management Shell, and the Exchange Help file) on a computer with a 32-bit processor running Microsoft Windows Server 2003 or Windows XP .

• Windows Server 2003 hotfix 921181   This hotfix is required for cluster continuous replication (CCR). It adds a file share witness option for a majority node set quorum and the ability to configure cluster heartbeats. For more information about this hotfix, see Microsoft Knowledge Base article 921181, An update is available that adds a file share witness feature and a configurable cluster heartbeats feature to Windows Server 2003 Service Pack 1-based server clusters. We recommend reviewing this article in addition to the documentation for CCR.
• Existing Exchange Installations   If you are installing into an organization that contains Exchange servers, those servers must meet the following requirements:
  • No Exchange Server 5.5 servers are in the forest.
  • Exchange Server 2003 servers must have a minimum version of Exchange Server 2003 Service Pack 2 installed.
  • Exchange 2000 Server servers in your organization must have a minimum version of Exchange 2000 Server Service Pack 3.

• Command line Setup changes    If you run Setup from a command prompt, and if you are installing the first Exchange server in the organization, you must include the /OrganizationName parameter to specify the name of your Exchange organization. This is a required parameter, and Setup will fail if it is not included.
• Installing CAS might affect existing ASP.NET applications   Installing the Client Access server role sets the default ASP.NET version and the version for all ASP.NET scriptsmaps to v2.0.5027. This setting may break existing applications that require a different version of ASP.NET. To fix this issue, run aspnet_regiis.exe -s <Metabase_Path_to_virtual_directory> from the appropriate version of ASP.NET for each affected virtual directory. Typically you can find the aspnet_regiis.exe for installed versions of ASP.NET in the c:\windows\microsoft.net\framework\<asp.net_version_number>\ folder.
• Organizations with Exchange 2000 Server require an update to the Exchange 2000 Exchange System Manager   Before you install Exchange 2007 into an organization with Exchange 2000 servers, the Exchange 2000 servers require the installation of the latest Microsoft Exchange 2000 Server Post-Service Pack 3 (SP3) Update Rollup. The Exchange 2007 setup prerequisite checks cannot detect whether this rollup is installed. The update rollup includes the updated exadmin.dll, which helps the Exchange 2000 Exchange System Manager work better with Exchange 2007 object versioning. Without the update rollup, the Exchange 2000 Exchange System Manager is versioning ignorant. For more information about the update rollup and to download the update rollup, see Microsoft Knowledge Base article 87540: Availability of the August 2004 Exchange 2000 Server Post-Service Pack 3 Update Rollup.

  Note:
  If you have computers that have the Exchange 2000 Exchange System Manager installed on them, such as Microsoft Windows XP computers, you should install the latest Exchange 2000 Server Post-Service Pack 3 (SP3) Update Rollup on those computers also. If you have already done this, you should also apply Exchange 2000 Service Pack 3 to those computers as it is a prerequisite to installing the rollup.

• The Default Accepted SMTP domain is automatically set to your Active Directory FQDN during setup  When you install Exchange 2007, it uses the Active Directory directory service domain name for the default accepted domain. Some Active Directory DNS zones are internal only and have no relationship to your external DNS zone. To set a new accepted domain, see "How to Create Accepted Domains" in the Exchange 2007 Help.
• CAS role cannot be upgraded in place   To upgrade an Exchange 2007 server with the Client Access server role installed, you must remove the Client Access role from the server prior to running Setup. There is no in-place upgrade path for Client Access server.
• Setup order to support DAV in a single server topology   When you install Exchange 2007 into your topology with the CAS, Mailbox, and Hub Transport server roles on the same server, the CAS role must be installed before the Mailbox role because the Mailbox role install will register the proper DLL for handling DAV requests on the local machine. Otherwise, the CAS server install registers the Exproxy DLL to proxy requests to other machines and requests will not make it to the local server if it is installed after the Mailbox role. This install order is currently the default behavior when you install a new server and select all of the roles.
• Need to reinstall the CAS role if you remove the mailbox role from a server with the CAS role installed   If you remove the Mailbox role from a server that has the mailbox and CAS roles installed, you must remove the CAS roles and then re-install the CAS role to have Exproxy re-registered to handle DAV requests and proxy them to the appropriate Mailbox server.
• Log file locations have been updated after a Help topic was published   In the Exchange 2007 Help topic "Verifying an Exchange 2007 Installation", the content for Setup Log files points to the wrong log file locations for some of the log files. The following table contains the correct paths for the incorrect entries.

  Location	Contents	Server role
  <system drive>\ExchangeSetupLogs\Exsetup.log	This file contains information about the status of the prerequisite and system-readiness checks that are performed before installation starts. This log is the first log file to perform a quick verification that the server roles were installed as expected.	Hub Transport, Mailbox, Client Access, and Unified Messaging
  <system drive>\ExchangeSetupLogs\ExchangeServer.msilog	This file contains information about the extraction of the Exchange 2007 code from the installer file.	Hub Transport, Mailbox, Client Access, Unified Messaging, and Edge Transport
  <system drive>\ExchangeSetupLogs\Exchange Server Setup Progress.log	This file contains information about the changes that the Exchange 2007 installation makes to your operating system, including changes to the registry.	Hub Transport, Mailbox, Client Access, and Unified Messaging

• Windows Firewall SCW not supported in Beta 2   Using the Windows Server 2003 Secure Configuration Wizard (SCW) is not supported for the Exchange 2007 Beta 2 deployment.
• Windows x64 introduces CDOEX and ExOLEDB instabilities   The x64 version of Windows Server 2003 can lead to instability in certain components that depend upon ExOLEDB or CDOEX. You may encounter store crashes due to this instability. If you are experiencing these crashes, see Microsoft Knowledge Base Article 918980, FIX: The IRow::GetColumns function of the Exchange OLE DB provider unexpectedly returns error code 0x80010105 on a server that is running a 64-bit version of Windows Server 2003 Service Pack 1.

• UM dial plans are set to US English by default   As part of the finalization of deployment that occurs after the setup of the first Exchange 2007 server that is running the UM role, the UM server is added to a UM Dial Plan. The available UM languages (US English plus one other language, depending on installation language, for non-English Exchange versions) are added to the Dial Plan's available languages. However, the default language for the UM Dial Plan is always set to US English, even if the Exchange installation is not English. This setting will be changed for RTM. Use the Exchange Management Console or the Exchange Management Shell to configure the UM Dial Plan to use the required language. For more information, see "Default Dial Plan Language" later in this document.
• An approved IP PBX or VoIP gateway is required for the UM server role   To enable Unified Messaging, an approved IP PBX system or connection to a legacy PBX system via a VoIP (Voice over IP) gateway is required to connect Exchange Unified Messaging to a PBX. Current approved VoIP gateways are manufactured by Intel and AudioCodes. Exchange Server Unified Messaging uses the VoIP protocols SIP and RTP for voice communication. Because traditional PBX systems do not support these protocols directly, a VoIP gateway is required to convert from traditional telephony protocols to VoIP protocols. For more information about VoIP gateways, see "Understanding Unified Messaging Subscriber Access" in the Exchange 2007 Help.
• Spanish language package improperly displayed in a few places   The Spanish (Latin America) UM language pack is incorrectly identified by the characters "es-MX" in two places:
  • Part of the name of the Microsoft Windows Installer package for the language pack (umlang-es-MX.msi).
  • The code required to specify the language pack when adding it to an existing UM installation (exsetup /addumlanguagepack es-MX ...).
  The Spanish (Latin America) language pack is correctly identified by the characters "EsMx" when it is displayed (as a default UM language, or part of a set of available UM languages) by the Exchange Management Console or the Exchange Management Shell.
• Speech recognition is only available in English in Beta 2   Unified Messaging relies on the Text-to-Speech (TTS) engine and Automatic Speech Recognition functionality that is provided through the Microsoft Speech Server service. Both the TTS engine and pre-recorded prompts for a given language with Unified Messaging are packaged as "language packs.” The Unified Messaging language packs are offered in 16 different languages, and all 16 language packs are included on the product DVD. However, not all of the UM language packs contain support for Automatic Speech Recognition. The UM language packs will be available on the Beta 2 DVD or via Web download.

  Note:

  when you install the Unified Messaging server role in Exchange 2007, default Unified Messaging language pack(s) will be automatically installed based on the administrative language of the server. You can then add and remove other language packs for Unified Messaging using the Exsetup.exe /addUMlanguagepack or Exsetup.exe /removeUMlanguagepack commands. There is no Exchange Management Shell command that will allow you to add or remove language packs for Unified Messaging. As an example, Exsetup /AddUmLanguagePack:de-DE /s:d:\Downloads\UmLanguagePacks adds the German Unified Messaging language pack from the specified source location, while Exsetup /RemoveUmLanguagePack:de-DE,fr-FR removes the German and French Unified Messaging language packs. The US English (en-US) Unified Messaging language pack cannot be removed. It will be installed and uninstalled automatically with the Unified Messaging role.

• Text-to-Speech will be used for some languages   Exchange 2007 Unified Messaging interacts with callers and users over the telephone by playing prompts and responding to speech and/or key presses. In the final release, the prompts will generally be prerecorded. However, for the Beta 2 release, speech synthesis (text-to-speech conversion) will be used for certain languages, for which prompts have not yet been recorded. Recorded prompts will be available for the following languages:
  • de-DE   German
  • en-US    English (United States)
  • fr-FR   French (France)
  • it-IT   Italian
  • ja-JP   Japanese
  Speech synthesis will be used for prompts in the following languages:
  • en-AU   English (Australia)
  • en-GB   English (United Kingdom)
  • es-ES   Spanish (Spain)
  • es-MX   Spanish (Latin America)
  • fr-CA   French (Canada)
  • ko-KR   Korean
  • nl-NL   Dutch
  • pt-BR   Portuguese (Brazil)
  • sv-SE   Swedish
  • zh-CN   Mandarin (China PRC)
• Grammar generation might discard some names   Exchange 2007 computers running the Unified Messaging role will generate speech grammars containing names from Active Directory. This happens first when the UM server joins a UM Dial Plan, and thereafter once per day (the default start time is 2:00 A.M.). Grammar generation reads display names, phonetic display names (if present) and e-mail aliases from Active Directory. Before inserting a particular user's details in the speech grammar, the generation code checks the name against a list of patterns that it uses to transform the name from something that is appropriate to visual display (for example, "David (Dave) Jones") to one or more names that are more likely to be spoken by callers (for example, "Dave Jones"). Names that do not match any of the configured patterns are passed through unchanged. When the pattern matching and replacement is complete, the (possibly changed) name is then examined to see whether there are multiple ways of speaking it. Some kinds of name (for example, names containing strings of digits, such as "Conference Room 3-103") permit many equivalent speech forms. To avoid uncontrolled expansion of the speech grammar and improve recognition accuracy in general, such names will be discarded and not entered into the speech grammar. Therefore, they can't be recognized by UM, even though the object exists in Active Directory and might otherwise be expected to be accessible though directory search from the voice user interface. Multiple equivalent forms of a name may also occur when the name contains certain acronyms (for example, "Jr."), or contains trailing information in parentheses (for example, "Jim Glynn (Human Resources)"). To inform the system administrator that such discards have occurred, UM will generate an event for each entry that is rejected. If the administrator wants a particular user's name to be accepted for the speech grammar, when it was previously rejected, they should determine how they would like the name to be recognized when spoken, and then use one of the following methods:
  • Set the Active Directory phonetic display name of the user (attribute: msDS-PhoneticDisplayName) to the desired name. This method is the preferred approach.

    Note:
    This attribute is not accessible through the "Active Directory Users and Computers" console in Windows Server 2003. Another directory editor such as ADSI Edit (AdsiEdit.msc.) must be used.

  • Set the display name of the user to the desired name.

    Note:
    This approach will affect the name as it is displayed in e-mail, and in all clients that read from Active Directory.

• Removing public folders   You will not be able to remove a public folder database if the public folder database is listed as the siteFolderServer for offline address books, free/busy data, or an administrative group. The siteFolderServer attribute must be changed before the Public Folder Database can be removed. Server Administrators do not have access to this attribute, which means that they will not be able to remove a public folder database that is a siteFolderServer. For Beta 2, removing a public folder database which is the siteFolderServer for any offline address book, administrative group, or free/busy data must be performed by an Exchange Organization Administrator in order for those items to continue to function correctly.
• Public folder management is not available in the Exchange Management Console   The Exchange 2007 Beta 2 release does not include public folder management tasks. In this release, Exchange 2007 public folders can be managed in the following ways:
  • If your organization has servers that are running Exchange Server 2003, use the System Manager.
  • If your organization does not have servers that are running Exchange Server 2003, use the latest version of the Exchange Server 2003 System Management Tools on a computer running Windows XP with Service Pack 2. See the Exchange Server 2003 documentation for installation steps.
• Folder quotas must be set now or they will never be able to be set   Exchange 2007 allows a quota to be set on individual managed custom folders as part of the messaging records management feature set. Currently, Exchange 2007 prevents a quota from being set on a managed folder that contains content. If you want to set a quota on a managed custom folder before it is deployed or think that you may do so in the future, you must set a quota at the time that the folder is empty. You may set this quota to its maximum value (2,097,151 KB) so that it will not interfere with your users' daily work habits. This quota must remain on the folder for that folder to be eligible to have a quota in the future, or until you install a version of Exchange in which this issue has been resolved. If you remove the quota before the fix for this issue is applied, you will never be able to set a quota on this folder even if you upgrade to a build where this issue has been fixed.
• Removal of the System Attendant mailbox will cause some mailbox operations to fail   If the mailbox database containing the System Attendant mailbox is deleted, move mailbox operations will fail on the server from which the move mailbox operation is being run. The failure error is: "Error was found for <mailbox name> because: The information store could not be opened. The MAPI provider failed. MAPI 1.0 ID no: 8004011d-0289-00000000, error code: -1056636928". To resolve this error, create a database on the server, and the System Attendant mailbox will be automatically re-created.

• CAS commands not working   Currently, if you have a multi-domain (parent child) topology, Get-CASMailboxPolicy succeeds, but Set-CASMailboxPolicy fails. This issue will be fixed for RTM.
• OWA segmentation administration tasks are not available in Beta 2   Outlook Web Access segmentation administrator tasks are not functional in Beta 2 of Exchange 2007.
• Domain Controller hotfix required if Exchange 2007 is talking to a non-English Domain Controller for the address book to function properly in Outlook Web Access   If you are using Outlook Web Access and the CAS server is connected to a Domain Controller running a non-English version of Windows, you must install hotfix KB919166 on your Domain Controller. Without this hotfix, address book operations in Outlook Web Access will fail if your users' User Interface culture is different from the Domain Controller culture.

  Note:
  At the time of this document's writing, KB919166 was not posted to the Web. However, it should be available by the time that Beta 2 is released. If it is on the Web, you can call Microsoft Help and Support and obtain this hotfix without being charged for the call.

• ActiveSync authentication settings   Currently, Exchange 2007 Exchange ActiveSync supports users on Exchange 2003 mailboxes by proxying the ActiveSync request from the device through the CAS server to the Exchange 2003 server. In Beta2, this request will result in an authentication failure from the Exchange 2003 server if Exchange ActiveSync is configured to require client certificate-based authentication on the Exchange 2007 side. To work around this issue, configure the Exchange ActiveSync virtual directory on the Exchange 2007 CAS server to require basic authentication (instead of certificate authentication) if you intend for it to service users on the Exchange 2003 mailbox server. This issue will be fixed for RTM.
• OWA and Availability service work better with this SSL setting   In order for Office Outlook Web Access and the Availability service to work well together, both must have the same SSL settings when proxying. By default, both will ignore invalid SSL certificates when proxying. To change this behavior, set the HKLM\System\CurrentControlSet\Services\MSExchangeOWA\RequireTrustedCertForProxying registry property to "1" for Office Outlook Web Access and the IgnoreAllCertificateErrors property in the web.config file under the /owa virtual directory to "0". If Office Outlook Web Access and the Availability service have different SSL settings, neither one may work correctly. The Availability service that works with Exchange Web Services under the /ews virtual directory is not affected by this restriction.
• UNC file access from mobile devices does not work with CAS server proxy   Currently, Windows SharePoint Services UNC file access via Office Outlook Web Access and ActiveSync will not work when the HTTP request coming from the mobile client or device is being proxied to and handled by another Exchange 2007 CAS server.
• Public folder data on Exchange 2007 servers will not be accessible via DAV   It is recommended that public folders not be installed on Exchange 2007 Mailbox servers if you require DAV access to those public folders. Currently, DAV cannot access public folder data on Exchange 2007 servers. Because Outlook Web Access on Exchange Server 2003 uses DAV for most of its access to public folders, this issue will affect browsing public folders.
• Public folder replication between Exchange 2003 and Exchange 2007 could result in clients being denied access   If you do have public folders replicated between Exchange 2003 and Exchange 2007 servers, there will be a 50 percent chance that a user will be returned a 501 Not Implemented status code from the Exchange 2007 server when trying to access the server with DAV. This result occurs if the Exchange 2007 server was the server selected to access the data when the request was sent. To fix this issue, remove all public folders that need to be accessed with DAV from Exchange 2007 Mailbox servers, and place that data on Exchange 2003 servers. Because Outlook Web Access on Exchange Server 2003 uses DAV for most of its access to public folders, this issue will affect browsing public folders.
• Some ActiveSync users might need to make new server partnerships   After you install Exchange 2007 Beta 2, Exchange ActiveSync users may receive the following message on their Windows Mobile device: “An error has occurred and your data will be deleted before resynchronization.” This error is due to a change in the Exchange ActiveSync state format in Exchange 2007, and all e-mail, calendar, and contacts information will be removed from the device temporarily. In some cases, it may be necessary for you to re-create the Exchange ActiveSync Exchange server partnership on your device. Go to Office Outlook Web Access, and then select Options, Mobile Devices. Highlight the device, and then select Remove device from list.
• OWA Virtual Directory issue with CAS and mailbox on the same server    There is an interoperability problem between the CAS and Mailbox roles where the legacy virtual directories are not handled correctly by the Outlook Web Access virtual directory tasks. When the CAS and Mailbox server roles are installed on the same server, setup for the Mailbox role creates the /exchange and /public virtual directories and configures them to use Windows Integrated authentication. The CAS role setup creates objects in Active Directory for /exchange, /public, and /exchweb. As a result, the objects in Active Directory do not reference valid Exchange 2007 Outlook Web Access virtual directories, resulting in warning messages when running Get-OwaVirtualDirectory and Set-OwaVirtualDirectory. You should use the Set-OWAVirtualDirectory task to configure the authentication settings you would like to use with these virtual directories. Only Basic and Forms-based authentication are valid for legacy virtual directories.

• Hub servers in different forests require cross forest configuration   For Exchange Hub Transport servers in different forests to successfully exchange mail, you need a two-way forest trust between the forests and you must configure the access control on both servers to authorize the external forest servers for mail exchange. For more information about how to set up Hub Transport servers to exchange mail with servers in other forests, see “Cross-Forest Connectors" later in this document.
• Exchange Management Console displays the Finalize Deployment page after creating an Edge Subscription   After creating an Edge subscription, the Exchange Management Console on an Edge server displays the Exchange Server 2007 Finalize Deployment page for roles other than Edge role, such as the Hub Transport role. The Edge tasks are at the bottom of this page and could be overlooked. You should disregard the non-Edge role sections for setting up your Edge server.
• Anonymous mail submission and open relay are turned off by default   Servers that are running the Exchange 2007 Hub Transport server role do not allow unauthenticated SMTP mail submission and/or open relay in a default installation. If you need anonymous mail submission and/or open relay features for your testing environment, you must enable this feature. To enable this feature from the Exchange Management Shell, run the following command after setup of the Hub Transport server role is complete:

  set-receiveconnector <id> -PermissionGroups:AnonymousUsers,ExchangeUsers,ExchangeServers,ExchangeLegacyServers add-adpermission <id> -User AN –ExtendedRights ms-Exch-SMTP-Accept-Any-Recipient

• Exchange 2003 servers should be allowed to send forest and organizational headers to Exchange 2007   Exchange 2003 servers can send forest headers and organizational headers to Exchange 2007 servers. This allows messages that are not supposed to bypass anti-spam filters to bypass the anti-spam filters. To fix this issue if you have Exchange 2003 servers in your organization, run the following Exchange Management Shell command on a Hub Transport server:

  add-adpermission <DN_Administrative_container> -user <ForestRootDomain>\Exchange2003Interop -ExtendedRights ms-Exch-Accept-Headers-Organization,ms-Exch-Accept-Headers-Forest,ms-Exch-Send-Headers-Forest,ms-Exch-Send-Headers-Organization -deny -InheritanceType Descendents

  Note:
  Command Example: add-adpermission "CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=youdomain,DC=com" -user Redmond\Exchange2003Interop -ExtendedRights ms-Exch-Accept-Headers-Organization,ms-Exch-Accept-Headers-Forest,ms-Exch-Send-Headers-Forest,ms-Exch-Send-Headers-Organization -deny -InheritanceType Descendents

• EdgeSync issues when all Hub servers are removed   Hub Transport servers deployed after an Edge Subscription is created will not participate in EdgeSync. To have the new Hub Transport server synchronize data to your Edge server(s), you must remove the Edge Subscriptions in the organization and on each Edge server. Then, perform the subscription process again.
• Update-ExchangeCertificate is no longer a valid command   The update verb for the ExchangeCertificate noun is deprecated. New X509 self-signed certificates and certificate requests for TLS should use the new verb, new-ExchangeCertificate, to generate a new self-signed certificate or new-ExchangeCertificate –generaterequest –path c:\requests –base64encoded to generate a pkcs#10 certificate request.
• Do not modify the default EdgeSync ports   If you intend to use EdgeSync, the default ports must not be modified by Setup or Post-Setup. EdgeSync depends on a hard-coded port of 50636. If the default ADAM ports are changed, EdgeSync will not work. The ports must be reverted to their original values to use EdgeSync. The default Edge Transport role installation uses an ADAM instance with the following default ports:
  • 50389 - Lightweight Directory Access Protocol (LDAP)
  • 50636 - Secure LDAP
• Ports 5000-6000 need to be open for POP3 and IMAP4   If any firewall, including Windows Firewall, is enabled on a server that is running Exchange that supports POP3 and IMAP4 clients, ports 5000-6000 must be open or you will experience connection issues.

• Do Not Use Exchange Virtual Server Menu Options in Cluster Administrator   Upgrade Exchange Virtual Server and Remove Exchange Virtual Server context menu items appear in Cluster Administrator, but they should never be used under any circumstances.
• The Cluster Service account needs to be a member of the Exchange Server administrator group   To use cluster continuous replication (CCR), the cluster service account needs to have Exchange Server Server Administrator permissions.
• Limit the number of storage groups on a CCR cluster   In a CCR environment, we recommend that you limit to between 15 and 30 the number of storage groups and databases.
• Windows Server 2003 Hotfix 921181 required   This hotfix is required for CCR. It adds a file share witness option for a majority node set quorum, and the ability to configure cluster heartbeats. For more information about this hotfix, see Microsoft Knowledge Base article 921181, "An update is available that adds a file share witness feature and a configurable cluster heartbeats feature to Windows Server 2003 Service Pack 1-based server clusters." We recommend reviewing this article in addition to the documentation for CCR.
• Transport dumpster must be manually enabled   The transport dumpster is required for CCR, but it is turned off by default. The transport dumpster is a feature of the Hub Transport server role. The Hub Transport server maintains a queue of mail that was recently delivered to a clustered mailbox server. In the event of a failover that is not lossless, CCR automatically requests every Hub Transport server in the site to resubmit mail from the transport dumpster queue. The information store automatically deletes the duplicates and re-delivers mail that was lost. You can use the Set-TransportConfig cmdlet to activate and configure the Transport Dumpster, which is controlled at the storage group level. We recommend configuring the MaxDumpsterSizePerStorageGroup parameter, which specifies the maximum size of the transport dumpster queue for each storage group, to a size of that is 1.25 times the size of the size of the maximum message that can be sent. For example, if the maximum size for messages is 10 MB, then you should configure the MaxDumpsterSizePerStorageGroup parameter with a value of 12.5 MB. We also recommend configuring the MaxDumpsterTime parameter, which specifies how long an e-mail message should remain in the transport dumpster queue, to a value of 07:00:00, which is 7 days. We believe this is sufficient to allow for an extended outage to occur without loss of e-mail. When using the transport dumpster feature, additional disk space will be needed on the Hub Transport server in order to host the transport dumpster queues. The amount of storage space required is roughly equal to the value of MaxDumpsterSizePerStorageGroup times the number of storage groups.
• Unattended Setup incorrectly continues without cluster service   In an unattended installation, Exchange Setup does not fail if the cluster service is not running. Instead, it installs a standalone node. Before performing the tasks to create a new clustered mailbox server, we recommend that you launch Cluster Administrator and verify that the cluster is online.
• File-already-exists error when using Update-StorageGroupCopy   When using the Update-StorageGroupCopy cmdlet, you might see recurring failures due to a file in the target location. The file is automatically created every 30 seconds. To resolve this issue, delete the file and immediately repeat the task.
• Uninstall fails if the System Attendant is online   The following error message is produced: Error of unknown type occurred while performing exsetdata operation; the original error code was 0xc1037b3f.
• Multiple Exchange Server Administrator groups incorrectly created   Performing New-ClusteredMailboxServer and then Remove-ClusteredMailboxServer repeatedly leaves many Exchange Server Administrator groups in Active Directory.
• Resetting Log Generation Number   LCR and CCR do not correctly handle resets of the log generation number. To reset the log generation numbers in an LCR configuration, we recommend that you disable LCR for that storage group, reset the log generation numbers, and then re-enable LCR for the storage group. In a CCR configuration, avoid this operation.

• MOM 2005 functionality depends on importing the current management pack   You cannot use the Exchange 2007 Management Pack for MOM 2005 unless you can import it into MOM. After you have the MOM 2005 environment installed, you must import the Exchange Management Pack to start monitoring the servers that are running Exchange 2007. For more information, see “How to Import the Exchange Management Pack” later in this document.
• The MOM agent action account needs to run as Local System   The Diagnostic Cmdlets in the Exchange Management Pack will not run unless the MOM Agent Action account on the server that is running Exchange is running as Local System. Open the MOM Administrator Console, locate Administration, Computers, Agent-managed Computers. Right-click the server in question, and then click Update Agent Settings. In the dialog box, under Which account do you want to use for the Agent Action Account, click Local System.
• UM MOM commands does not work   You cannot use Test-UMConnectivity from MOM to monitor remote connectivity without modifying the parameters of the scripts to provide a telephone number and gateway. Currently this funcality does not work. This will be fixed RTM

• Messages with 10 or more attachments bypass RMS   Currently, messages which contain 10 or more attachments will not be RMS-protected by the RMS Policy Application agent. The policy application agent will allow these messages to flow through the system without attempting to apply rights protection to them.
• Unauthenticated messages will not be pre-licensed by RMS   When a message is received from an unauthenticated sender, it will not be pre-licensed by the RMS policy agent.
• Message property loss for RMS messages   Currently, the following message properties will be lost when a message is received that is protected by the RMS policy agent:
  • For follow-up
  • Read receipt
  • Voting button
• Embedded message attachments bypass RMS   The RMS Policy application agent will not protect messages that contain an embedded message as an attachment. The agent allows these e-mail messages to be delivered without attempting to apply rights protection to them.

• Security settings restrict you from viewing .chm files   Enhanced security settings restrict you from viewing a .chm file from a file share. If the Exchange Server setup.exe is accessed remotely, the Help shortcut on the opening screen renders the .chm with a page-not-found error. To fix this issue, copy the exchhelp.chm file from the network share to your local hard drive, and then open the file from the local drive in order to view the help content. For more information, see Microsoft Knowledge Base article 896358, MS05-026: A vulnerability in HTML Help could allow remote code execution.
• Italian message tracking not working   Currently Exchange 2007 Italian servers do not support message tracking because of a localization issue. If you need to perform message tracking on an Italian server, you can manually search the message tracking files.
• Manage all address lists from the Exchange 2007 Management Console   Managing address lists in the Exchange 2003 Exchange System Manager that were created in the Exchange 2007 Management Console will cause errors and could crash Exchange System Manager. You should manage all address lists created inExchange 2007 only from the Exchange Management Console.
• Messages with e-mail messages attachments fail to send   Currently, messages with e-mail message attachments fail to send with a non-delivery report (NDR). This issue occurs for plain text, RTF, and HTML e-mail messages. There is currently no work around for this issue. This issue will be fixed for RTM.
• You must use the Beta 2 Outlook 2007 with Exchange 2007 Beta 2   You must use Office Outlook 2007 Beta 2 if you are using Office 2007 in order for free/busy and meeting suggestions functionality to work. Earlier Outlook 2007 builds are not compatible with Exchange 2007 Beta 2.
• Installing Exchange 2007 will force an OAB download for existing clients   Currently, installing the first server that is running Exchange 2007 in an existing organization forces a full offline address book (OAB) download for clients using offline address lists.
• You cannot administer down-level servers from the Exchange Management Console   You cannot administer servers that are running Exchange Server 2003 or Exchange 2000 Server from the Exchange Management Console, except for tasks that have been documented in this or other documents published on the Microsoft Web site.
• Active Directory Users and Computers should not be used to created Exchange 2007 objects   If the Exchange System Manager is installed, Active Directory Users and Computers will allow you create mailboxes on Exchange 2007 servers. However, this action is not supported. Mailboxes created in this way will be treated as “Legacy” (Exchange 2003 or Exchange 2000) mailboxes, even though they are on an Exchange 2007 server. Exchange 2007 has no recipient update service to update user attributes. Users created in Active Directory Users and Computers would not be fully configured unless there was an Exchange Server 2003 server or Exchange 2000 Server server in the organization that had a recipient update service configured to configure the newly created mailbox.
• You cannot administer Exchange 2007 servers from down-level administration consoles   You cannot administer Exchange 2007 servers from the management console of a server that is running Exchange Server 2003 or Exchange 2000, except for tasks that have been documented in this or other documents published on the Microsoft Web site.
• You cannot set the country property in the Exchange Management Console   You cannot set the country property for a mailbox or contact on the mailbox or contact property pages in the Exchange Management Console. To work around this issue, you can set the country property using Active Directory Users and Computers.
• Manually configure permissions for Exchange 2003 interoperability   When Exchange 2007 is deployed for coexistence and interoperability with Exchange Server 2003, you must manually configure the required permissions. Exch50 data must be sent over an authorized connection.
• ISA rule required when ISA is between users and servers   If you are using Internet Security and Acceleration Server (ISA) between users and Outlook Web Access servers, the ISA Server rule "Verify Normalization" must be turned off to enable Outlook Web Access document access functionality. Exchange 2007 sends double-encoded spaces in document and folder names that contain spaces, which is a behavior that is blocked by ISA Server. For detailed steps to turn off Verify Normalization in ISA Server 2004, see Reverse Proxy Configurations for Windows SharePoint Services and Internet Security and Acceleration Server.
• Fix invalid recipient objects   Beta 2 of Exchange 2007 includes a script that is designed to return information on invalid recipient objects in your Exchange organization and, if possible, attempt to fix them. CheckInvalidRecipients.msh, which is located in the Scripts directory of your Exchange installation, attempts to fix the following two classes of problems:
  • Primary SMTP Address Problems   If a recipient has multiple SMTP addresses listed as their primary SMTP address, or if a user's primary SMTP address is invalid, the script tries to set the user's WindowsEmailAddress as their primary SMTP address. The user's WindowsEmailAddress is the address that Exchange Server 2003 recognizes as the primary address; however, Exchange 2007 does not recognize it.
  • Distribution Group Hidden Membership   If a distribution group has HideDLMembershipEnabled set to true, but ReportToManagerEnabled, ReportToOriginatorEnabled, and/or SendOofMessageToOriginatorEnabled are set to true, the membership is not actually hidden. The script will set ReportToManagerEnabled, ReportToOriginatorEnabled, and SendOofMessageToOriginatorEnabled to false to properly hide the distribution group membership.
• The Change Password at next login setting does not work in the Exchange Management Console   The setting Change password at next logon doesn't work when it is set with the Exchange Management Console. To configure this setting, use Active Directory Users and Computers.
• FQDN of your AD domain required with some commands   You can't enable/connect a mailbox if the domain NetBIOS name is different than the domain DNS name. Use Fully Qualified Domain Name (FQDN) for domain when you are specifying a user using the enable and connect mailbox tasks.
• Term or service name changes   The following terms and service names have changed since Exchange 2007 Beta 1 was released:
  • EdgeTransportSvc is renamed MSExchangeTransport.
  • MSExchMailSubmissionSVc is renamed MSExchangeMailSubmission.
  • ADAM_MSExchangeAdam is renamed ADAM_MSExchange.

This procedure is a workaround for the following known issue:

MOM 2005 functionality depends on importing the current management pack   You cannot use the Exchange Management Pack for MOM 2005 unless you can import it into MOM. After you have the MOM 2005 environment installed, you must import the Exchange Management Pack to start monitoring the servers that are running Exchange 2007.

To import the Exchange Management Pack

These procedures are workarounds for the following known issue:

UM dial plans are set to US English by default   As part of the finalization of deployment that occurs after the setup of the first Exchange 2007 server that is running the UM role, the UM server is added to a UM Dial Plan. The available UM languages (US English plus one other language, depending on installation language, for non-English Exchange versions) are added to the Dial Plan's available languages. However, the default language for the UM Dial Plan is always set to US English, even if the Exchange installation is not English. This setting will be changed for RTM.

Use the Exchange Management Console or the Exchange Management Shell to configure the UM Dial Plan to use the required language.

To set the default dial plan language using the Exchange Management Console

To set the default dial plan language using the Exchange Management Shell

This section provides procedures to workaround the following known issue:

Hub servers in different forests require cross forest configuration   For Exchange Hub Transport servers in different forests to successfully exchange mail, you need a two-way forest trust between the forests and you must configure the access control on both servers to authorize the external forest servers for mail exchange.

This section explains how to use the Exchange Management Console or the Exchange Management Shell to configure Send connectors and Receive connectors to enable cross-forest communication.

To establish direct mail flow between Microsoft Exchange servers in different Active Directory forests, you must configure Send connectors and Receive connectors. The trust level that is required between the domains in the forests and the security settings that are required for the connectors depends on the Exchange Server version of the Exchange organization in each forest and the Active Directory forest functional levels.

This section explains how to configure cross-forest connectors for the following scenarios:

• Exchange Server 2007 to Exchange 2007 with a forest trust
• Exchange 2007 to Exchange 2007 without a forest trust
• Exchange 2007 to Exchange Server 2003

Before You Begin

Verify that your organization meets the prerequisites for each scenario. The prerequisites are listed in the procedures for each scenario.

Verify that the account that you use to perform these procedures has the required administrative group memberships as follows:

• To create an Exchange 2007 SMTP Send connector, you must be an Exchange Organization administrator.
• To create an Exchange 2007 SMTP Receive connector, you must be an Exchange Server Administrator for the server where you will create the connector. 

Exchange 2007 to Exchange 2007 with a Forest Trust

In this scenario, you create the cross-forest connectors between a Hub Transport server in one organization and a Hub Transport server in a second organization. You use the Transport Layer Security (TLS) /Kerberos authentication mechanism to provide mutual authentication and authorization between the servers in different forests. This scenario has the following prerequisites:

• Each Active Directory forest must be at a Windows Server 2003 forest functional level.
• A two-way forest trust must exist between the two forests.
• To restrict the scope of authentication in a forest for users and computers from another forest, you can enable selective authentication. If you have enabled selective authentication, you must confirm that the Exchange Servers security group in the source forest has been granted the Allowed to Authenticate permission on the Exchange servers in the target forest.
• Each forest must have an Exchange organization with Exchange 2007 servers. For more information about Active Directory functional levels, see Active Directory Functional Levels Technical Reference. For more information about Active Directory trusts, see Administering Domain and Forest Trusts.
• To establish mail flow between the forests, follow these steps:

1. Create a Send connector and select Internal as the intended use for this connector.
2. Set permissions on the Send connector.
3. Modify permissions on the default Receive connector for the Hub Transport server.

The following procedure establishes cross-forest mail flow between the Exchange 2007 Hub Transport servers in the Contoso.com and FourthCoffee.com forests. You must perform the procedure in each forest.

To configure cross-forest connectors between Exchange 2007 servers in a trusted forest

Exchange 2007 to Exchange 2007 Without a Forest Trust

In this scenario, you create the cross-forest connectors between the Hub Transport servers in two Active Directory forests that are both running Exchange 2007 but do not have a forest trust relationship. Basic authentication, basic authentication over TLS, or external authentication mechanisms provide authentication and authorization between the servers in different forests when there is no forest trust. This scenario has the following prerequisites:

• Each forest must have an Exchange organization with Exchange 2007 servers.
• If you are using basic authentication, a domain account must exist in each forest to use for basic authentication. For example, provide a user account that has the universal principal name (UPN) FourthCoffee@Contoso.com as the credentials that must be used for authentication by the Exchange servers in the Fourth Coffee domain when sending to the Exchange servers in the Contoso domain.
• If you are using basic authentication over TLS, the target server must be configured to use an X.509 certificate with a FQDN that is the same as the FQDN of the Receive connector.
• If you are using external authentication, a trusted connection must exist between the Hub Transport servers. This connection may be an IPSec (Internet Protocol security) association, or the servers may reside in a trusted physically controlled network.

To establish mail flow between the forests, follow these steps:

1. Create a Send connector.
2. Set permissions on the Send connector.
3. Modify permissions on the Hub Transport server's default Receive connector, or for externally secured connectors, create a new Receive connector.

   Note:
   If you are using basic authentication over TLS, you must provide the FQDN of the remote Hub Transport server in the Smart Host settings. You cannot use an IP address.

The following procedure establishes cross-forest mail flow between the Exchange 2007 Hub Transport servers in the Contoso.com and FourthCoffee.com forests. You must perform the procedure in each forest.

To configure cross-forest connectors between Exchange 2007 servers without a trust relationship by using Basic authentication or Basic authentication over TLS

To configure cross-forest connectors between Exchange 2007 servers without a trust relationship using external authentication

Exchange 2007 to Exchange 2003

In this scenario, you create the cross-forest connectors between an Active Directory forest that is running Exchange 2007 and a second Active Directory forest that is running Exchange 2003. You can create the Send and Receive connectors between the Exchange 2007 Edge Transport server and the Exchange 2003 bridgehead server or between the Exchange 2007 Hub Transport server and the Exchange 2003 bridgehead server.

To establish mail flow between the forests, follow these steps:

1. Create a Send connector and select Legacy as the intended use for this connector on either the Exchange 2007 Edge Transport server or Hub Transport server.
2. Modify the permissions on the default Receive connector on the Exchange 2007 transport server.
3. Create an SMTP connector on Exchange 2003.

The following procedure establishes cross-forest mail flow between the Exchange 2007 transport servers in the Contoso.com forest and the Exchange 2003 bridgehead servers in the FourthCoffee.com forest. After you perform this procedure, we recommend that you test mail flow by sending a message between the two organizations. You should also examine the protocol logs to verify that EXCH50 data is propagated to Exchange 2003.

To configure cross-forest connectors between Exchange 2007 and Exchange 2003 servers in separate forests