Adding a Windows 2003 server to a Windows 2000 domain

  • Thread starter Thread starter Michael Hewson
  • Start date Start date
M

Michael Hewson

I would like to add a Windows 2003 Server to a Windows 2000 domain and then
make it a Domain Controller.

What would the best way to go about doing this?

In addition we would then replace our existing mail server which runs
Exchange 2000 and replace it with a new machine with Windows 2003 and
Exchange 2003.

Are there any significant hurdles to watch out for when best implementing
this scenario.

many thanks,
 
In order to add a Windows 2003 DC to a Windows 2000 domain, you have to run
adprep /forestprep and then adprep /domainprep and then promote a 2003 DC.

With Exchange, if you update the domain first, then you need to implement
the InetOrgPerson 'mangled attributes' fix.

Otherwise, you can update Exchange first, and then update the domain.

There are MS KBs for all the above at http://support.microsoft.com
 
What if I have a a Windows 2003 Servers with AD configured to
xxx.mycompany.com and I want to add a new primary just mycompany.com? Any
suggestions on how to do this? The server I wish to add will be Wiindows 2003
but I want it to be the parent. I don't know who came up with
xxx.mycompany.com but I don't think we would have an easy time integrating
with Exchange.
 
What if I have a a Windows 2003 Servers with AD configured to
xxx.mycompany.com and I want to add a new primary just mycompany.com? Any
suggestions on how to do this? The server I wish to add will be Wiindows
2003
Click to expand...
but I want it to be the parent. I don't know who came up with
xxx.mycompany.com but I don't think we would have an easy time integrating
with Exchange

Good question! You have to create a new domain in a new forest, create a
trust between the two domains and migrate users, computers, mailboxes, etc.

If you've installed as child.company.com then this is the forest root; you
cannot go higher in the namespace than this. In your scenario it will be
essential (it is in all, but you have similar names so I'm going to STRESS
this) to get name resolution working properly before doing anything.
 
I notice you have "adprep /forestprep". I am in the process of installing an
Exchange 2003 server on a Windows 2003 member server. I am up to the
"/forestprep" point. My question is the "adprep/forestprep" / "/forestprep"
What is the difference? I will be running the commands from the CD.

Thanks
 
Carl,

It is similar to when you install Exchange 2000 into a WIN2000 Active
Directory environment. You are essentially extending the Schema. To
simplify, the *attributes* necessary do not exist in the 'current' AD Schema
so they need to be added. If you pay attention to the /forestprep part you
will notice that it 'imports' 10 .ldf files.

To take this example to WIN2003, a WIN2000 AD environment will not have all
of the same *attributes* that are found in a WIN2003 AD environment. So,
how to resolve this? Extend the Schema in the WIN2000 environment so that
it now holds those *attributes*. Then, and only then, can you install a
WIN2003 Domain Controller.

Now, specifically to your question:

You need to do the /forestprep to extend the Schema so that the *attributes*
necessary will be there. This is a forest-wide thing. Not to get into the
whole Naming Context thing, but there are three Naming Contexts, or
Partitions, that exist in WIN2000 Active Directory: the Schema NC, the
Configuration NC and the Domain NC. The first two NCs are forest-wide while
the last one is for each domain in the forest.

You need to do the /domainprep in each domain that you have in the forest
that will have mail-enabled objects. Running this adds a security group or
two and adds some permissions.
--
Cary W. Shultz
Roanoke, VA 24012
Microsoft Active Directory MVP

http://www.activedirectory-win2000.com
http://www.grouppolicy-win2000.com
 
Back
Top