Hello,
We had a person on samba-technical mailing list complaining about
replication issues when openchange schema is added.
After some investigation I discovered that he add replication issue
because its schema was broken.
The reason why the schema is broken is because openchange lacked an
attribute and use a control to relax checks and samba had a too much
relaxed check for the mayContain attribute.
The missing attribute is:
#
dn: CN=msExch-Proxy-Gen-Options,${SCHEMADN}
objectClass: top
objectClass: attributeSchema
cn: msExch-Proxy-Gen-Options
attributeID: 1.2.840.113556.1.4.7000.102.50044
attributeSyntax: 2.5.5.9
isSingleValued: TRUE
showInAdvancedViewOnly: TRUE
adminDisplayName: msExch-Proxy-Gen-Options
adminDescription: msExch-Proxy-Gen-Options
oMSyntax: 2
searchFlags: 0
lDAPDisplayName: msExchProxyGenOptions
name: msExch-Proxy-Gen-Options
schemaIDGUID: 974c9a02-33fc-11d3-aa6e-00c04f8eedd8
isMemberOfPartialAttributeSet: FALSE
objectCategory: CN=Attribute-Schema,${SCHEMADN}
By adapting this ldif to your provision (ie. replacing ${SCHEMADN} by
CN=Schema, CN=Configuration,DC=domain,DC=tld) you should be able to load
this attribute and make your schema valid.
I also changed the relax on samba so that this kind of relax check
didn't occur anymore during samba or openchange provision but only for
very particular case.
Note: Don't forget to set "dsdb:schema update allowed" to yes in the
smb.conf while trying to load this ldif.
Matthieu.
_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel
