RE: "Simple" nt4 to win2003 migration

Frances,
Thanks for the info. I am assuming Emulator Role will allow me to keep my
nt4 BDC? Otherwise if I migrate my old nt4 PDC to a new win2k3 PDC I will no
longer have a BDC unless I add win2k3 BDC? Once I get the everything migrated
to the win2k3 domain do I really need the nt4 domain anymore? My domain is
small and I would kind of like to start fresh, rather than have a mismatch of
nt4 and win2k3 servers. Right now I have:

1 - nt4 PDC
1 - nt4 BDC
1 - win2k SQL server
26 - win2k pro desktops
6 - nt4 desktops
3 - xp pro desktops
2 - win95 desktops

I would like to end up with 1 win2k3 PDC and 1 win2k3 BDC. It seems like
migrating to a new domain will give me what I want. I am just concerned what
happens to the "old" nt4 domain after the migration.

Eric

"Frances [MSFT]" wrote:

> Hello Eric,
>
> Good to hear from you.
>
> I understand that you want to migrate from NT to win2k3 domain. Your main
> goal seems to make the new win2003 server to host PDC Emulator Role.
>
> If this is the case, besides your plan to have two domains, and use ADMT to
> migrate from NT to win2k3, there is another plan which can achieve your
> goal: not-in-place upgrade. This way, there is only one domain and you can
> have the same domain name.
>
> According to your message, I assume your domain is small. Upgrade provides
> the easiest and lowest-risk migration path if the network environment is
> simple. The following steps are the general steps to perform a not-in-place
> upgrade. It is just for your information.
>
> As a kind reminder, please backup the whole system before you take any
> action. Also, it is best if you perform the upgrade process during a
> non-business time such as the weekend. :)
>
> Performing a "not in place" upgrade
> =========================
> 1.Install NT 4.0 BDC on the new box.
>
> 2.Promote the BDC to the PDC, which demotes the original PDC to a BDC.
>
> 3.Do a full backup of the former PDC and remove it from the network.
>
> 4.Upgrade the new PDC to Windows Server 2003.
>
> 5.Dcpromo the win2k3 server to be a DC.
> The Active Directory service imports the existing user accounts, groups,
> and other settings from the PDC.
>
> 6.Run for a test period.
>
> 7.If desired you can do a clean installation of Windows Server 2003 on the
> former PDC, and bring it online as an Active Directory domain controller.
>
> 8.Transfer all Flexible Single-Master Operation (FSMO) roles to the clean
> installed Windows Server 2003 domain controller.
>
> 9.Verify all directory information has replicated.
>
> 10.Demote the first domain controller to a member server, and remove from
> the domain.
>
> If you are interested in this plan, please refer to the newsgroup. There
> are many similar posts here.
>
> Hope this helps. If you have any further questions, don't hesitate to get
> in touch!
>
> Best regards,
>
> Frances He
>
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> =====================================================
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
.

Relevant Pages

  • Re: Second Trust
    ... Will the Trust be there when I change my current PDC and make my new ... server a PDC? ... you'll have AD with the NT4 server as a BDC" Why would it be a BDC and ...
    (microsoft.public.win2000.active_directory)
  • Re: NT 4.0 to windows 2003 AD in place upgrade.
    ... PDC that I make a BDC is the one I will take offline before I do the ... Exchange server the PDC, allow to SYNC. ...
    (microsoft.public.windows.server.migration)
  • Re: PDC/BDC problem
    ... Did your BDC got all the FSMO rules after takeover? ... Seems that it is missing one of the roles after you take out the broken server and cleanup your metadata. ... The PDC arrived last Monday. ... everything to reestablish the trust. ...
    (microsoft.public.win2000.networking)
  • RE: nt4 appserver migration
    ... I understand your mainly concern is you want to migrate a NT4 PDC to Win2k3 ... need to keep the NT4 server. ... want to demote the BDC to be a member server. ...
    (microsoft.public.windows.server.migration)
  • Re: PDC/BDC problem
    ... Even com away from PDC and BDC. ... So which server from you has which role in the moment? ... I tried everything to reestablish the trust. ...
    (microsoft.public.win2000.networking)