Startup Programs do not run in Windows Server 2008 RemoteApps
In Windows Server 2008 Terminal Services RemoteApps, most startup programs will not run in every session. Is this a bug, or a feature? It may be a little of both depending on how you look at it. The reason on why this happens is detailed in an article written by Dan Shappir. Dan writes:
“To understand why this happens lets turn again to the excellent AutoRuns utility from SysInternals. AutoRuns not only shows which applications and scripts run at system startup or logon, but also where they are registered to be run. For example, AutoRuns shows me that on my system nod32kui.exe, part of the NOD32 Antivirus System, is registered at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run. This is a common location used by applications that register themselves to always run at logon for all the users on the system. Turning now to another excellent SysInternals utility, Process Explorer, I can see that nod32kui.exe was launched by explorer.exe - Windows Explorer. This then is the root cause of the problem: Windows Explorer is not run at all inside TS RemoteApp sessions. As a result, nod32kui.exe will also not be run in such sessions.”
Since RemoteApps are seamless application (no desktop), there is not explorer.exe in each session. Published desktops in Windows Server 2008 Terminal Services will continue to run startups since there is an explore.exe in each session.
Technorati : Autorun, RemoteApp, Seamless, Startup Programs, Terminal Services, Windows Server 2008
Del.icio.us : Autorun, RemoteApp, Seamless, Startup Programs, Terminal Services, Windows Server 2008
Ice Rocket : Autorun, RemoteApp, Seamless, Startup Programs, Terminal Services, Windows Server 2008
