Re: NT to 2003 domain upgrade - DNS related question

From: gottaplayd (jayshaw91_at_yahoo.com)
Date: 06/21/04


Date: Mon, 21 Jun 2004 16:48:42 -0400

My first thought is that if you're making the new machine a BDC, then
running W2K3 on it as an upgrade, it will automatically assume the "PDC
Emulator" FSMO role. This will in essence put two PDC's on your network,
which isn't good news, of course.

So first off, you're going to have to re-think this part. Your choices are
to promote your current PDC (take a BDC offline that's been synched up
before you do this in case things go way south) to W2K3, then you can just
load W2K3 on the new boxes and you won't have to load the OS twice on the
new, shiny servers.

*OR* make the new machine a BDC, take the old PDC offline and stash it away,
promo the new box to PDC, and THEN do the in-place upgrade.

The problem is that you're going to lose your DNS server if you do plan B
because you'll be removing the server running your DNS from the environment.
May want to try moving your NT4 DNS and WINS to the new box, then do the
above. Regardless, you're going to have to make a decision on waht to do
with your DNS/WINS box prior to doing anything with the new server.

This help?

-- 
There are 10 types of people in the world.
Those who understand binary, and those who don't.
"Greg G" <greg@golightly.us> wrote in message
news:77c904c4.0406211214.1cfbaaa0@posting.google.com...
> I am leading a NT4 to 2003 AD upgrade this weekend.
> Our domain is a simple single domain and I have done all the testing
> and planning required, so I am comfortable with this.
> My issue is DNS related:
> Our current PDC is our DNS and WINS server.  All our clients are
> static IP (not my doing, was here before I got here).  They all point
> to this PDC for DNS and WINS.
>
> My plan is to do an in place upgrade on a new machine (which will be
> created as a BDC and then promoted prior to upgrade).  The old PDC
> will stay in place for a while (we will not go 2003 native for a month
> or two).  I plan on leaving my clients pointing to this DNS server (it
> is not feasible to change all the IP info clients) with the new
> network.  I will make sure its DNS and WINS have new server info in
> them (we have 9x clients, so WINS must stay).
>
> Is this going to cause a show stopping problem?  Bascially, all my
> clients will still point to this NT4 DNS and WINS server for that
> info.
>
> In a week or two, I plan on taking the current PDC's IP address and
> giving it to a secondary card on one of the new servers, so all
> clients will point to it for name resolution.  I just do not want to
> do this at the same time this weekend - too worried about not being
> able to troubleshoot a problem with too much change going on.
>
> Do I need to do anything with this NT4 DNS server (like make it point
> to the newer DNS server or setup a secondary type relationship?
>
> Thanks
> Greg


Relevant Pages

  • Re: NT to W2K3 Migration
    ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: Migrating NT4 to Windows 2003
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT to W2K3 Migration
    ... You cannot just promote a member server to AD. ... upgrade your PDC to windows 2000 or 2003, whichever flavor of AD you want to ... Upgrading from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • RE: NT 4.0 to Windows Server 2003 Upgrade
    ... 325851 How To Set Up ADMT for a Windows NT 4.0-to-Windows Server 2003 ... NT 4.0 to Windows Server 2003 Upgrade ... | the AD wizard, my client systems are still able to log into the domain ... |> | would it be better to configure DNS through the AD wizard? ...
    (microsoft.public.windows.server.migration)
  • Re: Native 2003 mode and NT4 workstations?
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)