Vmware View Client 4.5 Mac Download Updated

Vmware View Client 4.5 Mac Download

Horizon Client for Mac 2111 | thirty November 2021

These release notes encompass the following topics:

Fundamental Features
What'south New in This Release
Internationalization
Before You Brainstorm
Resolved Issues
Known Issues

Key Features

Horizon Customer for Mac makes information technology easy to access your remote desktops and published applications from your Mac with the all-time possible user experience on the Local Area Network (LAN) or across a Wide Area Network (WAN).

Back up for macOS Catalina (10.xv), macOS Big Sur (11), and macOS Monterey (12)- 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.
Unmatched operation - The adaptive capabilities of the PCoIP display protocol and the VMware Blast display protocol are optimized to deliver the best user feel, even over low-bandwidth and high-latency connections. Your remote desktop or published application is fast and responsive, regardless of where you are.
Simple connectivity - Horizon Client for Mac is tightly integrated with VMware Horizon for unproblematic setup and connectivity. Speedily reconnect to your remote desktop or published application past selecting shortcuts in Horizon Customer.
Secure from any location - At your desk or abroad from the office, your data is delivered securely to you wherever you lot are. Enhanced certificate checking is performed on the client. Horizon Client for Mac also supports optional RADIUS and RSA SecurID authentication

Acme of Page

What'southward New in This Release

Horizon Client for Mac 2111 includes the following new features:

Codec Parameter is Configurable for Real-Fourth dimension Audio-Visual (RTAV)
Yous can gear up the pinch technology used by RTAV. The default value is VmwH264Speex; however, you can change to VmwTheoraSpeex. If the value you enter is invalid, the default value remains. See Configuring Real-Time Audio-Video on Mac Client.
Increased integration with assistive technologies
These accessibility enhancements include improved interoperability with screen readers such as VoiceOver.
Ability to assign 3-key operations
Some hosted applications override common ii-primal mappings. You can customize your keyboard by assigning operations, such as switching between applications, to a 3-key performance.
Enhanced USB management
Yous can manage USB services from the Connexion card and specify redirection to start upwards automatically for all or certain USB devices. Run across Apply USB Devices.
The awarding icon in the Dock displays a counter for new items
For seamless applications, the particular counter was missing from the application icon in the Dock. In this release, the application icon includes a counter. This counter indicates the inflow of new items. In the event of a disconnection, the counter updates afterward reconnecting and a new item arrives.
Keystroke Encryption
You lot can enable encryption between the keyboard and the client to avoid key-logging malware on the endpoint.

For information well-nigh new remote desktop features, run across theVMware Horizon eight 2111 Release Notes.

Internationalization

The user interface and documentation for Horizon Client are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, Korean, and Castilian.

Elevation of Page

Before You Begin

Horizon Client requires a macOS Catalina (ten.15), macOS Large 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 Customer for Mac is supported with the latest maintenance release of Horizon 7 version 7.v and after releases.
To install Horizon Client for Mac, download the deejay image file from the VMware Horizon Customer download page. For organisation requirements and installation instructions, see the VMware Horizon Client for Mac Installation and Setup Guide document.
Starting time with Horizon Client for Mac 2006, Virtual Printing (also known as ThinPrint) is not supported. Use VMware Integrated Press instead.

Resolved Problems

The number provided before each resolved consequence refers to the VMware internal issues tracking system.

Known Issues

The known problems are grouped every bit follows.

USB Redirection
Smart Menu Authentication
Displays and Keyboards
Touch Bar
Miscellaneous

USB Redirection

If you use the PCoIP display protocol, connecting some password-protected storage devices (such as IronKey USB flash drives) might not work correctly. For example, subsequently you redirect the device to the remote desktop, the countersign prompt does non appear. The remote desktop shows that a new bulldoze was added and so displays a new drive alphabetic character just no corresponding characterization to identify the device.

Workaround: Configure Horizon Customer to automatically connect the device when you insert it. From the Horizon Client carte du jour bar, select Desktop > USB > Autoconnect USB Devices on Insert.
When y'all insert an SD card into a Transcend USB 3.0 bill of fare reader attached to your Mac client organization, the SD card is non mounted automatically. Considering the SD card is not mounted on your Mac client organisation, the device does not appear in the carte du jour in Horizon Client and you cannot use the USB redirection feature to connect the device to the remote desktop.

