Windows Server

Firesky · Guest

We are looking at replacing our current server with another. We have
installed Windows 2000 Server and have put the machine on the network and
promoted it to be a DC. The AD information has replicated. However, we also
need to install Exchange on this server (temporarily) while we take down the
current server which also has exchange installed on it. Our plan, once we
have taken down the current server, fixed all it's problems, and rebuild the
operating system, is to then install Windows 2003 Server on this original
machine and put it back on the network as the main domain controller again.

My question to you: What steps to do I need to follow to do this
successfully?

Frances [MSFT] · Guest

Hello,

Thanks for your post.

From your message, I understand that the issue is to replace the original
DC and upgrade to win2k3 domain. Is it correct?

I am not sure whether I am completely clear concerning the steps you
performed. To clarify, I would like to name the new server ComA, and the
current DC ComB. I assume you have taken the following steps. Please have a
check.

1.Install win2k on ComA and promote it to be the additional DC for ComB

2.Run to test that the replication is OK.

3. Install Exchange 2k on ComA.

4. Take down ComB with Exchange and then rebuild with win2k3 later.

If this is the case, please follow the steps below to achieve your goal.

Note: before your take down ComB, you need to do some extra work to ensure
everything is OK in the win2k domain. Please follow the steps 1 to 4 to
make sure.

As a kind reminder, please backup the whole system before you take any
action. Also, it is best if you perform the upgrade process during a
non-business time such as the weekend.

Performing an upgrade regarding your scenario:
==================================

1. Install AD-integrated DNS on ComA. This process will auto replicate DNS
from 2k to 2k3.

2. Move Global Catalog to ComA.

3. Switch FSMO Roles to ComA.

4. Add DHCP role to ComA.

Please refer to the following KB:

130642 How to Move a DHCP Database to Another Windows Server
http://support.microsoft.com/?id=130642

5. Demote ComB and take it offline.

6. Rebuild ComB with win2k3.

7. Run Adprep /forestprep, Adprep /domainprep on ComA.

How to use the adprep command at the command line
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/proddocs/en
tserver/adprep.asp

8. Join ComB to the win2k domain.

9. Promote ComB to be an additional DC.
This process will replicate user/computer accounts from 2k to 2k3.

10. Install AD-integrated DNS on ComB.

11. Move Global Catalog to ComB.

12. Switch FSMO Roles to ComB.

13. Add DHCP role to ComB.

14. Run for a test period and make sure everything is OK.

15. Demote ComA and make a clean install of win2k3. Promote it to be an
additional DC. (optional)

The additional DC in a domain can offer fault tolerance and ensure the
single DC is not overloaded.

Regarding the Exchange part, I suggest you post all Exchange-related
question in the following newsgroup since they are the experts in Exchange
and will provide the most accurate information:
microsoft.public.exchange.setup

If you have any further questions don't hesitate to get in touch!

Best regards,

Frances He

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

	Windows Server Forum Index -> Migration	All times are GMT
Page 1 of 1