O Always use Receiver for HTML5 Select Use Receiver for HTML5 if local install fails Step2: Enable ICA WebSockets connections policy in Citrix Studio (i.e. On your XenDesktop and XenApp servers) Once the configuration on the Citrix Studio end is complete, follow the below steps to enable WebSockets policies using the Citrix Studio management. In our environment, we are using the Citrix XenApp Plugin for Hosted Apps on our PC's for the end users to access various apps hosted on our Citrix farm. We now have the need to find a similair app for all the Mac's on our network. I couldn't locate a Citrix XenApp plugin for Hosted Apps for Mac, but I did find a Citrix Receiver for Mac. Citrix Virtual Apps, formerly XenApp, fits the enterprise need to bring legacy apps into a cloud management environment. This article describes how to configure the default device access behavior of Receiver, XenDesktop and XenApp. In XenApp and XenDesktop 7.6 FP3, the Client USB device optimization rules can be applied to devices to disable generic usb optimization for interrupt devices, or to change the optimization mode. When a user plugs in a USB input device, the host checks if the device is allowed by the USB policy settings. Download Citrix Workspace App, Citrix ADC and all other Citrix workspace and networking products. Receive version updates, utilities and detailed tech information.
XenDesktop VDI Virtual Delivery Agent 7.1
(Citrix recommends the 7.6.3 Long-Term Service Release or the latest 7.x Current Release)Citrix Receiver 4.1.02 for Windows
(Citrix recommends the latest 4.x release)Virtual desktop OS: Windows 7 with Service Pack 1
Endpoint OS: Windows 7 with Service Pack 1 or Windows Embedded Standard 7 with Service Pack 1
On XenApp 7.1/7.5 and XenDesktop 7.1/7.5, Citrix recommends applying hotfix ICAWS750WX64029 (not required with XenApp/XenDesktop 7.6 or above). For the list of issues resolved in this hotfix, refer to CTX140257 - Hotfix ICAWS750WX64029 - For VDA Core Services 7.1/7.5 for Windows Desktop OS (64-bit) - English.
For optimized delivery of the Skype/Lync client to Mac and Linux devices, see HDX RealTime Optimization Pack.
System Requirements
Per Microsoft TechNet article jj205304, “The [VDI Plug-in] user must be homed on Lync Server 2013”. Skype for Business Server 2015 is not listed as a supported platform. Likewise, Office 365 / Skype for Business Online is not listed. Furthermore, Citrix has no plans to test the VDI Plug-in solution with Skype for Business Server 2015 or Office 365 / Skype for Business Online.
Lync Server 2013 must be configured with EnableMediaRedirection set to True.
32-bit Microsoft VDI Plug-in installed on a Windows device running a supported version of Windows; for Microsoft VDI Plug-in installation requirements see Lync VDI Plug-in Prerequisites. Citrix Receiver for Windows requires the 32-bit version of the Microsoft VDI Plug-in on the device, even on a 64-bit Windows machine. The 64-bit version is not compatible with Citrix Receiver for Windows since the bitness of the VDI Plug-in must match the bitness of Receiver.
A Skype for Business / Lync Server certificate installed on the user device as well as on the XenApp/XenDesktop server.
Note: If Microsoft Office is to be installed locally on the device, you must use the 32-bit version of Office
Instructions
To Install the Microsoft VDI Plug-in
Download the latest release of Citrix Receiver 4.x for Windows and install on the user device.
Download the Microsoft VDI Plug-in (32-bit) from the Microsoft Download Center.
Install the VDI Plug-in on the device. See Deploying the Lync VDI Plug-in.
Note: Be sure to install the latest Microsoft updates.Install the Skype/Lync Server certificate on the device.
To Validate the Configuration of Skype for Business / Lync
The recommended best practice is to use the Microsoft RDP client first to validate your Skype for Business / Lync configuration independent of any Citrix software, and then switch to Citrix Receiver. When you validate your configuration with the Microsoft RDP client, the bit version of the Microsoft Lync VDI Plug-in must match that of the RDP client and the Windows operating system, as described in Lync VDI Plug-in Prerequisites.
If you perform verification on a 64-bit Windows OS, substitute the 32-bit version of the Microsoft VDI Plug-in when you switch from RDP to ICA and the Citrix Receiver for Windows.
To validate proper pairing of the VDI Plug-in
When Skype/Lync and the VDI Plug-in have paired correctly, the icon under the Contacts list includes a green checkbox and the Audio Device settings appear as displayed in the following screen shot:
As noted on the above screen, audio device tuning is not supported when using the VDI Plug-in.
Troubleshooting Methodology
Issues Pairing the Skype/Lync client with the VDI Plug-in
When Skype/Lync and the VDI Plug-in are not paired correctly, then the icon under the Contacts list does not include the green checkbox and the Audio Device settings show the remote devices as displayed in the following screen shot:
In case of issues pairing the Microsoft Skype for Business / Lync client with the VDI Plug-in:
Look for DHCP errors as these can cause connectivity between the Skype for Business / Lync client and the VDI Plug-in to become intermittent, with frequent disconnects.
Restart the device.
Make sure the endpoint OS is 32-bit and has the 32-bit VDI plug-in installed, not the 64-bit version.
Make sure there is an exception on the Windows firewall for the Lync ports (or disable the firewall). Do this on both the endpoint and VDA. The list of ports used by Lync is here: http://technet.microsoft.com/en-us/library/gg398833.aspx. Ensure that any routers between the endpoints, VDAs and Lync server aren’t blocking the port; the endpoints and VDAs both need to be able to reach the Lync server.
Ensure that the EnableMediaRedirection policy is set to True on the Lync server (see http://technet.microsoft.com/en-us/library/jj205154.aspx).
Make sure that the latest Skype/Lync updates from Microsoft have been installed.
The file version for c:Program FilesMicrosoft OfficeOffice15LyncVdiPlugin.dll on the endpoint must be at least 15.0.4517.1504
The file version for c:Program FilesMicrosoft OfficeOffice15Lync.exe on the VDA must be at least 15.0.4517.1504
Ensure that an audio/video device is plugged into the endpoint.
After establishing a connection to the VDA, use a tool such as Process Explorer to verify that LyncVdiPlugin.dll is loaded by the wfica32.exe process. Process Explorer can be found here: http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx. To check if the DLL is loaded, on the menu, go to Find, then Find Handle or DLL.
For more information about troubleshooting the Microsoft VDI Plug-in, see Troubleshooting the Lync VDI Plug-in.
Log Locations
To capture log files, complete the following:
In the main Skype/Lync window, go to Tools > Options > General.
For Logging, choose Full.
Select the checkbox for Also turn on Windows Event logging to collect troubleshooting information.
Collect the logs from the following locations:
On the Lync Server: %localappdata%MicrosoftOffice15.0LyncTracing
On the device: %localappdata%MicrosoftOffice15.0LyncTracing
To capture logs for the Virtual Delivery Agent (VDA), complete the following:
Use CTX130147 - Citrix Scout to run a CDF trace with XenApp/XenDesktop 7.x. The relevant trace modules for the VDA are:
MF_DLL_CtxDvcApi
MF_Driver_CtxDVC
MF_Driver_Wdica
Upload the trace file to Citrix Insight Services (a.k.a. Tools-as-a-Service).
Review the trace on the Citrix Insight Services site.
Known Issues and Workarounds
Issue: When right-clicking on a voice message in and selecting Play, the message cannot be heard.
Workaround: Double-click on the voice message or click on the View More in Outlook link to open the voice message in Outlook; this enables the message to be heard through the speakers on the user device.
Alternatively, if you select this icon and choose Call Voice Mail, you can listen to the voice message through your USB headset.
Third-party Issues
Check directly with Microsoft for updates regarding the following issues:
When a call starts, the audio volume on the device is reduced. Use the device audio controls to increase the volume.
Camera is activated when user hovers mouse over the video preview if camera is present on the 'server side' (host) computer (physically or virtually). Preview is shown, despite text on the screen that says video preview is not supported. Video fails to start for the rest of the call if the video preview was shown. The issue does not occur if a video call is started by right clicking a contact and selecting “Make video call” or by using the Meet Now dialog. This issue is caused by the fact that Skype/Lync, when paired with the VDI plug-in, still loads any webcam devices present on the [virtual] desktop. Therefore, the virtual webcam device provided by generic HDX Webcam Video Compression is loaded, locking the webcam and preventing Skype/Lync from using it. A possible workaround is to disable generic HDX Webcam Video Compression, which is turned on by default. This can be accomplished by configuring a policy on the Desktop Delivery Controller (DDC). The policy is under Multimedia Settings and is called “Multimedia Conferencing”. It is a machine-wide policy. The drawback to disabling generic HDX Webcam Video Compression is that users of other video conferencing applications, such as Citrix GoToMeeting, or users who do not have the VDI plug-in installed, will not be able to use their webcam in a XenApp/XenDesktop session.
For feature limitations of the VDI Plug-in, refer to Known Limitations for VDI on the Microsoft TechNet site. The VDI Plug-in is not supported on Windows Thin PC, Windows XPe, WES 2009 or Windows Server 2012 [R2]. The VDI Plug-in does not support smart card authentication and users must enter their credentials manually if their device is not domain-joined. And the VDI Plug-in solution does not support delivery of the Skype/Lync client as a seamless/published application.
Additional Resources
Disclaimer