Video Capture Policy Group
The Video Capture policy group contains the following device bitmap and video capture driver policies. You can modify policy parameter values by double-clicking a policy to display the Setting Properties dialog.
Note: Some other remote control products, including Microsoft NetMeeting, employ low-level video driver hooks that are dynamically installed when required. Unfortunately, interference between these hooks can cause interoperability issues. We therefore recommend that you do not connect using multiple remote control products at the same time.
If True, specifies that the host automatically use a CPU and memory-intensive aggressive caching technique when the available session bandwidth is low to further reduce the bandwidth requirements of Remote Control.
You may want to disable this behavior on computers with limited CPU or memory resources, for example, point-of-sale terminals. However, Remote Control will automatically avoid using aggressive caching if 256MB or less of RAM is installed.
Default: True
Enables device bitmaps if set to True. Device bitmaps increase the performance of viewer sessions, but they require more memory on the viewer.
Default: True
If True, specifies the use of the substantially enhanced video capture system in Client Automation r12 that improves performance in low bandwidth environments. The performance of this capture system should be better than the performance of the Unicenter DSM r11 video capture system in nearly all cases.
If False, reverts to the Unicenter DSM r11 video capture system in the unlikely event that remote control performance for a specific application is degraded.
Default: True
Specifies the size, in bytes, of the kernel mode buffer used to store temporary data generated by the video capture driver.
Default: 4194304
Specifies that the Remote Control video drivers be loaded when the host is started and remain loaded until the host stops. If False, Remote Control dynamically loads its video drivers when a remote control session starts and unloads them when the session ends.
On Windows platforms, the act of loading the video drivers causes a slight screen flicker. To facilitate a completely flicker-free connection for stealth mode connections on these platforms, enable this setting (True).
This setting can also be enabled to alleviate some DirectDraw/Direct3D related problems, such as Java applications not being visible on the Remote Control viewer after connecting. However, loading the video drivers may prevent some applications, such as DVD players, from working.
Note: On Linux, the video driver is not dynamically loaded, so this setting has no effect.
Default: False
Limits the maximum amount of memory in megabytes that the host allocates for caching of bitmaps.
Reducing this value will reduce the maximum memory consumption of the host, when in session, at the expense of increasing potential bandwidth requirements for the session.
However, Remote Control automatically limits the size of the bitmap cache if 256MB or less of RAM is installed.
Default: 64MB
Specifies how the host is to send the following legacy system fonts to the viewer computer:
Note: TrueType and other third-party legacy fonts are not affected.
The host sends system font name and size information to the viewer. This information is very small and requires very little network bandwidth. However, if the viewer computer does not have the font installed that the host is using, it cannot exactly reproduce a view of the host's desktop from this information. Typically, this occurs if the host computer has nonstandard system fonts installed, for example, a Hebrew command prompt font.
The Send system fonts setting can be used to make the host computer send bitmaps of the system font's characters to the viewer computer. This permits the viewer to exactly reproduce a view of the host's desktop, even if it does not have the same font installed. This bitmap font information is larger than the equivalent name and size information—approximately 12 KB per font face and size. However, the host will send bitmaps for each font only once, when it is used for the first time.
This setting can be overridden at the viewer computer by disabling the Embed Missing Fonts option on the Experience tab in the Connection Settings dialog. For more information, see the Remote Control Viewer section of the DSM Explorer Help.
Note: Microsoft Windows installs several language versions of each system font by default. Therefore, it is not usually necessary to use this setting to enable support for viewer sessions between computers configured for different languages.
Valid values are as follows:
Specifies that system font bitmaps not be sent.
Specifies that console (that is, command prompt) fonts be sent as bitmaps.
Specifies that all system fonts be sent as bitmaps.
Default: None
Indicates whether the host prevents the slight display flicker that can take place when a remote control session connects. This setting does not affect stealth mode connections, which always try to suppress the display flicker.
For this setting to be effective on Windows, the Load driver on start policy must also be enabled.
Default: False
Indicates the video capture mode for capturing screen changes. There are two methods of capturing screen changes, Driver capture and Polling capture. Driver capture uses a low-level video driver to capture the changes to the screen image. Polling capture works by periodically scanning the screen image for changes.
Typically, the Driver capture mode provides better performance than the Polling capture mode. However, there are some types of applications that cannot be captured by the Driver capture method. These are typically OpenGL or Direct3D based applications, such as computer-aided design applications.
The polling capture mode is capable of capturing screen changes from OpenGL & Direct3D applications.
There are three video capture mode settings for the Remote Control host:
In this mode, Driver capture is used if it is available. If the video driver cannot be installed for some reason, or the machine resources are too limited to load the driver, Polling capture is used as a fallback.
Driver capture is used exclusively. There is no fallback to Polling mode if the Driver mode is unavailable.
Polling mode is used exclusively.
Windows: See Notes on Secure Control in Polling capture mode on Windows.
Default: Auto
Note: Mac OS X Hosts do not have a Driver mode of video capture. They rely on a specially enhanced Polling capture mode, which uses low-level OS support to accelerate video capture. Therefore, modifying this setting has no effect on this platform.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|
