We had a group policy that was redirecting user folders to a share on a server that died, with no backup.  We were able to recover 85% of the users data and migrated it all to a new VM, and setup a new group policy for folder redirection to the new server.  

Most of the PC's still want to sync to the old location, gpupdate /force won't get them to dump everything to the new location. Those PC's will not redirect their desktops and documents to the new location, they remain local to the PC.

The old policy had "Leave Contents" for Policy Removal behavior.

The New server seems to work perfectly fine and normal for all users that RDP to RD farm via thin clients, and all new users cretaed since.

In fact I'm getting constant broadcast  ARP trying to find the dead and gone server still.  

I think I just need to clean up any remnants of this server in AD, but I really need some guidance.

Hi,
 
If the Policy Removal has been set to Leave the folder in the new location when policy is removed, then the folder redirection would stay how it is currently configured with the folder(s) redirected. To stop File Redirection correctly, you should first update the GPO and set the Policy Removal to Redirect the folder back to the user profile location when policy is removed and then change the redirection option to Not Configured.
 
For the detailed steps on how to stop Folder Redirection, please refer to this KB article: https://support.microsoft.com/en-us/kb/888203
 
Also, please note that running gpupdate /force wont update Folder Redirection policy. All users who are affected by your GPO modification must log off and back on to any computers where they have logged on before the changes are applied.
 
If you have deleted the old GPO that contains the settings, you might want to re-apply the setting, then follow the correct steps to remove the redirection setting.
 
Hope this helps.
 

Regards,

Eth

Ethan

Thanks for your response, it is much appreciated.

Do you think this will work even though the old server that all these machines are trying to redirect to is no longer on the network, and not available to be on the network?

Should I disable my "new" folder redirection policy, before modifying the old one and making the changes?

TIA