<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Sreekanth,</p>
<p>Thanks for the link. I'd already seen that article (or one very
similar), but it does provide a lot of useful information about
replication.</p>
<p>The Docs issues I mentioned in the conference call are as
follows:<br>
</p>
<p>1). A fortnight ago, I raised a minor issue with MS-DRSR
4.1.10.6.14 ProcessLinkValue(). i.e.
<a class="moz-txt-link-freetext" href="https://msdn.microsoft.com/en-us/library/dd207759.aspx">https://msdn.microsoft.com/en-us/library/dd207759.aspx</a></p>
<p>In the following block of code that checks the link target, it
looks like it's missing a null check for targetObject. <br>
</p>
<p><font face="Courier New, Courier, monospace"><font size="-1">targetObject
= GetDSNameFromAttrVal(replValinf.attrTyp, replValInf.pAval)<br>
if ((IsRecycleBinEnabled() and targetObject!isRecycled) or<br>
(not IsRecycleBinEnabled() and targetObject!isDeleted))
then<br>
if (DRS_GET_TGT in ulMoreFlags) then<br>
/* nothing to do */<br>
return 0<br>
else<br>
return ERROR_DS_DRA_RECYCLED_TARGET<br>
endif</font><br>
</font></p>
<p>Presumably it should also return ERROR_DS_DRA_RECYCLED_TARGET if
targetObject is null, as this is what triggers the use of the
DRS_GET_TGT flag.<br>
</p>
<p>2). Related to this, the error code used here isn't documented,
i.e. it isn't listed on
<a class="moz-txt-link-freetext" href="https://msdn.microsoft.com/en-us/library/cc231199.aspx">https://msdn.microsoft.com/en-us/library/cc231199.aspx</a></p>
<p>I think it should be something like:<br>
</p>
<p>ERROR_DS_DRA_RECYCLED_TARGET 0x000021BF<br>
</p>
<p> Thanks for your help.</p>
<p>Tim</p>
<div class="moz-cite-prefix">On 08/06/17 09:56, Sreekanth Nadendla
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:DM5PR21MB0505132E5E728DE8395D3016C5C80@DM5PR21MB0505.namprd21.prod.outlook.com">
<pre wrap="">Hello Tim, below is the article I mentioned and it provides some useful details about Linked value replication scenarios.
<a class="moz-txt-link-freetext" href="https://technet.microsoft.com/en-us/library/cc772726(v=ws.10).aspx">https://technet.microsoft.com/en-us/library/cc772726(v=ws.10).aspx</a>
Regards,
Sreekanth Nadendla
Microsoft Windows Open Specifications
-----Original Message-----
From: Sreekanth Nadendla
Sent: Thursday, June 1, 2017 5:03 PM
To: 'Tim Beale' <a class="moz-txt-link-rfc2396E" href="mailto:timbeale@catalyst.net.nz"><timbeale@catalyst.net.nz></a>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:cifs-protocol@lists.samba.org">cifs-protocol@lists.samba.org</a>; MSSolve Case Email <a class="moz-txt-link-rfc2396E" href="mailto:casemail@microsoft.com"><casemail@microsoft.com></a>
Subject: 117060115827644 Question about DRS client behaviour with linked attributes
Hello Tim, I will be assisting you with this issue.
Regards,
Sreekanth Nadendla
Microsoft Windows Open Specifications
-----Original Message-----
From: Tim Beale [<a class="moz-txt-link-freetext" href="mailto:timbeale@catalyst.net.nz">mailto:timbeale@catalyst.net.nz</a>]
Sent: Wednesday, May 31, 2017 8:18 PM
To: Interoperability Documentation Help <a class="moz-txt-link-rfc2396E" href="mailto:dochelp@microsoft.com"><dochelp@microsoft.com></a>; <a class="moz-txt-link-abbreviated" href="mailto:cifs-protocol@lists.samba.org">cifs-protocol@lists.samba.org</a>
Subject: Question about DRS client behaviour with linked attributes
Hi,
We're trying to add DRS GET_TGT support to Samba and have a question about the behaviour of linked attributes. We noticed that you can sometimes get linked attributes that span a partition.
For example you can have an object in the Configuration partition with a linked attribute to an object in the Domain partition:
dn:
CN=RWDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=SAMDOM,DC=EXAMPLE,DC=COM
serverReference: CN=RWDC,OU=Domain Controllers,DC=SAMDOM,DC=EXAMPLE,DC=COM
And you can also have an object in the Domain partition with a linked attribute to an object in the Configuration partition:
dn: CN=RWDC,CN=Topology,CN=Domain System Volume,CN=DFSR-GlobalSettings,CN=System,DC=SAMDOM,DC=EXAMPLE,DC=COM
serverReference: CN=NTDS
Settings,CN=RWDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=SAMDOM,DC=EXAMPLE,DC=COM
>From what I could see from testing, when the DRS_GET_TGT flag is set in the ReplicateNCRequestMsg, Windows does not resolve a target object that is in another partition.
This results in a cyclical dependency between the partitions being replicated, E.g. you can't commit all the linked attributes in the Domain partition until all the objects in the Configuration partition have been received, but you can't commit all the linked attributes in the Configuration partition until all the objects in the Domain partition have been received. This problem could be resolved if you manage to replicate the target object before the link is replicated.
My question is: how does the Windows replication behaviour resolve this problem?
- Does this mean the client always has to replicate the partitions in parallel? i.e. it can't replicate them in series because it can't commit an entire partition until it has received portions of another partition.
- What happens when the client encounters a linked attribute with an unknown target object? ProcessLinkValue() in the MS-DRSR seems to imply the client will ignore it (if it's already tried with GET_TGT). So how does the client ensure that it receives the linked attribute eventually?
Thanks for your help.
Tim
</pre>
</blockquote>
<br>
</body>
</html>