This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DFS as a Target Path in a policy

Hello,

I’d like to create a policy that maps the user’s home folder to a DFS location, so that we can utilise DFS Replication between file servers. I’ve read the “Configuring DFS Folders” section of the documentation and updated the Description area of the folder target with the preferred UNC path. I’ve navigated to the “Server Resource List” tab and “Discovered” and then click “Rebuild” – this then shows the newly provisioned DFS path in the list of Storage Resource List.

However, when I try to add the DFS path to a policy, the File System Path Browser does not list any DFS paths when I try to “Add Target Paths” (all shares on the servers are listed). How can I add a DFS path as a Target for a policy?

Thanks,

Jonathan
  • 0
    On 4/4/2014 9:36 AM, JonathanCox wrote:
    >
    > Hello,
    >
    > I�d like to create a policy that maps the user�s home folder to a DFS
    > location, so that we can utilise DFS Replication between file servers.
    > I�ve read the �Configuring DFS Folders� section of the documentation and
    > updated the Description area of the folder target with the preferred UNC
    > path. I�ve navigated to the �Server Resource List� tab and �Discovered�
    > and then click �Rebuild� � this then shows the newly provisioned DFS
    > path in the list of Storage Resource List.
    >
    > However, when I try to add the DFS path to a policy, the File System
    > Path Browser does not list any DFS paths when I try to �Add Target
    > Paths� (all shares on the servers are listed). How can I add a DFS path
    > as a Target for a policy?
    >
    > Thanks,
    >
    > Jonathan
    >
    >

    Jonathan,

    Make certain that the CIFS sharing rights include a "Full Control" entry
    for the NSMProxyRights group on BOTH the DFS Namespace root share (on
    all servers hosting the namespace) as well as each share linked to in
    the DFS namespace. If even one DFS link in the namespace lacks those
    rights, the NSM Engine won't be able to get complete information about
    the namespace and won't be able to use it as a policy path. (That
    behavior will change in future versions.)

    -- NFMS Support Team
  • 0 in reply to 
    Hi. Many thanks, that was it! I had skipped reading the “Creating DFS Namespace Permissions”. As you’ve mentioned, each server that hosts the Namespace needs to have the permissions set. It may be worth having that included in documentation the next time it’s updated.

    Regards,

    Jonathan