Re: Questions regarding configuring Windows Server 2003 as a DC

Tech-Archive recommends: Fix windows errors by optimizing your registry

Thanks for the link to KB 314649. In our scenario I added Exchange 2000 to
an existing Windows 2000 forest. As a result all I really need to do is run
Inetorgpersonfix.ldf before running the Windows Server 2003 adprep /
forestprep command, correct?

Thank you.

"Jorge Silva" wrote:

Hi

Basic rules are:

Because you have exchange first take a look at:
http://support.microsoft.com/kb/314649/

Then you need to prepare the Forest and the domain where you're adding the
2003 DCs.
dcpromo /forestprep on schema master and /domainprep on IM.
Promote the Windows 2003 to additional DCs in the existent domain.
- Make the Servers DNS servers (configure the DNS servers as AD Integrated).
- Make sure that everything is replicated across existent DCs.
- Transfer the Fsmo roles to the new servers.
- Make the 2 new W2K3 servers GCs.
- Transfer any other role that you might have in the Windows 2000
(like:DHCP, Wins, Apps, etc.)
- Make sure that the clients use the NEW DNS servers in their TCP/IP Primary
and secondary DNS server.
- After everything is in place, disconnect the DCs to be removed- a week or
so... if everything Ok, connect the 2000 servers again and use DC promo to
remove them from AD.
- Note: you need to remove them manually from Active Directory Sites and
Services.
Voilá you're Done.

Lots of info here:
http://www.microsoft.com/windowsserver2003/upgrading/w2k/default.mspx
http://support.microsoft.com/kb/555040/en-us
http://support.microsoft.com/?kbid=325379
--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator
"mike dunphy" <mikedunphy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E6AC4D07-3C2D-4726-A73A-13CDAAE7E4B2@xxxxxxxxxxxxxxxx
Hello. I'm the release engineer of a small software company, and also
assume
all system administration responsibilities. Our network consists of 14
servers, among those servers we have (2) Windows 2000 Server domain
controllers, each having a copy of the global catalog. Additionally each
of
these DC servers is also a DNS server. The remaining servers run Windows
Server 2003 with the exception of our Exchange 2000 server that runs on
Windows 2000 Advanced Server.

These domain controllers are running on hardware that is over 5 years old,
and beyond backing these systems up there is no real redundancy built in.
I
would like to install Windows Server 2003 on two new servers, so that I
can
retire the domain controllers running on this old equipment. Beyond
configuring these new servers as domain controllers during the initial
installation what other steps need to be taken? I'll also configure these
servers as DNS servers, and replicate the global catalog over, but it
seems
to me there must be more that has to happen.

If my existing hardware wasn't so old I would look to upgrade these
systems
to Windows Server 2003 and upgrade the schema master using adprep.
However,
in this case it makes more sense to start with new hardware.

I appreciate any comments, tips and criticisms that can point me in the
right direction.

Thank you.




.

Relevant Pages

  • Re: Enumerate Windows NT4 *Servers*
    ... Windows NT Workstation and Windows NT Server are both noted in Active ... snippet that also excludes domain controllers from the search results: ... Are you saying the value of operatingSystem is the same for member servers ... report the OS as the same as NT4 Workstations. ...
    (microsoft.public.windows.server.scripting)
  • Re: Secure all IP Traffice in domain
    ... you can not use it to secure traffic between domain controllers and non ... domain controllers (workstations and member servers), ... 2000 - I am not sure about Windows 2003. ...
    (microsoft.public.win2000.security)
  • From Tracker....
    ... Remember, we're talking about Windows Platforms 95,98 ... provided with Cable/DSL dial-up accounts. ... Wrong IP no news. ... We aren't talking about News Servers here (at the ...
    (comp.security.firewalls)
  • number 2
    ... Remember, we're talking about Windows Platforms 95,98 ... provided with Cable/DSL dial-up accounts. ... Wrong IP no news. ... We aren't talking about News Servers here (at the ...
    (alt.computer.security)
  • From Tracker....
    ... Remember, we're talking about Windows Platforms 95,98 ... provided with Cable/DSL dial-up accounts. ... Wrong IP no news. ... We aren't talking about News Servers here (at the ...
    (microsoft.public.security)