The Lync VDI plug-in was not pairing with the VM workstation. I had the correct version of Office 2013, bit-levelwise went through everything with a fine tooth comb. "Bitness" as some documentation calls it is very important for Lync VDI with VMware Horizon View
. Pay special attention to the chart on page 7 of this document
I found that if I removed the VMware Horizon View Agent component on the virtual machine along with removing any VMware registry key folders in HKLM and reinstalled with the components that are outlined in the documentation (PCoIP Server and Virtual Printer), the pairing process worked without any issue.
After digging some more my client used a batch script to install the agent and called a custom registry file. The command to install the agent was as follows:
VMware-viewagent.5.2.exe /s /v ADDLOCAL=Core,USB,PCoIP,VmVideo,VmwVaudio,Appblast /qn REBOOT=ReallySuppress
When looking at the options, I discovered that ThinPrint which installs the Virtual Printer component was missing. Along with this the “pcoip.enable_vchan"=dword:00000001 key was missing from the custom registry file that was used to set the VMware Horizon View agent as part of their virtual workstation provisioning process.
Once these items where set, then all was well.
Other important documentation:
Deploying the Lync VDI Plug-in
Lync 2013 Virtual Desktop Infrastructure (VDI) Client scenarios