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.
.gif) 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.
|