RDPACTIVEX协议（转贴，以后用）

控件属性

WIDTH:终端服务显示宽度

HEIGHT:终端服务显示高度

CODEBASE:用于WEB调用的参数

• Is the path and file name of the Terminal Services ActiveX Client Control (Mstscax.cab). This file is in the directory where you installed the ActiveX Client Control and sample pages (Default &＃61; C:/Inetpub/Wwwroot/Tsweb).

  
  

PARAMNAME

• Can be any of the parameters supported in Msrdp.ocx.

  
  

• Note   The ActiveX Client Control Object parameters are not listed in this document. To view them, open Msrdp.ocx in a tool such as Oleview.exe or the Visual Basic® Object Browser. Msrdp.ocx is located in Mstscax.cab, which is installed in the directory where you installed the ActiveX Client Control and sample Web pages. See the implementation of the  
  

  Where MyServer is the name of the Terminal server to which you want the ActiveX Client Control to connect.

  
  

  • Note   See Section 1.2, “The Secured Settings Interface – Specifying a Program to Start” for information on specifying a program to run upon connection.

    
    

  
   

  
  

  3.0 Using the ActiveX Client Control with Virtual Channels

  Virtual channels are software extensions that can be used to add functional enhancements to a Terminal Services deployment, such as support for special types of hardware, audio, or other additions to the core functionality provided by the Terminal Services Remote Desktop Protocol (RDP). A virtual channel application has two parts, a client side and a server side. The server side is an executable program running on the Terminal server. The client side is a Dynamic Link Library (dll) which must be loaded into memory on the client computer when the Terminal Services client program is run.

  If you have enabled a Virtual Channels application in your Terminal Services deployment you can make this application available to client computers that access the Terminal server by means of the ActiveX Client Control. To do so, you must do the following:

  
  
  1. Deploy the server side of the application and make sure it is running on the Terminal server. For information about deploying virtual channels applications on the server, see http://msdn.microsoft.com/isapi/msdnlib.idc?theURL&＃61;/library/psdk/termserv/wtsapi_9t2r.htm .  
     In the connection page of your Terminal Services Web application on your Web server, use the PluginDlls property of the Advanced settings interface to specify the name of your virtual channels .dll. If you have more than one plugin, specify a comma-delimited list of .dll names. For instance, if your virtual channel plug-in is called “MyPlugin.dll”, use the following code:
  
  

  • MsTsc.AdvancedSettings.PluginDlls &＃61; "myplugin.dll"

    
    
  
  

  • If you have two virtual channels .dlls, MyPlugin.dll and Vdriver.dll, use the following code:

    
    
  
  

  • MsTsc.AdvancedSettings.PluginDlls &＃61; "myplugin.dll,Vdriver.dll"

    
    
  
  

  • IMPORTANT   For security reasons, the PluginDlls property only accepts a named list of virtual channels .dll&＃39;s. The control returns an error if any form of path (filesystem or UNC) is specified.

    
    

  
   

  
  
  2. Ensure that the client .dll for the virtual channels application is installed in the %windir%/system32 directory on client computers.
  
  

  • Note   By default, the ActiveX Client Control loads virtual channel client .dll&＃39;s from the %windir%/system32 directory. It is possible for an administrator to change this default client plugin .dll directory.  To do so, edit the following registry key on the client computer:

    
    
  
  

  • HKLM/Software/Microsoft/Terminal Server Client/vdllpath

    
    
  
  

  • Note that this directory path cannot be specified in the UNC format.

    
    

  For example, in the sample connection page (connect.asp) provided with the Terminal Services Advanced Client, you can edit the window_onload() subroutine as follows: 
  

  
   

  
  

  Appendix -- Terminal Services Shortcut Keys

  
   

  
  

  Shortcut Key	Description
  ALT&＃43;PAGE UP	Switches between programs from left to right.
  ALT&＃43;PAGE DOWN	Switches between programs from right to left.
  ALT&＃43;INSERT	Cycles through the programs in the order they were started.
  ALT&＃43;HOME	Displays the Start menu.
  CTRL&＃43;ALT&＃43;BREAK	Switches the client between a window and full screen.
  CTRL&＃43;ALT&＃43;END	Brings up the Windows 2000 Security dialog box.
  ALT&＃43;DELETE	Displays the Windows menu.
  CTRL&＃43;ALT&＃43;MINUS SIGN (-) symbol on the numeric keypad	Places a snapshot of the active window, within the client, on the Terminal server clipboard (provides the same functionality as pressing PRINT SCREEN on a local computer.)
  CTRL&＃43;ALT&＃43;PLUS SIGN (&＃43;) symbol on the numeric keypad	Places a snapshot of the entire client window area on the Terminal server clipboard (provides the same functionality as pressing ALT&＃43;PRINT SCREEN on a local computer.)

  
  

  
   

  
  

  • Note   On an NEC98, these shortcut keys are different in two cases:

    
    
  
  
  • CTRL&＃43;ALT&＃43;BREAK is replaced by F12.
  • CTRL&＃43;ALT&＃43;END is replaced by F15.