[THIN] FW: Re: Remote Desktop Web Connection ActiveX

  • From: Cláudio Rodrigues <Claudio.Rodrigues@xxxxxxxxxxxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Mon, 15 Sep 2003 14:43:58 -0400

This is the answer I got from Microsoft.

 

Cláudio Rodrigues

 

Microsoft MVP

Windows Technologies - Terminal Server

-----Original Message-----
From: XXX [mailto:XXX@xxxxxxxxxxxxxxxxxxxxx] 
Sent: Monday, September 15, 2003 1:17 PM
To: Claudio.Rodrigues@xxxxxxxxxxxxxxxxxxxxx
Subject: RE: [THIN] Re: Remote Desktop Web Connection ActiveX

 

You can?t hide the connection bar in the web case because it?s a
security feature. We want to ensure people know they?re doing something
remote, and prevent Trojan horse opportunities in web pages.

 

To clarify the discussion below, the ocx and the client are basically
identical, the main place you?ll see differences is what?s available
from script. They are only different so that if you go in to IE and
remove web components, you don?t wreck mstsc.exe or the TS MMC
functionality (as system components).

 

  _____  

From: Cláudio Rodrigues [mailto:Claudio.Rodrigues@xxxxxxxxxxxxxxxxxxxxx]

Sent: Sunday, September 14, 2003 10:23 PM
To: XXX
Subject: FW: [THIN] Re: Remote Desktop Web Connection ActiveX

 

Hey XXX,

 

Would you be able to pass this around to the developers to see what is
up? Why some methods/properties do not work properly on the latest RDP
OCX? The guy explained in detail what he is trying to accomplish and
where it is failing.

 

Thanks!

 

Cláudio Rodrigues

 

Microsoft MVP

Windows Technologies - Terminal Server

-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Cláudio Rodrigues
Sent: Monday, September 15, 2003 1:06 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Remote Desktop Web Connection ActiveX

 

Both have their CONs and PROs. MSIs would be perfect for an organization
using AD to deploy software for example. The OCX may give you issues
when a security patch is released (do you remember the 052, don?t you?).


I will ask the guys at MS to see what they say before we try to hack the
OCX, as we did with the executable. :-)

 

Cláudio Rodrigues

 

Microsoft MVP

Windows Technologies - Terminal Server

-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Sjolund, Dag
Sent: Monday, September 15, 2003 12:32 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Remote Desktop Web Connection ActiveX

 

 

Thanks for the feedback.  If you are talking about the controls used by
the inadequate "sample page" that MS provides with the ActiveX, that may
be the case, but with the OCX release that accompanied Windows 2003
Server your statement is not accurate.  It may be the other way around
actually.......  You will need to expand somewhat (read: "greatly") on
the "sample page" to get the desired functionality, however.  I
currently have every control and function that the MSI (GUI)
incorporates working properly with the OCX version, except for the
Connection bar issue (which really is a minor one, but should work
properly nonetheless).  Just as an FYI, below is a partial, alphabetical
list of "methods" or control functions that you have available with the
Win2k3 based OCX version.

 

Not that you asked, but the only advantage I see with the MSI version is
the ability to save the "Connection Settings" as a file for later use.
This, however, is minor in comparison to the benefits of having a
centralized (and customizable) web based launch point vs. the major
disadvantages of a distributed PC based (and controlled) MSI client
architecture.  From client configuration, upgradability, and overall
flexibility perspectives, I would have strong reservations about using
the MSI version for any decent size Terminal Services solution.

 

Regards,

 

Dag Sjolund

Senior Systems Engineer

Best Western International, Inc. "THE WORLD'S LARGEST HOTEL CHAIN®"

 

OCX Methods and controls:


MsRdpClient.AdvancedSettings.PluginDlls


MsRdpClient.AdvancedSettings2.AcceleratorPassthrough


MsRdpClient.AdvancedSettings2.BitmapCacheSize


MsRdpClient.AdvancedSettings2.BitmapPersistence


MsRdpClient.AdvancedSettings2.BitmapVirtualCache16BppSize


MsRdpClient.AdvancedSettings2.BitmapVirtualCache24BppSize


MsRdpClient.AdvancedSettings2.BitmapVirtualCacheSize


MsRdpClient.AdvancedSettings2.ClearTextPassword


MsRdpClient.AdvancedSettings2.ConnectToServerConsole


MsRdpClient.AdvancedSettings2.DedicatedTerminal


MsRdpClient.AdvancedSettings2.DisableCtrlAltDel


MsRdpClient.AdvancedSettings2.DisplayConnectionBar


MsRdpClient.AdvancedSettings2.DoubleClickDetect


MsRdpClient.AdvancedSettings2.EnableAutoReconnect


MsRdpClient.AdvancedSettings2.EnableMouse


