Managing Exchange 2003 Settings in a Coexistence Environment
Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
Applies to: Exchange Server 2007, Exchange Server 2007 SP1, Exchange Server 2007 SP2, Exchange Server 2007 SP3
This topic explains how and where to manage Exchange 2003 features and settings in a Microsoft Exchange Server 2007 and Exchange Server 2003 coexistence scenario.
Administrative Differences
Exchange 2003 uses Administrative Groups to organize Exchange objects for the purposes of delegating permission to manage those objects. Exchange 2007 does not use Administrative Groups as a logical management unit for administrative delegation. However, to support coexistence between Exchange 2003 and Exchange 2007, all Exchange 2007 servers are automatically included in a single Administrative Group when Exchange 2007 is installed. This Administrative Group is recognized in the Exchange System Manager of earlier versions of Exchange as Exchange Administrative Group (FYDIBOHF23SPDLT). Administrative groups are not displayed in the Exchange Management Console in Exchange 2007.
Warning
Do not move Exchange 2007 servers out of Exchange Administrative Group (FYDIBOHF23SPDLT) and do not rename Exchange Administrative Group (FYDIBOHF23SPDLT) by using a low-level directory editor. Exchange 2007 must use this administrative group for configuration data storage. We do not support moving Exchange 2007 servers out of Exchange Administrative Group (FYDIBOHF23SPDLT) or renaming of Exchange Administrative Group (FYDIBOHF23SPDLT).
Exchange System Manager Features
In Exchange 2003 and Exchange 2007 coexistence scenario, the following functionality applies to the Exchange System Manager:
You cannot use Exchange System Manager to manage Exchange 2007 features. You can use only the Exchange Management Console or the Exchange Management Shell.
You can delete or remove Exchange 2003 features by using the Exchange Management Console or the Exchange Management Shell, but you cannot create Exchange 2003 objects. However, some Exchange 2003 objects can be edited from Exchange 2007.
For more information, see Planning for Coexistence.
Organization Settings
The following table lists organization settings for Exchange System Manager and where you should manage them. In some cases, you can edit Exchange 2003 features from both Exchange 2003 and Exchange 2007. Any feature name changes are displayed in the "Exchange 2007 Equivalent Name" column. If the name has not changed, or if the feature has been deprecated, the field contains "NA".
| Exchange 2003 Feature | Exchange 2007 Equivalent Feature Name | Can be administered from Exchange 2007 | Can be administered from Exchange 2003 | Comments |
|---|---|---|---|---|
Delegate Control |
NA |
No |
Yes |
Delegation control rights for Exchange 2003 must be administered in Exchange 2003. |
Internet Mail Wizard |
NA |
No |
Yes |
In cases where an Exchange 2007 Edge Transport server is identified, this feature will not work. |
Stop Public Folder Content Replication |
NA |
Yes |
Yes |
Exchange Server 2003 Service Pack 2 and later will use this setting. |
Global Settings
The following table lists Exchange 2003 features in the global settings of Exchange System Manager and where you should manage them in an Exchange 2003 and Exchange 2007 coexistence scenario. In some cases, you can edit Exchange 2003 features from both Exchange 2003 and Exchange 2007. Any feature name changes are displayed in the "Exchange 2007 Equivalent Name" column. If the name has not changed, or if the feature has been deprecated, the field contains "NA".
| Exchange 2003 Feature | Exchange 2007 Equivalent Feature Name | Can be administered from Exchange 2007 | Can be administered from Exchange 2003 | Comments |
|---|---|---|---|---|
Internet Message Format |
Remote Domains |
Yes |
Yes |
This feature is directly replaced by the Remote Domains feature in Exchange 2007. The feature can be managed from either version of Exchange. However, after they have been edited by Exchange 2007, the object is considered upgraded and cannot be edited by Exchange 2003. |
Message Delivery Properties - Sender Filtering, Recipient Filtering |
Sender Filtering and Recipient Filtering |
No |
Yes |
The Exchange 2003 global message delivery settings are replaced by new entries in Exchange 2007. These settings are managed in the Exchange Management Console on an Edge Transport server or in the Exchange Management Shell on a Hub Transport server. |
Message Delivery Properties - Connection Filtering |
IP Allow List, IP Block List, IP Allow List Providers, IP Block List Providers |
Yes |
No |
The Exchange 2003 global message delivery settings are replaced by new entries in Exchange 2007. These settings are managed in the Exchange Management Console on an Edge Transport server or in the Exchange Management Shell on a Hub Transport server. |
Intelligent Mail Filter — Gateway Blocking Threshold |
Edge Transport Server Content Filtering - Actions |
No |
Yes |
Exchange 2003 stores the Intelligent Mail Filter threshold and action configuration in a different location than Exchange 2007. Therefore, each Exchange server's threshold actions must be maintained separately as two independent settings. |
Intelligent Mail Filter Store Junk E-Mail Configuration settings |
Set-OrganizationConfig SCLJunkThreshold |
Yes |
Yes |
This property can be maintained from either Exchange 2007 or Exchange 2003. |
Sender ID Filtering |
NA |
No |
Yes |
There is no interoperability of this feature. Exchange 2003 objects must be maintained in Exchange 2003 and Exchange 2007 objects must be maintained in Exchange 2007. |
Mobile Services |
NA |
No |
Yes |
In Exchange 2007 Outlook Mobile Access, Always-up-to-date (AUTD) System Management Server SMS, Exchange ActiveSync, and DirectPush have been moved into each of the respective sections in the Exchange Management Console for the Client Access servers. Exchange 2003 objects must be maintained by Exchange 2003 and Exchange 2007 objects must be maintained in Exchange 2007. |
Recipients
The following table lists where you should change Exchange System Manager recipient features in an Exchange 2003 and Exchange 2007 coexistence scenario. In some cases, you can edit Exchange 2003 features from Exchange 2003 and Exchange 2007. Any feature name changes are displayed in the "Exchange 2007 Equivalent Name" column. If the name has not changed, or if the feature has been deprecated, the field contains "NA".
| Exchange 2003 Feature | Exchange 2007 Equivalent Feature Name | Can be administered from Exchange 2007 | Can be administered from Exchange 2003 | Comments |
|---|---|---|---|---|
Details Templates and Address Templates |
NA |
No |
Yes |
Exchange server's details and addresses templates must be maintained separately as two independent settings. |
Global Address List / Address Lists |
NA |
Yes |
Yes |
You can edit global address list (GAL) and address list objects from Exchange 2003 or Exchange 2007. However, you must upgrade Exchange 2003 objects before they be edited by Exchange 2007. After you upgrade the object, it cannot be edited by Exchange 2003. |
Offline Address Book |
NA |
Yes |
Yes |
You can edit the Exchange 2003 offline address book (OAB) from Exchange 2003 or Exchange 2007. However, to administer the OAB from Exchange 2007, it must be moved to the Exchange 2007 server by using the Exchange 2007 tools. When the object has been moved to Exchange 2007, the object is considered upgraded and cannot be edited by Exchange 2003 unless it is moved back to Exchange 2003 by using the Exchange 2007 tools. |
Offline Address Book - Rebuild Action |
Update-OfflineAddressBook |
Yes |
Yes |
You can use Exchange Server 2003 or 2007 to update or rebuild the Exchange server 2003 offline address book. In addition, you can trigger the update or rebuild action of an Exchange 2007 offline address book from Exchange 2003. |
Recipient Update Service |
Udate-AddressList and Update-EmailAddressPolicy |
No |
Yes |
The Recipient Update Service does not exist as a service for Exchange 2007; therefore, you cannot configure an Exchange 2007 server as a Recipient Update Service server. However, Exchange 2007 servers will show up in the list of Recipient Update Service servers because the filter searches for all Exchange servers that are not front-end servers. Setting an Exchange 2007 server as a Recipient Update Service server will cause the Recipient Update Service to cease functioning. |
Recipient Policies |
E-mail Address Policy and Accepted Domains |
See Comment |
See Comment |
In Exchange 2003, the recipient policy object defines both the proxy addresses that are stamped onto the recipient objects and the set of domains for which e-mail is accepted into the organization for an authoritative domain. In Exchange 2007, these two concepts are separated into E-mail Address Policies and Accepted Domains. They are completely separate settings in Exchange 2007; however, any accepted domains will be available to the e-mail address policy. Note If you have any Exchange 2003 or Exchange 2000 recipient policies that have not been applied, making any change to an Exchange 2003 or Exchange 2000 mailbox by using Exchange 2007 tools will force the recipient policies to be re-evaluated and applied to the mailbox. Examples these changes include moving mailboxes by using the Exchange 2007 Move Mailbox wizard or the Move-Mailbox cmdlet or setting properties by using the Set-Mailbox cmdlet. Before you make changes to an Exchange 2003 or Exchange 2000 mailbox, make sure that you want to apply all of the existing recipient policies. If you have an existing recipient policy that you do not want to apply, clear the Automatically update e-mail address based on e-mail address policy check box in Active Directory Users and Computers. For more information, see the Exchange Server Team Blog article Yes, Exchange 2007 really enforces Email Address Policies. |
Recipient Policies |
Accepted Domains |
Yes |
No |
You can add recipient policies from Exchange 2003; however, accepted domains must be manually added as Exchange 2007 acceptable domains or they will not be routable. If you add a new accepted domain in Exchange 2007, you must manually add any accepted domains from Exchange 2007 into Exchange 2003 recipient policies to be able to have Exchange 2003 servers route for them. Note The Exchange Best Practices Analyzer can calculate which objects are mismatched and provide a warning. |
Recipient Policies |
E-mail Address Policy |
Yes |
Yes |
E-mail address policies can be edited from Exchange 2003 or Exchange 2007. However, to administer the e-mail address policy from Exchange 2007, you must first upgrade the object. When the e-mail address policy has been upgraded, it cannot be edited from Exchange 2003. If you add a new e-mail address policy in Exchange 2007, you must link it to an existing Exchange 2007 accepted domain. This ensures that all routing created in Exchange 2007 will be properly reflected by Exchange 2003. Although Exchange 2007 ignores the fact that the e-mail address policy implies an accepted domain, Exchange 2003 does not. Note The Exchange Best Practices Analyzer can calculate which objects are mismatched and provide a warning. |
Recipient Policy - "Apply this policy now" action |
E-mail Address Policy - Update-EmailAddressPolicy |
Yes |
Yes |
The stamping behavior for Exchange 2003 Recipient Update Service is different than address provisioning in Exchange 2007. If the change is made in Exchange 2003, then the change will not take effect until the Recipient Update Service applies the changes to the objects. If the change is made in Exchange 2007, then Exchange 2007 will always stamp the updated proxy addresses after the policy is changed. |
Mailbox Manager Policy |
N/A |
Yes |
Yes |
Although the Exchange 2007 mailboxes are stamped with the mailbox manager policy, processing against these Exchange 2007 mailboxes does not take place. |
Servers
The following table lists where you should change Exchange 2003 server features. Any feature name changes are displayed in the "Exchange 2007 Equivalent Name" column. If the name has not changed, or if the feature has been deprecated, the field will contain "NA".
Note
Although you will be able to see the Exchange 2007 servers in Exchange System Manager, you will not be able to edit or delete any Exchange 2007 objects.
| Exchange 2003 Feature | Exchange 2007 Equivalent Feature Name | Can be administered from Exchange 2007 | Can be administered from Exchange 2003 | Comments |
|---|---|---|---|---|
Queues |
Queue Viewer |
No |
Yes |
The Exchange System Manager queue viewer functionality uses Windows Management Instrument (WMI), which has been removed from Exchange 2007. Therefore, Exchange System Manager queue viewer will not work against an Exchange 2007 server. However, you will still be able to view Exchange 2007 servers in the Exchange 2003 Queue Viewer. If you attempt to access the connection, you will receive an error stating that Exchange “failed to retrieve the queues”. |
Storage Group |
NA |
No |
Yes |
You must use Exchange System Manager to maintain the Exchange 2003 storage group settings. |
Mailbox Store |
NA |
No |
Yes |
You must use Exchange System Manager to maintain the Exchange 2003 mailbox store settings. |
Public Folder Store - |
NA |
No |
Yes |
You must use Exchange System Manager to maintain the Exchange 2003 public folder store settings |
Protocols - X.400 Connectors and Mail Transfer Agent (MTA) Object |
NA |
No |
Yes |
X.400 connectors and the MTA object in Exchange System Manager are deprecated in Exchange 2007. However, because the configuration is ignored by Exchange 2007 servers, you can use Exchange System Manager to manage X.400 connectors and MTA objects that are located in Exchange 2003 routing groups. |
SMTP Virtual Server |
Receive Connector |
No |
Yes |
SMTP virtual servers are deprecated in Exchange 2007. However, you can use Exchange System Manager to manage SMTP virtual servers that are configured on Exchange 2003 servers. |
SMTP Virtual Server - Resolve anonymous e-mail |
Receive Connector - externally secured with Exchange Servers permission group configured |
No |
Yes |
You can create an Exchange 2007 object that has the same functionality as an Exchange 2003 SMTP virtual server that is configured to resolve anonymous e-mail. Create a new Receive connector, or modify an existing Receive connector, on an Exchange 2007 Hub Transport server. Configure the Receive connector to assign the Exchange Servers permission group and to use Externally Secured as the authentication mechanism. |
Routing Groups
Exchange 2003 uses routing groups and routing group connectors to determine an intra-organizational routing topology. Exchange 2007 uses Active Directory sites and IP site links to determine an intra-organizational routing topology. However, to support coexistence between Exchange 2003 and Exchange 2007, all Exchange 2007 servers are automatically included in a single routing group when Exchange 2007 is installed. In previous versions of Exchange, this routing group is recognized in Exchange System Manager as Exchange Routing Group (DWBGZMFD01QNBJR). In Exchange 2007, routing groups are not displayed in the Exchange Management Console.
Warning
Do not move Exchange 2007 servers out of Exchange Routing Group (DWBGZMFD01QNBJR) and do not rename Exchange Routing Group (DWBGZMFD01QNBJR) by using a low-level directory editor. Exchange 2007 must use this routing group for communication with earlier versions of Exchange. We do not support moving Exchange 2007 servers out of Exchange Routing Group (DWBGZMFD01QNBJR) or renaming of Exchange Routing Group (DWBGZMFD01QNBJR).
Note
You can set most Exchange 2007 message size limits by using the Exchange Management Console or the Exchange Management Shell. However, some message size limits are not visible by using the Exchange Management Console or the Exchange Management Shell. For more information, see How to Modify Exchange 2003 Global Message Size Limits in Exchange 2007 RTM.
The following table lists Exchange 2003 routing group objects and where they should be managed in an Exchange 2003 and Exchange 2007 coexistence scenario.
| Exchange 2003 Feature | Exchange 2007 Equivalent Feature Name | Can be administered from Exchange 2007 | Can be administered from Exchange 2003 | Comments |
|---|---|---|---|---|
Routing Group |
NA |
No |
Yes |
The Exchange Routing Group (DWBGZMFD01QNBJR) cannot be modified. It can contain only Exchange 2007 servers. Placing Exchange 2003 and Exchange 2007 servers in the same routing group is not supported. |
Routing group connectors |
Routing group connectors |
Yes |
Yes |
A routing group connector that is configured to use an Exchange 2007 server as a source or target server cannot be managed by using Exchange System Manager. If an Exchange 2007 server is specified in the routing group connector configuration, you must use the New-RoutingGroupConnector and Set-RoutingGroupConnector cmdlets in the Exchange Management Shell. |
SMTP Connectors |
Send Connectors |
No |
Yes |
Because of differences in schema configuration, you must manage these connectors by using the tools specific to the server version on which the connector is created. You cannot apply Exchange 2007 Send connector settings to Exchange 2003 SMTP connectors. Exchange 2007 also does not recognize Exchange 2003 SMTP connector settings that do not exist in Exchange 2007. For more information, see Message Routing in a Coexistence Environment. |
Exchange 2003 Active Directory Users and Computers Settings
In an Exchange 2003 and 2007 coexistence scenario, the following applies to Active Directory Users and Computers in Exchange 2003:
Exchange 2007 mailbox features cannot be managed from the Exchange 2003 Active Directory Users and Computers.
All Exchange 2003 objects can be managed from Exchange 2003 Active Directory Users and Computers.
User and InetOrgPerson Properties
The following table lists where you should change the User and InetOrgPerson properties in an Exchange 2003 and Exchange 2007 coexistence scenario. Any feature name changes are displayed in the "Exchange 2007 Equivalent Name" column. If the name has not changed, or if the feature has been deprecated, the field will contain "NA".
| Exchange 2003 Active Directory Users and Computers Feature | Exchange 2007 Equivalent Feature Name | Can be administered from Exchange 2007 | Can be administered from Exchange 2003 |
|---|---|---|---|
Outlook Mobile Access: Enable or Disable |
Exchange ActiveSync |
No |
Yes |
ActiveSync and Up-to-Date Notifications |
Exchange ActiveSync |
No |
Yes |
Protocols - Outlook Web Access, POP3, and IMAP4: Enable or Disable |
NA |
No |
Yes |
Mailbox Rights |
Set-MailboxPermission |
No |
Yes |
Delivery Restrictions |
Set-MailboxPermission |
No |
Yes |
Delivery Options |
Set-MailboxPermission |
No |
Yes |
Storage Limits |
Set-MailboxPermission |
No |
Yes |
User and InetOrgPerson Exchange Tasks
The following table describes where you should change the User and InetOrgPerson tasks in an Exchange 2003 and Exchange 2007 coexistence scenario. If there has been a feature name change, then the Exchange 2007 name of the feature is displayed in the "Exchange 2007 Equivalent Name" column.
Note
To move mailboxes from Exchange 2003 directly to Exchange 2007, you can use the Move Mailbox wizard or the Move-Mailbox cmdlet. You cannot use the Exchange System Manager or Active Directory Users and Computers to move mailboxes from Exchange 2003. For more information about moving mailboxes across mailbox databases, see Moving Mailboxes.
| Exchange 2003 Active Directory Users and Computers Feature | Exchange 2007 Equivalent Feature Name | Can be administered from Exchange 2007 | Can be administered from Exchange 2003 |
|---|---|---|---|
Establish E-mail Address |
Enable-Mailbox |
No |
Yes |
Enable Mailbox |
Enable-Mailbox |
No |
Yes |
Delete Mailbox |
Disable-Mailbox |
No |
Yes |
Configure Exchange Features |
Set-Mailbox or New-Mailbox |
No |
Yes |
Remove Exchange Attributes |
Disable-Mailbox |
No |
Yes |
Contact Actions
The following table describes where you should change contact actions in an Exchange 2003 and Exchange 2007 coexistence scenario. If there has been a feature name change, then the Exchange 2007 name of the feature is displayed in the "Exchange 2007 Equivalent Name" column.
| Exchange 2003 Active Directory Users and Computers Feature | Exchange 2007 Equivalent Feature Name | Can be administered from Exchange 2007 | Can be administered from Exchange 2003 |
|---|---|---|---|
Establish E-Mail Address |
Enable-MailContact |
No |
Yes |
Delete E-Mail Addresses |
Disable-MailContact |
No |
Yes |
Remove Exchange Attributes |
Disable-mailContact |
No |
Yes |
Group Properties and Actions
The following table describes where you should change group properties and actions in an Exchange 2003 and Exchange 2007 coexistence scenario. If there has been a feature name change, then the Exchange 2007 name of the feature is displayed in the "Exchange 2007 Equivalent Name" column.
| Exchange 2003 ADUC Feature | Exchange 2007 Equivalent Feature Name | Can be administered from Exchange 2007 | Can be administered from Exchange 2003 |
|---|---|---|---|
Add E-mail Addresses |
NA |
Yes |
Yes |
Delete E-mail Addresses |
NA |
Yes |
Yes |
Add Query-Based Distribution Group to the Group |
NA |
Yes |
Yes |
Add Public Folder to the Group |
NA |
Yes |
Yes |
For More Information
For more information about feature name changes between Exchange 2003 and Exchange 2007, see Discontinued Features and De-Emphasized Functionality in Exchange 2007
For more information about coexistence, see the following topics: