Administrator Guide

• ThinOS uses the VMware binary. For information about the Skype for Business limitations, see the Configuring Skype for Business
document at docs.vmware.com.
Known issues
Table 18. Known issues
Description Workaround
If the Blast session resolution is higher than 1920 x 1080 during SFB calls
with full screen, the mouse stops responding.
Do not use full screen during SFB calls in the blast session
with resolution greater than or equal to 2560 x 1440.
After you install the JVDI package, the Trap 14 error occurs if you switch
the playback device from HD audio to DP audio during the Horizon SFB call.
Do not load the JVDI package if you want to use only the
Horizon package.
You cannot use the key on the headset to pick up or end a call. There is no workaround in this release.
Optimized mode and Fallback mode
In Optimized mode, the Skype for Business delivers an optimal performance. In Fallback mode, the Skype For Business calls are not
optimized. On the lower right of the virtual desktop, the tooltip of the Virtualization Pack icon indicates the VMware Horizon Virtualization
Pack for Skype for Business mode.
The following screenshot displays the Virtualization pack for Skype for Business in Optimized mode:
Figure 19. Optimized mode
If the Optimized mode icon is not displayed, the Virtualization Pack is running in Fallback mode. This is because of the version mismatch
between the Horizon Client on the thin client and the Horizon Agent on virtual desktop.
For information about compatibility of Horizon Virtualization Pack for SFB components, see the Horizon Client 4.8 or later and Agent 7.5
or later Virtualization Pack for Skype for Business is not compatible with older Client and Agent releases article at kb.vmware.com.
Change Optimized mode to Fallback mode
To change the Optimized mode to Fallback mode, or to disable the Virtualization pack for Skype for Business on the Horizon desktop, do
the following:
1. On the VMware Horizon desktop, open the Windows Registry Editor.
2. Rename the registry keys based on the following deployment scenarios:
Table 19. Registry keys
Deployment scenario Registry key
View Desktops (64-bit) with Skype for Business (64-bit) Rename HKLM/Software/Microsoft/Office/Lync/
VdiMediaProvider to HKLM/Software/Microsoft/
Office/Lync/VdiMediaProviderDisabled.
View Desktops (64-bit) with Skype for Business (32-bit) Rename HKLM/Software/Wow6432Node/Microsoft/
Office/Lync/VdiMediaProvider to HKLM/Software/
Wow6432Node/Microsoft/Office/Lync/
VdiMediaProviderDisabled.
View Desktops (32-bit) with Skype for Business (32-bit) Rename HKLM/Software/Microsoft/Office/Lync/
VdiMediaProvider to HKLM/Software/Microsoft/
Office/Lync/VdiMediaProviderDisabled.
3. Close the Windows Registry Editor.
Configuring the connection brokers
87