Migrating Win2000 domain to Win2003

Migrating Win 2000 to Win2003

Part 1:AD Migrating

Updated:Jul-20-2009

Leo Li

1.       Make sure the win2000 domain control running is normal and already installed the newest service packs.

2.       Make sure the win2000 AD 5 FSMO in the first domain control(we need migration this FSMO to win2003).

3.       Insert the win2003 setup CD to win2000 first domain control.In the command line,go to CD folder \I386,run: adprep /forestprep,after successful then run:adprep /domainprep

Type C then Enter

NOTE:need run "adprep.exe /domainprep /gpprep" 

4.       Install the win2003 sp2 to new hareware and install the newest service packs.

5.       Make sure the new pc win2003 can access the network and fill the right DNS server,can connect to 2000 domain.

6.       Install the DNS service in win2003

7.       Running the command :dcpromo in win2003,upgrade the win2003 as the 2000 additional domain control.

8.       Make sure the DNS synchronization completed then change the win2003 DNS IP as self.

9.       Change the win2003 as the “Glocal Catalog” server

10.   Move FSMO role to win2003

11.   Downgrade the win2000

12.   AD migration completed.

13.   END

 

 

 

problem 1(11/Dec/1009):

error msg when upgrade 2003 as the AD:

1.the version of the active directory schema of the source forest is not compatible with the version of active directory on this computer.

 

solve: use adprep.exe R2 version to update the 2000 server.it be in "disk2\cmpnents\r2\adprep\"

check the schema version:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters

 

13=Microsoft Windows 2000

30=Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 (SP1)

31=Microsoft Windows Server 2003 R2

 

 

ADSI EDIT tools in Windows 2000 support tools

copy "adsiedit.msc" and "adsiedit.dll" to windows 2000 server "system32\"

then run "regsvr32 adsiedit.dll"

 

use adsiedit.msc to check the AD if is completed.

 

 

problem 2(8/Apr/2010):adprep /forestprep There is a schema conflict with Exchange 2000

"Adprep was unable to extend the schema.
[Status/Consequence]
There is a schema conflict with Exchange 2000. The schema is not updated.
[User Action]
The schema conflict must be resolved before running adprep. Resolve the schema conflict, allow the change to replicate between all replication partners, and then run Adprep. For information on resolving the conflict, see Microsoft Knowledge
Base article Q325379."

**************************************************************************************
solve:

Microsoft Article ID : 314649

Scenario 2: Exchange 2000 Schema Changes Are Installed Before You Run the Windows Server 2003 adprep /forestprep Command
If Exchange 2000 schema changes have already been installed, but you have not run the adprep /forestprep command in Windows Server 2003, 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 administrators enterprise administrators groups.  
2. Enable Schema Updates on the schema master. For additional information about how to permit updates to the Active Directory schema, click the following article number to view the article in the Microsoft Knowledge Base:
285172 () Schema Updates Require Write Access to Schema in Active Directory  
3. Click Start, click Run, type notepad.exe, and then click OK.
4. Copy the following text that appears between [start copy here] and [end copy here] (including the trailing "-" characters), and then paste this text into Notepad.

[start copy here]
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
-
[end copy here]
5. Save the contents of the Notepad file as %systemdrive%\IOP\Inetorgpersonprevent.ldf (where %systemdrive% is the logical drive that is hosting the Windows 2000 operating system and \IOP is a folder that you create in the Save dialog box of Notepad. Quit Notepad.
6. Run the InetOrgPersonPrevent.ldf script: a.  Click Start, click Run, type cmd, and then click OK.
b.  At a command prompt, type :
cd %systemdrive%\iop
and then press ENTER.
c.  Type the following command:
ldifde -i -f inetorgpersonprevent.ldf -v -c DC=X "dn path for forest root domain"
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 enclosed in quotation marks ("dc=corp,dc=tailspintoys,dc=com") is the domain name path for the root domain of the forest. (Include the quotation marks.) Press ENTER.
 
7. Verify that the LDAPDisplaynames for the CN=ms-Exch-Assistant-Name, the CN=ms-Exch-LabeledURI, and the 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 command.
8. Run the adprep /forestprep command and the /domainprep command.

For more information, view the "Overview: Upgrading Windows 2000 Domain Controllers to Windows Server2003" section of the following Microsoft Knowledge Base article:
325379 () How to Upgrade Windows 2000 Domain Controllers to Windows Server 2003  
**************************************************************************