Re: Windows NT 4.0 to Windows 2003 AD migration, why two windows 2003 DC's?

• Previous message: Frank: "RE: Rename domain"
• In reply to: a-sswann: "Windows NT 4.0 to Windows 2003 AD migration, why two windows 2003 DC's?"
• Next in thread: Bob Qin [MSFT]: "Re: Windows NT 4.0 to Windows 2003 AD migration, why two windows 2003 DC's?"
• Reply: Bob Qin [MSFT]: "Re: Windows NT 4.0 to Windows 2003 AD migration, why two windows 2003 DC's?"
• Messages sorted by: [ date ] [ thread ]

Date: 18 May 2004 11:52:01 -0700

Shayne:

Thank you for your response.

regarding your reply to question 1: I completely agree with you,
except that I do not want to upgrade any pdc/bdcs. They are on subpar
equipment, and the configuration is not the way we want it.

We essentially want to take pdc/bdcs offline, and in its place migrate
the sam database, and data over to the 2003 AD server. I'm tempted to
use ADMT 2.0 to do this....what do you think? would you still
consider the method you describe a better method than to use ADMT? We
also do not want to reuse the same server name we have on the current
PDC.

I'm also faced with the issue that the PDC was a print server as well,
so if i wanted to cut over to a new DC with a new name, all the
clients printers that have been setup using the old PDC need a new
mapping. Is there an easy way of doing this?

Thanks...

Tom

"a-sswann" <anonymous@discussions.microsoft.com> wrote in message news:<e6e001c43cc9$ff78b3d0$a401280a@phx.gbl>...
> Thomas,
>
> Question 1.
>
> If you plan to do an in-place upgrade, here is the
> suggested method of the upgrade process.
>
> 1. Introduce a Windows Server 2003 - Based Member Server
> into your NT4.0 environment (you can use your new server
> for this).
>
> 2. Enable the Windows Server 2003 Interim Functional
> Level (Interim Mode).
>
> 3. Relocated the LMRepl File Replication Service.
>
> 4. Secure Domain Data.
>
> 5. Freeze Changes to the NT4.0 Environment (Sync at least
> one BDC and take it off line).
>
> 6. Ensure DNS functionality.
>
> 7. Upgrade the NT 4.0 PDC
>
> 8. Configure the system to protect against Authentication
> Overload - Enabling NT 4.0 Emulation
> (http://support.microsoft.com/?id=298713) -
> (http://support.microsoft.com/?id=284937
> ).
>
> 9. Sync File Replication Services.
>
> 10. Verify Active Directory Functionality.
>
> 11. Add Additional domain controllers to the Windows 2003
> Domain (you can upgrade you 2003 Member Server from step
> one).
>
> 12. Upgrade Windows NT 4.0 BDC's to Windows Server 2003.
>
> Here are some resources to help you with this process:
> 1. Migrating from Windows NT Server 4.0 to Windows Server
> 2003 (webcast PPT)
> http://www.microsoft.com/seminar/shared/asp/view.asp?
> url=/Seminar/en/20030324TNT1-74/manifest.xml
>
> 2. Microsoft Windows Server 2003 Deployment Kit
> http://www.microsoft.com/resources/documentation/windowsse
> rv/2003/all/deployguide/en-us/?frame=true
>
>
> Question 2.
>
> The reason that it is suggested to have two domain
> controllers that are Windows server 2003 is because of
> redundancy (specifically to protect against domain
> controller authentication overload on your new 2003
> domain controllers). These two articles explain the
> reason fairly well. But basically what happens when you
> introduce a Windows Server 2003 Domain Controller into a
> Windows NT 4.0 Domain with W2K and or XP clients, the W2K
> and XP clients will have an affinity to logon to the
> Windows Server 2003. And the way this problem is resolved
> is to either bring up at least 2 Windows Server 2003 DC's
> or to Emulate NT 4.0 domain.
>
> If you have any problems, please reply.
>
> Shayne
>
> >-----Original Message-----
> >I currently have a working Production Windows NT 4
> network that I will
> >be upgrading to a Windows 2003 Active Directory
> environment.
> >
> >I have two general groups of questions that plague my
> mind:
> >
> >
> >
> >Question 1:
> >
> >For the new Windows 2003 Active Directory environment,
> we have
> >allocated 1 new server for this cut over. I plan on
> using the ADMT
> >(Active Directory Migration Tool) to carry out the
> user/group/printer
> >cutover from a current NT4 PDC/BDC environment
> >
> >At this point of time, I am wondering if it would be
> simpler to use
> >ADMT or to actually deploy this as the microsoft white
> paper
> >suggests...that is
> >
> >1)reformat the new server with win NT4 as a BDC
> >2)apply all services packs,
> >3)remove all production PDC/BDC after replication off
> the network
> >(freeze)
> >4)upgrade to BDC to windows 2003
> >5)Install AD.
> >This way I can avoid using the ADMT.
> >
> >
> >
> >Question 2:
> >
> >Also in the white papers, microsoft states that 2
> windows 2003 domain
> >controllers are required. Why is this? I have not
> found any reason
> >behind this except for failover. If the one windows
> 2003 DC is
> >running a multi-mode FSMO, I do not see why you could
> not just install
> >one windows 2003 domain controller first, then shortly
> after install
> >another domain controller for failover.
> >
> >
> >Does anyone have any suggestions?
> >Thanks in advance for any help/assistance...
> >
> >Thomas Tsai
> >.
> >

• Previous message: Frank: "RE: Rename domain"
• In reply to: a-sswann: "Windows NT 4.0 to Windows 2003 AD migration, why two windows 2003 DC's?"
• Next in thread: Bob Qin [MSFT]: "Re: Windows NT 4.0 to Windows 2003 AD migration, why two windows 2003 DC's?"
• Reply: Bob Qin [MSFT]: "Re: Windows NT 4.0 to Windows 2003 AD migration, why two windows 2003 DC's?"
• Messages sorted by: [ date ] [ thread ]