I'm experimenting with AD running in a W2008R2 virtual machine. AD is
running in 2003 mode. It's a fresh, empty instance except for my defined
attributes and an import of the "eduperson" schemas.
I'm adding a new object class, ported over from our existing OpenLDAP
directory. At first I added the "dalPerson" class using the Schema MMC;
it added it fine, and even with the correct attributes, but it used
'cn' as the rdnAttrId (it didn't ask), which is wrong. So I marked the
object as defunct and composed an .ldif file:
dn: CN=dalPerson,CN=Schema,CN=Configuration,DC=Dal,DC= Ca
objectClass: classSchema
cn: dalPerson
lDAPDisplayName: dalPerson
adminDisplayName: dalPerson
adminDescription: Consists of a set of data elements or attributes about individuals at Dalhousie
governsID: 1.3.6.1.4.1.13095.2.2.1
objectClassCategory: 3
rdnAttId: dalUUID
mayContain: dalBannerID
mayContain: dalChangePasswordCode
mayContain: dalLastSeen
mayContain: dalPasswordExpiresOn
mayContain: dalExpiresOn
mayContain: dalPublish
mayContain: dalBarCode
mayContain: dalPersonExpiredAffiliation
mayContain: dalPersonInternationalNumber
mayContain: dalPersonEmergencySMSNumber
mayContain: dalPersonEmployeeTypeClass
mustContain: dalUUID
defaultObjectCategory: CN=dalPerson,cn=Schema,cn=Configuration,dc=DAL,dc= CA
systemOnly: FALSE
Now when I try to add this using ldifde, it gives me a "will not perform"
error with the explanation "duplicate RDN". Even if I go in and try
changing 'cn' from 'dalPerson' to 'dalPersonv2' it still fails with the
same error. I've even gone to the extreme of renaming the defunct schema
definition to 'dalperson-Old' and it made no difference.
A google search finds the "duplicate rdn" cited many, many times but no
explanations of the cause or the fix in this context.
What "rdn" is it complaining about here?
--
Brandon Hume - hume -> BOFH.Ca,
http://WWW.BOFH.Ca/
Linear Mode
