Topic Last Modified: 2008-05-15
See the "Legal Notice" section later in this document for important information.
Welcome to Microsoft Exchange Server 2007. This document contains the following sections:
- Release Notes for Exchange Server 2007 Management
Pack for Microsoft Operations Manager
- Known Issues
- Workarounds for Selected Known Issues
- Legal Notice
Release Notes for Exchange Server 2007 Management Pack for Microsoft Operations Manager
The release notes for the Microsoft Exchange Server 2007 Management Pack for Microsoft Operations Manager are available as a stand-alone .htm file from the Microsoft Exchange Server 2007 Management Pack for Microsoft Operations Manager Web page.
In this release of Exchange 2007, known issues are described in the following sections:
- Setup Issues that affect setup,
upgrade, or are affected by setting up a new Exchange 2007
- Windows Server Issues related to a
specific build of Microsoft Windows Server, or that will
affect a Windows server.
- Unified Messaging Issues related to the
Unified Messaging (UM) server role.
- Mailbox Issues related to the Mailbox
- Client Access Issues related to the
Client Access server (CAS) role.
- Edge and Hub Transport Issues related
to the Hub Transport or Edge Transport server roles.
- Single Copy Clusters Issues related to
single copy clusters (SCC).
- Cluster Continuous Replication and Local Continuous
Replication Issues related to cluster
continuous replication (CCR) and local continuous replication
- Miscellaneous Issues not related to a
particular product, feature, or server role.
- Setup does not support commas at the command
line Setup does not support the use of commas
in network names at the command line. To work around this issue,
specify a network name with a comma in an answer file.
- Manual steps needed to remove the last Exchange 200x
server You must take some steps to remove the
last Exchange 2000 or 2003 server from your organization. See "How
to Remove the Last Exchange 200X server" later in this
Note: Features that were available in Exchange 2003 and Exchange 2000 are not available in Exchange 2007. You should be familiar with the changes in functionality before you remove the last Exchange 2000 or 2003 server from the organization. For the complete list of changes, see Discontinued Features and De-Emphasized Functionality.
- Upgrade from previous versions of Exchange 2007 not
supported Upgrades from previous versions of
Exchange 2007 (formerly Exchange "12"), such as Beta 2,
are not supported unless noted by your involvement in a prerelease
program such as the Rapid Deployment Program (RDP). You must
uninstall previous versions of Exchange 2007, and then install
the original release (RTM) version of Exchange 2007.
- Administration tools-only upgrades from previous builds of
Exchange 2007 not supported Upgrading the
Exchange 2007 administration tools from previous versions of
Exchange 2007 is not supported. To upgrade the administration
tools, you must uninstall and then reinstall the RTM version of
- Windows 2003 Enterprise Edition required for clustered
servers Microsoft Windows Server 2003,
Enterprise Edition is required to use the cluster continuous
replication and single copy cluster features in
- 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 at least
Exchange Server 2003 Service Pack 2 installed.
- Exchange 2000 Server servers in your organization
must have at least Exchange 2000 Server Service Pack 3
- No Exchange Server 5.5 servers are in the forest.
- 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 with
Exchange 2007 object versioning. Without the update rollup,
the Exchange 2000 Exchange System Manager is versioning
unaware. 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, such as computers running Microsoft Windows XP, you should also install the latest Exchange 2000 Server Post-Service Pack 3 (SP3) Update Rollup on those computers also.
- 64-bit version of msclus.dll required to administer an
Exchange 2007 cluster Installing the 64-bit
administration pack on Microsoft Windows XP installs the
32-bit version of msclus.dll, not the 64-bit version. The
Exchange 2007 administration tools require the 64-bit version.
To work around this issue, copy "%systemroot%\system32\msclus.dll"
from a 64-bit Windows Server 2003 server to the same
location on the 64-bit Windows XP machine and run "regsvr32
- 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.
- 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 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.
- Installing or running the RTM version of Exchange 2007 on
computers that are running the Windows Server 2008
operating system is not supported. Consider the following when you
are planning to deploy Windows Server 2008 in your
- It is not supported to upgrade your operating system to
Windows Server 2008 and then upgrade Exchange 2007
to Exchange 2007 SP1.
- It is also not supported to upgrade Exchange 2007 to
Exchange 2007 SP1 and then upgrade your operating system to
Windows Server 2008.
- To deploy Exchange 2007 SP1 on
Windows Server 2008, you must install
Windows Server 2008 on a computer that does not have
Microsoft Exchange installed, and then install
Exchange 2007 SP1.
For information about Exchange 2007 SP1, visit the Microsoft Exchange Server 2007 SP1 Release Notes Web page.
- It is not supported to upgrade your operating system to Windows Server 2008 and then upgrade Exchange 2007 to Exchange 2007 SP1.
- Inbound faxes might not be received or received as
incomplete when the fax is sent using certain fax
machines Inbound faxes might not be received
or received as incomplete when the fax is sent using certain fax
machines and is routed through an AudioCodes gateway. To fix this
issue, change the configuration file for the gateway and set the
baud rate to 9600 instead of the default 14400. To change this
setting, see the AudioCodes documentation at the
Microsoft Exchange 2007 UM Resource Page at http://www.audiocodes.com/content.aspx?voip=2331.
Note: The third-party Web site information in this topic is provided to help you find the technical information you need. The URLs are subject to change without notice.
- Cannot add, remove, or change extensions to a UM-enabled
user After enabling a user for Unified
Messaging with one extension, you cannot add, remove, or change
extensions. You may want to change extensions for a user if they
are migrating from a test to a production environment, and you may
want to add extensions to a user if you wanted to add a secondary
or fax number. You can effectively change the extension by running
disable-UMMailbox on the user and then running
Enable-UMMailbox with the new extension and/or additional
extensions. See the following Exchange Management Shell
Enable-UMMailbox -identity:<user> -extensions:<ext1>, <ext2>, ...
Note: After this command has been run, the user's UM mailbox PIN will be reset.
- UM might crash when a gateway name is not formatted
correctly When running Unified Messaging in
Session Initiation Protocol (SIP)-secured mode, the Unified
Messaging worker process may crash. This situation occurs if there
is a gateway with an IP address that resolves to a fully
qualified domain name (FQDN) that matches another gateway or
Exchange server with a name not entirely in lower-case characters.
In this situation, existing phone calls will be dropped. The
workaround is to specify an FQDN in all lower-case characters
instead of using an IP address when using the
new-UMIPGateway cmdlet and running in SIP-secured mode.
- Removal of the System Attendant mailbox causes 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.
- Registry key settings required to support self-signed SSL
certificates over multiple CAS servers
Exchange 2007 installs with a default self-signed Secure
Sockets Layer (SSL) certificate. You can use this certificate when
enabling SSL for Exchange ActiveSync,
Microsoft Office Outlook Web Access, and the
Availability service; however, users will receive a prompt because
the certificate is considered invalid by most client applications.
Exchange ActiveSync and Microsoft Office
Outlook Web Access support proxying from one Client
Access server to another Client Access server. In order for
proxying to be successful when a self-signed certificate is used,
you must configure the following registry keys as shown:
Caution: Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Problems resulting from editing the registry incorrectly may not be able to be resolved. Before editing the registry, back up any valuable data.
- HKLM\System\CurrentControlSet\Services\MSExchangeOWA\AllowInternalUntrustedCerts = 1
- Internet Explorer 7 page zoom feature can cause errors with
Outlook Web Access Using the
Windows Internet Explorer 7.0 page zoom feature with the
Exchange Server 2007 version of
Office Outlook Web Access causes the insertion point
to display incorrectly on the screen. This can cause unexpected
behavior. To work around this issue, change the font size instead
of using the zoom feature in Internet Explorer 7.0.
- Domain Controller hotfix required if Exchange 2007 is
connected 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 Client Access
server is connected to a domain controller running a non-English
version of Windows, you must install the hotfix described in
Knowledge Base article 919166 on your domain controller. Without
this hotfix, address book operations in
Outlook Web Access will fail if your users' User
Interface locale setting is different from the domain controller
culture. See Knowledge Base article 919166, The address book function on Exchange 12 is
broken when the Exchange OWA client and the Windows Server
2003-based domain controller do not have the same locale
Edge and Hub Transport
- A subscribed Edge Transport server might not appear as
licensed to the Exchange organization For Edge
Transport servers to appear licensed, the license key must be
applied on the Edge Transport server before the Edge Subscription
is created. If the license key was applied after subscription, you
must remove the Edge Subscription from both the Edge Transport
server and the Active Directory site and start the
subscription process from the beginning.
- EdgeSync issues when all Hub Transport 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 Edge
server(s), you must remove the Edge Subscriptions in the
organization and on each Edge server. Then, perform the
subscription process again.
Single Copy Clusters
- Running the New-Mailbox cmdlet on a single copy cluster with
more then two active nodes When a single copy
cluster with more than two active clustered mailbox servers is
deployed, the New-Mailbox cmdlet fails on at least one of
the clustered mailbox servers. Specifically, the New-Mailbox
cmdlet fails with the following message:
Error: A proxy generator DLL on server <servername> could not be found or failed to initialize. Proxy addresses for the current recipient cannot be calculated. Please ensure that all the proxy address generator DLLs have been installed on the target server.
The failure is the result of a missing object in Active Directory. The object is correctly created for the first clustered mailbox server that is created in the cluster, but the object is not correct for subsequent mailbox servers. You can fix the issue by manually creating the object as described in Knowledge Base article How to enable mailbox creation on the second or later clustered mailbox server (CMS) of an Exchange 2007 Single Copy Cluster (SCC)
Note: You may experience the same problem on all clustered mailbox servers if you delete the first clustered mailbox server and then add a different clustered mailbox server back. Even when experiencing this problem, the Move-Mailbox cmdlet functionality works correctly. Therefore, users can be moved to the server without issue.
Cluster Continuous Replication and Local Continuous Replication
- Multiple Exchange Server Administrator groups incorrectly
New-ClusteredMailboxServer and then
Remove-ClusteredMailboxServer repeatedly leaves many
Exchange Server Administrator groups in
- Error with event ID 7005 is by
design This error can be ignored. The
Microsoft Exchange Transport Log Search service
(MSExchangeTransportLogSearch) logs error event ID 7005
(ComputerNameNotCurrentlyAvailableException) every 10 minutes on
the passive node in a cluster. This action occurs because
MSExchangeTransportLogSearch can't obtain the configuration of a
clustered mailbox server. On clustered nodes, the Mailbox server
name is not the same as Environment.MachineName Therefore,
MSExchangeTransportLogSearch can't find the local server, which is
what is used to perform message tracking searches. The transport
log search service works only on the active node; on the passive
node, it just waits to become active.
- Get-StorageGroupCopyStatus can report incorrect
status In the following scenarios,
Get-StorageGroupCopyStatus reports a status of healthy even
when the status is not healthy:
- Logical database corruption occurs, resulting in the database
being unmountable on both the active and passive nodes.
- No backup is available for some reason; therefore, at the file
system level, all database-related files are deleted on both nodes
of the cluster and a new, blank database is mounted. Alternatively,
an old backup is restored, but the entire set of logs required to
bring the database fully up-to-date is missing. In either case, the
log generation on the active node lags behind what the passive node
is expecting, so the passive node keeps waiting for the "next" log
file to show up.
In these situations, Get-StorageGroupCopyStatus shows the database as healthy, when no data is present on the passive node. Restarting the Microsoft Exchange Replication Service will cause the health status to be reported correctly.
- Logical database corruption occurs, resulting in the database being unmountable on both the active and passive nodes.
- SMTP Bytes sent performance counter is not counting every
byte sent The SMTP Bytes sent performance
counter does not count correctly the message bytes; it is counting
only the protocol conversation and it is not counting Transport
Layer Security (TLS) information. Message bytes are the bytes in a
message (for example, just message size).
- Build version numbers vary The
Exchange Server 2007 RTM build version number is 685.25.
When you view the version in the Exchange Management Console or in
the AdminDisplayVersion property of Exchange Server in
the Exchange Management Shell, they show the version as 685.24
instead of 685.25. When you view the Exchange version in the
Registry, it shows 685.25. In addition, the Microsoft Operations
Manager (MOM) shows the Exchange servers as 685.25. Outlook
indicates that you're connected to 685.24. These inconstancies are
by design and can be ignored.
- Setting the GzipLevel property of Outlook Web Access to High
causes compressed attachments to become
corrupt Compressed files (for example, .zip
files) accessed through Microsoft Windows SharePoint will also be
corrupt if Windows SharePoint and the Exchange CAS role are
installed on the same machine, and the Outlook Web Access
GzipLevel property is set to High. If your users do not
access compressed files, it is acceptable to set the GzipLevel
property to High (for example,
set-owavirtualdirectory -identity <OWA_Site> -GzipLevel High). If your users do work with compressed files, either disable compression (set GzipLevel to Off), or leave it at its default value of Low. Installing SharePoint and the Exchange CAS role on the same server is not recommended.
- After you install Microsoft .NET Framework 2.0 Update for
Exchange 2007, scripting and macros functionality might not work
correctly for VSA or macros in Visual
Studio If you have installed Microsoft .NET
Framework 2.0 Update for Exchange 2007 and are working with
applications using either Microsoft Visual Studio for
Applications (VSA) or macros in Microsoft Visual Studio
with Exchange 2007, scripting and macros functionality might
not work correctly. The issue occurs because the VSA component DLLs
cannot be launched correctly. An update is available for this
issue. To run VSA/Visual Studio Macros applications, download the
VSA Runtime hotfix (FIX: Custom applications that use the Visual
Studio for Applications Visual Basic Runtime may be unable to
compile macros or to run macros ). To create, debug, or compile
macros by using VSA or Visual Studio, also download the appropriate
design-time hotfix, FIX: You cannot run a macro in Visual Studio
- The event log entry with the source MSExchangeTransport and
event ID 1036 is inaccurate The current text
of event ID 1036 states "Inbound direct trust certificate with
thumbprint %1 has expired. Run New-ExchangeCertificate to generate
a new direct trust certificate." The event should state "The
default TLS certificate for the server has been superseded but the
new certificate has not been enabled for SMTP. Please run
Enable-ExchangeCertificate to enable the new certificate for
- Serbian-Latin (Sr-Latn-CS) is not supported in Exchange
2007; only Serbian-Cyrillic (Sr-Cyrl-CS) is
supported The Exchange 2007 Beta 2
release stated that both languages would be supported.
Serbian-Latin (Sr-Latn-CS) is not supported in Exchange 2007.
Only Serbian-Cyrillic (Sr-Cyrl-CS) is supported.
- SCW registration will fail on non-English versions of
Exchange 2007 running on Windows MUI
mode Security Configuration Wizard (SCW)
registration is necessary to use SCW with Exchange 2007 on
Windows Multilingual User Interface (MUI) Pack mode. SCW
registration will fail on a server that has a non-English version
of Exchange 2007 installed. To work around this issue, open
Exchange2007.xml and Exchange2007Edge.xml files in the
<installdir>\scripts folder and then change the
LocaleID setting to "0409" within
the SCWLocalization tag.
- Unlimited message size limits ignored and set to Exchange
2007 defaults on
upgrade Exchange Server 2003 message
limits are set to Exchange 2007 default values after the first
Exchange 2007 server is installed if the Exchange 2003
message limits were set to unlimited.
- Exchange Server Administrators rights are required to
operate the Exchange Queue
Viewer Exchange Server Administrators
rights are required to operate the Queue Viewer. You must log on by
using a domain account that has the permissions assigned to the
Exchange Server Administrators role. The account must also be
a member of the local Administrators group on the computer on which
you are running the Queue Viewer.
- The export command syntax documented in the Help topic, "How
to Deploy Message Classification for Outlook 2007" is
incorrect The export command syntax documented
in the Exchange 2007 Help topic "How to Deploy Message
Classification for Outlook 2007" is incorrect. In addition, the
message classification export functionality has been updated. The
correct information is as follows:
- To export all existing message classifications to a
Classifications.xml file, run the following command:
- To export all existing message classifications of a specific
locale to a Classifications.xml file, run the following command,
where "en" is the locale code:
./Export-OutlookClassification.ps1 -Locale "en" >Classifications.xml
Note: You cannot pipe specific message classification instances to the Export-OutlookClassification.ps1 script. To remove specific message classifications, you must manually remove the instances from the Classifications.xml file.
- To export all existing message classifications to a Classifications.xml file, run the following command:
- Exchange ActiveSync should be disabled for users on a dial
tone database When a mobile device
synchronizes to a dial tone database, duplicate items can be
created in the user's mailbox. You should disable
Exchange ActiveSync for users whose mailboxes are in a dial
tone database. The following Exchange Management Shell command is
an example of how to disable Exchange ActiveSync for a single
Set-CASMailbox <user_name> -ActiveSyncEnabled:$False
- Exchange Server Administrators group should be Exchange
Server Administrators role Several Help topics
currently state "To perform the following procedures...you must log
on by using a domain account that has the permissions assigned to
the Exchange Server Administrators group." There is no such
security group. Instead, the required permissions are that the
account has to be a member of the Exchange Server Administrators
role. You can grant this role to a user or group by using the
Add-ExchangeAdministrator cmdlet in the Exchange Management
Shell. You can also grant this role by using the Add Exchange
Administrator Wizard in the Exchange Management Console.
- The "User must change password at next logon" check box does
not reflect changes if "Password never expires" is set to
true In Active Directory Users and
Computers, if you select User must change password at next
logon and the Password never expires check box is also
selected and then you click Apply, a warning message is
shown and the user will not be required to change the password at
next logon. Currently, when you change the User must change
password at next logon setting in the Exchange Management Shell
and the Exchange Management Console and Password never
expires is selected, the change is ignored, but no warning is
- 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 to view the Help. For more information,
see Knowledge Base article 896358, MS05-026: A vulnerability in HTML Help could
allow remote code execution.
- 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 in Exchange 2007 only from the Exchange
- 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.
- 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.
- Active Directory Users and Computers should not be used to
create Exchange 2007 objects If the Exchange
System Manager is installed, Active Directory Users and
Computers allows you to create mailboxes on Exchange 2007
servers. However, this action is not supported. Mailboxes created
in this way are considered “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 2000 Server
server or an Exchange Server 2003 server in the
organization that had a Recipient Update Service configured to
provision the newly created mailbox.
Workarounds for Selected Known Issues
This section contains the following information:
- How to remove the last Exchange 200x server
How to Remove the Last Exchange 200x Server
This section provides the steps that you must take to correctly remove the last Exchange 200x server from an Exchange 2007 organization. There are steps that you must take before removing the server, and then you can actually remove the last Exchange 200X server.
How to prepare to remove the last Exchange 200x server from an Exchange Server 2007 organization
Finish moving all mailboxes to Exchange 2007. For more information about moving mailboxes, see How to Move a Mailbox Within a Single Forest.
Move all public folder replicas from the Exchange 200x server to the Exchange 2007 server. To do this, open Exchange System Manager, expand the server you are removing, expand all storage groups, and then locate the public folder store. Right-click the store, and then select Move all Replicas. Select a public folder database on an Exchange 2007 server.
Change the generating server for your offline address books (OAB) by using either the Exchange Management Shell or the Exchange Management Console. For more information see How to Move the Offline Address Book Generation Process to Another Server.
If you have not created outbound SMTP connectors on your Exchange 2007 servers for all outbound SMTP connectors on your Exchange 200x servers, Then re-create all outbound Exchange 200x SMTP connectors as Send connectors on an Exchange 2007 transport server.
Note: If you are deploying the Exchange 2007 Edge role, this step is not needed.
Using Exchange System Manager, remove the public folder and mailbox databases from the Exchange 200x servers.
Note: Exchange System Manager in Exchange 2003 Service Pack 2 prevents you from removing the public folder and mailbox databases until all the public folder replicas have completed their background move process and all mailboxes have been moved. Replica relocation can take a substantial amount of time. Be prepared to wait days, if necessary. Removing them forcefully before replication has completed could mean data loss. If you have an earlier version of Exchange System Manager (for example Exchange 2000), look in the Public Folder Instances node under the public folder database you are deleting. When that panel is empty, you can safely remove the database.
Verify that all inbound mail is routed to an Exchange 2007 Transport server.
Verify that all inbound protocol services (Exchange ActiveSync, Office Outlook Web Access , Outlook Anywhere, POP3, IMAP4, Autodiscover service, and any other Exchange Web Service) point to an Exchange 2007 Client Access server.
Delete the routing group connectors that connect the Exchange 200x routing group and the Exchange 2007 routing group. You can do this from the Exchange 200x Exchange System Manager, or you can use the Remove-RoutingGroupConnector cmdlet in the Exchange Management Console.
Using the Exchange 200x Exchange System Manager, navigate to your Recipient policies. Check the properties of all policies. If you have some recipient policies that are solely Mailbox Manager policies (meaning that they do not define an e-mail address type and there is no E-Mail Address tab), you can delete those policies. If you have policies that are both E-mail and Mailbox Manager policies (you will see the Mailbox Manager Settings tab), right-click those policies and select Change Property Pages. Then, clear the Mailbox Manager settings section. Perform this step for all your policies.
How to remove the last Exchange 200x server from an Exchange Server 2007 organization
Before you perform this procedure, complete the "How to prepare to remove the last Exchange 200x server from an Exchange Server 2007 organization" procedure earlier in this document.
In Exchange 200x Exchange System Manager, move the public folder hierarchy from the Exchange 200x administrative group to the Exchange 2007 administrative group.
- Using the Exchange 200x Exchange System Manager, right click
the Exchange 2007 administrative group, select New, and
then select Public Folders Container.
- Go to the Exchange 200x administrative group that contains the
Public Folders tree, expand Folders, and then drag Public
Folders to the Folders under the Exchange 2007
Note: Failure to complete this step could result in the Exchange 2007 public stores not mounting if the last Exchange 200x Administrative Group is deleted in the future.
- Using the Exchange 200x Exchange System Manager, right click the Exchange 2007 administrative group, select New, and then select Public Folders Container.
Delete the domain Recipient Update Service(s). In Exchange 200x Exchange System Manager, navigate to Recipients, select Recipient Update Services, and then delete the domain Recipient Update Service.
You will not be able to delete the Enterprise Recipient Update Service by using Exchange 200x Exchange System Manager. You must use AdsiEdit (AdsiEdit.msc), as follows:
- Open AdsiEdit, navigate to Configuration NC, Services,
Microsoft Exchange, <Exchange_Org_Name>, Address Lists
Container, Recipient Update Services, and then delete the
Recipient Update Service (Enterprise Configuration).
Note: Do not use AdsiEdit to modify or delete any Exchange 2007 objects. The deletion action in this step is to remove legacy objects not needed by Exchange 2007.
- Open AdsiEdit, navigate to Configuration NC, Services, Microsoft Exchange, <Exchange_Org_Name>, Address Lists Container, Recipient Update Services, and then delete the Recipient Update Service (Enterprise Configuration).
Un-install Exchange 200x by using Add/Remove Programs.
Note: You can keep Exchange 200x Exchange System Manager installed on one of the computers in your domain. By keeping Exchange 200x Exchange System Manager, you will be able to perform public folder administration through the Exchange System Manager interface. Exchange 2007 does not currently have a graphical user interface for public folder administration and Details Templates and Address Templates. If you want to leave Exchange 200x Exchange System Manager, choose a Change action in the Exchange 200x Setup wizard and then remove the Messaging and Collaboration component but not the Management Tools. Note: You should not delete any Exchange 200x administrative groups (legacy administrative groups) that held mailboxes at any point of time. Users' LegacyExchangeDNs still reference the old administrative groups and as long as clients are using versions of Outlook other than Outlook 2007, the LegacyExchangeDNs are used for finding free/busy information. After the administrative groups no longer exists, it is uncertain that the free/busy folder for users that have the matching LegacyExchangeDN will exist and therefore those users might have difficulties finding or publishing free/busy information. In addition, users' LegacyExchangeDN is used when delegating the access to folders through the Outlook client.
You should also not delete any recipient e-mail policies that have e-mail addresses that you still want defined in your organization. Exchange 2007 will use those policies when provisioning new recipients.
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2008 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows Mobile, Windows Server, Windows Vista, Active Directory, ActiveSync, Internet Explorer, Outlook, SharePoint, and Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
All other trademarks are property of their respective owners.