Helping out a client with a medium data migration this weekend and running into issues with DFS from their file server.
Server 'DATA04' was Server 2003, hosting all network drives at DFS Namespace '\\client.ads\shares' (domain in the format 'client.ads'
Using Robocopy all user data was copied to external (keeping all NTFS Permissions intact)
Wiped server 'DATA04'
Installed Server 2008 R2
Installed File Services Role with DFS (Namespace & Replication)
Robocopied data back
Removed the existing DFS Root from AD as per http://support2.microsoft.com/?id=224384
Have setup the same Namespace on 2008 DFS Namespace on the newly built DATA04 server - which worked
Setup first Target, exactly the same as the Target on 2003 server
When testing this target (which is the 'userdata' share (which hosts all users redirected Desktops & My Documents) user computers are getting:
p refers to a location that is unavailable. It could be on a hard drive on this computer, or on a network. Check to make sure that the disk is properly inserted, or that you are connected to the Internet or your network, and then try again. If it still cannot be located, the information might have been moved to a different location.
This seems to indicate that the system is trying to access "\\clientads\shares" and not "\\client.ads\shares"
I have checked their Drive Maps in GPO and they are all setup with "\\clientads\shares".
Any idea folks?
Need an answer before end of the day today!
It seems that your domain NetBIOS name is clientads and not only "client", this is changed from default to custom during domain deployment.
Your earlier name space must be created on domain controller
Other wise it would not possible to get path like clientads\path
In new environment, when you run \\client.ads, it should show you "shares" dfs name space as well, then only it can resolve \\clientads\Shares, for that you need to install name space on DC servers
Also it is required to add this DFS name space on every DC server, otherwise some times it will create resolution issue, because \\clientads points to any random DC server in that AD site and if DFS name space is not installed on that DC, probably you will run in issues