[THIN] Re: Remote Desktop Web Connection ActiveX

So you have the OCX doing everything from Printer and com port redir,
Disk drive access, sound, initial program settings, 

Can disable background, setup windows animation and bitmap caching?

 

And believe me you don't have to preach to me about centralizing
anything.... I am king of centralization. If you can get the initial
program thing done via the OCX then that is something.  Then I wouldn't
need the Centrally Stored RDP files launched with the RDC client via a
web browser as explained in My (SIMPLE) RDPWeb doc on my downloads page.

 

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: Sunday, September 14, 2003 11:32 PM
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(r)"

 

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: