Windows server Replacement folder redirection does not work

Question

Good morning! We are hoping someone in the community can guide us in the right direction. We have scoured the internet looking for a solution and nothing we have tried works.

We have a windows server that we set up a very basic folder redirection policy on. We added a user to the OU associated with it, and it worked flawlessly. The user’s account mapped the folders to the correct location and was able to save data.

We then wanted to use a different folder, so we created a second policy identical to the first, but pointing to a different root folder. We applied the group policy to the server, then moved the user from the original OU to the new OU.

The original redirection policy disassociated, but the new one will not apply. We simply get an error message in gpresult that states “Cannot complete this function”.

We have duplicated this in a live environment and a lab environment, so it seems clear that it is something that we are doing wrong or not understanding about how this is supposed to work.

Has anyone run into this\have any guidance for us? Is our expectation of how this should work unrealistic?

Thanks very much.

Answer 1

Hello @Angie on the help desk

Your expectation is reasonable, but moving a user from one Folder Redirection target to another can fail if Windows can't access/create the new target or migrate the existing redirected content.

I would first check Event Viewer → Applications and Services Logs → Microsoft → Windows → Folder Redirection → Operational. The gpresult message “Cannot complete this function” isn't specific enough; the Folder Redirection event normally provides the actual error.

Also verify:

• The new target uses a UNC path, such as \NewServer\Redirected$%USERNAME%, rather than a mapped drive. Microsoft recommends UNC paths for Folder Redirection.
• The user has the appropriate share and NTFS permissions on the new root.
• Check whether Move the contents of Documents/Desktop to the new location is enabled. When enabled, Windows attempts to move the user's existing redirected data to the new target.
• Run gpupdate /force, then sign out and back in before testing again.

As a test, try the second policy with a new user who has never received the original Folder Redirection policy. If that works, the new GPO/share configuration is probably correct and the problem is specifically the transition from the old redirected location.

If you can post the Folder Redirection event ID and error details generated during logon, that should tell us exactly where the migration is failing.

Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.