Discussion Locked

Help moving Exchange to a Win 2k domain.

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am the administrator of a small NT network, with one PDC, one BDC, and about 30 users. Exchange 5.5 SP3 is installed on the PDC. The network was configured this way when I took this job, and I have since been simply maintaining it. We are now migrating to Windows 2000 for our server platform (all clients are already 2k pro), and the new mail server will be set up as Exchange 5.5 sp3 or 4 on Windows 2000 server.

Because of the age of the hardware and the clutter on these machines, I will be setting up our new Win2k domain in a test environment, and not upgrading the existing servers. When it's ready, I'll cut everyone over from the NT domain to the 2k domain.

I have already planned out the new domain, and don't believe I'll have any problems. However, I'm not sure how I'm going to move the Exchange mailboxes and public folders from the old server to the new one. What's the easiest way to go about doing this? Please contact me if you need more info.

10 replies

by lazarus long

If you prepare your new machine following the configuration and naming convention of the old machine, you may be able to back up the data from the old and restore onto the new. I'm uncertain if online backup will work this way, so an offline backup looks to be a better possibilty. You'll need to determine the locations of the database and log files for the directory service, and the database files for public and private information stores, and the log files for the IS. Copy the files to their appropriate locations on the new box, start the directory service, run ISINTEG -patch, and start the information store service. (standard offline restore procedure). From the looks of it, that should work.
btw, a company called Commvault has a product named Galaxy that will allow you to backup and Exchange 5.5 machine and restore it to an Exchange 2000 machine.
regards, lazarus.

by tony.colgrove

Answer 1 will not work properly. The service account will not have the same SID in the new domain, so if you copy over the directory service you will not be able to start any Exchange Services.
I would possibly look at ExMerge as a solution. ExMerge allows you to extract mailboxes to a pst which then can be merged into a new server (which doesnt have to belong to the same org or site). It will create mailboxes and you can set naming rules for the import.
If you stay with Ex5.5 on Win2K server, you should also use the Active Directory Connector to keep your AD and Ex Directories in Synch.
Another thing to watch out for is: If you install Ex5.5 on a Win2K server running AD, you need to change the LDAP port on the Exchange Server.

by gbainbridge

The research that I've done thus far suggests that answer number 2 is accurate in saying that Answer number 1 won't work because of the SID issues on the exchange service account.

However, if I create my Win2k domain by setting up my first DC as an NT BDC in the NT domain, and synchronize to get the accounts in order, then move it to a private network and upgrade it to Win2k and run dcpromo to install Active Directory, wouldn't the Exchange service account retain the SID? If so, I assume that answer number 1 would work.

Any input on this?

by stephen mynhier

Your proposed modification of Answer #1 would work, however you must be certain that you take the PDC (containing Exchange) offline first and promote another BDC to PDC. Then when you install NT on the new machine it must have the same name as the offline PDC. Here's why: in order to restore the back-up of the IS, the OS and Exchange versions and Service Packs must match. In addition, the Org and Site names must match exactly. For the DS to be restored, the service account must also match.

After installing the OS on the new box, apply the exact SP as your PDC. Then install Exchange (do not run Optimizer) and install the exact SP for Exchange. Run Optimizer, stop all Exchange services, copy the dir.edb, priv.edb, and pub.edb (and no other files) into the appropriate directories on the new server. Restart the Exchanges services. Chances are that you will get Error -1011. If you do, run ISINTEG.EXE -PATCH. If you don't get the error, don't run the patch. This should allow for complete reinstall and restoration of Exchange on the new server.

After you upgrade to W2k, don't forget to rerun optimizer.

The problem with ExMerge is that it is limited to the priv.edb. You also lose single-instance storage when exporting to ExMerge (causing the database to potentially increase in size significantly). And, when importing the mailboxes back into your new server, the mailboxes must be manually created and populated before ExMerge can see it. It's a very good utility, but still has significant limitations when trying to use it as a back-up/restore tool.

by boydandrews

msmerge.exe is a utility supplied on the Exchange 2000 CD. This utility when run extracts mailboxes as pst files or imports mailboxes as pst files. Be sure to check the number of items in each mail box to be sure that all items are imported.

This discussion is closed to new replies.