HP mt20 Administrator Guide 8 - Page 103
Primary IP, IP List, NetBIOS. If FQDN is not desired, one of the, RD Web Access
View all HP mt20 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 103 highlights
Registry key root/ConnectionType/freerdp/connections/ /rdWebFeed/filter//name root/ConnectionType/freerdp/connections/ /rdWebFeed/keepResourcesWindowOpened root/ConnectionType/freerdp/connections/ /rdWebFeed/ trustedPublisherSha1Thumbprints root/ConnectionType/freerdp/connections/ /rdWebFeed/verifyPublisherSignature root/ConnectionType/freerdp/connections/ /rdp6Buffering root/ConnectionType/freerdp/connections/ /rdp8Codecs root/ConnectionType/freerdp/connections/ /rdpEncryption root/ConnectionType/freerdp/connections/ /rdpH264Codec root/ConnectionType/freerdp/connections/ /rdpProgressiveCodec root/ConnectionType/freerdp/connections/ /redirectPreference root/ConnectionType/freerdp/connections/ /remoteApp root/ConnectionType/freerdp/connections/ /remoteDesktopService root/ConnectionType/freerdp/connections/ /remoteFx Description Specifies the name of a resource for the resource filter. RemoteApp and Desktop resources with a matching name will be available to users. If set to 0, the resource selection window is closed automatically after a resource has started. If set to 1, the resource selection window is kept open after resources have started. This allows a user to start several resources before closing the resource selection window. Specifies a comma-separated list of SHA1 thumbprints of the trusted resource publishers. Note that a certificate that matches one of these thumbprints is not verified. Import the publisher's root CA for better security. Also see the registry key verifyPublisherSignature and Certificate Manager in Control Panel. If set to 1, the publisher's signature is verified when available in published .rdp files. Only resources with a valid signature from a trusted publisher can be run. If set to 0, no verification of the signature is done. Also see the registry key trustedPublisherSha1Thumbprints. If set to 1, non-RemoteFX graphics performance is increased at the cost of less frequent screen updates. If set to 1, RDP 8 codecs are used if available. This setting should be disabled only in the case of a defect specific to RDP 8 codecs. Disabling this setting might also disable more advanced codecs. If set to 1, standard RDP encryption is used to encrypt all data between the client and the server. If set to 1, RDP 8 H.264 codecs are used if available. This setting has known visual errors, particularly in multi-monitor configurations, and should be considered experimental and unsupported. Enabling this setting simply advises the server that the thin client supports H.264 for desktop display. The server must also support H.264, and the server makes the final decision on what codecs are used. This setting affects only the desktop codecs. It does not affect multimedia redirection codecs. If set to 1, RDP 8 progressive codecs are used if available. This setting should be disabled only in the case of a defect specific to RDP 8 progressive codecs. Disabling this setting might also disable more advanced codecs. For redirection, the RDP client is given several destination possibilities. It normally tries them in the following order: FQDN, Primary IP, IP List, NetBIOS. If FQDN is not desired, one of the alternatives can be tried first by setting this registry key. If the specified method does not work, the RDP client falls back to the original order. A setting of auto forces the original order. Specifies the name of an available application to run in Remote Application Integrated Locally (RAIL) mode. If set to Remote Computer, a direct RDP connection to a remote computer is done. If set to RD Web Access, a connection to an RD Web Access service is done first to retrieve a feed of the published RemoteApp resources. If set to 1, RemoteFX in the style of RDP 7.1 is used if available. This setting is deprecated and might disappear in a future release ConnectionType 91