Hi All,
Sorry for the delay in posting this info.
We have been able to successfully get the VDI 32-bit Plugin to work on Windows 7-64 bit, Windows 7 32-bit, and Windows 2008 R2 VMs. Also, we have gotten it to work via RDP and PCoIP thru the VMware Horizon View app.
However…
My findings contradict the VMware documentation on Lync VDI.
- Internal/External Lync certificates are not required to be installed on the VM or the client in order to get the VDI plugin to work.
- Bit-ness also has no bearing when using the View Client. We used the following clients in our test: Windows 7 SP1 64-bit, 32-bit, and Windows 8 64-bit. Some had Office 2013 installed, others had no version of Office at all.
- Running the Lync Metro App on the client PC does not prevent Lync VDI from working
- When a successful VDI connection occurs, the user is prompted for their Lync credentials. Once successfully entered, a registry key is created on the client PC in the following location:
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\LyncVdiPlugin
This key will contain a subfolder with your Lync sign-on name, and a sub-folder with all of the Lync Autodiscover records. This is ONLY created once a successful connection between the VDI plugin and the VM Lync Client occurs. Manually entering in this information will not help (we tried in our testing).
5. Biggest issue: If the Lync Desktop client is installed on your client PC (i.e Lync Client that comes with Office 2013), you will NOT be able to pair the VDI plugin with the VM Lync client. No way, no how.