First, remove the server from the Namespaces
Launch powershell as an admin and run this:
Dfsutil.exe server registry dfsdnsconfig set <ServerName>
Reboot the server
Add to the namespace, if configured correctly, the server path will show up \\<ServerName>.<Domain> under the path in Folder Targets.
I recently added a third server to the DFS, and it didn't show up with .domain in the folder targets. It did show up with its FQDN in Namespace Servers.
If your server is not displaying its FQDN in folder targets, and you've already followed the above steps, go to Replication, and go to the Replication Group. Select the Replicated Folders tab, right click the folders, removing them from the namespace, right click and add them back. Boom, server.domain FQDN populates for the new server.
Subscribe to:
Post Comments (Atom)
Samsung refrigerator not making ice
How I got my stupid fridge to work again. Normally, I press/hold the blue button till it chimes. Well that didn’t work this time. Darn. I re...
-
Situation: Vizio sound bar works. But all of a sudden, no sound. The movie is playing fine, but no sound. On the sound bar itself, two ind...
-
I have a customer that would like 3 monitors, for whatever reason. The Dell 9020 is capable of this, and this is how I got it to work. No ...
No comments:
Post a Comment