Any tips on migrating Exchange 5.5 on NT 4.0 to 2000 Server

[cgbrown]

We have an existing Exchange 5.5 server on NT 4.0 and will be migrating it to Windows 2000 Server on a new box. Any tips will help.

 

[ashleym]

I just did this, but I cheated.

My advice:

Plan, plan plan. If you can, setup a test environment first and try and replicate your migration.

Make sure you have stellar backups before your migration.

If you have a heavily used mailserver/public folders, do the migration over a weekend as moving mailboxes that are a few hundred megabytes can be time consuming, as can replicating public folders.

Here is an article that will help:


The information in this article applies to:



- Microsoft Exchange 2000 Server

- Microsoft Exchange Server, version 5.5

------------------------------------------------------------------------
-------





IN THIS TASK

------------



- SUMMARY



- Prepare Microsoft Windows 2000 Active Directory for Exchange 2000 Server

Installation

- Prepare Exchange Server 5.5 for Migration

- Prepare Active Directory for Installation of Exchange 2000

- Install Exchange 2000 into same site as the existing Exchange 5.5 server

- Migration of Mailboxes and Public Folders

- Removal of the Last Exchange 5.5 Server



- To Reroute Incoming Internet E-mail to the Exchange 2000 Server

- To Reroute Outgoing Internet E-mail Through the Exchange 2000 Server

- Removing the Last Exchange 5.5 Server



- REFERENCES



SUMMARY

=======



This step-by-step article describes how to install Exchange 2000 Server into an

existing Exchange 5.5 organization, migrate mailboxes to Exchange 2000 by using

the Move Mailbox method, and how to remove the last Exchange 5.5 server from the

Exchange organization.



Prepare Microsoft Windows 2000 Active Directory for Exchange 2000 Server Installation

------------------------------------------------------------------------
-------------



NOTE: Before you migrate mailboxes from Exchange Server 5.5 to Exchange Server

2000, you must first migrate the User Accounts to Microsoft Windows 2000 Active

Directory. The preferred method to perform this procedure is to upgrade your

existing User Account Domain to Microsoft Windows 2000 Active Directory, or you

can use the Active Directory Migration tool to migrate User Accounts by using

security identifier (SID) history to retain permissions. If your Exchange Server

5.5 computer is in a different domain than the Exchange 2000 domain, you must

establish a two-way trust between the domains.



Verify that your Domain Name System (DNS) configuration is properly updating your

Active Directory. To do so:



1. Run NETDIAG on the server that is to host Exchange 2000 Server, and then

ensure that all of the tests are passed.



2. Run DCDIAG and NETDIAG on all domain controllers (DCs), and then ensure that

all of the tests are passed.



3. From the server that is to host Exchange 2000 Server, run the "nltest

/dsgetsite" (without the quotation marks) command. A site name should be

returned that contains no errors.



4. From the Exchange Server 5.5 computer, use the ping command to search for the

short (NetBIOS) name of server in which you are going to install Exchange

2000. The response returns the fully qualified domain name (FQDN) of the

server. For example, when you run the "ping e2k" (without the quotation

marks), the following data is displayed:



pinging e2k.addomain.internal [192.168.1.10] with 32 bytes of data



However, you expect the following data, which contains the NetBIOS name, to be

displayed:



Pinging e2k [192.168.1.10] with 32 bytes of data



If the FQDN does not appear, configure the proper name resolution for the

Exchange Server 5.5 computer. This may require that the Exchange Server 5.5

computer that you are migrating from is pointed to your Windows 2000 DNS

server for DNS.



NOTE: Other configurations are possible.



Verify that Microsoft Windows 2000 Service Pack 2 (SP2) and the Simple Mail

Transfer Protocol (SMTP) and Network News Transfer Protocol (NNTP) protocols are

installed on the server in which Exchange 2000 Server is to be installed. In

addition, verify that Microsoft Windows 2000 Service Pack 2 (SP2) is installed

on all domain controllers.



NOTE: Because Exchange 2000 Server is typically the first program installed in a

Microsoft Windows 2000 domain that requires Active Directory to be properly

updated by DNS dynamically with Server Resource Records, it is critical that DNS

