In my previous post, I mentioned that Microsoft and Citrix now support Audio/Video with Lync Server 2013 backend. This blog shows how to configure the backe and and deploy the clients.
Make sure you have XenApp 6.x (or higher) deployed.
On the backend, we need to define a clientpolicy (http://technet.microsoft.com/en-us/library/jj205204.aspx) to allow Media redirection. This can be done using the following command:
Set-CsClientPolicy -EnableMediaRedirection $True
- Download and install the Citrix 4.0 receiver (or higher) from http://receiver.citrix.com/
Download the VDI plugin from one of the following locations:
- 32bit: http://www.microsoft.com/en-us/download/details.aspx?id=35457
- 64bit: http://www.microsoft.com/en-us/download/details.aspx?id=35454
Remark: The 64 plugin is not supported by Citrix, so currently only for Microsoft VDI solutions.
Install the VDI plugin on a (thin) client, e.g. Wyse Zx0 (now owned by Dell) or laptop.
Optional… Create a registry key (based on http://support.microsoft.com/kb/2833618), as we’ve experienced that the VDI plugin doesn’t prompt for certificate warnings….
Value: ActiveDirectoryDomainFQDN (e.g. internal.local)
Logon to the XenApp desktop (using weburl or ICA)
Once you are signed in into your Lync client, you will notice the following:
- This means that Lync is configured correct and you can benefit the bypass of Audio/Video (Call Admission Control and Location Information Services).
There are some limitations, described here: http://technet.microsoft.com/en-us/library/jj204982.aspx. This basically comes down to that all peer to peer A/V features are available. Multiparty and more enhanced isn’t (example shown below)
If you have any questions or want to have it deployed… feel free to contact me.