We help IT Professionals succeed at work.

DFS Migration 2003 to 2008 R2

251 Views
Last Modified: 2014-12-01
Helping out a client with a medium data migration this weekend and running into issues with DFS from their file server.

Scenario:
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'
Reorganized disks
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:
"[Window Title]
Open Folder
[Content]
\\clientads\shares\udata\mark.galvin\V2\Desktop 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.
[OK]"

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!

Thanks
Mark
Comment
Watch Question

Network Engineer
CERTIFIED EXPERT
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
MaheshArchitect
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
Totally agree with above comment

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
Mark GalvinPrincipal Consultant
CERTIFIED EXPERT

Author

Commented:
Hi both

This is a client domain which I have inherited as a client so was not involved in the setup of domain.

Sounds like you are both correct. DATA04 was not a DC. Interestingly, when I tried to add the DFS Namespace to the rebuilt DATA04 it could see the Domain DFS Namespace from before and added it but when trying to expand it the error “The namespace cannot be queried. Element not found” appeared.

To work around the issue (and given time constraints) I deleted the DFS root from AD and recreated as domain namespace and recreated all the folders in there. Then went through all the GPOs that referenced “\\clientads” and updated to \\client.ads which has done the trick. Now we can see the DFS Namespace on other, non dc, based storage servers.

Thanks
Mark
kevinhsiehNetwork Engineer
CERTIFIED EXPERT

Commented:
If you have multiple DCs hosting the namespace in the future this should be a non-issue as the namespace will survive the loss of any server. Actually, you probably could have just added a different server to be the namespace server and it would have been okay, since the namespace configuration is stored in AD. Glad you got it all working.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.