RemoteApp Server 2008 R2 Folder/Drive publishing Explorer.exe

On my Remote Desktop 2008R2 server Farm I have a published RemoteApp to connect to H:\ a mapped network drive, with shortcut %SystemRoot%\explorer.exe /e,h:

Like this one I also have a RemoteApp with a shorcut:
"C:\Windows\SysWOW64\explorer.exe e,::{20d04fe0-3aea-1069-a2d8-08002b30309d}"

Up to today these RemoteApps have been working fine for the last couple of years.

Suddenly from today only an administrator can startup these explorer.exe RemoteApps. Users are failing to startup a RemoteApp or a explorer.exe shortcut, as soon as there is any switch added to it.

Tips and support on what can be the coase of this are highly appreciated.
NicoNLAsked:
Who is Participating?
 
robdlConnect With a Mentor Commented:
I've run TS WebAccess and now RD Web for several years. I have found that occasionally, when Windows Updates are done, things stop working until a reboot. I would check the AD Groups that are assigned the APP, check the permissions tab for the app in the Remote App Manager and reboot. If you are using a Gateway server, same thing should apply.
0
 
NicoNLAuthor Commented:
Last week a Roaming Profile Directories Exclusion Group Policy was added to the RDS Farm for the Documents;Desktop;Downloads;Pictures;Music;Videos folders.
A ProcMon capture was made of a failing and succesfull user with.

First difference in the capture results:
capture 1:
explorer.exe      CreateFile      C:\Users\Succesfull_User\Documents      SUCCESS
explorer.exe      QueryBasicInformationFile      C:\Users\Succesfull_User\Documents
explorer.exe      CloseFile      C:\Users\Succesfull_User\Documents      SUCCESS

capture 2:
explorer.exe      CreateFile      C:\Users\Failing_User\Documents      NAME NOT FOUND

For all logged in users withaout a Documents folder in their profile could't start up explorer.exe with any switch added to it, for instance %SystemRoot%\explorer.exe e,::{20d04fe0-3aea-1069-a2d8-08002b30309d}
As soon as the Documents folder was added to the profile %SystemRoot%\explorer.exe e,::{20d04fe0-3aea-1069-a2d8-08002b30309d} was allowed again.

So it's back to the drawing board to configure Folder redirection for the Library folders.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.