Workaround: Reinsert the SD carte du jour into the Transcend menu reader. Later on the device is connected to the remote desktop, reinsert the SD card again to brand the disk volume appear in the remote desktop.
If yous 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 yous copy or move to the drive do non announced on the bulldoze after you disconnect the drive from the remote desktop.

Workaround: Redirect the external hard drive to the remote desktop over again. The files announced on the drive.
When you connect to a Windows remote desktop, kickoff USB services, redirect a USB storage device to the remote desktop, disconnect from the remote desktop, and and so effort to reconnect to the remote desktop, either USB services are not bachelor in the remote desktop or you cannot reconnect to the remote desktop. In Horizon Ambassador, the state of the machine is Agent unreachable.

Workaround: If you are an finish user, restart Horizon Client and attempt again. If you lot are a Horizon administrator, restart Horizon Amanuensis in the automobile.
After you connect to a remote desktop with the USB Automatically connect at startup setting enabled, the desktop connection is sometimes disconnected.

Workaround: None.
When you start the USB service on a macOS 10.xv or afterwards system, the System Extension Blocked dialog box appears.

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

Smart Card Authentication

On macOS 10.15 or later, if yous are using a TokenD commuter, the Keychain Admission app does not refresh when you lot unplug and re-plug in a smart bill of fare/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.xv or afterwards:
- Smart bill of fare authentication does not piece of work after you lot unplug and re-plug in a smart card/smart card reader.
- Smart card redirection might not piece of work after yous unplug and re-plug in a smart carte du jour/smart bill of fare reader several times.
- The Disconnect user sessions on smart card removal pick in Horizon Ambassador does non work.
- The smart card removal policy on the agent machine might not work.
Workaround: Switch to the CryptoTokenKit driver on macOS ten.fifteen or later. If you desire to continue using the TokenD driver, for the smart card authentication effect, quit both Keychain Access and the Horizon Customer app, relaunch Horizon Customer, and perform smart card hallmark again, making sure that Keychain Admission is not launched. For the smart card redirection result, reboot the Mac client machine, launch Horizon Client, and perform smart carte du jour authentication once more, making certain that Keychain Admission isn't launched. 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 and so plug it back in.
With the IDPrime .Net card, when the SafeNet Authentication Customer middleware is installed, you can view or change the smart card's enshroud type. If the cache type for the IDPrime .Net carte is "Normal Cache," the client might non verify the smart card'south PIN during server authentication when the smart card PIN is cached.

Workaround: Change the Cache Type to "Always Prompt" for the IDPrime .Net menu. This setting enables the customer to verify the smart carte du jour'due south Pivot each fourth dimension the user connects to the server.
TokenD support for physical smart cards does not work well with macOS Catalina 10.xv.4 and after.

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

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

Displays and Keyboards

Keyboard shortcut mappings do not work if yous are connected to a remote desktop or awarding and the Mac Input Source is Traditional Chinese or Korean.

Workaround: Earlier you lot connect to the remote desktop or application, switch to the English Input Source on the Mac customer system. If yous 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 arrangement before you connect to the remote desktop or application.
If you launch a remote desktop with the PCoIP brandish 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 than 4K (4096 x 2160), car fit does not piece of work for the remote desktop if you lot alter the display to total resolution.

Workaround. None. This problem is caused by a PCoIP limitation.
When yous connect to a remote desktop that is running Windows ten Creators Update with the VMware Blast display protocol, autofit fails when the desktop enters full screen with two displays.

Workaround: Resize the window and autofit recovers.
When you connect to a remote desktop with the VMware Blast display protocol from a Mac customer organisation that has an NVIDIA GeForce GT 755M graphics carte du jour, the desktop stops responding.

Workaround: None. This is a 3rd-party event.
If you lot first a remote desktop with the VMware Blast display protocol in full-screen or window mode on an iMac that has a Retina brandish or a monitor that supports a 5K display with Full Resolution manner, and then disconnect and reconnect with the PCoIP display protocol, the connection fails and the remote desktop does not start.

Workaround: This problem is caused by a PCoIP limitation. Change to Normal mode and use the PCoIP or VMware Blast brandish protocol.
When y'all open an application session on a MacBook 2012 or earlier, the mouse pointer may lag or flicker as it moves over the awarding window.

