Horizon View Ssl Connection Was Shut Down While Reading

Stratodesk makes sure NoTouch has latest versions of the VMware Horizon View client (formerly known equally VMware View client) for Linux integrated. Our VMware Horizon View client implementation supports both PCoIP and RDP protocol with USB forwarding, making a perfect VMware Horizon View endpoint solution, without any demand for installing software, cryptic configuration files or control line options! NoTouch provides a complete configuration environment for the View client, and then you don't have to work with command-line options or config files - everything tin be configured and managed via the local NoTouch configuration carte equally well as centrally with NoTouch Center.

This commodity gives an overview of the different configuration scenarios and after describes VMware specific configuration steps. We presume that you basically empathise how NoTouch Bone is configured and particularly how server connections are created and configured.

Contents

• 1 Bones connectedness setup
• ii FAQ/Common configuration scenarios
• 3 Automatic connection
• 4 Multimonitor/Dualscreen functioning
• 5 HTTPS/SSL and certificates
• half dozen Protocols
  • vi.1 Blast Farthermost performance
  • half-dozen.two PCoIP operation
  • half-dozen.iii RDP operation
• vii USB forwarding
• 8 Smartcard support

Basic connectedness setup

This assumes you are familiar with configuring NoTouch locally or via NoTouch Middle. Making your endpoint connect to a VMware Horizon View server is easy and requires just ii steps:

1. Create a connection and set up the connection mode to "VMware Horizon View" (or "VMware View" in older software versions)
2. Type in your View connectedness banker URL into the connection target parameter. Typically this is something like https://myviewserver.mycompany.com/

This is enough to connect to a Horizon VDI server - it's really that easy. From there you can of course change many unlike options. For instance, you lot can configure the client to come up automatically afterward boot time; and you tin can modify all VMware View client options (submenu VMware Horizon View) under the Connection options. Meet below for the configuration possibilities.

Your NoTouch endpoint tin can be configured every bit well from both the local configuration and NoTouch Center.

FAQ/Common configuration scenarios

Before describing all bachelor options, we want to shine a light on a few "FAQ"-type scenarios:

• I utilize a private certificate and don't want the alarm to appear. Either add your private root CA document to the client, or disable the certificate bank check (less secure). For the latter, ready the "Certificate Check" parameter to "Allow unverifiable connection".

• I want the arrangement to connect automatically to a specific desktop. Simply type in the name of your desktop (pool) into the "Desktop proper name" parameter. In that location is some other parameter called "Connect automatically if enough values are given" that needs to exist set to "on", which is the default value, merely delight double-bank check.

• I don't want the View client to stay open after the users disconnect from their desktops. Set the parameter "Exit on disconnect or error" to "on".

• I don't desire to run into this menu bar on superlative of the screen, it confuses my users. Set the parameter "Disable fullscreen dropdown menu bar" to "on".

If you experience enlarged and distorted icons with the Blast protocol, On the VMware Horizon View tab

• Set Blast - H.264 Decoding and Blast h.264 Loftier Color Accurateness to On

Automatic connection

To make the View customer automatically connect to a specific desktop, two things need to exist set up:

• The "Desktop name" parameter must contain the proper noun of the desktop or pool to connect to - please make sure you lot spell it exactly as configured on the server
• The "Connect automatically if plenty information present" parameter must be set to "on". This is the default, so commonly yous don't have to do anything hither.

Y'all might also desire to have the connexion automatically starting at kicking time, for this to happen fix the "Autostart at boot" parameter to on (in the Connection options, not the VMware Horizon View options).

If you don't want the View client to stay open later the users disconnect from their desktops, set the parameter "Get out on disconnect or error" to "on". This prevents your users to take to logoff twice, one time from the desktop and a second fourth dimension from the View customer.

If you similar the idea of everything being fully automated, you may have a wait at the Activeness after exit parameter. This would allow you command the behavior of when the View client exits (the View client, not the VDI desktop; these may be dissever events, depending on the "Go out on disconnect" setting above) and brand NoTouch to restart the connexion, or reboot or shutdown the machine.

Multimonitor/Dualscreen performance

The VMware View client will accept advantage of multiple monitors automatically and information technology volition report screen geometry to the server with PCoIP and FreeRDP. Please make sure Multimonitor support works, more than information can be establish here: Multimonitor performance with NoTouch

Two parameters influence the dualmonitor/multimonitor behavior - the effects of these parameters are entirely upwards to VMware and may change with different versions of the View client:

• Desktop size
  • All. This is the default. All monitors are available to the View customer.
  • Full. Only one monitor will be used, and the full monitor can exist used.
  • No setting. NoTouch will not gear up this parameter at all when launching the View client.
  • Custom size WxH.
  • Large. The View customer will occupy a large portion of the screen.
  • Pocket-sized. The View client will occupy a small portion of the screen.
