Re: Migrating Windows 2000 domain to Windows 2003

Hello,

Thanks for your update.

For your current situation, you have installed exchange 2003 on Windows
2000 server and now you want to upgrade Win 2000 server to Win 2k3.

Based on my research, if it will be affected the windows upgrade, it is
determined by whether the Exchange 2000 schema changes has been installed
before.

There is a KB article describes the scenario:

325379 How to Upgrade Windows 2000 Domain Controllers to Windows Server 2003
http://support.microsoft.com/?id=325379

Based on your scenario, the Scenario 2 and 3 should be applied to and you
need to follow the steps in it and confirm it:

Scenario 2: Exchange 2000 schema changes will be installed before the
Windows Server 2003 adprep /forestprep command
If Exchange 2000 schema changes have already been installed but you have
NOT run the Windows Server 2003 adprep /forestprep command, consider the
following action plan:
1. Log on to the console of the schema operations master by using an
account that is a member of the Schema Admins security group.
2. Click Start, click Run, type notepad.exe in the Open box, and then click
OK.
3. Copy the following text including the trailing hyphen after
"schemaUpdateNow: 1" to Notepad.
dn: CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,DC=X
changetype: Modify
replace:LDAPDisplayName
LDAPDisplayName: msExchAssistantName
-

dn: CN=ms-Exch-LabeledURI,CN=Schema,CN=Configuration,DC=X
changetype: Modify
replace: LDAPDisplayName
LDAPDisplayName: msExchLabeledURI
-

dn: CN=ms-Exch-House-Identifier,CN=Schema,CN=Configuration,DC=X
changetype: Modify
replace: LDAPDisplayName
LDAPDisplayName: msExchHouseIdentifier
-

dn:
changetype: Modify
add: schemaUpdateNow
schemaUpdateNow: 1
-

4. On the File menu, click Save. In the Save As dialog box, follow these
steps:
a. In the File name box, type the following:
\%userprofile%\InetOrgPersonPrevent.ldf
b. In the Save as type box, click All Files.
c. In the Encoding box, click Unicode.
d. Click Save.
e. Quit Notepad.

5. Run the InetOrgPersonPrevent.ldf script.
a. Click Start, click Run, type cmd in the Open box, and then click OK.
b. At a command prompt, type the following, and then press ENTER:
cd %userprofile%
c. Type the following command
c:\documents and settings\%username%>ldifde -i -f inetorgpersonprevent.ldf
-v -c DC=X "domain name path for forest root domain"
Syntax notes: o DC=X is a case-sensitive constant.
o The domain name path for the root domain must be enclosed in quotation
marks.
For example, the command syntax for an Active Directory forest whose forest
root domain is TAILSPINTOYS>COM would be:
c:\documents and settings\administrator>ldifde -i -f
inetorgpersonprevent.ldf -v -c DC=X "dc=tailspintoys,dc=com"

6. Verify that the LDAPDisplayNames for the CN=ms-Exch-Assistant-Name,
CN=ms-Exch-LabeledURI, and CN=ms-Exch-House-Identifier attributes in the
schema naming context now appear as msExchAssistantName, msExchLabeledURI,
and msExchHouseIdentifier before you run the Windows Server 2003 adprep
/forestprep commands.
7. Go to the "Overview: Upgrading Windows 2000 domain controllers to
Windows Server 2003 " section to run the adprep /forestprep and /domainprep
commands.

Scenario 3: The Windows Server 2003 forestprep command was run without
first running inetOrgPersonFix

If you run the Windows Server 2003 adprep /forestprep command in a Windows
2000 forest that contains the Exchange 2000 schema changes, the
LDAPDisplayName attributes for houseIdentifier, secretary, and labeledURI
will become mangled. To identify mangled names, use Ldp.exe to locate the
affected attributes:

1. Install Ldp.exe from the Support\Tools folder of the Microsoft Windows
2000 or Windows Server 2003 media.

2. Start Ldp.exe from a domain controller or member computer in the forest.
a. On the Connection menu, click Connect, leave the Server box empty, type
389 in the Port box, and then click OK.
b. On the Connection menu, click Bind, leave all the boxes empty, and then
click OK.

3. Record the distinguished name path for the SchemaNamingContext
attribute. For example, for a domain controller in the CORP.ADATUM.COM
forest, the distinguished name path might be
CN=Schema,CN=Configuration,DC=corp,DC=company,DC=com.

4. On the Browse menu, click Search.

5. Use the following settings to configure the Search dialog box: o Base
DN: The distinguished name path for the schema naming context that is
identified in step 3.
o Filter: (ldapdisplayname=dup*)
o Scope: Subtree

6. Mangled houseIdentifier, secretary, and labeledURI attributes have
LDAPDisplayName attributes that are similar to the following format:
LDAPDisplayName: DUP-labeledURI-9591bbd3-d2a6-4669-afda-48af7c35507d;
LDAPDisplayName: DUP-secretary-c5a1240d-70c0-455c-9906-a4070602f85f
LDAPDisplayName: DUP-houseIdentifier-354b0ca8-9b6c-4722-aae7-e66906cc9eef

7. If the LDAPDisplayNames for labeledURI, secretary, and houseIdentifier
were mangled in step 6, run the Windows Server 2003 InetOrgPersonFix.ldf
script to recover, and then go to the "Upgrading Windows 2000 domain
controllers with Winnt32.exe" section.
a. Create a folder named %Systemdrive%\IOP, and then extract the
InetOrgPersonFix.ldf file to this folder.
b. At a command prompt, type cd %systemdrive%\iop.
c. Extract the InetOrgPersonFix.ldf file from the Support.cab file that is
located in the Support\Tools folder of the Windows Server 2003 installation
media.
d. From the console of the schema operations master, load the
InetOrgPersonFix.ldf file by using Ldifde.exe to correct the
LdapDisplayName attribute of the houseIdentifier, secretary, and labeledURI
attributes. To do so, type the following command, where <X> is a
case-sensitive constant and <dn path for forest root domain> is the domain
name path for the root domain of the forest:
C:\IOP>ldifde -i -f inetorgpersonfix.ldf -v -c DC=X "domain name path for
forest root domain"
Syntax notes:o DC=X is a case-sensitive constant.
o The domain name path for the forest root domain must be enclosed in
quotation marks.

After confirmation, you can upgrade from Win2k to Win2k3.

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: AcVbrQ3/16RkBhh8RauA5VYYS+8deQ==
>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>
<DEE756D4-E65F-4644-B0AA-36C49027B7B3@xxxxxxxxxxxxx>
<cM6FJMsWFHA.2476@xxxxxxxxxxxxxxxxxxxxx>
>Subject: Re: Migrating Windows 2000 domain to Windows 2003
>Date: Wed, 18 May 2005 06:25:27 -0700
>Lines: 312
>Message-ID: <6BFC1CC8-DBC1-4C76-90F3-722FCB9EAC6B@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:10225
>X-Tomcat-NG: microsoft.public.windows.server.migration
>
>Hi Amanda
>
>Though our domain is on windows 2000. We have exchange Server 2003 running
>on a Windows 2000 server box. and we have one Windows Server 2003 member
>server (which is our file server). Do I have to take any special
precautions,
>before i proceed with the upgrade?
>
>Thanks
>K.V
>
>"Amanda Wang [MSFT]" wrote:
>
>> 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"
>

.

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)