[cifs-protocol] [REG: 115022012423947] what are the arguments when "MS-ADTS 126.96.36.199.14 Scheduled and Event-Driven Replication" calls IDL_DRSGetNCChanges?
edgaro at microsoft.com
Fri Feb 20 15:21:08 MST 2015
I will research this for you as well. The email subject has been updated to facilitate tracking.
From: Matt Weber
Sent: Thursday, February 19, 2015 10:55 PM
To: Andrew Bartlett
Cc: cifs-protocol at lists.samba.org; MSSolve Case Email
Subject: [REG: 115022012423947] connecting MS-DRSR 188.8.131.52 IDL_DRSReplicaSync and ReplicateNCRequestMsg
[Case number in subject]
[Casemail to cc]
[Dochelp to bcc]
I have created a separate case, 115022012423947, for this additional question. One of our team members will follow up with you soon.
Matt Weber | Microsoft Open Specifications Team
From: Andrew Bartlett [mailto:abartlet at samba.org]
Sent: Thursday, February 19, 2015 11:05 PM
To: Interoperability Documentation Help
Cc: cifs-protocol at lists.samba.org
Subject: Re: connecting MS-DRSR 184.108.40.206 IDL_DRSReplicaSync and ReplicateNCRequestMsg
On Fri, 2015-02-20 at 16:18 +1300, Andrew Bartlett wrote:
> MS-DRSR 4.1.23 IDL_DRSReplicaSync has some great pseudo-code in
> 220.127.116.11 Server Behavior of the IDL_DRSReplicaSync Method. However,
> it finishes with this text statement:
> Perform a replication cycle as a client of IDL_DRSGetNCChanges.
> 18.104.22.168.1) 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 22.214.171.124), etc., until the replication cycle is
> This is great, but I need to know what parameters are passed in to
> 126.96.36.199.1 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?
Also, what are the arguments when
Scheduled and Event-Driven Replication" calls IDL_DRSGetNCChanges?
Authentication Developer, Samba Team http://samba.org
Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba
More information about the cifs-protocol