Skip to content Skip to sidebar Skip to footer

Vmware Horizon Uploading Files Looses Mouse and Keyboard

VMware Horizon Client for Mac 2111.1 | x MAR 2022

Check for additions and updates to these release notes.

What's New

Horizon Client for Mac 2111 fixes the keyboard issue that caused repeating keystokes

For information about new remote desktop features, see the VMware Horizon viii 2111 Release Notes.

Internationalization

he user interface and documentation for Horizon Client are available in English language, Japanese, French, High german, Simplified Chinese, Traditional Chinese, Korean, and Spanish.

Before You Begin

  • Horizon Customer requires a macOS Catalina (ten.15), macOS Big Sur (11), or macOS Monterey (12) operating system running on a 64-bit Intel-based Mac or ARM M1-based Mac running in emulation with Rosetta 2.
  • Horizon Client for Mac is supported with the latest maintenance release of Horizon 7 version 7.5 and after releases.
  • To install Horizon Client for Mac, download the disk image file from the VMware Horizon Client download page. For arrangement requirements and installation instructions, encounter the VMware Horizon Client for Mac Installation and Setup Guide document.
  • Beginning with Horizon Customer for Mac 2006, Virtual Printing (also known every bit ThinPrint) is non supported. Use VMware Integrated Press instead.

Resolved Bug

  • E911 For Microsoft Teams Optimization upshot : Teams condition shows as disconnected if network switch PortID name has non-utf8 character and E911 is enabled.
  • While using Horizon Customer for Mac 2103 and 2111, the keystrokes go repeated intermittently.

Known Issues

  • USB Redirection
  • Smart Card Hallmark
  • Displays and Keyboards
  • Bear upon Bar
  • Miscellaneous

USB Redirection

  • Connecting countersign-protected storage devices may non work correctly

    If you utilize the PCoIP display protocol, connecting some countersign-protected storage devices (such as IronKey USB flash drives) might not piece of work correctly. For case, after y'all redirect the device to the remote desktop, the password prompt does not announced. The remote desktop shows that a new drive was added and then displays a new bulldoze letter but no corresponding label to identify the device.

    Workaround: Configure Horizon Client to automatically connect the device when you insert it. From the Horizon Customer bill of fare bar, select Desktop > USB > Autoconnect USB Devices on Insert.

  • Files practise non get copied or moved to Transcend USB 3.0 external hard drive when using USB redirection characteristic

    If y'all use the USB redirection feature to connect a Transcend USB 3.0 external hard drive to a remote desktop from your Mac client system, files that you lot re-create or move to the drive practice not appear on the bulldoze afterward you disconnect the bulldoze from the remote desktop.

    Workaround: Redirect the external hard drive to the remote desktop once again. The files appear on the drive.

  • USB services non available in remote desktop or yous cannot reconnect to remote desktop in certain circumstances

    When y'all connect to a Windows remote desktop, start USB services, redirect a USB storage device to the remote desktop, disconnect from the remote desktop, and and then endeavor to reconnect to the remote desktop, either USB services are non available in the remote desktop or y'all cannot reconnect to the remote desktop. In Horizon Ambassador, the state of the machine is Agent unreachable.

    Workaround: If yous are an end user, restart Horizon Client and try again. If you are a Horizon administrator, restart Horizon Agent in the car.

  • Desktop connection is sometimes disconnected

    After you connect to a remote desktop with the USB Automatically connect at startup setting enabled, the desktop connection is sometimes disconnected

    Workaround: None.

  • System Extension Blocked dialog box appears when you starting time USB service

    When you lot showtime the USB service on a macOS 10.15 or afterwards system, the Arrangement Extension Blocked dialog box appears.

    Workaround: Click OK in the Organization Extension Cake dialog box, navigate to System Preferences > Security & Privacy, and permit the extension to load.

