| An Introduction To Terminal Services Remote Programs (Part 3) |
| Thursday, 07 December 2006 by Michel Roth | |||
|
At the conclusion of Part 2, we had configured an application for remote execution. What this means is that the server that will be hosting the remote application is fully configured, and ready to go. The trick now is to make the remote application accessible to the end users. As I’m sure you know, when a user runs a normal Terminal Server session, the user establishes a connection to the server by using client software that communicates with the server using the RDP protocol. Things work a little bit differently when a user is executing remote programs. The user’s computer will still have to communicate with the Terminal Server using the Remote Desktop Protocol, but the normal Terminal Server client software won’t cut it. The Terminal Server client software is designed to provide the user with access to an entire remote operating system environment. Remember that the whole point of running remote programs is that we want the user to be able to work off of their own desktop. We don’t want to force the users to use the Terminal Server desktop. Even so, the users will require some sort of client software in order to access the remote programs. In order to run remote programs, the client computer must have the Remote Desktop Connection (RDC) 6.0 software installed. The software is included with Longhorn Server and Windows Vista. A version intended for users running Windows XP or Windows Server 2003 will eventually be available for download. Read the entire article here.
Show/Hide comment form
|
|||
