Microsoft’s “Ask the Performance Team” recently posted a new article about the Windows Server 2008 Terminal Services RemoteApp feature. If you have read any of their articles in the past, you know that they do a good job of getting in the “nuts and bolts” of technology. This new article on RemoteApp is no exception. Here is an excerpt from the article:

“There are two executables in particular to be aware of:

• RDPINIT.EXE
• RDPSHELL.EXE

An instance of RDPINIT.EXE runs on the Terminal Server for each users RemoteApp session. RDPINIT.EXE is loaded by USERINIT.EXE as a RemoteApp specific implementation of USERINIT.EXE. RDPINIT.EXE acts as a watchdog to launch RDPSHELL.EXE and monitor process startup and shutdown. RDPSHELL.EXE is the shell that is used instead of EXPLORER.EXE to provide RemoteApp functionality. RDPINIT.EXE monitors the process lifecycle of RDPSHELL.EXE and restarts it in the event that it abnormally terminates. RDPSHELL.EXE loads a set of Windows event hooks onto each user desktop in the session. These event hooks allow RDPSHELL.EXE to monitor the state of all windows on the desktop. When a Remote Application is terminated, the process on the Terminal Server that is associated with that application is terminated. However, the Terminal Server session itself remains in a disconnected state until it is reset by an administrator or the Group Policy setting that defines the time limit for disconnected sessions to remain in that state.”

The article goes on to explain how to publish RemoteApps, as well as some nuances in a 64 bit environment.

Continue at source…

Technorati : Architecture, RemoteApp, Seamless, Terminal Services, Windows Server 2008
Del.icio.us : Architecture, RemoteApp, Seamless, Terminal Services, Windows Server 2008
Ice Rocket : Architecture, RemoteApp, Seamless, Terminal Services, Windows Server 2008