PCoIP Connection.Horizon Client for Mac 2103 | 23 March 2021VMware is now using the Blast protocol by default and does not allow you to change to the older PCOIP protocol. Important Notes To connect to virtual machines running the VMware Horizon View Direct Connection. This release is a security update with bug fixes to version 5.2.1 and is recommended for all users of older releases. Teradici Important Product Update Notice SeptemPCoIP Zero Client Firmware 5.2.2 GA PCoIP Zero Client Firmware 5.2.2 is a firmware for Tera2 Zero Clients only (not Remote Workstation Cards).Unmatched performance - The adaptive capabilities of the PCoIP display protocol and the VMware Blast display protocol are optimized to deliver the best user experience, even over low-bandwidth and high-latency connections. Support for macOS Mojave (10.14), macOS Catalina (10.15), and macOS Big Sur (11) - Use a 64-bit Intel-based Mac or ARM M1-based Mac running in emulation with Rosetta 2 to work on your remote desktop or published application. The new Horizon Client is available for Windows, MAC, Ubuntu, iOS.Horizon Client for Mac makes it easy to access your remote desktops and published applications from your Mac with the best possible user experience on the Local Area Network (LAN) or across a Wide Area Network (WAN). Recommend the Teradichi PCOIP client or have the developers allow the customer to choose the protocol.These release notes cover the following topics:Components of VMware Horizon View 6 The core components of VMware Horizon View 6.Horizon Client for Mac also supports optional RADIUS and RSA SecurID authentication.Top of Page What's New in This Release Horizon Client for Mac 2103 includes the following new features: Enhanced certificate checking is performed on the client. Secure from any location - At your desk or away from the office, your data is delivered securely to you wherever you are. Quickly reconnect to your remote desktop or published application by selecting shortcuts in Horizon Client. Simple connectivity - Horizon Client for Mac is tightly integrated with VMware Horizon for simple setup and connectivity.DPI synchronization for published applicationsThe DPI Synchronization feature is now supported for published applications. User interface changes for Section 508 complianceKeyboard navigation enhancements are implemented for Section 508 compliance. See Configuring Media Optimization for Microsoft Teams. Media Optimization for Microsoft Teams supportMedia Optimization for Microsoft Teams redirects audio calls, video calls, and viewing desktop shares for a seamless experience between the client system and the remote session without negatively affecting the virtual infrastructure and overloading the network.
Vmware Pcoip Client Update With BugHorizon Client for Mac is supported with the latest maintenance release of Horizon 7 version 7.5 and later releases. Horizon Client requires a macOS Mojave (10.14), macOS Catalina (10.15), or macOS Big Sur (11) operating system running on a 64-bit Intel-based Mac or ARM M1-based Mac running in emulation with Rosetta 2. InternationalizationThe user interface and documentation for Horizon Client are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, Korean, and Spanish. See Using a High-Resolution Mac with Retina Display and Allow Display Scaling.For information about new remote desktop features, see Release Notes for VMware Horizon Version 2103. ![]() Because the SD card is not mounted on your Mac client system, the device does not appear in the menu in Horizon Client and you cannot use the USB redirection feature to connect the device to the remote desktop.Workaround: Reinsert the SD card into the Transcend card reader. From the Horizon Client menu bar, select Desktop > USB > Autoconnect USB Devices on Insert.When you insert an SD card into a Transcend USB 3.0 card reader attached to your Mac client system, the SD card is not mounted automatically. The remote desktop shows that a new drive was added and so displays a new drive letter but no corresponding label to identify the device.Workaround: Configure Horizon Client to automatically connect the device when you insert it. Smart card redirection might not work after you unplug and re-plug in a smart card/smart card reader several times. Smart card authentication does not work after you unplug and re-plug in a smart card/smart card reader. Because of this issue, the following problems might occur in Horizon Client on macOS 10.14 or later: If you are a Horizon administrator, restart Horizon Agent in the machine.After you connect to a remote desktop with the USB Automatically connect at startup setting enabled, the desktop connection is sometimes disconnected.When you start the USB service on a macOS Mojave (10.14) or later system, the System Extension Blocked dialog box appears.Workaround: Click OK in the System Extension Block dialog box, navigate to System Preferences > Security & Privacy, and allow the extension to load.On macOS 10.14 or later, if you are using a TokenD driver, the Keychain Access app does not refresh when you unplug and re-plug in a smart card/smart card reader, and the Mac client cannot obtain the update status for the smart card. In Horizon Administrator, the state of the machine is Agent unreachable.Workaround: If you are an end user, restart Horizon Client and try again. The files appear on the drive.When you connect to a Windows remote desktop, start USB services, redirect a USB storage device to the remote desktop, disconnect from the remote desktop, and then try to reconnect to the remote desktop, either USB services are not available in the remote desktop or you cannot reconnect to the remote desktop. Text edit for macIf the cache type for the IDPrime. Net card, when the SafeNet Authentication Client middleware is installed, you can view or change the smart card's cache type. There is no workaround for the smart card removal policy issue with a TokenD driver.If you set the Horizon Client security preference ( VMware Horizon Client > Preferences > Security) to Do not verify server identity certificates and connect to a server that has a valid root-signed certificate, Horizon Client might stop responding.Workaround: Unplug the smart card reader and then plug it back in.With the IDPrime. For the smart card redirection issue, reboot the Mac client machine, launch Horizon Client, and perform smart card authentication again, making sure that Keychain Access isn't launched. If you want to continue using the TokenD driver, for the smart card authentication issue, quit both Keychain Access and the Horizon Client app, relaunch Horizon Client, and perform smart card authentication again, making sure that Keychain Access is not launched. The smart card removal policy on the agent machine might not work.Workaround: Switch to the CryptoTokenKit driver on macOS 10.14 or later. This problem is caused by a PCoIP limitation.When you connect to a remote desktop that is running Windows 10 Creators Update with the VMware Blast display protocol, autofit fails when the desktop enters full screen with two displays. If you are already connected to the remote desktop or application, reconnect to the Connection Server instance and switch to the English Input Source on the Mac client system before you connect to the remote desktop or application.If you launch a remote desktop with the PCoIP display protocol in full screen or window mode on an iMac with a Retina or monitor that supports a 5K display, and the screen size is more than 4K (4096 x 2160), auto fit does not work for the remote desktop if you change the display to full resolution.Workaround. This setting enables the client to verify the smart card's PIN each time the user connects to the server.TokenD support for physical smart cards does not work well with macOS Catalina 10.15.4 and later.Workaround: Use CTK instead, or modify the following option to enable TokenD support:#sudo defaults write /Library/Preferences/com.apple.security.smartcard Legacy -bool trueKeyboard shortcut mappings do not work if you are connected to a remote desktop or application and the Mac Input Source is Traditional Chinese or Korean.Workaround: Before you connect to the remote desktop or application, switch to the English Input Source on the Mac client system.
0 Comments
Leave a Reply. |
AuthorJerryboy ArchivesCategories |