Revision Summary Date Revision History Revision Class Comments 7/25/2008 0.1 Editorial Initial Availability. 8/29/2008 1.0 Major Added section 2.3. 10/24/2008 2.0 Updated and revised the technical content. 12/5/2008 2.0.1 Editorial Changed language and formatting in the technical content. 1/16/2009 2.0.2 Editorial Changed language and formatting in the technical content. 2/27/2009 2.1 Clarified the meaning of the technical content. 4/10/2009 2.2 Clarified the meaning of the technical content. 5/22/2009 2.3 Minor Clarified the meaning of the technical content. 7/2/2009 2.3.1 Editorial Changed language and formatting in the technical content. 8/14/2009 2.3.2 Editorial Changed language and formatting in the
technical content. 9/25/2009 3.0 Updated and revised the technical content. 11/6/2009 3.0.1 Editorial Changed language and formatting in the technical content. 12/18/2009 4.0 Major Updated and revised the technical content. 1/29/2010 5.0 Major Updated and revised the technical content. 3/12/2010 6.0 Major Updated and revised the technical content. 4/23/2010 6.0.1 Editorial Changed language and formatting in the technical content. 6/4/2010 7.0 Major Updated and revised the technical content. 7/16/2010 8.0 Updated and revised the technical content. 8/27/2010 9.0 Major Updated and revised the technical content.
10/8/2010 10.0 Major Updated and revised the technical content. 11/19/2010 11.0 Major Updated and revised the technical content. 1/7/2011 12.0 Major Updated and revised the technical content. 2/11/2011 13.0 Major Updated and revised the technical content. 3/25/2011 14.0 Major Updated and revised the technical content. 5/6/2011 15.0 Major Updated and revised the technical content. 6/17/2011 15.1 Minor Clarified the meaning of the technical content. 9/23/2011 15.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 16.0 Major Updated and revised the technical content. 3/30/2012 16.1 Minor Clarified the meaning of the
technical content. 7/12/2012 16.2 Minor Clarified the meaning of the technical content. 10/25/2012 17.0 Major Updated and revised the technical content. 1/31/2013 17.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 18.0 Major Updated and revised the technical content. 11/14/2013 18.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 18.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 18.0 None No changes to the meaning, language, or formatting of the technical content.
user ([MS-ADSC] section 2.268) CN=<name>, CN=Users, <root> mSMQSiteLink section 2.167) CN=<routing link name>, CN=MsmqServices, CN=Services, CN=Configuration, <root> mSMQSettings section 2.166) CN=MSMQ Settings, CN=<computer name>, CN=Servers, CN=<site name>, CN=Configuration, <root> ([MS-ADSC] section 2.160) CN=<name>, CN=Users, <root> group ([MS-ADSC] section 2.55) CN=<name>, CN=Users, <root> name> MUST be the "QueueName" portion of an MSMQ Queue Name as specified in section 2.1.1. <computer name> MUST be the "Computer" portion of an MSMQ Name as specified in section 2.1.1. <site name> MUST be the Site.Name ADM element attribute specified in section 3.1.1.7. <routing link name> is specified in section of this document. <name> is a string identifier that MUST be unique among all objects of the same type in Active Directory. In each case, <root> MUST be a common root for these entries, which is the rootDomainNamingContext as specified in section 3.1.1.3.2.16. Attributes of Directory Objects This table lists the attributes used by the Directory Service Schema Mapping for each of the classes listed in section . Object Attributes mSMQQueue objectGUID ( section 2.44) mSMQLabelEx ( section 2.549) whenCreated ([MS-ADA3] section 2.371) whenChanged ([MS-ADA3] section 2.370) mSMQQueueType ([MS-ADA2] section 2.564) mSMQJournal ([MS-ADA2] section 2.546)
Raise a event. The event takes no arguments. If the rStatus returned is not DirectoryOperationResult.Success, rStatus MUST be set to DirectoryOperationResult.DirectoryNotConnected, and processing MUST end. Otherwise, let DirectoryServerConnection be a variable of type ADCONNECTION_HANDLE ([MS-DTYP] section 2.2.2), which is initialized to the value returned in rADConnection. If iGuid is supplied, perform the following steps: Raise a event with the following arguments: = iGuid iADConnection = DirectoryServerConnection If the value of rStatus returned by the event is not DirectoryOperationResult.Success, rStatus MUST be set to the value of rStatus returned by the event, and processing MUST end. Set iPath to the value of rDN. Construct an LDAPMessage ( section 4.1): messageID = set as described in [RFC2251] section 4.1.1.1. protocolOp = searchRequest controls = none baseObject = iPath scope = baseObject derefAliases = neverDerefAliases sizeLimit = 0 timeLimit = 0 typesOnly = filter = "(objectClass=*)" attributes = a one-element list consisting of the string "objectClass" Perform the Performing an LDAP Operation on an ADConnection ( section 7.6.1.6) task with the following parameters: TaskInputADConnection = DirectoryServerConnection TaskInputRequestMessage = the LDAPMessage constructed in the preceding step If the value of TaskReturnStatus is not success, as defined in [RFC2251] section 4.1.10, the algorithm MUST perform the following steps: rStatus MUST be set to a DirectoryOperationResult enumeration value according to the conversion rules for TaskReturnStatus specified in section . Raise a event. Processing MUST end. Construct an LDAPMessage: messageID = set as described in [RFC2251] section 4.1.1.1.
TaskInputRequestMessage = the LDAPMessage constructed in the preceding step If the value of TaskReturnStatus is not success, as defined in [RFC2251] section 4.1.10, the algorithm MUST perform the following steps: rStatus MUST be set to a DirectoryOperationResult enumeration value according to the conversion rules for TaskReturnStatus specified in section . Raise a event. Processing MUST end. Extract the value of the distinguishedName attribute from the result message returned in TaskOutputResultMessages and set rDN to that value. Set rStatus to DirectoryOperationResult.Success. Processing MUST end. Data Element Directory Attribute Tables QueueManager The QueueManager ADM element is specified in section 3.1.1.1. The following table lists only those QueueManager ADM element attributes that are stored in the directory. QueueManager ADM element attributes MUST be stored as attributes of an mSMQConfiguration ( section 2.162) object, except for those noted in the following table, which MUST be stored on the computer ([MS-ADSC] section 2.21) object that is the parent of the mSMQConfiguration object in the directory. In addition, any QueueManager ADM element instance for which one or more of the RoutingServer, DirectoryServer, or SupportingServer ADM attributes is TRUE MUST have an mSMQSettings ([MS-ADSC] section 2.166) object in the directory, the attributes of which MUST have the same values as certain attributes of the mSMQConfiguration object. The for these three objects (mSMQConfiguration, computer, and mSMQSettings) are specified in section . QueueManager ADM element attribute Stored on computer object? Identifier no ComputerName no QueueManagerVersion no OperatingSystemType no QualifiedComputerName yes CreateTime no ModifyTime no DirectoryServerType no RemoteAccessServer no QueueManagerQuota no JournalQuota no ForeignSystem no
A Abstract data model data elements 29 29 28 28 29 29 28 28 12 14 C 12 134 13 directory objects 14 13 16 16 16 D Data model - abstract data elements 29 29 28 28 29 29 28 Data 13 Data types - common directory objects 14 13 16 16 16 Directory objects 14 13 16 25 25 E 25 127 F 12 G 9 H 16 I 128 130 11 29 9 L 13 Local events create 93 31 90 107 delete 45 109 121 112 LDAP connection 120 126 read 49 56 70 69 resolve 88 88 113 set object 116 118 70 M 30 Messages 13 directory objects 14 13 16 16 16 25 13