[cifs-protocol] FW: FW: Inconsistencies in ad-schema docs and text files SRX090109601490

[Hongwei Sun]

Trige,

   According to schema class document (MS-ADSC),  The adminDescription and AdminDisplayName are listed as systemMayContain  instead of SystemMustContain  in cn:Top.   The sub-level class attributeSchema and classSchema also don't require these two attributes as SystemMustContain.   Based on the schema,  it looks like that they are not mandatory attributes for either class or attribute object.  Actually  since  they are not listed for any attribute or class in the MS-ADAx/MS-ADSC documents so they are not included in the schema files we generated from the documents.
     
   I am so glad to see that you are making a lot of progresses.  It is a pleasure to work with you.   I downloaded and played the video,  but I can only hear your voice, not video.  Maybe it has something to do with Windows Media Player.

Thanks!

Hongwei   


-----Original Message-----
From: tridge at samba.org [mailto:tridge at samba.org] 
Sent: Monday, January 11, 2010 3:13 PM
To: Hongwei Sun
Cc: Andrew Bartlett; cifs-protocol at samba.org
Subject: RE: [cifs-protocol] FW: FW: Inconsistencies in ad-schema docs and text files SRX090109601490

Hi Hongwei,

 >   For adminDescription and adminDisplayName,  it looks like that they are already included in the schema file (MS-AD_Schema_2K8_R2_Attributes.txt).  Have I missed something ? 

Each attribute and class in the schema should have an adminDescription
and adminDisplayName attribute.

I suspect they aren't critical for most things, it would probably only
matter if some user app looked for the values specifically, but if you
can include them that would be great. I would hope apps would normally
look at the ldapDisplayName instead.

For now we're setting them equal to the cn in the little python script
that munges the raw schema into something we can load.

btw, with these schema fixes, the dcpromo test we worked on in Redmond
is now quite reliable. I've put out a little movie to demonstrate it:

   http://blog.tridgell.net/?p=12

Thanks very much for all of the help you gave us to make this
possible!

Cheers, Tridge