Folder Redirection Migration to new volume - bizarre outcome

Question

I've tested this twice now and get the same results.

GOAL: create a brand new share for Folder Redirection using the same Drive letter and same share in order to give users a brand new folder with quotas.

1. Create a standard folder redirection policy on a U drive with a UserData share - works great - but one day you realize you want to get rid of this huge mess of folders and start NEW so you go to step 2.
2. Re-label the U drive to X: and create a new U volume with a new share
3. Users login and get errors on any redirected folder link as Windows believe those links are going to the OLD U drive

So, even though the drive and the share name are the same, I guess there are Volume IDs and cached links still active under the hood?

Why do links not work within My Computer and users get an error to the SAME path on a new volume? Totally strange. I've verified this twice in 2 domains - its real. :)

Answer 1

Hello,

Thank you for posting in Q&A forum.

I believe the change is already successfully applied but perhaps some cache data is still here and leads to this issue.

Please try below steps to further check this issue:

1. Restart the Windows machine to apply the change.
2. Log off and log back on to see if it works.
3. If there's any GPO applied, please run gpupdate/force in CMD window to get it updated.
4. Press Win + R and Run "mobsync", clear offline file cache if there's any.

Hope this answer can help you well.