Windows Server

bob_bot · Guest

I am receiving this message when running the forest prep. I do not have
an Exchange server in my forest so I'm baffled as to why I am getting the
message.

"isSingleValued" attribute value for objects defined in Windows 2000 schema
and extended schema do not match.

A previous schema extension has defined the attribute value as "TRUE" for
object "CN=uid,CN=Schema,CN=Configuration,DC=win2k,DC=domain,DC=local"
differently than the schema extension needed for Windows 2003 server .

[Status/Consequence]

Adprep cannot extend your existing schema

[User Action]

Contact the vendor of the application that previously extended the schema to
resolve the inconsistency. Then run adprep again.

Vincent Xu [MSFT] · Guest

Hi Bob,

I have following suggestions.

1. Check if you running command from win2k3 CD on schema master as an
enterprise admin.

2. Send me adprep.log

3. Non-RFC compliant OIDs added to Schema by third party applications cause
the Froestprep schema update to fail.There are 5 different 3rd-party
applications that cause this problem - Cisco Call Manager, Cognos, SAP,
Trinity, and Apple. They all add a non-RFC compliant OID to the schema.
However each application does it for a different object.To determine which
object is causing ADPREP to fail, Please follow the steps as below:
1) I attached a zip file, uncompress it.
2) Run command LDIFDE -d "cn=schema,cn=configuration,dc=<forest root
domain>,dc=com" -f schema.ldf
Note: The above command should be on one line.

3)Get the .ldf file referenced in the ADPREP error (usually sch18.ldf). You
can get this from the Windows Server 2003 CD-ROM or from the
%systemroot%\system32 folder.

4)Copy the schema.ldf you created in step #2 and the sch18.ldf file into
the same directory as schchk.vbs, then run the command below:
cscript schchk.vbs schema.ldf sch18.ldf

Note: Since wscript is the default scripting engine, you must either
specify cscript as in the command above, or change the default scripting
engine to cscript by running "cscript //h:cscript"

Schchk.vbs will compare the two files and return output saved to
schchk.log. Send me the schchk.log.

My email is: v-xuwen@microsoft.com

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

--------------------

Vincent Xu [MSFT] · Guest

Hi Bob,

From the log you sending me:

DN cn=uid,cn=schema,cn=configuration,dc=bi,dc=brin,dc=com is attempting to
change oid from 1.2.840.113556.1.4.7000.187.102 to 0.9.2342.19200300.100.1.1
Oid will not be changed resulting in probable failure to add a new class.

Class inetOrgPerson has a systemMayContain attribute that is not present
0.9.2342.19200300.100.1.1 done (0.1015625).

we will find that the uid object was causing the error. The other object
that commonly causes this is the labeledURI object.

Follow the steps as below:

1.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

2.Open LDP on the schema master.

Regarding LDP, please refer to:
<http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/Tech
Ref/4efcf47f-e3eb-46e4-9c6c-842b39eca201.mspx>

3.Click the Connection menu, select Bind (no need to specify credentials if
you are logged in as administrator).

4.Click the View menu, select Tree

5.Type the following in the BaseDN: field:

cn=schema,cn=configuration,dc=<forest root domain>,dc=com

6. In the left pane, right-click the object causing the error and select
Modify (the object will be CN=uid )

7.In the Modify dialog box, added the following and Clicked Enter, then
Run.:
Attribute: adminDisplayName
Values: COGNOSuid
Operation: Replace

8. Modified the LDAPDisplayName attribute in the same way, changing uid to
COGNOSuid.

9. Selected the Browse menu, clicked Modify RDN. Made the following change:
Old Dn: CN=uid,CN=Schema,CN=Configuration,dc=bi,dc=brin,dc=com
New Dn: CN=COGNOSuid,CN=Schema,CN=Configuration,dc=bi,dc=brin,dc=com

10. Ran adprep /forestprep to see the efforts.

Hope it helps.

Best regards,

Vincent Xu
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.

This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx.

Newsgroup Web Interface Upgrade

Please complete a one-time registration process on your first visit to the
Partner Portal beginning July 11, 2005 at 9 A.M. PST by entering the secure
code mspp2005 when prompted. This secure code will be valid for 6 months
after which you will need to update your registration by entering the new
secure code. We will post announcements in the newsgroups prior to
expiration. Once you have entered the secure code mspp2005 , you will be
able to update your profile and access the the partner newsgroups. Please
update your Favorites link to the newsgroups web page, your current link
will redirect until November 1, 2005.

Please post any comment, questions or concerns to the
microsoft.private.directaccess.partnerfeedback newsgroup. For more
information, please go to:
https://partner.microsoft.com/global/technicalsupport/registeredsupport/4001
4662

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

Vincent Xu [MSFT] · Guest

Hi,

It maybe the ldp's problem. We may ignore it. We may use adsiedit.msc to
edit the object too.

Hope it helps.

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

--------------------

Vincent Xu [MSFT] · Guest

Hi,

1. run "adsiedit.msc"
2. expand "schema" at left column and click "cn=schema,cn=configuration...."
3. find "cn=uid...." at right column and double click it
4. find Attribute: adminDisplayName and click edit and change it to
COGNOSuid
5. find Attribute: LDAPDisplayName and click edit and change it to COGNOSuid

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

--------------------

	Windows Server Forum Index -> Migration	All times are GMT
Page 1 of 1