[cifs-protocol] [REG:111092948476937] FRSRPC: questions about schedule
obaidf at microsoft.com
Fri Sep 30 13:32:11 MDT 2011
I'll help you with this issue and will be in touch as soon as I have an answer.
Escalation Engineer | Microsoft
From: Matthieu Patou [mailto:mat at samba.org]
Sent: Thursday, September 29, 2011 2:35 AM
To: Interoperability Documentation Help; pfif at tridgell.net; cifs-protocol at samba.org
Subject: FRSRPC: questions about schedule
Hello dochelp team,
In ms-frs1.pdf we have at paragraph "126.96.36.199.1 SYSVOL Connection ScheduleTimer"
SYSVOL connection between sites. SYSVOL replication is initiated between two inter-site members at the start of the 15-minute interval, assuming the schedule is open. The connection MUST be using a trigger schedule. When a triggering schedule is used, the upstream partner ignores its schedule and responds to any request by the downstream partner. When the schedule closes, the upstream partner unjoins the connection only after the current contents of the outbound log, at the time of join, have been sent and acknowledged.
Given the fact that, from my understanding, FRS is pushed based, what's the implication of this ?
Because even if it's the downstream partner that is sending change notification it has to wait for the upstream to create a connection and once it's done it can start to send files.
Also the unjoin command is send by the one who created the connection that is to say the downstream partner, so how can the upstream partner "unjoin" the connection ?
Also can you clarify what's the meaning "when the schedule close" means exactly ? I understand that by default you have a schedule open every 15 minutes, but for how long it is open ?
Microsoft is committed to protecting your privacy. Please read the Microsoft Privacy Statement for more information.The above is an email for a support case from Microsoft Corp.REPLY ALL TO THIS MESSAGE or INCLUDE casemail at microsoft.com IN YOUR REPLY if you want your response added to the case automatically. For technical assistance, please include the Support Engineer on the TO: line. Thank you.
More information about the cifs-protocol