Hi All,
I'm unable to create a working DFS-N root using New-DFSNRoot. The runs without issue and the DFS-N is visible but if I then try to issue a New-DfsnFolder I get the following;
New-DfsnFolder : Access to a CIM resource was not available to the client.
At line:1 char:1
+ New-DfsnFolder –Path "\\example.com\Root1\Folder1" -TargetPath $SMBSourc ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : PermissionDenied: (MSFT_DfsNamespaceFolder:Root\Microsoft\...NamespaceFolder) [New-DfsnFolder], CimException
+ FullyQualifiedErrorId : MI RESULT 2,New-DfsnFolder
If I attempt to add the folder via the MMC I get;
\\example.com\Root1\Folder1: The folder target \\fileserver1\Folder1 cannot be added to the folder. Access is denied.
Creating the Root and Folder using the MMC alone works without issue. I'm running the powershell from a 2012 R2 box on a 2003 functional level forest/domain (so the DFS-N root can't be in 2008 mode).
When looking at the object in ADSI edit (CN=Root1,CN=Dfs-Configuration,CN=System,DC=example,DC=com) and comparing to another root created using the MMC the security permissions appear to be lacking an entry for the root server (permission to read/write all
properties). When the permissions are manually added (and permitted to propagate) the I am able to add a folder to the namespace using both powershell and mmc.
So I guess my question is can anybody else confirm this issue or is it something specific to our environment?