Windows Server

SpencerG · Guest

I am at a site where they had an existing 2000 Domain. A 2003 server was
installed and took over as the DC. A second one was then installed again
as a DC.
The old 2000 server was retired.
There is still one 2000 server running Exchange2000. This will be updated
to 2003 server and Exchange 2003 server but only after this first bit is
sorted.
As I am aware, ADPREP was not run on the new boxes pre their
installation..
As a result, the permissions are in a bit of a mess and all the user data
on the new server appearsas READ ONLY.
Can I run ADPREP on both the 2003 servers DC post the server instal. i.e
now ?
Will this repair the problems ?
Or is a manual reapir job ?

One of the servers is also SQL2000.
This does not need to be a DC so can I,
after the problems are resolved, demote it ?

Thanks for your time.

Rebecca Chen [MSFT] · Guest

Hi Spencer,

I would like to confirm the network topology of this scenario:

1. Win2k is the old DC running Exchg 2k, let us call it win2k.
2. Add a win2k3 server as a DC, call it win2k3_1
3. Add the secondary win2k3 server as a DC, call it win2k3_2

As you have stated "ADPREP was not run on the new boxes pre their
installation", what kind of ADPREP has not been run, ADPREP for exchange or
ADPREP for win2k3 server?

Based on my knowledge, we cannot promote win2k3 to be the additional DC in
win2k domain without running windows ADPREP.
The adprep /domainprep command is a one-time operation that you run on the
infrastructure operations master domain controller of each domain in the
forest that will host new or upgraded Windows Server 2003 domain
controllers. The adprep /domainprep command verifies that the changes from
forestprep have replicated in the domain partition and then makes its own
changes to the domain partition and group policies in the Sysvol share.

If you take the win2k DC offline and then promote the win2k3 server to be
a DC with the same domain name, and then take the win2k back online, these
two DCs are not in the same domain even if they have the same domain name.

Another point is the ADPREP for exchg and windows are different. When you
upgrade win2k to win2k3 domain, you need to run windows ADPREP; whereas
when you upgrade exchg from 2k to 2k3, you need to run exchg ADPREP.

You can use the following steps to verify that the adprep /forestprep
command successfully ran on the schema operations master.

1. The CN=Windows2003Update object is written under
CN=ForestUpdates,CN=Configuration,DC=forest_root_domain. Record the value
of the Revision attribute.

2. (Optional) The schema version incremented to version 30. To do so, see
the ObjectVersion attribute under
CN=Schema,CN=Configuration,DC=forest_root_domain

Please take a close look at the following article, which details how to
upgrade Windows 2000 domain controllers to Windows Server 2003:

How to upgrade Windows 2000 domain controllers to Windows Server 2003
http://support.microsoft.com/?id=325379#2

In addition, you are unable to determine the whether or not the adpresp has
been run before the please refer to the following article to gather the
MPSreport (Domain controller) version on both win2k and win2k3 servers,
compress the MPSreport and send it to v-rebc@microsoft.com for research.

Overview of the Microsoft Configuration Capture Utility (MPS_REPORTS)
<http://support.microsoft.com/default.aspx?scid=kb;en-us;818742>

Any update, let us get in touch!

Best regards,

Rebecca Chen

MCSE2000 MCDBA CCNA

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