We help IT Professionals succeed at work.

folder redirection not updating to new server via GP

I just had a server crash and I replaced it with a new 2008 windows server. I restored the backups of the my documents redirected files and then changed the group policy to point to the new server and path. Some users seem to be working. I know of one user in particular that is not working. I did a gpupdate /force and I reinitialized the offline files but it still points to the old server path.

How do I force this to update?

Also, it used to folder redirect to a another server before I worked here. It still tries to sync to that folder. How do I remove that from all the computers in this office so that it doesn't try to sync to an old server that doesn't exist anymore?

Thanks,

Justin
Comment
Watch Question

Ove

Commented:
any entries inside eventlog ?

Ove

Commented:
folder redirection to a new server will usually fail if the old server hosting the original location for the redirection is not avaialble.  What you will need to do is put another server workstation online that has the same hostname, share name and folder structure as the original server hosting the redirected folders but leave the contents blank.  When the new GPO tries to redirect the folder, it will look to the old location to move the files to the new location, see that there are no files in that folder and the redirection will be successful.

Instead of setting up another workstation or server, you could add a CNAME or an A record in DNS with the same name as the original server but point it to the new server.  You could also, if you're not using NETBIOS name instead of FQ DNS name for the mapping (ie: you're using \\oldservername\Sharename\Folder and not using \\oldservername.fqdn.tld\Sharename\Folder), you could add a static (manually entered) WINS entry with the IP Address of the new server for OLDSERVERNAME.

Author

Commented:
Ove,

I checked the event log on the server and couldn't find any errors with folder redirection on the server. When I check the client event log, I see folder redirections messages.


Event Type:      Error
Event Source:      Folder Redirection
Event Category:      None
Event ID:      106
Date:            6/11/2010
Time:            4:31:28 PM
User:            GIS\michelleh
Computer:      BUR-2400-001
Description:
Failed to perform redirection of folder My Documents. The full source path was <\\gs-serv1\users\Michelle\my documents>. The full destination path was <\\gs-serv1\users\michelleh\my documents>. At least one of the shares on which these paths lie is currently offline.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The problem with this is that gs-serv1 has not been available for I don't know how long. So many computers still try to sync to that and the newest server is not even logged from what I can see.




rehamris,

If I create a cname and point it to the new server, will that allow the redirected folders to be corrected since the share is the same name and will be available?

Thanks,

Justin

Commented:
It looks like the source and destination server and sharename are identical? Simply add a folder called Michelle\my documents in the users share of the gs-serv1 server. Redirection should see the source folder is empty and successfully redirect to the michelleh folder.

Commented:
In the group policy management console, edit the policy you have for Folder Redirection.  Find the Option under User Confi > Windows Settings > Folder Redirection
Right-click "My Documents", click Properties, click the Settings Tab:
If you uncheck the option to Move the Contents to the new location, the redirection may succeed with the original source not being available.
FolderRedirectionGPO.jpg

Author

Commented:
rehamris,

gs-serv1 is a server that was removed before I started working here. For some reason, clients still attempt to sync to that server at log off and fail every time since it is not available. I would like an automated way to remove that if possible.

I checked the folder redirection settings and 'move the contents of my documents to the new location is not checked.'

Unchecking that setting has helped me in the past but not this time.
Commented:
You may "repair" this problem via a registry-script.
The reg-path responsible is:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
There you'll find the different entries for Documents, Music, Pictures, etc...

Depending on your client-os you may run a reg-script which sets your used entries to e.g. \\gs-servNEW\users\%username%\my documents.

Due to the fact, that this is located in HKEY_CURRENT_USER every user has the permission to change the value(s).
This can then easily be set via login-script, or via gpo (Windows -> Start-Script).

Ove

Author

Commented:
Ove,

Manually modifying the registry did work and now the user has access to my documents redirection.

I restarted the computer and it still works. However when I check RSOP. I still get this message.


Wednesday, June 16, 2010 1:46:30 PM

Folder Redirection failed due to the error listed below.
The share is currently offline or does not exist.

Additional Information:
Failed to perform redirection of folder My Documents.
The full source path was <\\gs-serv1\users\Michelle\my documents>.
The full destination path was <\\gs-serv1\users\michelleh\my documents>.
At least one of the shares on which these paths lie is currently offline.

It doesn't even reference the two servers that are newer and the policy says it is applied.

This only seemed to affect one user also. I asked another user and they are able to access their my documents just fine.

How do I get it to stop syncing to gs-serv1? Would the earlier suggestion of adding a CNAME or A record to DNS help pointing the old server name to the new one?

Thanks,

Justin
Ove

Commented:
we did it: adding a cname-dns-entry for the old server pointing to the new server...so the "old" shares are seemingly still "alive".
If the problem ONLY persists on ONE machine you may also try to add a line to c:\windows\system32\drivers\etc\hosts containing the ip-address of the new server and the name of the old server.


Ove

Author

Commented:
One machine only had the problem of not being able to access my documents that I know of. Several are trying to sync to the old server so I will try the cname thing and get back with you.

Thanks,

Justin

Author

Commented:
I have put this solution in place but I have been unable to confirm if the CNAME solution is working. I am going to ask a user today that should be directly affected by it. I"ll post as soon as I hear from her.

Thanks,

Justin

Author

Commented:
This solution worked for me for my main problem. I should not of posted two problems at the same time. I am giving Ove full points for solving my main issue and i'll start a new question for the other similar issue.

Thanks,

Justin
Hey everyone, I had what seemed to be the same problem, though my solution was different.

We had performed a file server role migration and had disabled the shares on the old server.  The GPO was set to copy the my docs data to the new location for us, but since we had disabled the share on the old server as part of our migration, applying the GPO failed as it couldn't reach the original location.  The solution here was to disable the setting in the GPO to not copy the data for us (since we had done this manually) and request the users to log out and back in.

Figured I'd post my solution here as well to bring this to light for others having the same issue.