RE: Exchange 2000 and Server 2003 issue

From: Gayle Heizer [MSFT] (gaylehei_at_online.microsoft.com)
Date: 09/03/04 

Date: Fri, 03 Sep 2004 19:56:39 GMT

Hi Gene,

It looks like you are in Scenario two situation. Like most everyone. Then
you need to do the following steps and you should be good to go. You will
meet the criteria if you have exchange 2000 installed in the windows 2000
enviroment.

I hope this helps.

Gayle

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:

        KBLink:285172.KB.EN-US: Schema Updates Require Write Access to Schema
        in Active Directory

3. Click Start, click "Run", type "notepad.exe" (without the quotation
   marks), 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" (without the quotation marks),
and then click "OK".

        b. At a command prompt, type :
                
                 "cd <%systemdrive%>\iop" (without the quotation marks) and then press
ENTER.

        c. Type the following command:
                
                 "ldifde -i -f inetorgpersonprevent.ldf -v -c DC=<X> "<dn path for forest
root domain>"" (without the quotation marks) 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.

Relevant Pages

  • Re: Pre-ADPREP Question
    ... Upgrading Windows 2000 domain controllers to Windows Server 2003 ... Early Microsoft documentation recommends that you isolate the schema ...
    (microsoft.public.windows.server.migration)
  • Re: ADPrep /forestprep failed 2000 to 2003 r2
    ... Additional post the output from "schupgr" from the command prompt on the 2000 DC. ... Disclaimer: This posting is provided "AS IS" with no warranties, ... So which adprep version from the R2 disk do you run, ... Click Active Directory Schema, ...
    (microsoft.public.windows.server.active_directory)
  • Re: ADPrep /forestprep failed 2000 to 2003 r2
    ... Here is the output of the "schupgr" command. ... Upgrading schema to version 31 ... So which adprep version from the R2 disk do you run, ... "Active Directory Schema" is displayed in the Add/Remove ...
    (microsoft.public.windows.server.active_directory)
  • Re: Execute stored procedure via web method.
    ... The only thing I might add is that you can generate a class named Command ... from this schema that lets you bypass any need to directly manipulate XML ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Active Directory Schema Update
    ... The Windows Server 2003 R2 schema upgrades are required for R2 features. ... "You must update the schema before you upgrade an existing domain controller to Windows Server 2003 R2 or before you add the Active Directory domain controller role on a computer running Windows Server 2003 R2 by using the Active Directory Installation Wizard. ...
    (microsoft.public.windows.server.active_directory)