ObjectClass property in Forest-schema-files result in unintended update events

[AndiBellstedt]

The following PSD1 file for the schema attribute 'ms-DFSR-ReplicationGroupType' will result in a "unintended" update event.
Schema attribute "ms-DFSR-ReplicationGroupType" is listed in property 'mustContain' and NOT in property 'mayContain'. ADMF should take care on those differences and handle this.
Maybe ObjectClass has to split up in to attributes in the definition file?

Forest schema definition file

@{
    OID = '1.2.840.113556.1.6.13.3.10'
    Name = 'ms-DFSR-ReplicationGroupType'
    AdminDisplayName = 'ms-DFSR-ReplicationGroupType'
    LdapDisplayName = 'msDFSR-ReplicationGroupType'
    OMSyntax = 2
    AttributeSyntax = '2.5.5.9'
    SingleValued = $True
    AdminDescription = 'Type of Replication Group'
    SearchFlags = 0
    ObjectClass = 'ms-DFSR-ReplicationGroup'
    IsDefunct = $False
    Optional = $False
    ContextName = ''
    AdvancedView = $True
},

ADMF "change"-event

Type          : Update
ObjectType    : Schema
Identity      : ms-DFSR-ReplicationGroupType
Changed       : {ObjectClass: +ms-DFSR-ReplicationGroup}

AD class ms-DFSR-ReplicationGroup

the schema attribute "ms-DFSR-ReplicationGroupType" is listed in property 'mustContain' and NOT in property 'mayContain'.

>Get-ADObject -Filter 'Name -eq "ms-DFSR-ReplicationGroup"' -SearchBase $schemaNC -Properties * | Format-List adminDisplayName, *cont*


adminDisplayName : ms-DFSR-ReplicationGroup
mayContain       : {msDFSR-OnDemandExclusionDirectoryFilter, msDFSR-OnDemandExclusionFileFilter, msDFSR-DefaultCompressionExclusionFilter,      
                   msDFSR-Options2...}
mustContain      : {msDFSR-ReplicationGroupType}

ADMF version: 1.13.98
ForestManagement version: 1.5.71

[FriedrichWeinmann]

You are totally correct.
The next version (soon(tm)) shall have that resolved, by adding support for MayBeContainedIn and MustBeContainedIn settings.