[windows2000] Re: Active directory conversions
- From: "Jim Hathaway" <JimH@xxxxxxxxxxxxxxx>
- To: <windows2000@xxxxxxxxxxxxx>
- Date: Fri, 5 Sep 2003 09:11:22 -0700
Craig,
The only thing that I've seen be a problem with the 'swing' method of
domain migration is that you should make sure your FQDN of the NT 4.0
PDC that you're upgrading to win2k is correct prior to the upgrade.
Once win2k is installed to that server, and it's auto dc-promo'd you
won't be able to change it's FQDN. This can make it a challenge to bring
other win2k DC's into the domain to move the FSMO roles over.
For example:
- The NT 4.0 PDC has an FQDN of "pdc.your.domain" set within the
DNS tab of the properties of TCP/IP on the server, prior to the win2k
upgrade.
- During the upgrade and subsequent promotion to a win2k DC, you
decide to name your new domain DNS as "win2k.domain".
- The domain upgrade wizards will finish, and your new win2k
domain will have a DC that's stuck with an unchangeable FQDN of
"pdc.your.domain", but a DNS domain space of "win2k.domain".
- all other servers attempting to dcpromo will join the domain
as "servername.win2k.domain" and will have difficulty resolving your
incorrectly named PDC emulator.
It's a small setting, but can cause major headaches if mis-set. So, be
sure to have your DNS naming convention fully defined prior to beginning
the PDC upgrade process.
Aside from that the swing method is a great way to upgrade domains with
minimal downtime for your end users.
My $.02
J
PS - I absolutely agree, OS upgrades are completely evil. You never know
what kind of junk will remain on the upgraded system to cause you
headaches down the road. Do the upgrade to a single, clean system, the
bring in other freshly installed win2k / win2k3 servers and get the
upgraded system out of there.
-----Original Message-----
From: Craig Gauss [mailto:GauCra@xxxxxxxxxxxxxxxxx]
Sent: Friday, September 05, 2003 8:38 AM
To: 'windows2000@xxxxxxxxxxxxx'
Subject: [windows2000] Re: Active directory conversions
That is basically what the instructor said. There is just too much to
go
wrong. Plus you are dealing with the partition sizing problems with
NT4.0.
-----Original Message-----
From: Sullivan, Glenn [mailto:GSullivan@xxxxxxxxxxxxxx]
Sent: Friday, September 05, 2003 10:32 AM
To: 'windows2000@xxxxxxxxxxxxx'
Subject: [windows2000] Re: Active directory conversions
Because Upgrade Installs are evil.
I could go into more detail, but it would take too long.
Glenn Sullivan, MCSE+I MCDBA
David Clark Company Inc.
-----Original Message-----
From: Bill Beckett [mailto:Bill.Beckett@xxxxxxxxxx]
Sent: Friday, September 05, 2003 11:23 AM
To: 'windows2000@xxxxxxxxxxxxx'
Subject: [windows2000] Re: Active directory conversions
Seems a bit overkill to me. Why not just build a BDC, synch it and then
take
it off line. Do your migration and if something goes sideways, bring it
back
online and promote it.
> -----Original Message-----
> From: Craig Gauss [SMTP:GauCra@xxxxxxxxxxxxxxxxx]
> Sent: Friday, September 05, 2003 11:21 AM
> To: 'windows2000@xxxxxxxxxxxxx'
> Subject: [windows2000] Re: Active directory conversions
>
> This is what the instructor of our AD class told us is a good way to
do
> it,
> just want to check if I may be missing anything:
>
> 1 - Build a temporary box as a NT4.0 BDC
> 2 - Promote the temporary box to a PDC
> 3 - Check replication
> 4 - Upgrade the temporary box to Windows 2k or 2k3
> 5 - Wipe out one of the existing NT4.0 BDC's and set it up from
scratch
> with
> 2k or 2k3 as a member server
> 6 - Run DCPROMO on the member server
> 7 - Transfer the 5 roles to this newly promoted machine
> 8 - Demote the temporary box and remove it
>
>
> Does this sound like a good start?
>
> Right now I have the temp box setup as a NT4.0 BDC.
> I have 6 servers I need to bring into this newly formed W2k AD
structure
> when all is said and done.
>
> **********************************************************
> To Unsubscribe, set digest or vacation
> mode or view archives use the below link.
>
> http://thethin.net/win2000list.cfm
**********************************************************
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
**********************************************************
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
**********************************************************
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
**********************************************************
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
Other related posts:
