none
[MS-OXCDATA] 2.12 Restrictions - undocumented restrictType? RRS feed

  • Question

  • I was chasing down a parse error that only seemed to occur under Loadgen with the Exchange 2007 profiles. The problem turned out to be an undocumented RestrictType, 0xFF, that apparently means NONE or EMPTY. It is used as a placeholder value in properties with pidTagRuleCondition, pTypRestriction. RestrictType values are documented in [MS-OCXDATA] 2.12.

    I understand that LoadGen is not supported, but since Exchange server 2007 will both accept this in RopModifyRules and return it in RopQueryRows to any client, it seems like it should be documented.

    Anyway it's dirt simple. No parameters, just the restrictType byte.

    Thanks,

    John Lowery, Quest Software

     

    Friday, August 26, 2011 11:36 PM

Answers

  • Hi John,

    Closing the loop on this on the forums.  The restrictType value will be documented in a future release of the documentation.

    Regards,

    Mark Miller

    Escalation Engineer

    US-CSS DSC PROTOCOL TEAM

    Friday, December 2, 2011 9:55 PM

All replies

  • Hi, John,

       Thanks for the question.  One of our team members will work on it and respond to you soon.

     

     

     


    Hongwei Sun -MSFT
    Saturday, August 27, 2011 9:04 PM
  • Hi John,

    I will investigate and submit a request for this to be documented.

    Regards,

    Mark Miller

    Escalation Engineer

    US-CSS DSC PROTOCOL TEAM

    Tuesday, August 30, 2011 2:19 PM
  • Hi John,

    Closing the loop on this on the forums.  The restrictType value will be documented in a future release of the documentation.

    Regards,

    Mark Miller

    Escalation Engineer

    US-CSS DSC PROTOCOL TEAM

    Friday, December 2, 2011 9:55 PM