is properly configured. The DNS server referenced by the Exchange 2000 server

should be an internal DNS server. No external DNS servers should be referenced,

other than as Forwarders in your internal DNS server's settings.



Prepare Exchange Server 5.5 for Migration

-----------------------------------------



Verify that only one mailbox is associated with each user account. Use the

NTDSNoMatch utility if necessary, this utility is also sometimes referred to as

NTDSATRB. For the latest version of this utility, download the latest service

pack and view the \Support\Utils\i386\Ntdsatrb folder for instructions and the

executable file.

For additional information, click the article number below to view the article in

the Microsoft Knowledge Base:



Q274173 XADM: Documentation for the NTDSNoMatch Utility



On the Exchange Server 5.5 computer, run DS/IS Consistency Adjustment on the

public folder store and on the Mailbox Store to remove "zombie" Access Control

Entries (ACEs). To run DS/IS Consistency Adjustment:



1. In the Exchange Server 5.5 Administrator program, select a server that run

Exchange Server 5.5 and that contains a public information store.



2. On the File menu, click Properties, and then click the Advanced tab.



3. Click Consistency Adjuster.



4. In DS/IS Consistency Adjustment, click the "Remove unknown user accounts from

public folder permissions" check box, click the "Remove unknown user accounts

from mailbox permissions" check box, and then click the "All inconsistencies"

button.



IMPORTANT: Clear all other check boxes.



Public Folder Tip: Prevent Permissions Problems When Migrating Public Folders to

Exchange 2000
(

http://www.microsoft.com/exchange/using/tips/Folder_tip1.asp)

Verify that only valid characters (Alpha/Numeric/hyphen) are used for

Organization and Site name, and then change the display name if necessary.



Verify that all distribution lists (DLs) are configured for "Any Server in Site"

for DL Expansion. You can perform this procedure manually or through a "best

effort" utility named XChangeXS, which is available from Microsoft Product

Support Services.



Prepare Active Directory for Installation of Exchange 2000 Server

-----------------------------------------------------------------



NOTE: Microsoft recommends that Exchange 2000 Server be installed into a Windows

2000 native mode domain before you configure ADC Connection Agreements (CAs).

Failure to do so, or failure to properly configure Recipient CAs, can result in

Public Folders being inaccessible unless they are republished, as per a Disaster

Recovery scenario. You can either convert a domain that exists to native mode or

create a new native mode domain. Configure a Recipient Connection Agreement to

replicate Exchange Server 5.5 distribution lists to the native mode Windows 2000

domain.



Install Exchange 2000 Active Directory Connector (ADC) from the Exchange 2000

CD-ROM (install both the ADC and Management components). Configure a two-way ADC

Recipient Connection Agreement.



Run Exchange 2000 Setup with the ForestPrep and DomainPrep. The account used to

run the /forestPrep switch and your first Exchange 2000 installation must have

at least view only permissions on the Site and Configuration containers in the

existing Exchange 5.5 organization. Verify that the Exchange Organization object

is present in Active Directory Sites and Services; if the Services node is not

visible go to View, Show Services Node). For more information on the /forestprep

and /domainprep switches, for more information refer to Forestprep and

Domainprep paper

(

http://www.microsoft.com/Exchange/techinfo/deployment/2000/PrepUtility.

asp)



Configure a two-way ADC Public Folder Connection Agreement.



Install Exchange 2000 into same site as the existing Exchange 5.5 server

------------------------------------------------------------------------



Run the Setup.exe program for Exchange 2000. After setup completes, verify that

the Microsoft Exchange services have started, and that the Information Store is

mounted. Test functionality by creating a new Active Directory user account with

a mailbox on the Exchange 2000 Server.



Apply any Exchange 2000 Service Packs. Exchange 2000 Service Pack 2
(SP2) is

currently released. For more information on installed Exchange 2000 Service Pack

2, for more information refer to Exchange 2000 SP2 Deployment Guide

(

http://www.microsoft.com/exchange/techinfo/deployment/2000/SP2Deploymen

t.asp)



A Recipient Policy is automatically created in the Exchange System Manager, under

