<div class="content" name="NetrDfsModifyPrefix" uuid="94aec68c-00b2-4b87-bb9e-7f144ab7a7fc"><p>The NetrDfsModifyPrefix method changes the path that
corresponds to a <a href="1709f6a7-efb8-4ded-b7ae-5cee9ee36320#gt_0611e93d-f0e7-42ee-a591-d77ebcbb6619" data-linktype="relative-path">DFS link</a>
on the <a href="1709f6a7-efb8-4ded-b7ae-5cee9ee36320#gt_434b0234-e970-4e8c-bdfa-e16a30d96703" data-linktype="relative-path">server</a>. An
implementation MAY<a id="Appendix_A_Target_152"></a><a aria-label="Product behavior note 152" href="ebb74ff2-abb1-4e1b-a76a-563a5cbbea9a#Appendix_A_152" data-linktype="relative-path">&lt;152&gt;</a> choose to support this
method.</p><dl>
<dd>
<div><pre> NET_API_STATUS NetrDfsModifyPrefix(
   [in, string, unique] SRVSVC_HANDLE ServerName,
   [in] GUID* Uid,
   [in, string] WCHAR* Prefix
 );
</pre></div>
</dd></dl><p><b>ServerName: </b>An <a href="5f8329ee-1965-4ea1-ad35-3b29fbb63232" data-linktype="relative-path">SRVSVC_HANDLE (section 2.2.1.1)</a>
pointer that identifies the server. The <a href="1709f6a7-efb8-4ded-b7ae-5cee9ee36320#gt_60e0e1fa-66fe-41e1-b5e3-ceab97e53506" data-linktype="relative-path">client</a> MUST map this
structure to an RPC binding handle (see <a href="https://go.microsoft.com/fwlink/?LinkId=89824" data-linktype="external">[C706]</a> sections 4.3.5
and 5.1.5.2). The server MUST ignore this parameter.</p><p><b>Uid: </b>Specifies the <a href="1709f6a7-efb8-4ded-b7ae-5cee9ee36320#gt_f49694cc-c350-462d-ab8e-816f0103c6c1" data-linktype="relative-path">GUID</a> that corresponds to
the DFS link that needs to be changed. This GUID MUST be obtained by using the
NetrDfsGetInfo (Opnum 4) method, specified in <a href="../ms-dfsnm/95a506a8-cae6-4c42-b19d-9c1ed1223979" data-linktype="relative-path">[MS-DFSNM]</a>
section <a href="../ms-dfsnm/b5dd4568-3ea4-4f27-ae03-3ebb19fa4b13" data-linktype="relative-path">3.1.4.1.6</a>.</p><p><b>Prefix: </b>A pointer to a null-terminated UTF-16
string that specifies the path of the updated DFS link.</p><p><b>Return Values: </b>The method returns 0x00000000
(NERR_Success) to indicate success; otherwise, it returns a nonzero error code.
The method can take any specific error code value, as specified in <a href="../ms-erref/1bc92ddf-b79e-413c-bbaa-99a5281a6c90" data-linktype="relative-path">[MS-ERREF]</a>
section <a href="../ms-erref/18d8fbe8-a967-4f1c-ae50-99ca8e491d2d" data-linktype="relative-path">2.2</a>.</p><p>In response to a NetrDfsModifyPrefix message, the server
SHOULD<a id="Appendix_A_Target_153"></a><a aria-label="Product behavior note 153" href="ebb74ff2-abb1-4e1b-a76a-563a5cbbea9a#Appendix_A_153" data-linktype="relative-path">&lt;153&gt;</a> choose to perform no
processing and return an implementation-specific error code when this method is
called. If the server supports <a href="1709f6a7-efb8-4ded-b7ae-5cee9ee36320#gt_0b8086c9-d025-45b8-bf09-6b5eca72713e" data-linktype="relative-path">DFS</a>, the server MAY update
the path for a DFS link. This message is typically used by domain controllers
(DCs) to fix a bad prefix match.</p><p>The <i>Uid</i> parameter specifies the GUID that corresponds
to the DFS link that needs to be changed.</p><p>The <i>Prefix</i> parameter specifies the path of the
updated DFS link. The string MUST be in one of two forms: </p><ul><li><p><span><span> 
</span></span>The first form is \Dfsname\sharename\path_to_link, where <i>Dfsname</i>
is the name of the storage server that hosts the root of a <a href="1709f6a7-efb8-4ded-b7ae-5cee9ee36320#gt_07f90715-4bf2-479d-9c9d-1b2cd585a280" data-linktype="relative-path">standalone DFS implementation</a>;
<i>sharename</i> is the name of a shared folder that is published on the DFS
host server; and <i>path_to_link</i> specifies the path on the physical network
share.</p>
</li><li><p><span><span> 
</span></span>The second form is \DomainName\DomDfsname\path_to_link, where <i>DomainName</i>
is the name of the domain that hosts the <a href="1709f6a7-efb8-4ded-b7ae-5cee9ee36320#gt_639b7503-b879-4ef7-98a8-14adf85bc16d" data-linktype="relative-path">DFS root</a>; <i>DomDfsname</i>
is the name of the root of a domain-based DFS implementation that is published
in the directory service of the domain; and <i>path_to_link</i> specifies the
path on the physical network share.</p>
</li></ul><p>The server MAY<a id="Appendix_A_Target_154"></a><a aria-label="Product behavior note 154" href="ebb74ff2-abb1-4e1b-a76a-563a5cbbea9a#Appendix_A_154" data-linktype="relative-path">&lt;154&gt;</a>
enforce security measures to verify that the caller has the required
permissions to execute this call. If the server enforces these security
measures and the caller does not have the required credentials, the server
SHOULD<a id="Appendix_A_Target_155"></a><a aria-label="Product behavior note 155" href="ebb74ff2-abb1-4e1b-a76a-563a5cbbea9a#Appendix_A_155" data-linktype="relative-path">&lt;155&gt;</a> fail the call.</p></div>