Smart Card Authentication

  • Keychain Admission app does not refresh

    On macOS 10.15 or later, if you are using a TokenD driver, the Keychain Admission app does non refresh when you lot unplug and re-plug in a smart card/smart card reader, and the Mac client cannot obtain the update status for the smart card. Because of this issue, the following problems might occur in Horizon Client on macOS 10.15 or later:

    • Smart card authentication does not work afterwards you unplug and re-plug in a smart carte du jour/smart bill of fare reader.
    • Smart card redirection might not work after yous unplug and re-plug in a smart carte du jour/smart card reader several times.
    • The Disconnect user sessions on smart card removal selection in Horizon Administrator does not work.
    • The smart card removal policy on the amanuensis machine might non work.

    Workaround: Switch to the CryptoTokenKit driver on macOS 10.15 or later. If you want to continue using the TokenD commuter, for the smart carte hallmark event, quit both Keychain Admission and the Horizon Client app, relaunch Horizon Customer, and perform smart carte authentication again, making sure that Keychain Admission is not launched. For the smart card redirection issue, reboot the Mac client car, launch Horizon Client, and perform smart menu hallmark again, making certain that Keychain Access isn't launched. There is no workaround for the smart card removal policy upshot with a TokenD commuter.

  • Horizon Client might finish responding when you connect to a server that has a valid root-signed document

    If you fix the Horizon Client security preference (VMware Horizon Customer > Preferences > Security) to Do not verify server identity certificates and connect to a server that has a valid root-signed document, Horizon Client might stop responding

    Workaround: Unplug the smart carte du jour reader and then plug it dorsum in.

  • Client may not verify the smart card's PIN during server authentication

    With the IDPrime .Net card, when the SafeNet Authentication Client middleware is installed, you can view or modify the smart card'due south cache type. If the cache type for the IDPrime .Net card is "Normal Enshroud," the client may not verify the smart card's Pivot during server hallmark when the smart card Pivot is cached.

    Workaround: Alter the Cache Type to "Ever Prompt" for the IDPrime .Net card. This setting enables the customer to verify the smart card's PIN each time the user connects to the server.

  • TokenD support for concrete smart cards does not work

    TokenD support for physical smart cards does not piece of work well with macOS Catalina 10.fifteen.iv and later.

    Workaround: Utilize CTK instead, or modify the following option to enable TokenD support:

                      #sudo defaults write /Library/Preferences/com.apple.security.smartcard Legacy -bool true                

Displays and Keyboards

  • Auto fit does not piece of work for remote desktop if you lot change the brandish to full resolution

    If you launch a remote desktop with the PCoIP brandish protocol in full screen or window way on an iMac with a Retina or monitor that supports a 5K brandish, and the screen size is more 4K (4096 x 2160), auto fit does not work for the remote desktop if you alter the display to total resolution.

    Workaround. None. This problem is caused by a PCoIP limitation.

  • Remote desktop stops responding when y'all connect to it with the VMware Blast display protocol

    When yous connect to a remote desktop with the VMware Blast display protocol from a Mac client system that has an NVIDIA GeForce GT 755M graphics carte du jour, the desktop stops responding.

    Workaround: None. This is a third-political party effect.

  • Autofit fails when desktop enters full screen with two displays

    When you connect to a remote desktop that is running Windows x Creators Update with the VMware Blast brandish protocol, autofit fails when the desktop enters full screen with ii displays.

    Workaround: Resize the window and autofit recovers.

  • Desktop stops responding when you lot connect to a remote desktop with the VMware Smash display protocol

    When you connect to a remote desktop with the VMware Smash brandish protocol from a Mac client organization that has an NVIDIA GeForce GT 755M graphics menu, the desktop stops responding.

    Workaround: None. This is a tertiary-party effect.

  • Connectedness to remote desktop with VMware Nail display protocol in full-screen or window mode fails

    If yous commencement a remote desktop with the VMware Smash display protocol in total-screen or window mode on an iMac that has a Retina display or a monitor that supports a 5K display with Full Resolution mode, and and then disconnect and reconnect with the PCoIP display protocol, the connection fails and the remote desktop does not first.

    Workaround: This problem is caused by a PCoIP limitation. Change to Normal manner and utilize the PCoIP or VMware Blast display protocol.

  • Mouse arrow may lag or flicker when you open an awarding session

    When yous open up an application session on a MacBook 2012 or earlier, the mouse pointer may lag or flicker as information technology moves over the application window.

    Workaround: Add the viewClient.allowLossyCursor setting to ~/Library/Preferences/VMware Horizon View/config and then restart Horizon Client. If the ~/Library/Preferences/VMware Horizon View/ folder does non withal be, create the folder by running this command from Terminal.app: mkdir -p ~/Library/Preferences/VMware\ Horizon\ View

Bear upon Bar

  • Focus for front window is lost when you lot use the Touch Bar to switch between published applications

    Yous might lose focus for the front end window when you use the Impact Bar to switch betwixt published applications that are hosted on Windows Server 2016. This problem can too occur when you press Command+~, or click the dock icon, to switch windows. This trouble typically only occurs after switching windows several times.

    Workaround: Utilize the mouse to click the window and regain focus.

