RE: Adprep /Forestprerp Error on line 333

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: ESWAdmin (ESWAdmin_at_discussions.microsoft.com)
Date: 12/29/04 

Date: Wed, 29 Dec 2004 08:31:09 -0800

Bob,

We are in the process of moving from a Windows 2000 domain to a Windows 2003
domain. We are not currently running Exchange, but Exchange 2000 was used in
the past. I have read the articles about mangeled characters. My plan is to
upgrade the Forest and Domain using the adprep tool, promote my 2003 member
servers to Domain controllers, and then transfter the FSMO roles and retire
the old 2000 domain controllers. In running the adprep /Forestprep command,
I am receiving this same Error on line 333. I have been following along with
your response and was hoping that you could send me the schchk.vbs file so
that I could diagnose the problem. Thanks for your time.

"Bob Qin [MSFT]" wrote:

> Hi Will,
>
> Thanks for your posting here.
>
> Please try the following steps.
>
> 1.Download schchk.vbs attached in my post.
>
> 2 Now dump out the schema with the following command:
>
> LDIFDE -d "cn=schema,cn=configuration,dc=<forest root domain>,dc=com" -f
> schema.ldf
>
> 3. Get the .ldf file referenced in the ADPREP error (usually sch18.ldf).
> You can get this from the 2003 CD-ROM.
> 4. Copy the schema.ldf you created and the sch18.ldf file into the same
> directory as schchk.vbs, then run the command below:
>
> cscript schchk.vbs schema.ldf sch18.ldf
>
> The output will look similar to this:
>
> schchk run at 12/5/2003 5:16:29 PM
> schema file schema.ldf
> schema addition file sch18.ldf
> Reading schema: done (8.269531).
> 1080 attributes and 183 classes.
>
> Processing file to check:
> DN cn=preferredlanguage,cn=schema,cn=configuration,dc=orgbc,dc=com is
> attempting to
> change oid from 1.2.840.114050.1.1.1.1.90 to 2.16.840.1.113730.3.1.39
> Oid will not be changed resulting in probable failure to add a new class.
> Class inetOrgPerson has a systemMayContain attribute that is not present
> 2.16.840.1.113730.3.1.39
> done (0.015625).
>
> 5. Add the following registry value on the schema master.
>
> HKLM\System\CurrentControlSet\Services\NTDS\Parameters
> Value Name: Schema Update Allowed
> Value Type: REG_DWORD
> Value Data: 1
>
> 6. Open LDP on the schema master.
> 7. Click the Connection menu, select Bind (no need to specify credentials
> if you are logged in as administrator).
> 8. Click the View menu, select Tree.
> 9. Type the following in the BaseDN: field:
>
> cn=schema,cn=configuration,dc=<forest root domain>,dc=com
>
> 10. In the left pane, right-click the object causing the error and select
> Modify (the object will be either CN=preferredLanguage
>
> 11. In the Modify dialog box, add the following:
>
> Attribute: adminDisplayName
> Values: COGNOSpreferredLanguage
> Operation: Replace
>
> 12. Click Enter, then Run.
> 13. Modify the LDAPDisplayName attribute in the same way, changing either
> preferredLanguage to COGNOSpreferredLanguage.
> 14. Next select the Browse menu, click Modify RDN. Depending on which
> object is
> causing the error, make the following change:
>
> Old Dn: CN=preferredLanguage,CN=Schema,CN=Configuration,DC=<forest root
> domain>,DC=com
> New Dn: CN=COGNOSpreferredLanguage,CN=Schema,CN=Configuration,DC=<forest
> root
> domain>,DC=com
>
> Rerun ADPREP /FORESTPREP. Remember to remove the ¡°Schema Update Allowed"
> registry value when finished.
>
> Wish the information helps.
>
> Regards,
> Bob Qin
> Product Support Services
> Microsoft Corporation
>
> 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.
> ====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights

Relevant Pages

  • Re: Migration
    ... I have checked the object in the schema, still i can able to see all three ... if i am running exchange 2003 setup /forestprep whether ... so bring new windows 2003 DC i need to avoid the object mangling issue. ... If "Secretary" is missing I'd expect that those are mssing, ...
    (microsoft.public.exchange.admin)
  • RE: Adprep /Forestprerp Error on line 333
    ... Is this information in a knowledge base article that I can reference? ... an attribute so there is no conflict or a way to modify an attribute. ... > 2 Now dump out the schema with the following command: ... > preferredLanguage to COGNOSpreferredLanguage. ...
    (microsoft.public.windows.server.migration)
  • Re: How to split XML file based on data in BizTalk
    ... I cannot modify the source schema. ... I build a custom pipeline component that split the XML document into ...
    (microsoft.public.biztalk.general)
  • RE: Adprep /Forestprerp Error on line 333
    ... > 2 Now dump out the schema with the following command: ... right-click the object causing the error and select ... In the Modify dialog box, ... > preferredLanguage to COGNOSpreferredLanguage. ...
    (microsoft.public.windows.server.migration)
  • Re: User Default Attributes
    ... You have to modify the default security of the object class user within the ... Tools, Schema Manager, DSACLS as well Scripting. ... >I am trying to lock down a user's default attributes so that they cannot> change the fields themselves. ... > Click the Look In drop down box and select Active Directory> Look up the username you are logged in under and click Search> ...
    (microsoft.public.windows.server.active_directory)