Folder Redirection after Rename

I am having problems with folder redirection at one of my branches.  We had to do a server rename of the branch server.  After the rename I went into GP and made the change under folder redirection for the OU to the new server.  Since then about a third of the people at that branch are being redirected fine.  The others are getting an error message when they loging saying they are unable to access their desktop folder.  The error is showing the old server name instead of the new one.  I have tried doing a GPupdate /force, have had them reboot, but nothing seems to work.  I even tried pulling them out of the OU that is tied to that policy we are still getting the error.

We are running Windows Server 2003 Standard Edition with Windows XP SP3 Clients.

This is the error message appearing in the log on the client PC.
Event ID 107 Source Folder Redirection
Failed to perform redirection of folder Desktop.
The folder is configured to be redirected from <\\old_servername\users my documents\andrear\Desktop> to <\\new_servername\users my documents\andrear\Desktop>.
The following error occurred:
%%267


Archangel1982Asked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Archangel1982Connect With a Mentor Author Commented:
We found a solution to this problem.  Inside of the registry \HKEY_CURRENT_USER\Software\Microsoft\CurrentVersion\Explorer\User Shell Folder was a spot for the folder location of the desktop.  On the users we were having problems with this still show the path to the old server.  To get this resolved quickly we changed the path hear to the new server and it works fine.  Thanks for the tips.
0
 
coolsport00Connect With a Mentor Commented:
It still may be that these clients are getting the GP applied. Have you run the GPResults wizard/tool to see if these PCs are getting the updated GP?

~coolsport00
0
 
Archangel1982Author Commented:
I've run the GPresult on two client PCs, one where the user has problems and one where everything is working fine.  Looking over them they appear excactly the same as each other with one exception.  The one who is able to access their desktop without a problem has this inside of the results while the one that isn't working doesn't.
The following GPOs were not applied because they were filtered out
    -------------------------------------------------------------------
        Local Group Policy
            Filtering:  Not Applied (Empty)
This is unter the computer settings section.  I've tried having one of our users sign onto a PC where another user isn't having problem and they still have the problem so whatever the problem is it is in those users profiles.
0
 
minvisConnect With a Mentor Commented:
Try RSOP (MMC > Resultant Set Of Policies) on the clients to find out what GPO is causing the problem.
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.