[cifs-protocol] [REG: 115022012423941] connecting MS-DRSR IDL_DRSReplicaSync and ReplicateNCRequestMsg

Matt Weber mweber at microsoft.com
Thu Feb 19 21:54:55 MST 2015

[Case number in subject]
[Casemail to cc]
[Dochelp to bcc]

Hello Andrew,

Thank you for your request. Case number 115022012423941 has been created for this inquiry. One of our team members will follow up with you soon.

Best regards,
Matt Weber | Microsoft Open Specifications Team

-----Original Message-----
From: Andrew Bartlett [mailto:abartlet at samba.org] 
Sent: Thursday, February 19, 2015 10:19 PM
To: Interoperability Documentation Help
Cc: cifs-protocol at lists.samba.org
Subject: connecting MS-DRSR IDL_DRSReplicaSync and ReplicateNCRequestMsg

MS-DRSR 4.1.23 IDL_DRSReplicaSync has some great pseudo-code in Server Behavior of the IDL_DRSReplicaSync Method.  However, it finishes with this text statement:

Perform a replication cycle as a client of IDL_DRSGetNCChanges. to form the first request and send it. If not DRS_MAIL_REP in r.options, then wait for the response, process it, send the next request (section, etc., until the replication cycle is complete.

This is great, but I need to know what parameters are passed in to ReplicateNCRequestMsg

In particular, I'm trying to chase down an issue in our RODC case, where the SPECIAL_SECRETS_PROCESSING flag isn't being sent by our RODC to GetNCChanges.  I know how I *could* force it, but I don't know if it should always be forced, for example.  For example, should the server sending DsReplicaSync tell the RODC to request it, or should the RODC add it (and remove WRIT_REP) on it's own? 


Andrew Bartlett

Andrew Bartlett
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT          http://catalyst.net.nz/services/samba

More information about the cifs-protocol mailing list