I have a Windows 2008 R2 server we use with Citrix Xenapp 6.5. As such, folder redirection is configured via Active Directory, Group Policy. Recently, two problems have occurred. 1) folder redirection is not working for "new" users, existing user work fine; and 2) creating a folder or file on the server throws an error "Could not find this item. This is no longer located it...". The Application event log shows this error: "Failed to apply policy and redirect folder...." The System event log show this: "Windows failed to apply folder redirection settings..." The problem started to occur a few days after I applied the last set of Microsoft Updates for May 2012. After spending many days reading various blogs, I found blogs that dealt with both issues independent of each other, but not both together. Both problems seem to stem from a corrupt registry subkey: HKLM\software\microsoft\windows\currentversion\explorer\folderdescriptions I found one Microsoft KB article that deals with the file/folder creation problem, but it is geared towards Vista. I'm wondering if the same fix will work with Windows 2008 R2 Server. http://support.microsoft.com/kb/949109 Suggestions are greatly appreciated.

If it happen only for new user, check the share security and most of all if the folder exist. In my case I redirect user folder/desktop to their home directory, but If I forget to create the directory, nothing get redirected.MCP | MCTS 70-236: Exchange Server 2007, Configuring

Folder NTFS and share permissions are correct. It is not a folder permission problem. I believe it is indeed the corrupt registry key. Not sure if the Microsoft Updates caused the problem or not, but it is rather curious that it happened with the next new user after the updates were applied. As I said existing users are not affected. I did find another a possible solution here: http://www.nebev.net/blog/?p=258 It deals with the same registry key, but it is unclear wheather this is the same fix as the microsoft KB fix for vista.

Folder NTFS and share permissions are correct. It is not a folder permission problem. I believe it is indeed the corrupt registry key. Not sure if the Microsoft Updates caused the problem or not, but it is rather curious that it happened with the next new user after the updates were applied. As I said existing users are not affected. I did find another a possible solution here: http://www.nebev.net/blog/?p=258 It deals with the same registry key, but it is unclear wheather this is the same fix as the microsoft KB fix for vista.