Roaming profiles, folder redirection and Dfs

Hi,

We're looking to move our local profiles (win2k pro desktop)  to roaming profiles, along with using folder redirection for my docs, desktop and app data.

We want to host this data on a replicated Dfs mount, and have it hosted on two servers.

I've set up the DFS and replication, and all that seems to be working OK. A file or folder created on the mount replicates properly, and should one of the root hosts be down, the other takes over.

However, when I try to set up the folder redirects using a GPO, I get the following errors in the app log on the desktop:
Source: Folder Redirection Event ID 106
Failed to perform redirection of folder Desktop. The full source path was C:\Documents and Settings\tst001\Desktop. The full destination path was \\dfshost\dfsshare\useraccounts\tst001\desktop. At least one of the shares on which these paths lie is currently offline.
(I get one each for desktop, my docs and then app data)
Then I Get:
Source: UserEnv Event ID 1000
The Group Policy client-side extension Folder Redirection was passed flags (0) and returned a failure status code of (4350).
And then:
Source: UserEnv Event ID 1000
Windows cannot process extension Folder Redirection ProcessGroupPolicy. Return value (0x10fe).

If I click the share as listed in the eventlog it goes straight to the share.

I've tried almost everything I can think of. I've tried giving the account full contol on both ntfs and share permissions with no sucess. I've tried all manner of naming on the share, like \\domain\dfssharename \\server\dfssharename, etc including fqdns, etc.

So, firstly, should this work? I know others are doing it, but does it work in win2k?

If it should work, where am I going wrong?

HalibutAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
HalibutConnect With a Mentor Author Commented:
Got it!

http://support.microsoft.com/kb/309648

Offline folders set to off on the dfs shares (they should be) and set to be usable in the win2k clients.

Grrrrrr.
0
 
WadskiIT DirectorCommented:
There is no reason for this not to work.

Have you setup the folders correctly?

\\dfsroot\
profiles\ <-- Set the share level permissions to grant Everyone Full Control. You should then grant everyone Read permissions to the folder at the NTFS level.
0
 
HalibutAuthor Commented:
Yep. At the mo I'm working with a test account on a test group policy, and to eliminate that I've given the test account full control on the share and full control on the NTFS permissions to rule out problems with permissions. When logged in as the test user I can see the share, greate folder and files on the share and change permissions.
0
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

 
WadskiIT DirectorCommented:
When you point the profile in the Profile tab on the users Properties it should create a folder for user with the name <USERNAME> with the appropriate permissions for just that user.

Another thing to consider is creating the share with a name ending a $ to hide it from the users
0
 
HalibutAuthor Commented:
At the time you click apply, or when the user first logs in after the change?
0
 
HalibutAuthor Commented:
Right, Double checked this. The profile folder creation is ok, and creates a profile on the dfs share, so it is specificaly the folder redirection that's faulting.
0
All Courses

From novice to tech pro — start learning today.