In a domain-based DFS Namespace, clients should access content through the namespace path, not the underlying server/share target. The Windows Server Hybrid Core Infrastructure guidance explains that a domain-based namespace is published in AD DS and is addressed with the UNC pattern \\<domain FQDN>\<NamespaceName>\.... Namespace servers (like Server1) only host the namespace metadata; the folder target(s) can point to any SMB share path (here: \\Server2.contoso.com\Share1\Folder1). However, client mappings must use the DFS namespace root so that referrals, fault tolerance, and transparent target changes work.

Given the namespace Files and the DFS folder Folder1, the correct client path is \\contoso.com\Files\Folder1. Options such as \\Server2.contoso.com\Share1\Folder1 reference the physical share directly and bypass DFS; \\Server1.contoso.com\Files\Folder1 would work for a standalone namespace or when explicitly addressing a namespace server, but the requirement states to “use the path of the DFS Namespace,” which for a domain-based namespace is the domain FQDN. Therefore, the correct logon script command to map drive M: is:

net use m: \\contoso.com\files\folder1

This ensures users benefit from DFS features (referrals, site-awareness, and resiliency) while abstracting the backend target path.