Re: Migrating Windows 2000 domain to Windows 2003

Tech-Archive recommends: Speed Up your PC by fixing your registry

Dear,

You are right that first upgrade master DC and then the others.

Based on my experience, before performing an in-place upgrade, you need to
make sure that your software and hardware are compatible with the new
version of the operating system. You need run the Upgrade Advisor tools by
using the /checkupgradeonly parameter with the Winnt32.exe tool. The
Winnt32.exe tool is included in the I386 folder on the Windows?XP
Professional and Windows Server?2003 operating system CD. The command is
as following:

winnt32 /checkupgradeonly

For more information about win2k3 system requirement:
http://www.microsoft.com/windowsserver2003/evaluation/sysreqs/default.mspx

Meanwhile, don¡¯t forget to backup the system before take any action.

HTH!

Thanks & Regards

Amanda Wang [MSFT]

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.

=====================================================================

--------------------
>Thread-Topic: Migrating Windows 2000 domain to Windows 2003
>thread-index: AcVELQeNxRILU9W5TFqt0vSouxU6ig==
>X-WBNR-Posting-Host: 65.5.76.250
>From: =?Utf-8?B?Sy5W?= <KV@xxxxxxxxxxxxxxxxxxxxxxxxx>
>References: <8D1B22D0-DCD9-4336-AEF6-A9B319898B21@xxxxxxxxxxxxx>
<#U#Z83DQFHA.2520@xxxxxxxxxxxxxxxxxxxx>
<B205F7FD-50FF-4256-ABEE-8DE647993005@xxxxxxxxxxxxx>
<4kn8FaLQFHA.3892@xxxxxxxxxxxxxxxxxxxxx>
<548BD1F5-0802-45F0-BB2E-F2E46EC4B861@xxxxxxxxxxxxx>
<4v1fMOZQFHA.4032@xxxxxxxxxxxxxxxxxxxxx>
<9EC05F85-822D-46CD-8E6E-42CADEB692DB@xxxxxxxxxxxxx>
<DdNNOtARFHA.2316@xxxxxxxxxxxxxxxxxxxxx>
>Subject: Re: Migrating Windows 2000 domain to Windows 2003
>Date: Mon, 18 Apr 2005 08:41:04 -0700
>Lines: 191
>Message-ID: <72FE571F-0CBB-4FAF-BC8A-54F8BA129B8C@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.migration
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.migration:18443
>X-Tomcat-NG: microsoft.public.windows.server.migration
>
>Thanks for the 'Details' Amanda..at this point i am planning on doing an
>inplace upgrade..i,e., i wann upgrade an existing Windows 2000 domian
>Controller to windows 2003. The setup we have on our end is described
below..
>
>WIndows 2000 domain (native mode) with 4 domain controllers. One as Master
>(all roles) others one at each location. We have exch. 2003 on win 2000
box.
>
>We have plans start (master dc first, DC's at remote sites next, one at a
>time) upgrading our domain to 2003 in one month.
>
>Based on our scenario..do you think an inplace upgrade is a good idea ?
>
>Thanks
>K.V
>
>
>"Amanda Wang [MSFT]" wrote:
>
>> Hi,
>>
>> Thanks for your reply and let me know your question about the difference
>> between 'upgrading' and 'migrating'.
>>
>> Upgrade:
>>
>> Upgrading is performed just on the same server. You already have
installed
>> 2000 DC on it, and now you want to upgrade this server to Windows 2003
DC.
>>
>> Under the circumstance, you can keep the domain name.
>>
>> Migrate:
>>
>> Migrating is performed between the two servers in two domains and
>> establishes the trust relationship between them. One server is
installed
>> 2000 DC and the new server is installed 2003 DC. Now you just need to
>> replicate those account or computer settings and policies between 2000
DC
>> and 2003 DC.
>>
>> For the situation, you must use another domain name on the new 2003
server
>> during migration. If you want to use the same domain name on 2003 DC,
you
>> can rename the domain name after migration but we do not recommend this
way.
>>
>> And I have provided an example in my previous reply as following:
>>
>> For example,
>> The original win2k domain is named "OldDomain", you need to install
win2k3
>> on a new machine, promote it to be a DC with the domain name
"NewDomain",
>> and then use ADMT to migrate the all objects from "OldDomain" to
>> "NewDomain". You can rename win2k3 domain from "NewDomain" to
"OldDomain"
>> after complete migration. However, it is not a recommend way. If this is
>> your plan, I will suggest you install Win2k3 on a new machine, join it
to
>> the win2k "OldDomain" and then promote win2k3 to be an additional DC in
>> "OldDomain", this is the upgrade process. The following article has
clearly
>> addressed this process:
>>
>> How to upgrade Windows 2000 domain controllers to Windows Server 2003
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;325379
>>
>> With regards to the link, I have found the document has been
unexpectedly
>> removed. Please check the following article:
>>
>> Upgrading Windows 2000 Domains to Windows Server 2003 Domains
>>
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKi
>> t/8d926ba4-0323-45a6-96f0-db7f7cb33f6b.mspx
>>
>> HTH.
>>
>> Thanks & Regards
>>
>> Amanda Wang [MSFT]
>>
>> 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.
>>
>> =====================================================================
>>
>> --------------------
>> >Thread-Topic: Migrating Windows 2000 domain to Windows 2003
>> >thread-index: AcVBqJjHigHTJ8LJQi6yVcZbp2FehA==
>> >X-WBNR-Posting-Host: 68.105.159.112
>> >From: =?Utf-8?B?Sy5W?= <KV@xxxxxxxxxxxxxxxxxxxxxxxxx>
>> >References: <8D1B22D0-DCD9-4336-AEF6-A9B319898B21@xxxxxxxxxxxxx>
>> <#U#Z83DQFHA.2520@xxxxxxxxxxxxxxxxxxxx>
>> <B205F7FD-50FF-4256-ABEE-8DE647993005@xxxxxxxxxxxxx>
>> <4kn8FaLQFHA.3892@xxxxxxxxxxxxxxxxxxxxx>
>> <548BD1F5-0802-45F0-BB2E-F2E46EC4B861@xxxxxxxxxxxxx>
>> <4v1fMOZQFHA.4032@xxxxxxxxxxxxxxxxxxxxx>
>> >Subject: Re: Migrating Windows 2000 domain to Windows 2003
>> >Date: Fri, 15 Apr 2005 03:48:02 -0700
>> >Lines: 63
>> >Message-ID: <9EC05F85-822D-46CD-8E6E-42CADEB692DB@xxxxxxxxxxxxx>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain;
>> > charset="Utf-8"
>> >Content-Transfer-Encoding: 7bit
>> >X-Newsreader: Microsoft CDO for Windows 2000
>> >Content-Class: urn:content-classes:message
>> >Importance: normal
>> >Priority: normal
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >Newsgroups: microsoft.public.windows.server.migration
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.windows.server.migration:18399
>> >X-Tomcat-NG: microsoft.public.windows.server.migration
>> >
>> >Thanks Amanda..Ok here is the deal..we will not be 'Renaming the
>> Domain'..i
>> >think thats a give at this point. Also i am confused between
'upgrading'
>> and
>> >'migrating'...
>> >
>> >If i understand this right then we are migrating our Windows 2000
domain
>> to
>> >Windows 2003 domain! In anycase we have no plans to change the domain
name
>> at
>> >this point.
>> >
>> >Can you please clarify the difference between 'upgrading' and
'migrating'
>> >the domain.
>> >
>> >Thanks
>> >K.V
>> >
>> >"Amanda Wang [MSFT]" wrote:
>> >
>> >> Hi,
>> >>
>> >> Thanks for your update.
>> >>
>> >> One point I would like to confirm is " keep the domain name the
'same'".
>> >> Please know if you use ADMT to migrate the user infos from win2k to
>> win2k3,
>> >> you need to create a different domain name for win2k3 domain. For
>> example,
>> >> the original win2k domain is named "OldDoamin", you need to install
>> win2k3
>> >> on a new machine, promote it to be a DC with the domain name
>> "NewDomain",
>> >> and then use ADMT to migrate the all objects from "OldDoamin" to
>> >> "NewDomain". You can rename win2k3 domain from "NewDomain" to
>> "OldDoamin"
>> >> after complete migration. However, it is not a recommend way. If this
is
>> >> your plan, I will suggest you install Win2k3 on a new machine, join
it
>> to
>> >> the win2k "OldDoamin" and then promote win2k3 to be an additional DC
in
>> >> "OldDoamin", this is the upgrade process. The following article has
>> clearly
>> >> addressed this process:
>> >>
>> >> How to upgrade Windows 2000 domain controllers to Windows Server 2003
>> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;325379
>> >>
>> >> With regards to the link, I have found the document has been
>> unexpectedly
>> >> removed. Please check the following article:
>> >>
>> >> Upgrading Windows 2000 Domains to Windows Server 2003 Domains
>> >>
>>
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKi
>> >> t/8d926ba4-0323-45a6-96f0-db7f7cb33f6b.mspx
>> >>
>> >> HTH!
>> >>
>> >> Any update, keep in touch.
>> >>
>> >> Thanks & Regards
>> >>
>> >> Amanda Wang [MSFT]
>> >>
>> >> 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.
>> >>
>> >> =====================================================================
>> >>
>> >>
>> >
>>
>>
>

.

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: 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: 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: 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 ...
    (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 ...
    (microsoft.public.windows.server.active_directory)