DFSNamespaceRoot: The requested object was not found when adding another Namespaceserver #119
Labels
needs investigation
The issue needs to be investigated by the maintainers or/and the community.
Details of the scenario you tried and the problem that is occurring
We deploy in our configuration a hole Domain with 2 DCs. The DFSNamespaceRoot on the Primary DC is set up successfully.
After the domain is deployed and the second DC-Server is joined as DC I try to repeat the same DFSNamespaceRoot with a adjusted TargetPath to add the 2. DC to the namespace (TargetNode is the 2. DC). After that, the second DC is added but an error message appears and the configuratin fails: the object was not found. My research leads me to the command Get-DfsnRootTarget in the function (my assumption of the cause could be wrong).
I entered the command Get-DfsnRootTarget on the second DC and the error message was the same. Of course the TargetPath dont exist at the moment I try to add the Server (as already mentioned the Server is added after that).
The needed command would be New-DfsnRootTarget which comes after the error.
Maybe I just got the wrong approach to add another namespace server but I couldn't find another way.
Verbose logs showing the problem
Error not in English but the essence is that the the requested object was not found.
Suggested solution to the issue
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
OsName : Microsoft Windows Server 2019 Standard
OsOperatingSystemSKU : StandardServerEdition
OsArchitecture : 64-Bit
WindowsVersion : 1809
WindowsBuildLabEx : 17763.1.amd64fre.rs5_release.180914-1434
OsLanguage : de-DE
OsMuiLanguages : {de-DE}
Version and build of PowerShell the target node is running
PSVersion 5.1.17763.1007
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17763.1007
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Version of the DSC module that was used ('dev' if using current dev branch)
4.3.0.0
The text was updated successfully, but these errors were encountered: