Re: Migrating Windows 2000 domain to Windows 2003

Hello,

Thanks for your question.

Those hotfixes are applied to those scenarios. However, we still need to
confirm if these hotfixes have been included in Win 2k Server SP4. We can
go to the following website to check if they have been included in SP4:

List of bugs that are fixed in Windows 2000 Service Pack 4

http://support.microsoft.com/kb/327194/EN-US/

After confirmation and combined with the description in KB article 331161,
there is no hotfix you need to install.

Anything unclear, please feel free to post back. I'm very glad to help you.

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: AcVaMbrg/Ml9jSlLSeW3hkE5wF5bmg==
>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>
<72FE571F-0CBB-4FAF-BC8A-54F8BA129B8C@xxxxxxxxxxxxx>
<da5GW2MRFHA.1440@xxxxxxxxxxxxxxxxxxxxx>
<E60BD4B2-F513-4154-A833-A44F9101E85B@xxxxxxxxxxxxx>
<kq8GVikRFHA.17172@xxxxxxxxxxxxxxxxxxxxx>
<57048DBB-68BB-4AD8-B23A-CA64E174A2B0@xxxxxxxxxxxxx>
<o5qJe2hWFHA.388@xxxxxxxxxxxxxxxxxxxxx>
>Subject: Re: Migrating Windows 2000 domain to Windows 2003
>Date: Mon, 16 May 2005 09:10:08 -0700
>Lines: 307
>Message-ID: <DEE756D4-E65F-4644-B0AA-36C49027B7B3@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>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: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.migration:10200
>X-Tomcat-NG: microsoft.public.windows.server.migration
>
>Thanks Amanda. So if we are on Win 2k Server SP4 we don't have to worry
about
>any hotfixes, right?
>
>K.V
>
>"Amanda Wang [MSFT]" wrote:
>
>> Hello,
>>
>> You are right. These hotfixes only applied to the following scenarios:
>>
>> Microsoft Windows 2000 Advanced Server SP2
>> Microsoft Windows 2000 Advanced Server SP1
>> Microsoft Windows 2000 Service Pack 1
>> Microsoft Windows 2000 Service Pack 2
>>
>> HTH!
>>
>> 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: AcVX+JaRXJnWZBFAQ5eKGaZDYukedA==
>> >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>
>> <72FE571F-0CBB-4FAF-BC8A-54F8BA129B8C@xxxxxxxxxxxxx>
>> <da5GW2MRFHA.1440@xxxxxxxxxxxxxxxxxxxxx>
>> <E60BD4B2-F513-4154-A833-A44F9101E85B@xxxxxxxxxxxxx>
>> <kq8GVikRFHA.17172@xxxxxxxxxxxxxxxxxxxxx>
>> >Subject: Re: Migrating Windows 2000 domain to Windows 2003
>> >Date: Fri, 13 May 2005 13:16:03 -0700
>> >Lines: 311
>> >Message-ID: <57048DBB-68BB-4AD8-B23A-CA64E174A2B0@xxxxxxxxxxxxx>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain;
>> > charset="Utf-8"
>> >Content-Transfer-Encoding: 8bit
>> >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: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:10169
>> >X-Tomcat-NG: microsoft.public.windows.server.migration
>> >
>> >Hi Amanda, quick clarification on something..
>> >
>> >The hotfixes mentioned in article 331161, do they apply to domain
>> >controllers running windows 2000 SP4/ I don't think so! Just wanted to
>> double
>> >check.
>> >
>> >Thanks
>> >K.V
>> >
>> >"Amanda Wang [MSFT]" wrote:
>> >
>> >> Dear,
>> >>
>> >> You are always welcome. If you have any other questions or concerns,
>> don't
>> >> hesitate to post back. I'm very glad to help you.
>> >>
>> >> 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: AcVE4czmVristvaHS4uL1utJJU3v4A==
>> >> >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>
>> >> <72FE571F-0CBB-4FAF-BC8A-54F8BA129B8C@xxxxxxxxxxxxx>
>> >> <da5GW2MRFHA.1440@xxxxxxxxxxxxxxxxxxxxx>
>> >> >Subject: Re: Migrating Windows 2000 domain to Windows 2003
>> >> >Date: Tue, 19 Apr 2005 06:15:04 -0700
>> >> >Lines: 299
>> >> >Message-ID: <E60BD4B2-F513-4154-A833-A44F9101E85B@xxxxxxxxxxxxx>
>> >> >MIME-Version: 1.0
>> >> >Content-Type: text/plain;
>> >> > charset="Utf-8"
>> >> >Content-Transfer-Encoding: 8bit
>> >> >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:18473
>> >> >X-Tomcat-NG: microsoft.public.windows.server.migration
>> >> >
>> >> >great, Thanks a bunch for the detailed response. It will be atleast
2
>> >> weeks
>> >> >before we can start on our first DC upgrade. I will keep you posted.
In
>> >> the
>> >> >mean while if you can think of any 'tips' you can post them here.
>> >> >
>> >> >Thanks again.
>> >> >
>> >> >K.V
>> >> >
>> >> >"Amanda Wang [MSFT]" wrote:
>> >> >
>> >> >> 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",
>

.

Relevant Pages

  • SecurityFocus Microsoft Newsletter #178
    ... Microsoft Windows XP explorer.exe Multiple Memory Corruption... ... W3C Jigsaw Unspecified Remote URI Parsing Vulnerability ... Working Resources BadBlue Server phptest.php Path Disclosure... ...
    (Focus-Microsoft)
  • SecurityFocus Microsoft Newsletter #138
    ... Nessus LibNASL Arbitrary Code Execution Vulnerability ... Blackmoon FTP Server Username Information Disclosure... ... Microsoft Windows Media Player Automatic File Download and... ...
    (Focus-Microsoft)
  • Re: After setting up the network
    ... Windows firewall/Internet connection etc. ... Microsoft Windows XP ... Server is active on ... C:\Documents and Settings\Leon Perrins>net config workstation ...
    (microsoft.public.windowsxp.network_web)
  • [NT] Vulnerability in SMTP Allows Remote Code Execution (MS04-035)
    ... A remote code execution vulnerability exists in the Windows Server 2003 ... installed on Microsoft Windows 2000 Service Pack 3 or on Microsoft Windows ... * Microsoft Exchange Server 2003 and Microsoft Exchange Server 2003 ...
    (Securiteam)
  • RE: New Single NIC Problem
    ... and without maknig any changes I can still ping the any client ... I can RWW inwards and access server and clients. ... > Windows IP Configuration ... > Microsoft Windows XP ...
    (microsoft.public.windows.server.sbs)
Loading