Re: Upgrading to 2003 from NT



The new computer cannot run Windows NT, so if I install 2003 on the new
computer, and make it the first DC, then how do I demote the current PDC to
not being a DC at all? Will that require a reinstall?

Then, once that is done, we also have an Exchange 5.5 server. The new server
that we purchased for the 2003 will not run NT either. I need to install
Server 2003, then Exchange 2003, then how do I go about moving the
emails/mailboxes, groups, public folders, etc? Can that be done? Or would I
have to install 5.5 on the 2003 box, sync em up, then upgrade to 2003?

"Danny Sanders" wrote:

> > If we purchase a new computer to be the first 2003 DC, running AD, how do
> > I
> > get the PDC and BDC to recognize the new computer as the DC?
>
> On the new server install NT 4.0 on it as a BDC while connected to your
> existing network, promote to PDC (this demotes your existing PDC to BDC)
> then upgrade to Win 2k3 and AD.
>
> This will keep your old domain name (you should follow the DNS naming
> convention of mydomain.com to prevent problems associated with single label
> domain names)
> Your clients are already joined to the domain so you won't have to join them
> to the AD domain and have a new profile created. Your new server will carry
> the PDC emulator role and as long as you don't switch your domain to Win 2k
> native mode or higher they will continue to replicate with the AD PDC
> emulator.
>
>
> See:
> How To Upgrade a Windows NT 4.0-Based PDC to a Windows Server 2003-Based
> Domain Controller
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;326209
>
>
>
> With AD correctly configured DNS is a must. Don't use your ISP's DNS servers
> anywhere on your network except for setting it as a forwarder on your AD DNS
> server.
>
>
>
> See:
>
> Setting Up the Domain Name System for Active Directory
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;237675
>
> Best Practices for DNS Client settings in Windows 2000 server and in Windows
> Server 2003
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;825036
>
> How to configure DNS for Internet access in Windows Server 2003
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;323380
>
>
>
> hth
>
> DDS W 2k MVP MCSE
>
>
>
> "Pam" <Pam@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:D7CA666B-8030-4A61-9FFC-4CE579EE8088@xxxxxxxxxxxxxxxx
> > We have a small NT domain network. The current PDC is too old to upgrade
> > to
> > 2003. The BDC is OK to upgrade.
> >
> > If we purchase a new computer to be the first 2003 DC, running AD, how do
> > I
> > get the PDC and BDC to recognize the new computer as the DC? I wanted to
> > rename the new Domain the same as the Old domain, but I can't do that with
> > the old domain still running. Is it as easy as joining the old computers
> > to
> > the new domain?
> >
>
>
>
.



Relevant Pages

  • Re: NT Domain to AD migration
    ... Windows 2000/XP always prefer Kerberos authentication, ... Server 2003 Active Directory service, ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: Secondary DNS and PIX
    ... Of course I updated them with the DNS ... WINDOWS SERVER 2003 FOR SMALL BUSINESS SERVER, ... Windows SBS 2003 SP1 is available. ...
    (microsoft.public.windows.server.sbs)
  • Re: Find AD hostname from Linux command line
    ... The Windows XP workstation gets an IP ... "Register this connection's addresses in DNS" turned ON. ... If I am on a Linux server and do "ping lancelot.ad.mydomain.com", ...
    (microsoft.public.win2000.dns)
  • Re: Secondary DNS and PIX
    ... SBS SP1 was a very specific service pack comprising several ... Root hints for DNS means you leave the forwarders ... WINDOWS SERVER 2003 FOR SMALL BUSINESS SERVER, ...
    (microsoft.public.windows.server.sbs)
  • Re: Two Win2k3 questions ... Roaming Profiles & Access Privileges ...
    ... >DHCP, DNS, Print Server, and File Server responsibilities. ... lookup zone on Windows NT" ... http://support.microsoft.com?kbid=229873 "Delegate Control Wizard Cannot Be Used ...
    (microsoft.public.win2000.advanced_server)