Organization\Recipients\Recipient Policies. You will find a DEFAULT Policy with

a priority of Lowest; you may also have a Policy for the Exchange Site in which

you have just installed Exchange 2000 marked with a higher priority. Right-click

the highest priority policy, click Properties, click the Email
Addresses(Policy)

tab, and then verify that the Primary SMTP address (in bold) is correct. If it

is not, you can create an additional SMTP address if it is necessary and

designate it as primary. Select the Recipient Policy designated as highest, or

you only have a default Recipient Policy, create a new Recipient Policy with a

higher priority and modify the Email Addresses. If you create a new Recipient

Policy, ensure that the filter rules on the General tab are correct.



NOTE: Do not remove or modify the Default Recipient Policy. If necessary you can

modify the Alias name created by Recipient Policy. For additional information,

click the article numbers below to view the articles in the Microsoft Knowledge

Base:



Q285355 XADM: How to Modify Recipient Polices to Customize SMTP E-mail

Addresses



Q285136 XADM: How to Customize the SMTP E-mail Address Generators Through

Recipient Policies



A Recipient Update Service (RUS) is automatically created for the domain in which

you installed Exchange 2000. If you have any other domains with user accounts

that will be mailbox enabled (Parent or Child Domain), you will need to create

and configure a RUS for each of those additional Domains (go to Exchange System

Manager\Recipient Update Service\right-click\New\Recipient Update

Service\Browse\select appropriate domain).



Migration of Mailboxes and Public Folders

-----------------------------------------



1. Start the Exchange 5.5 Administrator program, and then connect to the

Exchange Server 5.5 computer.



2. Navigate to the following location, and then click "Public Folder
Recourses":



Organization\Site\Configuration\Server\ServerName\Public Information Store


3. For each public folder in the right pane, click File, and then click

Properties.



4. On the Replicas tab, ensure that only the Exchange 2000 server, is listed on

the right under "Replicate folders to". No Exchange 5.5 servers should be

present in this column.



Following these steps not only replicates all public folders to Exchange 2000,

but also "rehomes" them to Exchange 2000. This should include Schedule+ Free

Busy, Offline Address Book, and Organizational Forms, if present.



Move all Mailboxes to the new Exchange 2000 server using Active Directory Users

and Computers.



1. Select the Organizational Unit (OU), select the Recipient (or shift/control

-click to select multiple recipients).



2. Right-click the object(s), click Exchange Tasks, click Move Mailbox and then

click Next. This initializes the Move Mailbox Wizard, which guides you

through moving the mailboxes to the appropriate Exchange 2000 Server and

Mailbox Store.



3. Verify that all mailboxes have been removed by using the Exchange 5.5

Administrator program, at the server level, Private Information Store\Mailbox

Resources. No mailboxes should be visible here.



To Remove the Last Exchange 5.5 Server

--------------------------------------



Because both inbound and outbound Internet mail may have been flowing through the

Exchange 5.5 server, you must transfer these processes to Exchange 2000 Server

before you remove Exchange Server 5.5.



To Reroute Incoming Internet E-mail to the Exchange 2000 Server:



- If you have a firewall that routes mail to a private IP address on your

Exchange Server 5.5 computer, you can reconfigure your firewall to route mail

to the private IP address of the Exchange 2000 Server computer.



- Swap IP addresses of the new Exchange 2000 server and the old Exchange 5.5

server. Note that this can result in some temporary name resolution issues on

your network. At a command prompt, you must run "IPCONFIG FLUSHDNS" (without

the quotation marks), restart the Net Logon service on the Exchange 2000

server, and then restart the Exchange 5.5 server.



-or-



- Have your Internet Service Provider (ISP) update the mail exchange
(MX)

record to reference the new Exchange 2000 Sever computer. You can expect

Incoming E-mail to be disrupted for at least three hours, and up to three

days, while this update is replicated over the Internet.



To Reroute Outgoing Internet E-mail Through the Exchange 2000 Server:



1. Start the Microsoft Exchange Server 5.5 Administrator program, and then

connect to the Exchange Server 5.5 computer.



2. Navigate to the following location:



Organization\Site\Configuration container\Connections



