new-DFSnroot fails

Question

_{Friday, March 31, 2017 7:14 PM}

I'm not sure what I'm missing here. I keep getting the same error.  I replaced company details with [file server] and [domain]

just trying to spin up a new root.  Seems simple enough.  I've tried from my machine whith an account that has enough rights, from the Domain controller, all running the ISE as administrator. 

New-DfsnRoot  -TargetPath "\[file server]\Deals" -Type DomainV2 -Path "\[domain].local\DATA01e-Deals" -EnableAccessBasedEnumeration $True

New-DfsnRoot : A general error occurred that is not covered by a more specific error
code.
At line:1 char:1
+ New-DfsnRoot  -TargetPath "\[file server]\Deals" -Type DomainV2 -Path " ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
*    + CategoryInfo          : NotSpecified: (MSFT_DFSNamespace:ROOT\Microsoft\..FT_D*
*   FSNamespace) [New-DfsnRoot], CimException*
*    + FullyQualifiedErrorId : MI RESULT 1722,New-DfsnRoot*

All replies (7)

_{Monday, April 3, 2017 8:29 PM ✅Answered}

I got it!

After playing with get-dfsnroot to see the properties of the existing roots, I see the error of my ways

DFSroots are stored on the domain controller. 

Dfsfolders (Which I create and work with 90% of the time) have targets on other machines-where ever shares are. 

I was trying to point a root at a shared folder on another machine (File server). 

I should have specified that the path and the target are on the domain controllers.  Wires were crossed.

New-DfsnRoot  -TargetPath "\[Domain Controller\Deals" -Type DomainV2 -Path "\[domain].local\Deals" -EnableAccessBasedEnumeration $True

_{Friday, March 31, 2017 7:59 PM}

See this: https://support.microsoft.com/en-us/help/2102154/troubleshooting-ad-replication-error-1722-the-rpc-server-is-unavailable

\(ツ)_/

_{Friday, March 31, 2017 8:01 PM}

And this: https://social.technet.microsoft.com/Forums/office/en-US/90207283-5862-400c-9552-430b5aee2fd5/newdfsnfolder-access-to-a-cim-resource-was-not-available-to-the-client?forum=winserverpowershell

\(ツ)_/

_{Friday, March 31, 2017 8:17 PM}

Thanks checking them out...

_{Friday, March 31, 2017 8:39 PM}

First link resolutions: All checked out ok except one service 'Remote Procedure Call (RPC) Locator' needed to be running on the DC.  I started it on all DCs and set to auto.  Rebooted the DC I was testing on... no go.

I had found the second link as well.  No luck there.. no seeing anything that applied to my situation.  The share I'm pointing the DFS root at does exist... I created a DFS root manually as proof of concept and checking that all components are in place.  

_{Monday, April 3, 2017 7:00 AM}

Hi,

>>I had found the second link as well.  No luck there.. no seeing anything that applied to my situation.  The share I'm pointing the DFS root at does exist... I created a DFS root manually as proof of concept and checking that all components are in place.  

I have seen the similar error before,please check the TargetPath value,for example if you give a  server name like \servera\deals instead of \server-a\deals - you'll met with a general error.

Best Regards
Cartman
Please remember to mark the replies as an answers if they help. If you have feedback for TechNet Subscriber Support, contact [email protected]

_{Monday, April 3, 2017 3:17 PM}

Hey Catman,

As far as I can tell the target path is correct.  I can chdir to the \[server]\Deals folder as specified in the -targetpath parameter.  I also tried with \[server.][domain].local\Deals for kicks and I get the same error. 

I started to wonder if the '-' in the -path parameter was causing issues... same error when attempting to set a path \[domain].local\Deals

Also tried -targetpath "\[server]\Deals\ (trialing backslash) and... with/without quotes, single quotes on the path, targetpath because why not?

Nadda.... grrr

Always that 1722 error... BTW this also fails on the DC (always running as admin)