Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

How can I change 'Person' SUP ( Top $ ndsLoginProperties ) STRUCT URAL MUST to "'Person' SUP ndsLoginProperties STRUCTURAL MUST"

See for more informations: http://www.novell.com/support/viewContent.do?externalId=7003431&sliceId=1

It is the solution of an error which I had when I tried to create an user in AD. (Environnement: Many Netware server 8.7.X & 8.8 Server OES2 sp1 with DSfW)

Are there any risks to change this ldap parameter?

Cheers.

share|improve this question

1 Answer 1

There are really only two ways to modify base schema in eDirectory. Used to be only one, which was to call Novell Technical Services (NTS) and have them use DSDump, (effectively a hex editor for eDirectory) and twiddle the bits by hand.

I have had them do this when merging two trees that had ALMOST but not perfectly compatible schema (Two flags on three attributes were different for no apparent reason, and were meaninglessly different).

The second possible way is to delete, then add the attribute in a single LDIF operation. That is a shown as a possibility in this TID: Changing schmea

The LDIF ought to look something like:

ersion: 1

dn: cn=schema changetype: modify delete: objectclasses

objectClasses:(2.1.5.5.5)

add: objectclasses objectClasses: (2.1.5.5.5 NAME 'MyObjectClass' MAY (attr1) X-NDS_NOT_CONTAINER '1')

But in your case, replace the appropriate details with yours.

I suppose a third way, is when such a problem is identified and a specific fix is offered in DSrepair to fix it. (There was an old base schema setting for creatorsName and modifiersName that originally was DN syntax, but that was a terrible idea, as if you deleted the object that created users, the creatorsName was cleared, which caused all sorts of problems. There was a DSrepair addition that would recognize this error and fix it. If this turns out to be a real problem, they likely will offer this kind of a solution.

However until then, your best bet is to open an incident for NTS to dial in and use DSDump to fix it by hand. It literally can take a minute or three to do.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.