3. Select the Internet Mail Service properties, click the Address Space tab,

highlight the SMTP Address Space(s), and then click Remove.



4. Then recalculate routing from the Exchange 5.5 Administrator program,

Organization\Site\Configuration container, Site Addressing properties,

Routing Tab, and then click "Recalculate Routing".



Note that locally scoped address spaces are not allowed in Exchange 2000

environments (only Organization and Routing Group scopes are allowed).

After you verify that all mail flow is routed through the Exchange 2000 Server

computer, remove the Internet Mail Service (IMS). To do so, in the Exchange

Server 5.5 Administrator program, click "Internet Mail Service", click Edit, and

then click Delete.



Removing the Last Exchange 5.5 Server:



1. Stop Exchange 5.5 services, and then set the Microsoft Exchange System

Attendant to disabled.



2. From the Exchange 2000 Server use the Exchange 5.5 Administrator program.

Make sure that you are using the Exchange 2000 version of the Exchange 5.5

Administrator program, which is an option installed from the Exchange 2000

Setup program. After you start this version of the Exchange 5.5 Administrator

program, click File, click "Connect to Server" (to connect to the Exchange

2000 Server computer) to delete Exchange Sever 5.5 computer from the site.



3. Locate Active Directory Connection Manager, right-click the "Configuration

Connection Agreement" (Config_CA), and then force replication by clicking

"Replicate Now".



4. Wait for the Exchange 5.5 server to disappear from Exchange System Manager,

and then use Exchange System Manager to delete the Site Replication Service,

which is located under Organization\Tools\Site Replication

Services\YourSiteReplicationService



5. This deletes the Config_CA connection agreement; you can now delete the ADC

Recipient and Public Folder Connection Agreements.



6. Use Add Remove Programs to remove the ADC, (Active Directory Connection

Manager)



7. You can now go to Exchange System Manager, select the Organization/Properties

and switch to Native Mode. To do so, on the General tab click Change Mode.



NOTE: In the Application event log on the Exchange 2000 Server computer, you may

see some Event ID 9318s from the message transfer agent (MTA) and 1025s from the

MSExchangeIS Private information store after you apply these changes; these will

be warnings most likely due to Name Resolution failure using cached DNS naming

information in Active Directory. They will typically go away in 3 to 6 days.

Some customer have reported eradicating these warnings more quickly by rebooting

their Global Catalog Servers.



REFERENCES

==========



For additional information, click the article numbers below to view the articles

in the Microsoft Knowledge Base:



Q259427 XADM: 'SETUP /FORESTPREP' Does Not Work When Windows 2000 Sites Are

Incorrectly Defined



Q300202 HOW TO: Configure DNS for Internet Access in Windows 2000



Q291382 Frequently Asked Questions About Windows 2000 DNS



Q289671 XADM: Invalid Character Error Occurs When Upgrading or Joining an

Exchange Server 5.5 Site





Q296260 XGEN: How to Configure a Two-Way Recipient Connection Agreement for

Exchange Server 5.5 Users



Q257638 XCON: Locally Scoped Connectors Not Allowed in a Mixed Exchange

Server 5.5-Exchange 2000 Environment



Q284148 XADM: How to Remove the Last Exchange Server 5.5 Computer from an

Exchange 2000 Administrative Group



Q152959 XADM: How to Remove the First Exchange Server in a Site



Q260781 XADM: Change Mode Button Inactive in Organization Properties Dialog

Box After Upgrading Exchange 5.5 Service Pack 3 to Exchange 2000 Server



For more information, refer to the following:



Security Tip: Using Exchange Server 5.5 Distribution Lists in Exchange 2000

Public Folder Permissions

(

http://www.microsoft.com/exchange/using/tips/Sec_PubFolder.asp)

For general recommendations when migrating from Exchange 5.5 to Exchange 2000

refer to the following:



In-Place Upgrade from Microsoft(r) Exchange 5.5 to Microsoft(r) Exchange 2000



A Guide to Upgrading from MS Exchange Server 5.5 to Exchange 2000 Server

(

http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prod

technol/exchange/deploy/depovg/e2kguide.asp)



Additional query words: ad admt