Re: Update from NT4 to Server 2003 domain
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Sun, 19 Nov 2006 18:41:10 -0000
Hi
Inline
I have to update a NT4 domain to a Server 2003 domain.* Backup the Servers.
There are two DCs in the existing NT4 domain (PDC and BDC).
Is it a good idea to promote the BDC to PDC and then disconnect it from the
network, make the update to Server 2003 and then connect it back to the LAN
with Active Directory installed?
* Take at least one BDC Offline (In case of UPGRADE FAILURE you always can promote it to a PDC). The only drawback to this method is that all changes that were made while the safe BDC was offline are lost. To minimize this loss, you could periodically turn the safe BDC on and off (when the domain is in a stable state) during the upgrade process, to update its safe copy of the directory.
To convert the BDC to a PDC: Start -> Programs -> Administrative Tools -> Server Manager -> Select the BDC, then go to the Computer Menu -> choose Promote to primary Domain Controller.
* Make sure that the Hardware and apps meets the requirements.
* Make sure that all Apps installed are compatible with W2K3 and don’t cause problems with the upgrade process or pos upgrade process.
* Run from command prompt:
Cdsource\I386\winnt32.exe /checkupgradeonly
- Before Upgrade:
* You can install a new computer (more powerful) make it a BDC, SYNCRONIZE and promote it to PDC and them perform the upgrade on the new PDC.
* Windows 2000/XP always prefer Kerberos authentication, so if the newly upgraded NT4 to Windows 2003 goes down (Offline), the client machines won’t be able to authenticate in the domain.
* If this is the case, before upgrade the NT.4 PDC, make the necessary changes on the registry (NT4Emulator). If the NT4Emulator is configured on the newly PDC, and you want o upgrade the Existent BDCs, you also need to create a registry entry on the BDCs (NeutralizeNT4Emulator) before the upgrade.
Check:
Windows 2000-based clients connect only to the domain controller that was upgraded from Windows NT 4.0 in a mixed-mode domain
http://support.microsoft.com/?kbid=284937
How to prevent overloading on the first domain controller during domain upgrade
http://support.microsoft.com/kb/298713/
Once that all domain controllers are upgraded, remove the registry settings created in the previous steps.
Note: This sometimes may not need: E.g - if all existent BDCs will be sun upgraded to Windows 2003.
Migrating from Windows NT Server 4.0 to Windows Server 2003
http://www.microsoft.com/downloads/details.aspx?FamilyID=e92cf6a0-76f0-4e25-8de0-19544062a6e6&DisplayLang=en
Upgrading from Windows NT Server 4.0
http://www.microsoft.com/windowsserver2003/upgrading/nt4/default.mspx
How to Upgrade from Windows NT Server 4.0
http://www.microsoft.com/windowsserver2003/upgrading/nt4/howto/default.mspx
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA + Exchange + MSCE
Systems Administrator
"K-iS" <KiS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:308F3C8D-D072-4C8D-8AB7-E9840EF10431@xxxxxxxxxxxxxxxx
Hi,
I have to update a NT4 domain to a Server 2003 domain.
There are two DCs in the existing NT4 domain (PDC and BDC).
Is it a good idea to promote the BDC to PDC and then disconnect it from the
network, make the update to Server 2003 and then connect it back to the LAN
with Active Directory installed?
This would give me enough time to make the update and I have the BDC when
something wents wrong.
In addition the users are able to log on during the update of the PDC
because the BDC is still online.
I'm not sure if it could cause problems to update the PDC when it is not
connected to the LAN or when I connect it back with active directory
installed.
So I hope someone can give me an answer.
Sincerely
mak
.
- Prev by Date: Re: Update from NT4 to Server 2003 domain
- Next by Date: Re: Active Directory in Windows Server 2003 R2
- Previous by thread: Re: Update from NT4 to Server 2003 domain
- Next by thread: Re: Update from NT4 to Server 2003 domain
- Index(es):
Relevant Pages
|
Loading