Miscellaneous

  • Changes to webcam and sound devices non detected by Real-Time Audio-Video feature

    Changes to webcam and audio devices that are connected to, or asunder from, the Mac client organization during a remote desktop session are not detected by the Real-Fourth dimension Audio-Video feature.

    Workaround: Disconnect and reconnect to your remote desktop session to observe webcam and audio device changes. For example, if yous connect a USB headset to the Mac client system during a remote desktop session and you desire to use that headset on the remote desktop, you must disconnect and reconnect to the remote desktop session to make the headset available.

  • Unexpected results when you edit an application pool in Horizon Panel

    If an administrator edits an application pool in Horizon Panel and changes the path to point to a different application that already has an application pool associated with information technology, unexpected results can occur. For example, the original application might be launched from the Mac Dock instead of the new application.

    Workaround: Make sure that each application in a subcontract is associated with simply one application pool.

  • Cannot launch an application from Mac Dock

    Users cannot launch an application from the Mac Dock if multiple application pools signal to the aforementioned application in one farm, and if the application puddle the users selected was created with associated parameters in Horizon Panel. If a user saves the application in the Mac Dock and tries to open the saved item, the application fails to launch with the associated parameters.

    Workaround: Make sure that each application in a farm is associated with just one application pool.

  • Cannot launch an application from the Mac Dock if multiple application pools point to the same application

    Users cannot launch an application from the Mac Dock if multiple awarding pools point to the aforementioned awarding in one subcontract, and if the application pool the users selected was created with associated parameters in Horizon Console. If a user saves the application in the Mac Dock and tries to open the saved detail, the application fails to launch with the associated parameters.

    Workaround: Brand sure that each awarding in a farm is associated with merely one application pool.

  • Cannot log in to a server every bit a different user if the Retrieve this password check box is selected

    If you select the Recall this password check box when you log in to a server, you cannot log in to the same server every bit a different user if the credential caching timeout menses (clientCredentialCacheTimeout) on the server has not withal expired. Horizon Customer volition automatically employ the saved credentials to log you in to the server.

    Workaround: Remove the server from the Selector window (right-click the server icon and select the Delete menu item), click the Add Server button to add the server again, and then log in to the server equally the different user.

  • Response time of Windows Server 2016 hosted remote applications is slow

    On belatedly 2016 MacBook Pro customer systems, the response time of Windows Server 2016 hosted remote applications is slow in the kickoff few seconds after you launch a Windows Server 2016 awarding or switch the meridian window between Horizon Client and the Windows Server 2016 application window.

    Workaround: None. This is a tertiary-political party effect.

  • Remote application sessions are disconnected later pre-launch timeout expires

    If y'all connect to a remote application for which the pre-launch feature is enabled on a Horizon vii version 7.two server, and the Horizon Client reconnect behavior is set up to "Inquire to reconnect to open applications" or "Practise not ask to reconnect and exercise not automatically reconnect," resumed application sessions are asunder subsequently the pre-launch timeout expires (default 10 minutes).

    Workaround: Set up the Horizon Client reconnect behavior to "Reconnect automatically to open applications."

  • Maximize icon does not appear when you hover your mouse over the Shut icon

    With Moom 3.ii.12 (3240), the Moom UI appears when you hover your mouse over the Shut icon in Office 2016 and 2019 apps instead of the maximize icon.

    Workaround: None.

  • Horizon Customer for Mac stops responding

    Horizon Client for Mac stops responding if you unplug an external graphics processing unit of measurement (GPU).

    Workaround: None.

  • Cannot start a VMware App Volumes application

    You cannot start a VMware App Volumes application from the Dock on the client organisation.

    Workaround: Outset the application from Horizon Client, or use a shortcut.

  • Moom user interface does non work

    The Moom user interface does not work for UWP published applications.

    Workaround: None.

  • Focus for the front end window is lost when using custom controls

    You might lose focus for the front window when you apply custom controls in the Moom app to motility or resize published applications that are hosted on Windows Server 2016 or Windows Server 2019.

    Workaround: To regain focus, utilise your mouse to click on the title bar of the awarding window.

  • Horizon Client presents an alert message when URL Content Redirection feature is configured

    When the URL Content Redirection characteristic is configured, Horizon Customer presents an alert bulletin that asks you to change your default spider web browser to VMware Horizon URL Filter for using third-party apps, not including the Chrome and Edge browsers. You must click Yep to apply the URL Content Redirection feature. In macOS xi (Big Sur), even when you click Yes to the alarm message, the VMware Horizon URL Filter user interface is not shown in the default web browser of the general choice, which means you cannot change the default web browser from another browser to VMware Horizon URL Filter manually, and you must connect to the server once again. In macOS 10, the user interface is shown in the default spider web browser of the full general option. The URL Content Redirection extensions for the Chrome and Edge browsers are non influenced past macOS xi.

    Workaround: None. This trouble is a tertiary-party consequence.

  • Screen sharing with Microsoft Teams Optimization Pack is not supported

    When using Microsoft Teams Optimization Pack with Horizon Client for Mac or Horizon Customer for Linux published applications, screen sharing is not supported.

    Workaround: None.

cheque-circle-line assertion-circle-line close-line

Scroll to top icon

bowmansaund1960.blogspot.com

Source: https://docs.vmware.com/en/VMware-Horizon-Client-for-Mac/2111.1/rn/vmware-horizon-client-for-mac-21111-release-notes/index.html

Post a Comment for "Vmware Horizon Uploading Files Looses Mouse and Keyboard"