[cifs-protocol] [REG:115022012423947] [REG: 115022012423947] what are the arguments when "MS-ADTS 3.1.1.1.14 Scheduled and Event-Driven Replication" calls IDL_DRSGetNCChanges?

[Obaid Farooqi]

Hi Andrew:
I'll help you with this issue and will be in touch as soon as I have an answer.

Regards,
Obaid Farooqi
Escalation Engineer | Microsoft

Exceeding your expectations is my highest priority.  If you would like to provide feedback on your case you may contact my manager at nkang at Microsoft dot com

-----Original Message-----
From: "Edgar Olougouna" <edgaro at microsoft.com> 
Sent: Monday, March 2, 2015 12:11 PM
To: "Andrew Bartlett" <abartlet at samba.org>; "Obaid Farooqi" <obaidf at microsoft.com>
Cc: "cifs-protocol at lists.samba.org" <cifs-protocol at lists.samba.org>; "MSSolve Case Email" <casemail at microsoft.com>
Subject: [REG:115022012423947] [REG: 115022012423947] what are the arguments when "MS-ADTS 3.1.1.1.14 Scheduled and Event-Driven Replication" calls IDL_DRSGetNCChanges?

Andrew,
This case was transferred to my colleague Obaid as well. He'll will take care of this and follow-up. 

Thanks,
Edgar 

-----Original Message-----
From: Edgar Olougouna
Sent: Friday, February 20, 2015 4:21 PM
To: Andrew Bartlett
Cc: cifs-protocol at lists.samba.org; MSSolve Case Email
Subject: RE: [REG: 115022012423947] what are the arguments when "MS-ADTS 3.1.1.1.14 Scheduled and Event-Driven Replication" calls IDL_DRSGetNCChanges?

Andrew,
I will research this for you as well. The email subject has been updated to facilitate tracking. 

Thanks,
Edgar 

-----Original Message-----
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 4.1.23.2 IDL_DRSReplicaSync and ReplicateNCRequestMsg 

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

Hello Andrew, 

I have created a separate case, 115022012423947, for this additional question. 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 11:05 PM
To: Interoperability Documentation Help
Cc: cifs-protocol at lists.samba.org
Subject: Re: connecting MS-DRSR 4.1.23.2 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
> 4.1.23.2 Server Behavior of the IDL_DRSReplicaSync Method.  However, 
> it finishes with this text statement:
> 
> Perform a replication cycle as a client of IDL_DRSGetNCChanges. 
> 4.1.10.4.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 4.1.10.6), etc., until the replication cycle is 
> complete.
> 
> This is great, but I need to know what parameters are passed in to
> 4.1.10.4.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 
"MS-ADTS 3.1.1.1.14 
Scheduled and Event-Driven Replication" calls IDL_DRSGetNCChanges? 

Thanks, 

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