Remote Desktop and Remote Assistance
Other new features introduced by Windows XP that are now incorporated in Windows Server 2003 include two features for remotely controlling users' workstations: Remote Desktop and Remote Assistance. Both Remote Desktop and Remote Assistance use the Remote Desktop Protocol (RDP) for communicating between local and remote systems.
The name Remote Desktop is somewhat deceptive and can be confusing. There are actually two components to Remote Desktopthe client-side component (Remote Desktop Connection) and the server-side component (Remote Desktop for Administration). These two pieces are just new names for the previous Terminal Services client and Terminal Services server from previous versions of Windows.
For more information about Remote Desktop, see "Remote Desktop for Administration."
With Remote Desktop for Administration enabled, you can remotely connect to your Windows Server 2003 (or Windows XP) machines by using the Remote Desktop Connection (or any other Terminal Services client) and obtain a graphical interface as if you were physically at the server. This can be done whether anyone is at the server or not.
In fact, one cool new feature of Remote Desktop is that it supports VNC- or pcAnywhere-style connections right to the server's actual, physical consolejust as if you were standing in front of the server. This is in addition to the two "virtual desktops" that have been provided since Windows 2000's Remote Administration mode of Terminal Services.
Remote Assistance is similar to Remote Desktop, but it is designed primarily for helping someone who is physically at the box. Therefore, it has some significant differences from Remote Desktop. First, and probably most importantly, Remote Assistance is totally user (client-side) driven. The sessions are initiated by the user, and the decision to allow someone to remotely take control is determined by the user. Second, to protect the user, Remote Assistance imposes time restrictions on the length of the remote control session.
Just like Remote Desktop, Remote Assistance needs to be enabled before it can be used. You enable Remote Assistance from the Remote tab of the System Properties dialog box. You simply select Turn on Remote Assistance and Allow Invitations to be Sent from This Computer.
Remote Assistance is part of the Help and Support Center. To access it, you select Help and Support from the Start menu. In the Help and Support Center, you click Support. Next, you select Get Remote Assistance. To initiate the Remote Assistance process, the user (or the novice, as the Remote Assistance user interface says) must select Invite Someone to Help You. The following are three methods by which a user can send the invitation:
Instant messageThis method uses Windows Messenger to send the invitation to the helper. Unlike in Windows XP, Windows Messenger is not installed by default in Windows Server 2003. To send an invitation via Windows Messenger, Internet access is required.
EmailThis method sends the invitation to the helper (that's the expert referred to in the Remote Assistance interface) via email. The user fills in the address of the helper and sends the email. When the helper receives the email, he or she simply clicks the link to open a session. To send by email, some type of email application (such as Outlook or Outlook Express) needs to be installed. Outlook Express is installed by default.
FileThis method specifies a file location to save the invitation file. The file location must be accessible to both the user (to create the invitation) and the helper (to open and use it).
No matter which method is used to create the invitation, the user also specifies the duration (in hours) of how long the invitation is good. The helper then uses the invitation to connect to the user's machine. After the interval for the invitation expires, it is no longer good for accessing the machine. The user can provide further protection of the invitation by specifying a password. Of course, the password must be communicated to the helper somehow so he or she can open the invitation. The process works like this:
The user configures and sends an invitation to the helper.
The helper receives the invitation and clicks the URL or opens the file to respond.
As shown in Figure 3.5, the user is prompted to allow the helper to connect.
After the user accepts, the helper can see the user's desktop and send and receive chat messages, as shown in Figure 3.6.
3.5 This dialog box shows the helper attempting to connect to a Remote Assistance
Once connected, the user and helper can exchange files, but the process is still user driven. If the helper initiates sending a file, the user must accept it and designate where to store it.
The helper can request to take control of the user's desktop (see Figure 3.7).
3.7 The helper can only request to take control.
If desired, the user can allow the helper to take control. This then gives the helper access to the user's desktop, but the user can still see what the helper is doing.
Figure 3.6 A Remote Assistance session has been initiated.
Consistent with giving the user full power over the Remote Assistance session, the user can cancel the session at any time simply by pressing the Esc key. It's sort of a fail-safe to give the user a warm fuzzy. If the helper starts doing something the user doesn't like, the user can just press Esc.
Controlling Remote Assistance
A group policy enables helpers to solicit users for Remote Assistance sessions. This just enables the helper to prompt a user; the user still initiates a session, and it is still totally user driven.
Quite frankly, the Remote Assistance model is designed primarily for end-user desktops. Therefore, in most environments, it will probably be used more in Windows XP than in Windows Server 2003. Chances are that the user and the help desk support personnel will be running Windows XP instead of Windows Server 2003. You wouldn't ordinarily have anyone logged in and sitting at the server console to send and respond to Remote Assistance messages. Remote Desktop for Administration is the more viable remote control console for Windows Server 2003 because it enables administrators to connect to the server without anyone being therejust like Terminal Services.