Lync 2013 Virtual Desktop Infrastructure (VDI) Wont Pair WIth Non-Domain Thin Client

Domain joined HP t610: pairing works great

Non-domain joined HPt610: pairing never succeeds or fails, but remains in a try to connect to local device state

I've read a couple of posts about this issue, but I don't think there was a clear answer to the root cause of the issue.  Any help on how to fix this would be greatly appreciated since all our thin clients are not joined to the domain.

November 22nd, 2013 1:58pm

Does your domain and non-domain joined devices use the same DNS servers? Does the non-domain joined device trust your CA that issued certificates to the Lync servers?

Have you tired entering the Lync Servers fqdn into the host file of the non-domain joined device? Also confirm the date, time, timezone is correct on the Thinclient.

Free Windows Admin Tool Kit Click here and download it now
November 22nd, 2013 3:01pm

Does your domain and non-domain joined devices use the same DNS servers? Does the non-domain joined device trust your CA that issued certificates to the Lync servers?

Have you tired entering the Lync Servers fqdn into the host file of the non-domain joined device? Also confirm the date, time, timezone is correct on the Thinclient.

November 22nd, 2013 10:55pm

Does your domain and non-domain joined devices use the same DNS servers? Does the non-domain joined device trust your CA that issued certificates to the Lync servers?

Have you tired entering the Lync Servers fqdn into the host file of the non-domain joined device? Also confirm the date, time, timezone is correct on the Thinclient.

  • Marked as answer by olivesandtrees Monday, November 25, 2013 7:29 PM
Free Windows Admin Tool Kit Click here and download it now
November 22nd, 2013 10:55pm

Does your domain and non-domain joined devices use the same DNS servers? Does the non-domain joined device trust your CA that issued certificates to the Lync servers?

Have you tired entering the Lync Servers fqdn into the host file of the non-domain joined device? Also confirm the date, time, timezone is correct on the Thinclient.

  • Marked as answer by olivesandtrees Monday, November 25, 2013 7:29 PM
November 22nd, 2013 10:55pm

Adding our local CA to the non-domain machines fixed the issue.  I didn't try this right off the bat because our Lync certs were generated from GoDaddy, but thinking about it a bit more internal Lync clients use a different URL than external clients and that hostname was not included in the cert's SAN.

Free Windows Admin Tool Kit Click here and download it now
November 25th, 2013 2:32pm

Hi,

For your reference, here are other tips for Lync in a Virtual Desktop Infrastructure (VDI) environment:

http://office.microsoft.com/en-us/lync-help/faqs-for-lync-in-a-virtual-desktop-infrastructure-vdi-environment-HA103465485.aspx

November 28th, 2013 10:07pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics