How It Works – Microsoft Lync 2013 with View Integration

Lync2013-1Horizon View 5.2 provides Microsoft Lync 2013 client support, including full support for UC VoIP and Video on both RDP and PCoIP. This new feature enable a tighter integration between Microsoft Lync and Office applications with full collaboration capabilities.

Microsoft Lync 2013 client is a Unified Communications (UC) application that is installed on a desktop.  Microsoft Lync client is used for presence, instant messaging (IM) and other functions, such as placing a Voice over Internet Protocol (VoIP) or Video chat call.

In order to enable the Lync 2013 client to pair up with the Lync VDI plugin running on the client endpoint, VMware implemented Microsoft’s dynamic virtual channels (DVC) inside PCoIP. The Microsoft DVC provides a communications path between the virtual machine (VM) and the client endpoint, and the Lync 2013 client uses the DVCs to communicate with the Lync VDI plugin running on the client endpoint. The graph bellow depicts how the solution is architected.


Screen Shot 2013-03-28 at 7.27.24 AM


Using Horizon View 5.2 and Microsoft Lync 2013 together will enable the following features to be used:


  • Presence
  • Instant Messaging
  • Desktop Sharing
  • Application Sharing/PowerPoint sharing
  • Whiteboards
  • File Transfers
  • Online Meetings
    • Communication modes for Online Meetings are limited by peer-to-peer communication modes.  For example, if audio is not supported on the specified architecture, audio will not work in Online Meetings.
    • Joining online meetings from Microsoft Outlook meeting reminder and/or meeting invitation is not supported.
  • Office Integration
  • VoIP
    • Audio is supported only in a VDI environment. Audio is not supported in a session-based desktop delivery environment such as Microsoft RDS.
  • Video Chat
    • Multi-party video chat is not supported.


The solution works with Windows 7, Windows 8, Windows Embedded and Windows Thin PC. Before using Lync 2013 administrators must ensure that the client hardware meet the following specifications: CPU 1.5GHz, at least 2GB RAM and 4GB total storage.


Software Components Description
Microsoft Lync 2013 Server Components Backend server that the Microsoft Lync clients register with.
Microsoft Lync 2013 client

Microsoft Lync 2013 client application that is installed in VM.

Microsoft Lync VDI plugin The Lync VDI plugin is installed on the client machine.  Lync VDI plugin that pairs with Lync 2013 client in VM.  Once Lync VDI plugin is paired with Lync 2013 client, all media processing is automatically redirected to the client device.
View 5.2 (Agent and Client)

Need to use the View 5.2 agent and corresponding View 5.2 client

VM Operating System

Supported on Windows 7 VMs only with Service Pack 1.

Client Operating System

Supported on Windows 7 and Windows 8 client OS.  Please note that Windows 8 clients is only offered in Tech Preview.


There are also some additional restrictions to be observed:

  • PCoIP process running on the View client (32 & 64-bit) only operates in 32-bit mode.  Therefore only the 32-bit version of the Lync VDI 2013 plugin is supported.
  • Client Machine – the 32-bit version of the Microsoft Lync VDI 2013 plugin will not work from a machine that has the 64-bit version of Office 2013. This is unsupported by Microsoft.
  • RDP 8 is not supported.


I would like to acknowledge here the excellent work from Tony Huynh and his team to get these functionalities working. In my next post about Lync 2013 I will go a little deeper and explain how the communication works under the covers and provide some troubleshooting guidelines.


This article was first published by Andre Leibovici (@andreleibovici) at


1 ping

Skip to comment form

    • Dan Garcia on 03/28/2013 at 8:40 am

    Between User A and B it would appear there needs to be a “line of sight” for the AV/Media communication. The smae is true for User A and the Lync 2013 servers for the signaling. That’s fairly straight forward. My question is around a remote user, say User A is at home using the PCoIP Security Gateway. Is there a supported configuration with Lync Edge Servers that will enable User A (remote user w/ Security Gateway) to talk with User B (located inside the corporate network)? Or is a full VPN required to enable the “line of sight” for the communication?

    • Tony Huynh on 03/28/2013 at 9:00 am

    Hi Dan,

    The scenario that you mentioned with a remote user is supported when using a Microsoft Lync Edge server. In this case, the User A (at home) is connecting to their View desktop through the PCoIP security gateway. User A’s lync vdi plugin will be able to pair up with the Lync client running inside their View desktop, and all Lync VDI media traffic will be sent through the Lync Edge server.


    • Dan Garcia on 03/28/2013 at 10:39 am

    That’s great to hear. Thanks for clarifying and great work on the integration.

    • Anon on 03/31/2013 at 6:49 am

    I think you need version 5.3 of the View Client.

    • Aditya Kumar on 07/31/2013 at 5:56 am

    I appriciate your great help to capture this. It shows thin os or Linux base thin client or zero client will not work for lync 2013 and vmware view / Xendesktop / Microsoft environment

    • Aquiline George Neville on 10/27/2013 at 12:44 am

    Hi Dan,
    I am using ur guidelines and testing Lync 2013 with VMware View desktop 5.2. Unfortunately I am not able to get the solution working. I have crossed phase one in which the secondary logon screen comes but when I see it still states that its looking for audio or video device. I am also using a Microsoft lync supported LX 4000 headset and HD 3000 web cam but when i try to test I get just a noise and I am connected to the desktops through a VPN (SonicWall Netxender). Please advise.

    • Indrajith on 02/05/2014 at 9:46 am

    I have followed all the steps provided above and installed the Lync 2013 VDI client. I havent got the Lync 2013 client paired up with Lync 2013 plugin. how can i get the logs regarding this issue? please help me if i have to look into any other step

  1. […] Following up on the announcement for Microsoft Lync 2013 with Horizon View support I have been asked to cover a little bit more on how to stand up and troubleshoot the solution. If you are not yet familiar with the solution make sure you read my article How It Works – Microsoft Lync 2013 with View Integration. […]

Leave a Reply