Folder redirection to DFS Namespace stopped when moving target

Hello,

We have users My Documents directed to a DFS Namespace (so \\domain.local\allusers\username\MyDocs instead of \\server\allusers\username\MyDocs). The DFS Namespace only has 1 target, which was sitting on the domain controller. Last night i had migrated the share to a dedicated storage server (Windows Storage Server R2). Deleted and relinked the domain.local\allusers to the new server and tested.

Everything works except for folder redirections! I can map the UNC path manually via command prompt and browse to it ect.
- Admin has full access / user has full access to the destination folder.
- Share has full access to everyone
- Checked read-only archive bit and it's not set for anything
- RSOP has all the correct group policies applied (as it did before)
- Event Viewer shows the documents redirection to blah blah (showing correct path)
- User has full ownership of the documents folder.
- Added GPO to wait for network before logging on.

Server is Windows 2008 Terminal Server

The migration was done with robocopy preserving ACL's and ownership. The network was fully designed from the start using DFS Namespace for all shares, scripts etc and everything else works perfect EXCEPT for this redirections.

If i create a new user and test with a local access (ie no redirection), works fine. As soon as i manually set the redirection. The documents button on the start menu does nothing. As in you click it, and nothing happens. When you rightmouse and goto properties it doesn't list anything, like a dead or ACL blocked shortcut. You can't even set location after that point (same as if the GPO was doing the redirection).

This is driving me nuts.  Any help will be appricitated.

The only thing i can think of was before the share was on a domain controller, but now it's on a member server.
LVL 5
-Q-Asked:
Who is Participating?
 
-Q-Author Commented:
Ahhh!! Finally solved it last night. Will post the answer and a screen dump as soon as i get a chance. Basically it was an ACL on a parent folder (not even in the share path), acutally the one before a share!
0
 
Rob StoneCommented:
But this might be worth a go. You need to do it on the client machines.

Folder Redirectino Logging can be enabled by editing the following registry key:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Diagnostics.
Registry Value = FDeployDebugLevel.  Change the value to 0x0000000F for Verbose debugging.
http://support.microsoft.com/kb/907355/en-us

Then browse to windir\debug\usermode\fdeploy.log

Other than that, if you log on to one of the DC's and run MMC, then add RSOP you can run it in planning mode and select some of the target users.  I don't think this will show anything different to RSOP did on the client but you never know!


I've posted a few other things on another thread which has Folder redirect problems too
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_24408602.html
0
 
-Q-Author Commented:
Hi Stoner79,

Given it all a go but no success :(

Regkey for Folder Redirection doesn't exist in Windows 2008. Do you know of the key/or if you can on 2008?
0
 
Rob StoneCommented:
Afraid I don't know (I missed the 2008 bit in your post).

I've not seen 2008 so can't help any further without experience.

Good luck
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.