Windows 7 won't take new folder redirection from GPO

We have all Windows 7 Pro boxes with latest SP and patches.

We lost a server and that serve hosted our folder redirection.

After bringing up a new server and writing a new GPO, I notice that the computers are still referencing their old path for folder redirection.  When I go to a user's desk and look at the properties for the My Docs and Pictures, etc, the reference is \\oldserver\path\files instead of the new path that is specified in the new GPO.  

In the event logs, there are errors indicating that the new GPO was not applied.

Anyone have ideas on how to clear this up?  Or a work around?  I really need my users to have access to their files.

Thanks?

Cliff
crp0499CEOAsked:
Who is Participating?
 
Cliff GaliherCommented:
Ideally, I'd restore a backup of the old server temporarily. Do it on an old workstation or in a VM if need be. The only other oath is far more ugly. You basically have to manually yank the settings from the registry so any reference to the old GPO is not seen. The issue is that when GPCSE sees a change to folder redirection, it attempts to contact the old location to reconcile potential file changes and will nit apply the new setting until that reconciliation is complete. With the old location just "gone" GPCSE cant do that so it takes the "safe" path and bails on applying the new setting. By restoring a backup, the contact can be made, the policy applies, and the old server can then be quietly retired.
0
 
crp0499CEOAuthor Commented:
Not an option.  That server is gone, dead, blown up, deceased, buried, disassembled, etc.

Other options?
0
 
Cliff GaliherCommented:
I get that the server is gone/dead, but really? No backups??  Kinda like getting in a car accident without insurance and asking how to get a new car.  Yep, if you didn't have things in place for "what-if" contingency, sometimes it is just too late. As I said, the other option is very unpleasant. It requires editing the user registry for every user and is destructive existing user profiles.  Really, if there is *ANY* backup anywhere, pursue that path.
0
 
crp0499CEOAuthor Commented:
Well, no, we have a backup.  We use storage craft so we could boot the old server as a VM and do it that way.  In the interim, my fix was that the path to my new server with the old files on it is the same except for the server name.  So, in DNS, I created a CNAME alias and pointed oldserver.domain.com to newserver.domain.com and shazam!  All is right with the world!

:)
0
 
crp0499CEOAuthor Commented:
although I pursued an alternate solution, this solution would have solved 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.