Using Remote Desktop Web Connection with Chip PC's Thin Clients
Objectives
Remote Desktop WebConnection(RDWC) is included with Windows Server 2003 and Windows XP. RDWC enables a computer on which it is installed to host Terminal Services Web Client connections from a Web browser. In other words, the client need not use the Remote Desktop Connection client or Terminal Services client to connect to the remote computer. Instead, the client can use a Web browser to initiate the connection.
RDWC comprises an ActiveX control, sample Web pages, and other files that enable a computer running Internet Information Services 4.0 or later to host remote connections. So, Windows Server 2003, Windows NT, Windows 2000, and Windows XP are all supported as the target server platform. The client must be running a Windows operating system with Internet Explorer 5.0 or later.
RDWC is a good solution for remote administration, but it's also a useful tool to enable you to connect to client computers for management and remote assistance. Beyond that, RDWC also offers an easy means for business partners, roaming users, and others to access a remote session without the need for you to deploy remote access client software.
How does RDWC work? When you install RDWC, Setup adds a Tsweb virtual directory to the Administration Web site on the target server. When you connect to that virtual directory, Internet Explorer automatically downloads a CAB file to your client computer if the RDWC ActiveX control is not already installed or if the version installed is older than the one hosted by the server. The ActiveX control installs automatically from the CAB file and a connection page appears.
Inthe case of Chip PC thin client devices, the ActiveXcontrol is a built-in feature in the device's image and therefore is not downloaded from the server.
The ActiveX's ClassIDs vary forPCs and for Chip PC Thin Clients and therefore must be defined accordingly at the source of the Connection Page:
PC: CLASSID="CLSID:9059f30f-4eb1-4bd2-9fdc-36f43a218f4a"
ChipPC: CLASSID="CLSID:3523c2fb-4031-44e4-9a3b-f1e94986ee7f"
Procedures
How to update the Connection Page to work with Chip PC thin client devices:
Website Settings:
1. Edit the connection page using standard editor (Notepad, FrontPage ...).
2. Look for the "CLASSID" string.
3. Change the strings value to: "CLSID:3523c2fb-4031-44e4-9a3b-f1e94986ee7f"
4. Save the changes.
Device Settings:
1. Open the Internet Explorer plugin properties.
2.Checkmark the"ActiveX" check box.
3. Save the settings and restart the device.
Test:
1. Open The Local Browser on the device.
2. Type in the URL field the following: http://serverName/tsweb(where servername is the IP/DNS name of your webserver).
3. Make sure that the webpage appears and no massage is presented regarding ActiveX.
Note: In case that both PCs and Chip PC Thin Clients are to access the same web, a script that will check the device type and use the appropriate CLASSID according to the result must be implemented in the Connection Page.
Login
| Partners | Contact 
