I am going to put my 2003 server on the network as a member server firstly because it is going to store my new ERP system we are implementing. However, I also need it be a DC because I only have 1 DC on my network at this time. I figure since I have the resources, why not? (Dell Xeon Duel P4 2Ghz with 1gig ram
I actually read the 'manual' that came with Win2003 server and it explains in some detail and some resources on the net as what to do so have a pretty good understanding. I'm going to try to do this in a test environment first just to make sure. Another thing I need to do is upgrade 2 9x machines to XP and my 2 NT member servers to 2000 server as well
But, do I need to do anything to the NT member servers? I'm assuming they just need to have the latest patches/hotfixes
Zac
----- Brendon Rogers wrote: ----
Your W2K3 server can be a member server in the 2000 domain
The basic steps
Then run ADREP /FORESTPRE
Then run ADREP /DOMAINPRE
Then DCPromo the W2K3 server to a domain controller
Be warned though - this is not something to undertake lightly. There is n
idiot's guide because this is not something an idiot should be doing. It
fairly straightforward but if something goes wrong you can have seriou
problems
Research it a bit more, understand the steps involved then proceed
"The Zack" <(E-Mail Removed)> wrote in messag
news

A731830-9A5E-4A6B-B4AD-(E-Mail Removed)..
> Can I get a small step by step on how to do this? Do I put the 200
server on the network then run Adprep.exe, forest prep, domian prep, on th
2000 server them run dcpromo on the 2003 server? I'm not running Exchange
Also, all my clients are running XP
>> I also know that the server needs to point to itself first for DNS the
the other DC as secondary DNS
>> Zac
>>> ----- Brendon Rogers wrote: ----
>> Adding a W2K3 DC into a W2K domain is slightly more involved tha
simpl
> DCPromo'ing it
>> See http://support.microsoft.com/default...kb;en-us;32537
for mor
> info
>>