RE: Upgrade from NT4 to Windows 2003

Tech-Archive recommends: Fix windows errors by optimizing your registry



I am not sure what you are trying to accomplish by upgrading domain A to 2003
then demoting it! As you have described it, it is not possible, because you
will have two separate AD domains and you will still have to migrate all your
objects from one domain to the other.

Please clarify in a repost.

-Allen Firouz

"upgrade" wrote:

> I have domain "A" running windows NT4(PDC) and Domain "B" running 2003
> server. Is it possible to upgrade the PDC in Domain "A" to 2003 server then
> join domain "B" and demote to member server? Or is my only option backing up
> blanking drives and loading 2003, joining domain "B" then restoring data?
>
> Thanks,
>
> Mickey
.



Relevant Pages

  • 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: 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)
  • Re: NT to W2K3 Migration
    ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (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: upgrade wizard 6.5 to 2000
    ... I finally figured out a way to accomplish the upgrade... ... why the heck couldn't the darn Wizard figure out ... > But my import server IS sql server 2000! ...
    (microsoft.public.sqlserver.setup)