This is an simple explanation on how to setup a DFS Consolidation Root.
Microsoft has released a KB article with most of the same suggestions, I do however have some slight changes which I think is better. This is for the non clustered server.
Fast paced instructions:
- First of all install a new Windows server.
- Install DFS namespace without configuring any namespace
- Set the registry Server Consolidation Retry value to 1
- Set up the new Namespace called #oldserver
- Add the servername oldserver as an computer alternative
- Make sure the DNS contains entries for oldserver (ipconfig /registerdns)
- Reboot to get new kerberos ticket
#Add the key to enable Consolidation Readirection to the registry
New-Item -Type Registry HKLM:SYSTEM\CurrentControlSet\Services\Dfs
New-Ttem -Type Registry HKLM:SYSTEM\CurrentControlSet\Services\Dfs\Parameters
New-Item -Type Registry HKLM:SYSTEM\CurrentControlSet\Services\Dfs\Parameters\Replicated
New-ItemProperty HKLM:SYSTEM\CurrentControlSet\Services\Dfs\Parameters\Replicated ServerConsolidationRetry -Value 1
#Add Add the DFS Namespace feature
Add-WindowsFeature FS-DFS-Namespace
#Create a directory and share for the namespace
New-Item -Type Directory C:\DFSRoots\#oldserver
New-SmbShare -Name '#oldserver' -Path C:\DFSRoots\#oldserver
#Create the DFS namespace
New-DFSNroot -Type Standalone -TargetPath '\\localhost\#oldserver' -path \\localhost\#oldserver
#Add an alternative computername
netdom computername localhost /add oldserver.file.local
#Add something to the old computer to share..
New-DfsnFolder -Path \\localhost\#oldserver\sysvol -TargetPath \\file.local\sysvol
#Uppdate DNS
ipconfig /registerdns
#Reboot to allow windows to get kerberos with all alternative names
shutdown -r -t 0Now just try it from another machine.
\\oldserver\sysvol show you the domain sysvol. My domain is called file.local, so just change the domain when adding the alternative name and folder targets.