MsRdpClient.AdvancedSettings2.EnableWindowsKey


MsRdpClient.AdvancedSettings2.FullScreen


MsRdpClient.AdvancedSettings2.GrabFocusOnConnect


MsRdpClient.AdvancedSettings2.HotKeyAltEsc


MsRdpClient.AdvancedSettings2.HotKeyAltShiftTab


MsRdpClient.AdvancedSettings2.HotKeyAltSpace


MsRdpClient.AdvancedSettings2.HotKeyAltTab


MsRdpClient.AdvancedSettings2.HotKeyCtrlAltDel


MsRdpClient.AdvancedSettings2.HotKeyCtrlEsc


MsRdpClient.AdvancedSettings2.InputEventsAtOnce


MsRdpClient.AdvancedSettings2.KeepAliveInterval


MsRdpClient.AdvancedSettings2.KeyboardType


MsRdpClient.AdvancedSettings2.MaxEventCount


MsRdpClient.AdvancedSettings2.MaximizeShell


MsRdpClient.AdvancedSettings2.MaxReconnectAttempts


MsRdpClient.AdvancedSettings2.MinInputSendInterval


MsRdpClient.AdvancedSettings2.MinutesToIdleTimeout


MsRdpClient.AdvancedSettings2.NumBitmapCaches


MsRdpClient.AdvancedSettings2.OrderDrawThreshold


MsRdpClient.AdvancedSettings2.OverallConnectionTimeout


MsRdpClient.AdvancedSettings2.PerformanceFlags


MsRdpClient.AdvancedSettings2.PersistCacheDirectory


MsRdpClient.AdvancedSettings2.PinConnectionBar


MsRdpClient.AdvancedSettings2.RdpdrClipCleanTempDirString


MsRdpClient.AdvancedSettings2.RdpdrClipPasteInfoString


MsRdpClient.AdvancedSettings2.RdpdrLocalPrintingDocName


MsRdpClient.AdvancedSettings2.RDPPort


MsRdpClient.AdvancedSettings2.RedirectDrives


MsRdpClient.AdvancedSettings2.RedirectPorts


MsRdpClient.AdvancedSettings2.RedirectPrinters


MsRdpClient.AdvancedSettings2.RedirectSmartCards


MsRdpClient.AdvancedSettings2.ScaleBitmapCachesByBPP


MsRdpClient.AdvancedSettings2.ShadowBitmap


MsRdpClient.AdvancedSettings2.ShutdownTimeout


MsRdpClient.AdvancedSettings2.SingleConnectionTimeout


MsRdpClient.AdvancedSettings2.SmartSizing


MsRdpClient.AdvancedSettings2.SmoothScroll


MsRdpClient.AdvancedSettings3.ConnectionBarShowMinimizeButton


MsRdpClient.AdvancedSettings3.ConnectionBarShowRestoreButton


MsRdpClient.ColorDepth


MsRdpClient.SecuredSettings.AudioRedirectionMode


MsRdpClient.SecuredSettings.KeyboardHookMode


MsRdpClient.SecuredSettings.StartProgram


MsRdpClient.SecuredSettings.WorkDir

 

 

 

 -----Original Message-----
From: Ron Oglesby [mailto:roglesby@xxxxxxxxxxxx]
Sent: Sunday, September 14, 2003 2:57 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Remote Desktop Web Connection ActiveX

Having messed with that some I can tell you the OCX (web client) and the
MSI (Full RDC client) are worlds apart. While you may have several
controls and functions available on the full client most are sorely
lacking in the web version. You are most likely out of luck.

 

 

 

 

Ron Oglesby

Senior Technical Architect

 

RapidApp

Office 312.372.7188

Mobile 815.325.7618

email roglesby@xxxxxxxxxxxx

 

-----Original Message-----
From: Sjolund, Dag [mailto:Sjolund@xxxxxxxxxxxxxxx] 
Sent: Friday, September 12, 2003 10:09 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Remote Desktop Web Connection ActiveX

 

Using the Remote Desktop Web Connection ActiveX control, I am trying to
configure the Connection bar to ?Display? AND ?Auto-hide?.  Having the
Connection bar displayed is the default behavior, but the Auto-hide
option is not.  When the appropriate methods are called they error out.
Is there anyway to enable/configure the
?MsRdpClient.AdvancedSettings2.DisplayConnectionBar? and
?MsRdpClient.AdvancedSettings2.PinConnectionBar? methods?  If no, why
not?  The ?Display Connection bar? options is configurable in the
MSI/EXE version of the RDP client and should be available AND
configurable in the OCX version as well as.  Any input/feedback is
appreciated.

 

Thanks,

 

Dag

Other related posts:

  • » [THIN] FW: Re: Remote Desktop Web Connection ActiveX