Workaround: Add the viewClient.allowLossyCursor setting to ~/Library/Preferences/VMware Horizon View/configand and then restart Horizon Customer. If the ~/Library/Preferences/VMware Horizon View/ folder does not yet be, create the folder by running this command from Final.app:
```
mkdir -p ~/Library/Preferences/VMware\ Horizon\ View
```

Bear upon Bar

You might lose focus for the front window when you use the Touch on Bar to switch between published applications that are hosted on Windows Server 2016. This trouble tin also occur when y'all press Command+~, or click the dock icon, to switch windows. This problem typically just occurs after switching windows several times.

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

Miscellaneous

Changes to webcam and audio devices that are connected to, or disconnected from, the Mac client system during a remote desktop session are not detected past the Real-Time Audio-Video characteristic.

Workaround: Disconnect and reconnect to your remote desktop session to detect webcam and audio device changes. For example, if you connect a USB headset to the Mac client arrangement during a remote desktop session and you want to apply that headset on the remote desktop, y'all must disconnect and reconnect to the remote desktop session to brand the headset available.
If an ambassador edits an application pool in Horizon Console and changes the path to point to a different application that already has an application puddle associated with it, unexpected results can occur. For example, the original application might be launched from the Mac Dock instead of the new awarding.

Workaround: Make sure that each application in a subcontract is associated with simply one application pool.
Users cannot launch an awarding from the Mac Dock if multiple application pools signal to the aforementioned application in ane farm, 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 item, the awarding fails to launch with the associated parameters.

Workaround: Make certain that each awarding in a farm is associated with only i application pool.
Users cannot launch an application from the Mac Dock if multiple application pools betoken to the same awarding 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: Brand sure that each application in a farm is associated with simply one awarding pool.
If yous select the Call up this password check box when you log in to a server, you cannot log in to the aforementioned server as a different user if the credential caching timeout period ( clientCredentialCacheTimeout ) on the server has not yet expired. Horizon Client will automatically use 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 card item), click the Add Server button to add the server once again, and so log in to the server as the different user.
On tardily 2016 MacBook Pro client systems, the response time of Windows Server 2016 hosted remote applications is slow in the get-go few seconds after you launch a Windows Server 2016 application or switch the top window between Horizon Client and the Windows Server 2016 application window.

Workaround: None. This is a third-party result.
If you connect to a remote awarding for which the pre-launch feature is enabled on a Horizon seven version 7.2 server, and the Horizon Client reconnect behavior is set to "Inquire to reconnect to open applications" or "Do not ask to reconnect and do not automatically reconnect," resumed application sessions are disconnected after the pre-launch timeout expires (default x minutes).

Workaround: Fix the Horizon Customer reconnect beliefs to "Reconnect automatically to open applications."
With Moom 3.2.12 (3240), the Moom UI appears when yous hover your mouse over the Close icon, not the maximize icon, in Role 2016 and 2019 apps.

Workaround: None.
Horizon Customer for Mac stops responding if y'all unplug an external graphics processing unit of measurement (GPU).

Workaround: None.
You cannot start a VMware App Volumes application from the Dock on the customer system.

Workaround: Start the application from Horizon Client, or use a shortcut.
The Moom user interface does not piece of work for UWP published applications.

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

Workaround: To regain focus, use your mouse to click on the title bar of the application window.
When the URL Content Redirection feature is configured, Horizon Client presents an alert message that asks you to modify your default spider web browser to VMware Horizon URL Filter for using tertiary-party apps, non including the Chrome and Edge browsers. You lot must click Aye to use the URL Content Redirection feature. In macOS 11 (Big Sur), fifty-fifty when you lot click Yes to the alert bulletin, the VMware Horizon URL Filter user interface is non shown in the default spider web browser of the general option, which means you cannot change the default spider web browser from some other browser to VMware Horizon URL Filter manually, and you must connect to the server again. In macOS ten, the user interface is shown in the default web browser of the general pick. The URL Content Redirection extensions for the Chrome and Edge browsers are not influenced past macOS 11.

Workaround: None. This problem is a third-party issue.
When using Microsoft Teams Optimization Pack with Horizon Customer for Mac or Horizon Client for Linux published applications, screen sharing is not supported.

Workaround: None.