• Fullscreen mode
  • No setting. This is the default.
  • Enable fullscreen fashion across all monitors.
  • Enable fullscreen mode in single monitor style.

To fully understand these options one has to consider that the VMware View client itself is a window that can occupy space - mostly displaying available desktop choices - (desktop size), versus the manner the server side desktops are launched (fullscreen style).

NoTouch ii.35+ sets "Desktop size" to "All" as default which means that all monitors are fabricated bachelor to the View client and does not ready the fullscreen mode (launched desktops will be still exist fullscreen unless overriden in the server-side View configuration).

If you use RDP, yous can chose betwixt rdesktop and FreeRDP as available RDP clients. Please notation that rdesktop can not study screen geometry to the server, wheres FreeRDP does (as does PCoIP).

HTTPS/SSL and certificates

If y'all use private certificates, you lot may take to add together your own certificate - please refer to the documentation on certificates.

Furthermore, in that location is the parameter "Certificate check beliefs" with three options:

• Warn if connection may be insecure. This is the default setting. The View client will warn the user if information technology can non verify the document by displaying a dialog box.
• Reject unverifiable connection. The View client will not allow connecting to a server with a document that can not be verified. Connections to servers with private or self-signed certificate won't piece of work unless these certificates are added to the system.
• Let unverifiable connexion. This will basically turn the document verification off.

Please note that for certificate timestamp checks the VMware Horizon View customer might try to contact machines on the Internet.

Protocols

The VMware Horizon View implementation in NoTouch supports Blast Extreme, PCoIP and RDP; the latter with rdesktop and FreeRDP; both are open-source implementations of the RDP protocol, FreeRDP being more mod, rdesktop having a longer history and thus more installed base.

The "Preferred protocol" parameter controls the protocol choice:

• No setting. This is the default. Let the View server and/or user decide.
• Boom. Force the utilise of Boom Extreme, if the server allows it.
• PCoIP. Strength the employ of PCoIP, if the server allows information technology.
• RDP. Force the use of RDP, if the server allows it.

Blast Farthermost functioning

Nail Farthermost works without deeper configuration.

PCoIP operation

PCoIP works without deeper configuration.

RDP functioning

If you use RDP, the parameter "RDP customer to utilise" gives you command over which RDP customer software is to be used:

• No setting. Let the VMware View client make up one's mind. Every bit of NoTouch 2.35, this will lead to rdesktop.
• rdesktop. Strength using rdesktop.
• FreeRDP. Force using FreeRDP.

USB forwarding

By default, USB forwarding switched to on and USB devices will exist forwarded to the server automatically. So called HIDs (human interface devices, such as keyboards, mice, but as well mouse-emulating devices like digital dictation pes pedals) will non be forwarded, simply rather handled locally and brought to the VDI desktop as keystrokes and mouse movements - you tin alter that if y'all need, please see here: VMware Horizon View USB forwarding

If you lot experience problems with USB forwarding, you can change the version of the USB forwarding component. As of NoTouch 2.35, VMware allows to use the virtually contempo USB forwarder component too as version one.five.0 which was based on a different technology. The parameter "USB forwarder version" allows to choose betwixt those ii. If y'all change this, please brand sure the devices is rebooted for changes to take effect.

The VMware USB forwarder is a system service, thus information technology can be configured from the "Services" parameters, not the VMware View connection parameters. The startup beliefs is controlled by the parameter named "VMware USB forwarder" parameter. It has these options:

• "with VMware View connection". This is the default. Offset the VMware View USB forwarder but if at that place is a VMware View connection configured.
• "off". Exercise non get-go the VMware View USB forwarder.
• "on". Start the VMware View USB forwarder afterward system kick.

Smartcard support

VMware Horizon View can forrard smartcard readers and use these for login purposes. U.Due south. Federal customers will enjoy the CAC carte du jour back up. In that case, do non forrard the smartcard reader with generic USB forwarding. Configure smartcard support according to these instructions:

1. Verify your Horizon View agent has been installed with smartcard components. By default, they will not be installed, so you have to take action here. Refer to this guide
2. Switch on the "Smartcard service (PCSCD)" in the "Services" options
   • In most cases the default settings for the Smartcard commuter parameter will exist fine. Some readers need the Omnikey setting, non just Omnikey readers. You may have to experiment with that or contact back up.
3. Gear up the "Smartcard driver PKCS#eleven" parameter in the VMware Horizon View parameters to lucifer your cards
4. Make certain you lot have added your root certificates to the NoTouch system according to Certificates
   • The certificate must be in PEM class and have the extension .crt

gustafsonpereadesen.blogspot.com

Source: https://www.stratodesk.com/kb/VMware_Horizon_View

Share this post