Apply to the agent side (VM) via GPO or Local Policy: In Computer ConfigurationAdministrative TemplatesSystemDevice InstallationDevice Installation Restrictions, find the following policy and add the Device IDs below.Mobile Apps VMUG Mobile Apps VMUG Top Forums: vSphere NSX vSAN vCenter Fusion Horizon Workspace ONE vRealize Automation Workstation Skyline VMCloudOnAWS Error: You dont have JavaScript enabled.
This tool uses JavaScript and much of it will not work correctly without it enabled. USB Redirection was the only option available and the audio was very bandwidth inefficient. Unfortunately it was required in order for the Message Key to function. The keyboard also had a maximum latency of 25ms between Client and VM, at which point the audio would start stuttering. This configuration splits the Bloomberg Keyboard Audio device so that the audio is handled via PCoIP Audio Redirection while the Message Key functions via USB Redirection. ![]() It also allows the keyboard to be fully functional up to 75ms latency between Client and VM, at which point the fingerprint reader becomes slow enough that it is difficult to get a fingerprint read before the Bloomberg App times out waiting for it. Bloomberg Keyboard Driver On TheBloomberg Keyboard Windows 7 SP1 VMTested Configuration This configuration should work with Bloomberg Keyboards and Horizon View 5.1 or higher, however I only tested this on the following: Horizon View Connection Manager 5.2 Horizon View Client 5.3 Horizon View Agent 5.2.1 Bloomberg Keyboard FRE100 Windows 7 SP1 VM Windows Embedded Standard Client Windows Embedded Standard 7 Client How to Configure Install the Bloomberg Keyboard Driver on the client and confirm the keyboard is functional from the client side. Add the VMware View Client Configuration ADM Template to the client. In Administrative Templates for VMware View Client ConfigurationView USB Configuration: Split VidPid Device Enabled Add vid-1188pid-03ef(exintf:00;exintf:01;exintf:02) This splits the Bloomberg Keyboard Audio device. ![]() Audio, 01Audio Out, 02 Audio In, 03HID Device (Message Key). We want to exclude all three audio interfaces so they are handled by PCoIP and redirect only interface 03 (the Message Key) via USB Redirection. ![]() Add Registry Key to Client: HKLMSoftwarePoliciesVMware, Inc.VMware VDMClientUSB AllowDevDescFailsafe REGSZ True This allows devices to be redirected even if the View client fails to get the configdevice descriptors. This happens with the Bloomberg Keyboard and this key must be set for it to be redirected. Insure that Bloomberg Keyboard Audio is the default audio device on the client. Temporary workaround for VMware Bloomberg bugs that causes the Message Key to be unresponsive At the time of this writing this configuration is impacted by VMware Bloomberg bugs which can cause the Message Key to fail. When the Bloomberg Keyboard Audio device is split and excluded from redirection, the excluded audio interfaces still appear in the VMs Device Manager and they appear as HID devices instead of Audio Devices. This confuses the Bloomberg App and the Bloomberg App listens to the wrong HID interface for the Message Key causing the key to be unresponsive. Bloomberg Keyboard Software Update EitherBloomberg has a fix for this issue which they will incorporate into their monthly software update either in June or July 2013. Until then, applying the following GPO to the VM will block the keyboards audio interfaces from loading if they present themselves as HID devices when the device is split. This will cause the Bloomberg App to link to the correct interface the next time it is launched. This policy does not impede the Bloomberg Keyboard when it is locally connected or if it is redirected entirely via USB Redirection since the audio interfaces correctly present themselves as an Audio Device in these cases.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |