Distributed file System (DFS) has some service dependencies – so if those don’t start the DFS Namespace service will also not start.
The dependencies are:
- Remote Registry
- Security Accounts Manager
I have seen the Remote Registry service become the culprit of the DFS-N service not starting.
In my experience – this has been caused by antivirus software changing the Remote Registry service to Disabled start-up type so when the DFS-N server restarts, one of the dependency services:
Remote Registry does not start so if you have issues with the DFS-N service not starting – check the Remote Registry Start-up type is configured to Automatic and click Start to confirm there are no errors and try starting the DFS-N service again.
Note: RemoteRegistry – although it is Automatic, it will only Start when it is being used so don’t be alarmed if it is in a Stopped state.
I have also created a quick PowerShell script to do some general checking for the DFS namespace service – sets the Remote Registry service to Automatic startup, Gets the other DFS service dependancy services and changes the startup type to Automatic and starts them and finally tries to start the DFS Namespace service.