Microsoft Exchange Server 2003 Deployment Guide- P64 docx

631 Command option Description /targetgc Specifies the target global catalog server (required). /logfile Specifies the path and file name for the log file. The default is exprofre.log in the tmp directory, which is saved on the client computer. You can also redirect the log file to a server share by using the format /logfile=<path\filename>. /v Turns on verbose output. /f Keeps the favorites file (.fav or .xml). If this option is not specified, the tool renames the extension of the favorites file to .exprofre. 632 Command option Description /a Keeps the offline address book (.oab) files. If this option is not specified, the tool deletes the .oab files and resets Outlook to check the server for an updated set of .oab files. /r Specifies read-only mode. /o Deletes rather than renames the offline folder store file (.ost). If this option is not specified, the tool renames the extension of the .ost file to .exprofre. (This option is not required for Outlook 2003 or later. The .ost file for Outlook 2003 or later is always unchanged.) /p Specifies the front-end proxy server if you are using Outlook 2003 with RPC/HTTP turned on. 633 Command option Description /n Clears the Outlook nickname file (.nk2 or .nick). If this option is not specified, the tool keeps the nickname file. /s Updates profiles based on a change in server name rather than a change in the legacyExchangeDN attribute. Sample Command for Moves Across Exchange Organizations If you are moving mailboxes across Exchange organizations (cross-forest moves), it is recommended that you use only the /v and /n command options. All other options should be omitted to enable the tool to use its default settings. Because the user is moving to a new forest, most of the Outlook information stored on the user's workstation will be obsolete and must be updated with information about the new forest. By default, the tool deletes most of this obsolete information. 634 The following is a sample command for a mailbox move across Exchange organizations: Exprofre.exe /targetgc=<target global catalog server> /v /n /f Sample Command for Moves Across Administrative Groups If you are moving mailboxes across Exchange sites or administrative groups (within the same Exchange organization), much of the information stored on the user's computer is still valid because the mailbox has not moved to another forest. In this scenario, it is recommended that you keep the offline address book, favorites, and nickname files. The following is a sample command for a mailbox move across administrative groups: Exprofre.exe /targetgc=<target global catalog server> /v /f /a Sample Log File The following is sample output from Exprofre.exe: 635 [16:08:58] ************** Beginning exprofre run ************** [16:08:58] Starting exprofre on Windows 5.1.2600 at 16:08:58 11/20/03 Log File = "\\server1\shared\exprofre.log" Read Only = "No" OS version = 5.1.2600 Outlook 11 is installed. Default profile name = "John" Profile user = "/o=TIFOREST1/ou=First Administrative Group/cn=Recipients" Properties for the provider were successfully updated The default user profile and/or Outlook files were changed 636 [16:08:59] !!!!!!!!!! exprofre completed! Public Folder Migration Tool Before you run the Exchange Public Folder Migration tool (PFMigrate), it is recommended that you create replicas of Exchange 5.5 public folders on an Exchange 2003 server. By following this process, the user can still access public folders after the user is moved from the remote site to the central site. PFMigrate moves public folders from remote Exchange 5.5 servers to the central Exchange 2003 server. The latest version of PFMigrate contains a site consolidation command option (/sc) for moving public folders across administrative groups. Running PFMigrate with the /sc option moves only public folders. You should not move free and busy system folders during site consolidation because users' free and busy data is republished by using the new legacyExchangeDN attribute. For more information about moving your mailboxes, see the Exchange Server Deployment Tools for SP1. The latest version of PFMigrate is available from the Downloads for Exchange 2003 Web site (http://go.microsoft.com/fwlink/?linkid=25097). To verify that migrated public folders have been removed from your Exchange 5.5 servers, see How to Verify that Public Folders Have Been Removed in Exchange Server 5.5. 637 Object Rehome Tool The Object Rehome tool moves distribution lists and contacts from remote Exchange 5.5 servers to the central Exchange 2003 server. The Object Rehome tool enables you to update the legacy distinguished name for distribution lists and custom recipients to reflect the central site during site consolidation. By updating these objects to reflect the central site, you ensure that these objects are not lost when you remove the remote site. The Object Rehome tool also updates the distribution list expansion server to a specified server. If you want to clear the expansion server from all distribution lists, leave the target expansion server option blank so that the distribution lists use any expansion server. For more information about the Object Rehome tool, see the Exchange Server Deployment Tools for SP1. Consolidating Sites in Mixed Mode To consolidate a remote site that is running in Exchange mixed mode, you must remove Exchange 5.5, Exchange 2000, or Exchange 2003 before you begin the consolidation process. 638 Removing an Exchange 5.5 Server Before you remove an Exchange 5.5 server from your site, verify that there are no mail connectors on the server. If there are, open a connector on another server in the site, and then verify mail flow. Next, remove the connectors on the server to be deleted. Retest message flow. For more information about removing your Exchange 5.5 connectors, see the Exchange 5.5 Help. For detailed steps about how to remove Exchange Server 5.5, see How to Remove Exchange 5.5 Servers from Your Exchange 2003 Organization. Important: If this is the first server in the site to be removed, see Microsoft Knowledge Base article 152959, "XADM: How to Remove the First Exchange Server in a Site" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=152959). Removing the Last Exchange 5.5 Server Before you can switch from mixed mode to native mode, you must remove all Exchange 5.5 servers in your organization. For detailed steps 639 about how to remove the last Exchange 5.5 server in your organization, see How to Remove the Last Exchange 5.5 Server from Your Exchange 2003 Organization. Note: Ensure that the account to which you are logged on has Exchange Full Administrator permissions, as well as Exchange 5.5 service account administrator permissions to the site. Removing Exchange 2000 Before you remove Exchange 2000 servers from a site that you want to consolidate, you must remove any connectors to foreign mail systems. For detailed steps, see How to Remove a Connector from Exchange 2000 Server. To move the connector to another Exchange 2000 server or to your central site, reinstall the connector and reconfigure the connector tabs on your new Exchange 2000 server. For more information about setting up connectors to foreign mail systems for Exchange 2000, see the Exchange 2000 Server Help. 640 Removing Unsupported Components The following components are not supported in Exchange Server 2003:  Microsoft Mobile Information Server  Instant Messaging Service  Exchange Chat Service  Exchange 2000 Conferencing Server  Key Management Service For more information about removing these unsupported components, see Exchange 2000 Server Help and Mobile Information Server Help. Removing Exchange 2000 Servers The first Exchange 2000 server installed in an administrative group has certain important roles. For example, the first server hosts the offline address book folder, the Schedule+ Free/Busy folder, the Events Root folder, and other system folders. Therefore, use caution when you . Removed in Exchange Server 5.5. 637 Object Rehome Tool The Object Rehome tool moves distribution lists and contacts from remote Exchange 5.5 servers to the central Exchange 2003 server. . is running in Exchange mixed mode, you must remove Exchange 5.5, Exchange 2000, or Exchange 2003 before you begin the consolidation process. 638 Removing an Exchange 5.5 Server Before. systems for Exchange 2000, see the Exchange 2000 Server Help. 640 Removing Unsupported Components The following components are not supported in Exchange Server 2003:  Microsoft Mobile