Announcement

Collapse
No announcement yet.

Help with Adprep on a W2k machine running Exchange 2000

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Help with Adprep on a W2k machine running Exchange 2000

    Hi All,

    I inherieted a network which currently runs a W2k Server SP4 with Exchange Svr 2000. This machine is a DC with all the typical services running, AD, DNS, DHCP etc. I want to retire this machine and am in the process of building a W2k3 domain. We currently have one domain, one forest.

    The new network will host 2 machines - 1 DC (File Svr-W2k3-32bit); 1 member (Exchange 2007 - 64 bit/W2K3 64bit).

    My problem is with Adpreping the W2K machine. I have read the MS Article KB325379 as well as the link here on Petris website : W2k3 adprep fix for e2k and have had no joy.

    The first thing I did was to run ldifde.exe /i /f inetOrgPersonFix.ldf /c "DC=X" "DC=mycorp,DC=com"

    I received the following error:
    C:\IOP>ldifde.exe /i /f inetOrgPersonFix.ldf /c "DC=X" "DC=umallondon,DC=net"
    Connecting to "UMAL.UMALLONDON.NET"
    Logging in as current user using SSPI
    Importing directory from file "inetOrgPersonFix.ldf"
    Loading entries.
    Add error on line 3: No Such Object
    The server side error is "Directory object not found."
    0 entries modified successfully.
    An error has occurred in the program

    The version of Adprep on my W2k3 disk is 5.2.3790.2075.

    This the inetOrgPersonFix.ldf file syntax:

    dn: CN=secretary,CN=Schema,CN=Configuration,DC=X
    changetype: Modify
    replace: lDAPDisplayName
    lDAPDisplayName: secretary
    -
    dn: CN=labeledURI,CN=Schema,CN=Configuration,DC=X
    changetype: Modify
    replace: lDAPDisplayName
    lDAPDisplayName: labeledURI
    -
    dn: CN=houseIdentifier,CN=Schema,CN=Configuration,DC=X
    changetype: Modify
    replace: lDAPDisplayName
    lDAPDisplayName: houseIdentifier
    -
    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
    -

    I tried googling the error but could'nt find anything specific relating to my problem.

    So I thought perhaps the attributes may already be mangled and ran the inetOrgPersonPrevent.ldf. This is what I got:

    C:\IOP>ldifde -i -f inetorgpersonprevent.ldf -v -c DC=X "dc=umallondon,dc=net"
    Connecting to "UMAL.UMALLONDON.NET"
    Logging in as current user using SSPI
    Importing directory from file "inetorgpersonprevent.ldf"
    Loading entries
    1: CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,dc=umallondon,dc=n et
    Add error on line 1: No Such Attribute
    The server side error is "The parameter is incorrect."
    0 entries modified successfully.
    An error has occurred in the program

    This was as equally baffling and once again I tried googling the error as well as going on MS website.

    The syntax from the inetorgpersonprevent.ldf file is as follows:

    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
    -

    As I intially got errors, I just thought I would try adprepping the machine. At this point I thought what do I have to lose? Well, this time I get "Adprep was unable to extend the schema". Eh gads....

    Log info as follows:

    Adprep created the log file ADPrep.log under C:\WINNT\system32\debug\adprep\logs\20110303111255 directory.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\schema.ini from installation point to local machine under directory C:\WINNT.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\sch14.ldf from installation point to local machine under directory C:\WINNT\system32.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\sch15.ldf from installation point to local machine under directory C:\WINNT\system32.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\sch16.ldf from installation point to local machine under directory C:\WINNT\system32.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\sch17.ldf from installation point to local machine under directory C:\WINNT\system32.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\sch18.ldf from installation point to local machine under directory C:\WINNT\system32.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\sch19.ldf from installation point to local machine under directory C:\WINNT\system32.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\sch20.ldf from installation point to local machine under directory C:\WINNT\system32.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\sch21.ldf from installation point to local machine under directory C:\WINNT\system32.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\sch22.ldf from installation point to local machine under directory C:\WINNT\system32.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\sch23.ldf from installation point to local machine under directory C:\WINNT\system32.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\sch24.ldf from installation point to local machine under directory C:\WINNT\system32.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\sch25.ldf from installation point to local machine under directory C:\WINNT\system32.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\sch26.ldf from installation point to local machine under directory C:\WINNT\system32.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\sch27.ldf from installation point to local machine under directory C:\WINNT\system32.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\sch28.ldf from installation point to local machine under directory C:\WINNT\system32.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\sch29.ldf from installation point to local machine under directory C:\WINNT\system32.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\sch30.ldf from installation point to local machine under directory C:\WINNT\system32.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\sch31.ldf from installation point to local machine under directory C:\WINNT\system32.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\dcpromo.csv from installation point to local machine under directory C:\WINNT\system32\debug\adprep\data.

    Adprep copied file D:\CMPNENTS\R2\ADPREP\409.csv from installation point to local machine under directory C:\WINNT\system32\debug\adprep\data.

    Adprep successfully made the LDAP connection to the local domain controller UMAL.

    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is (null).

    LDAP API ldap_search_s() finished, return code is 0x0

    Adprep successfully retrieved information from the local directory service.

    Adprep successfully initialized global variables.
    [Status/Consequence]
    Adprep is continuing.


    ADPREP WARNING:

    Before running adprep, all Windows 2000 domain controllers in the forest should be upgraded to Windows 2000 Service Pack 1 (SP1) with QFE 265089, or to Windows 2000 SP2 (or later).

    QFE 265089 (included in Windows 2000 SP2 and later) is required to prevent potential domain controller corruption.

    For more information about preparing your forest and domain see KB article Q331161 at MS support

    [User Action]
    If ALL your existing Windows 2000 domain controllers meet this requirement, type C and then press ENTER to continue. Otherwise, type any other key and press ENTER to quit.

    Adprep was unable to extend the schema.
    [Status/Consequence]
    There is a schema conflict with Exchange 2000. The schema is not upgraded.
    [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.

    ADDITIONAL INFO:

    1. Ran FSMO roles and they all came back ok.
    2. Ran DCdiag - All tests passed
    3. Ran ldap - results came back 'null

    Not sure what else to check for. This is a single forest, single domain. I am logged on as Administrator.

    GAH!!!!...so, if anyone can shed some light on my problem, I would be more than grateful.

    Thanks in advance to anyone who can help.

    Best regards,
    Rhonda

  • #2
    Re: Help with Adprep on a W2k machine running Exchange 2000

    Hi,

    Go through this article

    How to upgrade Windows 2000 domain controllers to Windows Server 2003
    http://support.microsoft.com/kb/325379
    Thanks & Regards
    v-2nas

    MCTS 2008, MCTIP, MCSE 2003, MCSA+Messaging E2K3, MCP, E2K7
    Sr. Wintel Eng. (Investment Bank)
    Independent IT Consultant and Architect
    Blog: http://www.exchadtech.blogspot.com

    Show your appreciation for my help by giving reputation points

    Comment


    • #3
      Re: Help with Adprep on a W2k machine running Exchange 2000

      Hi v-2nas,

      If you read my above post, I already mentioned that I ran through MS KB 325379 with no luck.

      Thanks for the suggestion though.

      Regards,

      Rhonda

      Comment


      • #4
        Re: Help with Adprep on a W2k machine running Exchange 2000

        Right..ok I ran through Scenario 2 again via the KB 325379.

        This was my result:

        C:\Documents and Settings\Administrator>ldifde -i -f inetorgpersonprevent.ldf -v
        -c DC=X "dc=umallondon,dc=net"
        Connecting to "UMAL.UMALLONDON.NET"
        Logging in as current user using SSPI
        Importing directory from file "inetorgpersonprevent.ldf"
        Loading entries
        1: CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,dc=umallondon,dc=n et
        Add error on line 1: No Such Attribute
        The server side error is "The parameter is incorrect."
        0 entries modified successfully.
        An error has occurred in the program

        This is the Script Syntax I am using:
        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
        -

        Can anyone see any problems anywhere?

        Regards,

        Rhonda

        Comment


        • #5
          Re: Help with Adprep on a W2k machine running Exchange 2000

          Hi,

          What is service pack and rollup update on your exchange server.
          Thanks & Regards
          v-2nas

          MCTS 2008, MCTIP, MCSE 2003, MCSA+Messaging E2K3, MCP, E2K7
          Sr. Wintel Eng. (Investment Bank)
          Independent IT Consultant and Architect
          Blog: http://www.exchadtech.blogspot.com

          Show your appreciation for my help by giving reputation points

          Comment


          • #6
            Re: Help with Adprep on a W2k machine running Exchange 2000

            Hi v-2nas,

            Thanks for getting back to me.

            DC is running Windows 2000 SP4 Version 5.0 Build 2195 SP4 and Exchange Ver 6.0 Build 6249.4 SP3.

            Do you need any further info?

            Regards,

            Rhonda

            Comment


            • #7
              Re: Help with Adprep on a W2k machine running Exchange 2000

              Originally posted by RLH60 View Post
              Right..ok I ran through Scenario 2 again via the KB 325379.

              This was my result:

              C:\Documents and Settings\Administrator>ldifde -i -f inetorgpersonprevent.ldf -v
              -c DC=X "dc=umallondon,dc=net"
              Connecting to "UMAL.UMALLONDON.NET"
              Logging in as current user using SSPI
              Importing directory from file "inetorgpersonprevent.ldf"
              Loading entries
              1: CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,dc=umallondon,dc=n et
              Add error on line 1: No Such Attribute
              The server side error is "The parameter is incorrect."
              0 entries modified successfully.
              An error has occurred in the program

              This is the Script Syntax I am using:
              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
              -

              Can anyone see any problems anywhere?

              Regards,

              Rhonda
              why it's connecting to your child domain
              "dc=umallondon,dc=net"
              Connecting to "UMAL.UMALLONDON.NET"

              Try to run it from you root domain, on Schema master role holder. Just recreate the file and then try.

              Do you get an event logged in app log for this error? if, then post
              Last edited by v-2nas; 4th March 2011, 00:44.
              Thanks & Regards
              v-2nas

              MCTS 2008, MCTIP, MCSE 2003, MCSA+Messaging E2K3, MCP, E2K7
              Sr. Wintel Eng. (Investment Bank)
              Independent IT Consultant and Architect
              Blog: http://www.exchadtech.blogspot.com

              Show your appreciation for my help by giving reputation points

              Comment


              • #8
                Re: Help with Adprep on a W2k machine running Exchange 2000

                Hi v-2nas,

                I am not sure what your referring to in your question - i.e connecting to our child domain. As far as I can tell this is our root domain.

                ran this script just to verify: cscript forestroot2.vbs and this was my result.

                C:\>cscript forestroot2.vbs
                Microsoft (R) Windows Script Host Version 5.6
                Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
                Root Domain: DC=UMALLONDON,DC=NET

                This machine is the Schema Master - it also has all FSMO roles being the only DC in the forest.

                Apart from the lfide log being created, I couldn't find anything in my app log relating to this event.

                Any other suggestions? I am baffled as to why such a simple task has become such a nightmare.

                Regards,

                Rhonda

                Comment


                • #9
                  Re: Help with Adprep on a W2k machine running Exchange 2000

                  Any reason why you are updating an 11 year old operating system to an 8 year old operating system? If you are going to do all this work, why not go straight to Server 2008 R2 and not have to go through this process again for several years?
                  1 1 was a racehorse.
                  2 2 was 1 2.
                  1 1 1 1 race 1 day,
                  2 2 1 1 2

                  Comment


                  • #10
                    Re: Help with Adprep on a W2k machine running Exchange 2000

                    Hi biggles 77,

                    In response to your query, I would love to go ahead with a 2008 build, but we have a few constraints. Firstly, we are a small firm with limited money and resources. We already have a 2003 Server built waiting to be promoted into a new 2003 domain. We also have certain legacy accounting software that has not been tested to run off Windows 2008, and since this is the crux of our buisness we cannot afford to go ahead with 2008 willy nilly before talking to the vendors and PTB to see if this is a viable option in the future.

                    Secondly, we already own the licenses for 2003 server, and should we decide to upgrade to 2008, we would have purchase said licenses which costs have not been scheduled into the budget this year

                    Thirdly, we still would have to do adprep/domain prep into 2008 domain and I imagine I still would be getting grief with it, and until I can try 2008 in test environment, I really would not feel comfortable just forging ahead with a new build. Besides, I would like to famliarise myself with the software first.

                    So there are you answers in a nutshell. Thanks for you question, as I am sure anyone reading this was probably thinking the same thing.

                    Regards,

                    Rhonda

                    Comment


                    • #11
                      Re: Help with Adprep on a W2k machine running Exchange 2000

                      Hi,

                      I ran through the whole thread once again. I found that the first one, where you get an error at line 3 the text say IDAP instead of LDAP.
                      Ok that had been fixed but again you got the error at line 1
                      If you notice that last part of DN is incorrect, dc=n et, notice the space. I am not sure if it's due to copy and paste or if you really have it in the script file.

                      Cross check it.
                      Thanks & Regards
                      v-2nas

                      MCTS 2008, MCTIP, MCSE 2003, MCSA+Messaging E2K3, MCP, E2K7
                      Sr. Wintel Eng. (Investment Bank)
                      Independent IT Consultant and Architect
                      Blog: http://www.exchadtech.blogspot.com

                      Show your appreciation for my help by giving reputation points

                      Comment


                      • #12
                        Re: Help with Adprep on a W2k machine running Exchange 2000

                        Sorry Rhonda, not able to help you with your problem but as for the Legacy stuff, keep Virtualisation in the back of your mind. DOS 6.22 (and other apps) runs really fast in a Virtual PC.
                        1 1 was a racehorse.
                        2 2 was 1 2.
                        1 1 1 1 race 1 day,
                        2 2 1 1 2

                        Comment

                        Working...
                        X