Horizon View 5.2 & Lync 2013 Support – Are You Covered?

I think it’s amazing that VMware and Microsoft are working together to support Horizon View 5.2 and Lync 2013. From my understanding the two companies have only come together since last summer so this is great work at bringing the engineering teams together. The problem though for most enterprises that I see is the deployment of Zero Clients, which is will not supported for Lync 2013 when View 5.2 goes GA.

Lync 2013 features with VMware View desktops

Presence Supported
Instant Message Supported
Desktop Sharing Supported
Application Sharing Supported
PowerPoint Sharing Supported
Whiteboards Supported
File transfer Supported
Online meetings Supported
Office Integration Supported
Audio Supported (with Lync 2010, this used to only be supported via IP-Phone)
Video Supported (with Lync 2010, this was never supported)
Recording audio


You will have to deploy Lync software components on your virtual machines and client devices. So the client devices can only be Windows 7 or Windows 8 devices.

Lync 2013 and View 5.2

Different components of the VMware View and Microsoft Lync 2013 architecture

The Lync VDI plugin that runs on the Windows client needs to be at least have 1.5GHz CPU and minimum of 2GB RAM.

On your Lync Server 2013, ensure that EnableMediaRedirection is set to TRUE for all VDI users. As part of the Lync Server setup, make sure you generate a certificate and add this certificate to their Windows Client Machine. The certificate will need to be placed in the “Trusted Root Certificate Authorities” directory. The Lync VDI 2013 plugin will not pair up with the Lync 2013 client running inside the remote desktop if this step is not completed. You may also have to place a host file on the endpoint if the endpoint is not on the same domain as the Lync Server.

It’s also good point out you want to make sure the USB headsets and WebCams are not redirected to the VM. You want the traffic to go between the clients via the plugin.

Overall the Lync 2013 support is great but just make sure you know that zero clients are still not covered. Zero clients will still suffer from hair-pinning traffic in the datacenter and not get the benefits of WAN optimization for Voice traffic. Zero Clients can still work you just really need to nail down the Network Best Practices for PCoIP. Other clients will be added but it appears the ball is in Microsoft court. Microsoft still needs to provides it’s components to the other clients but Zero client support seem away down the road.