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.
For all non-media related functionality, such as presence, instant messaging and right-click to chat, the Microsoft Lync 2013 client performs all the functionality within the Horizon View desktop and acts just as another desktop application. For Lync 2013 client functionality that includes real-time media, such as VoIP and Video Chat, the Lync VDI plugin running on the client endpoint performs all the media processing, to offload the workload from the servers hosting the desktop VMs.
In order to enable this critical media offload functionality VMware created the following functions.
- VMware implemented a Microsoft dynamic virtual channel (DVC) to allow communications between the virtual machine and the client endpoint.
- The Microsoft Lync 2013 client running inside a Horizon View desktop uses the DVC to communicate and establish a connection with the Lync VDI plugin (running on the client endpoint).
- If the handshake between the Lync 2013 client and the Lync VDI plugin is successful, a popup window appears on the client endpoint running the VDI plugin.
- The user is asked to enter “Sign-in address” and password for the Lync VDI plugin (the username/password combo is the same as the credentials for the Lync 2013 client).
Before going ahead it is important to highlight the support matrix for the Lync VDI plugin with different client devices. The Lync VDI plugin is only supported with Windows clients at this time.
- VMware only supports the Lync VDI plugin when used with the PCoIP protocol. The Lync VDI plugin may function with RDP 8, however it has not been tested end to end with Horizon View desktops.
- Only the 32-bit version of the Lync VDI plugin can be used with Horizon View clients. The reason for this is because even though there are both 32-bit and 64-bit versions of the View client, the PCoIP client process running on the client is a 32-bit process.
- The Lync 2013 Client installed on the virtual desktop must match the Agent Bit-level. e.g. 32-bit Lync Client must be installed on a 32-bit Agent machine.
Configuration on Windows Client Endpoint
In order to enable the Lync VDI plugin to pair up with the Lync client, the end-user or administrator has to configure registry settings on the Windows client endpoint. Configure the following registry settings on the Windows client machine.
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\15.0\Lync] "ConfigurationMode"=dword:00000001" "ServerAddressInternal"="lyncsrv2013.lync.local" "ServerAddressExternal"="Access.lync.local"
Under the “ServerAddressInternal” and “ServerAddressExternal” fields only use the hostname for the respective servers. MIcrosoft does not recommend and support the use of IP addresses in the server fields.
The Pairing Process
1. Launch Horizon View Desktop
2. The Microsoft Lync 2013 Client will start on View Desktop and login to Lync Client
3. After successful login to Lync client, pairing icon will look like this (lower right corner of Lync client):
4. Pop up window appears (it may take 1-2 minutes for it to appear):
5. Enter login information
6. If pairing is successful a green checkmark will be displayed: (after login, it may take up to 3 minutes to pair)
7. If pairing is not successful a red X will be displayed (after 3 attempts):
I would like to acknowledge the help from my colleague Tony Huynh helping me out to put together this content. In my next post about Lync 2013 I will provide troubleshooting guidelines.
This article was first published by Andre Leibovici (@andreleibovici) at myvirtualcloud.net.