Sample Threads:

http://social.microsoft.com/Forums/en-US/partnerwinserversbs/thread/a79e869d-e0f0-497f-b272-51e7d112b00e

 

Issue:

 

Consider the following scenario:

 

1. You applied a GPO to redirect “My Documents” to a network share ex: “\\serverA\%username%\My Documents”.

2. You modify or use a new GPO to redirect “My Documents” to another location ex: “\\serverB\%username%\My Documents

3. The new GPO have the option “Move the contents of My Documents to the new location” checked.

4. The folder “\\serverA\%username%\My Documents” is no longer available because the administrator already move the data to the new server.

 

Result:

 

When a user open a session on a workstation using a fdeploy.dll Windows XP SP2 version, the redirection is done. In the event log we see an Informational 401 event indicate that “\\serverA\%username%\My Documents” is not available, error 3 (ERROR_PATH_NOT_FOUND).

 

But when a user open a session on a workstation using a fdeploy.dll 5.1.2600.5512 (Windows XP SP3), the redirection would fail. In the event log, we see an Error 107 event indicate that “\\serverA\%username%\My Documents” is not available, error 3 (ERROR_PATH_NOT_FOUND).

 

Resolution:

 

This issue only affected XP SP3 clients, and has been filed as a bug in XP SP3. A workaround has come out, which is to edit the new GPO, do NOT use the option “Move the contents of My Documents to the new location”. The data can be move manually.

 

Then run gpupdate /force on the XP SP3 client to refresh the policy. The user’s My Documents folder should point to the new path.

 

 


Best regards,

Tony Ma
Partner Online Technical Community
—————————————————————————————–
We hope you get value from our new forums platform! Tell us what you think:
http://social.microsoft.com/Forums/en-US/partnerfdbk/threads
——————————————————————————————
This posting is provided “AS IS” with no warranties, and confers no rights.

 

Comments are closed.