Pairing of Lync/Skype4Business randomly stops working in a VMware VDI Environment

%3CLINGO-SUB%20id%3D%22lingo-sub-21780%22%20slang%3D%22en-US%22%3EPairing%20of%20Lync%2FSkype4Business%20randomly%20stops%20working%20in%20a%20VMware%20VDI%20Environment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-21780%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20our%20company%2C%20we%20have%20a%20major%20issue%20with%20Lync%2FSkype4Business%20in%20a%20VmWare%20VDI%20Environment!%3C%2FP%3E%3CP%3EWith%20Lync%20VDI%20Plugin%20installed%20on%20Physical%20Computer%20the%20pairing%20randomly%20stops%20or%20can%20just%20never%20being%20done%2C%20until%20the%20reboot%20of%20the%20physical%20computer.%20It%E2%80%99s%20only%20after%20this%20operation%20that%20the%20pairing%20functions%2C%20if%20we%20are%20lucky.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20the%20Pairing%20is%20working%20there%20is%20a%20little%20green%20dot%20at%20the%20right%20bottom%20of%20the%20Lync%20client%20(see%20attachement)%3C%2FP%3E%3CP%3EIf%20the%20Pairing%20is%20not%20Working%20there%20is%20no%20little%20green%20dot%20and%20the%20trouble%20begins.%3C%2FP%3E%3CP%3EThere%20is%20NO%20sound%2C%20No%20Mic%20on%20the%20headset%20and%20eventually%20if%20it's%20a%20notebook%2C%20the%20Mic%20and%20Speakers%20take%20the%20relay%20giving%20a%20really%20bad%20quality%20and%20echo%20for%20the%20caller.%3C%2FP%3E%3CP%3EOutside%20of%20our%20Network%20company%20the%20VDI%20environment%20is%20accessible%2C%20but%20the%20Pairing%20can%20never%20be%20made.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20impacting%20all%20our%20users%20randomly%20and%20the%20confidence%20is%20somehow%20being%20lost%20with%20the%20product.%3C%2FP%3E%3CP%3EEverything%20was%20functioning%20pretty%20well%20with%20Lync%20when%20it%20was%20first%20installed%20on%20all%20our%20computers.%3C%2FP%3E%3CP%3EAnd%20it%20stills%20works%20fine%20on%20our%20physical%20computers%20But%20since%20the%20beginning%20of%20the%20year%2C%20we%20have%20been%20migrating%20all%20our%20company%20into%20a%20VMware%20VDI%20Horizon%20environment.%20The%20Problem%20has%20begun%20to%20happen.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20to%20clarify%20We%20have%20already%20opened%20a%20Microsoft%20Ticket%20incident.%3C%2FP%3E%3CP%3EThe%20MS%20engineers%20have%20already%20been%20working%20more%20than%2030%20hours%20without%20success%20so%20far.%3C%2FP%3E%3CP%3EThe%20problem%20has%20been%20escalated%20to%20the%20highest%20level%20in%20MS%20Support%20or%20at%20least%20we%20have%20been%20told%20so.%3C%2FP%3E%3CP%3EUntil%20now%2C%20we%20have%20provided%20MS%20at%20multiple%20times%20a%20lot%20of%20Lync%20logs%20and%20network%20captures%20and%20have%20seen%20no%20real%20solution%20until%20today!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20I%20give%20you%20some%20details%20about%20our%20Infrastructure%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20VDI%20Environment%20that%20is%20not%20Citrix%20but%20WMWare%20!%3C%2FP%3E%3CP%3EThe%20VMware%20VCenter%206.0.0%2C%202776511%20(is%20configured%20to%20work%20in%20conjunction%20with%20Unidesk%20and%20Norskale%20for%20confort%20in%20creation%20of%20Software%20Layers%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20multisite%20Network%20all%20routed%20through%20MPLS%20Links%3C%2FP%3E%3CP%3EThe%20Physical%20sites%20are%20all%20in%20private%20ranges%20192.168.xxx.yyy%3C%2FP%3E%3CP%3EThe%20Datacenter%20Hosting%20the%20VDI%20infrastructure%20is%20located%20on%20a%20Network%20Range%20172.16.16.xxx%3C%2FP%3E%3CP%3EAll%20the%20traffic%20is%20routed%20correctly%20for%20all%20the%20different%20ranges.%20And%20When%20it%20was%20only%20on%20physical%20computers%20we%20never%20had%20problems.%3C%2FP%3E%3CP%3EThe%20Lync%20Server%20is%20version%202013%20ans%20is%20hosted%20on%20Premises.%20We%20mainly%20use%20enterprise%20Licensing%3C%2FP%3E%3CP%3E3%20Frontends%20load%20balanced%20with%20a%20Netscaler%201WAC%202%20Edges.%3C%2FP%3E%3CP%3EThe%20Lync%20Infrastructure%20has%20been%20checked%20by%20an%20expert%20and%20has%20been%20proven%20to%20be%20correctly%20configured.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20we%20are%20using%20VMWare%20Horizon%20Clients%20to%20connect%20to%20our%20VDI%20environment.%3C%2FP%3E%3CP%3EOn%20the%20Physical%20Computers%20the%20Microsoft%20Lync%20VDI%20Plugin%202013%20(15.0.4569.1506)%20is%20installed.%3C%2FP%3E%3CP%3EAll%20Microsoft%20updates%20have%20been%20done%20and%20system%20is%20uptodate.%3C%2FP%3E%3CP%3EOn%20the%20VDI%20environment%20Microsoft%202013%20(15.0.4849.100%20and%20MSO%2015.0.4849.1000)%20is%20installed%3C%2FP%3E%3CP%3EEven%20when%20these%20were%20the%20last%20versions%2C%20the%20problem%20occurred%20so%E2%80%A6%20I%20think%20it%E2%80%99s%20something%20else%20than%20just%20upgrade%20to%20the%20last%20version%3C%2FP%3E%3CP%3EVMWare%20environment%20(running%20version%206)%20is%20certified%20by%20Microsoft%20for%20running%20Lync%202013%20in%20VDI.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20can%20provide%20more%20details%20on%20request%E2%80%A6.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBy%20Opening%20this%20thread%2C%20we%20wanted%20to%20know%20if%3A%3C%2FP%3E%3CP%3ESomeone%20else%20has%20been%20experiencing%20the%20same%20behaviour%20%3F%3C%2FP%3E%3CP%3EDid%20you%20manage%20to%20solve%20this%20Issue%20%3F%3C%2FP%3E%3CP%3EIf%20Yes%20How%20%3F%3C%2FP%3E%3CP%3EIf%20NO%2C%20what%20was%20the%20workaround%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20comments%20or%20ideas%20that%20might%20give%20us%20some%20new%20leads%20for%20resolving%20this%20issue%20are%20welcome%20!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20all%20for%20your%20help%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EChristian%20VEGA%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-21780%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EClient%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeployment%20%26amp%3B%20Operations%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EVoice%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-22822%22%20slang%3D%22en-US%22%3ERe%3A%20Pairing%20of%20Lync%2FSkype4Business%20randomly%20stops%20working%20in%20a%20VMware%20VDI%20Environment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-22822%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Christian%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20also%20been%20having%20pairing%20problems%20in%20our%20VMWare%20VDI%20environment%20since%20we%20started%20using%20it%20last%20year.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20VMWare%20View%20environment%20is%20version%206.1.4%20and%20local%20client%206.1.2%2C%20but%20despite%20several%20upgrades%20and%20tweaks%20suggested%20by%20VMWare%20and%20Microsoft%2C%20users%20still%20have%20issues%20where%20the%20pairing%20will%20randomly%20just%20drop%20-%20sometimes%20restarting%20the%20SfB%20client%20will%20fix%20it%2C%20other%20times%20either%20the%20VDI%20or%20local%20endpoint%20needs%20to%20be%20rebooted.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20OS%20are%20you%20using%3F%20We%20are%20running%20Win7%20on%20the%20endpoints%20and%208.1%20in%20the%20VDI%20clients%20(persistent%20desktops).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%20nobody%20seems%20to%20know%20where%20the%20problem%20is%2C%20and%20Microsoft%20apparently%20has%20no%20plans%20to%20upgrade%20the%20VDI%20plugin%20according%20to%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt740144.aspx.%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt740144.aspx.%26nbsp%3B%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAt%20this%20point%20we%20more%20or%20less%20have%20no%20option%20except%20to%20put%20up%20with%20it%20-%20the%20users%20who%20really%20need%20a%20stable%20phone%20connection%20are%20now%20using%20Polycom%20SIP%20phones%20rather%20than%20USB%20headsets.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EInterested%20to%20know%20if%20you%20get%20anywhere%20with%20Microsoft%20as%20we%20certainly%20haven't%20been%20able%20to!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMiriam%3C%2FP%3E%3C%2FLINGO-BODY%3E
Visitor

In our company, we have a major issue with Lync/Skype4Business in a VmWare VDI Environment!

With Lync VDI Plugin installed on Physical Computer the pairing randomly stops or can just never being done, until the reboot of the physical computer. It’s only after this operation that the pairing functions, if we are lucky.

 

If the Pairing is working there is a little green dot at the right bottom of the Lync client (see attachement)

If the Pairing is not Working there is no little green dot and the trouble begins.

There is NO sound, No Mic on the headset and eventually if it's a notebook, the Mic and Speakers take the relay giving a really bad quality and echo for the caller.

Outside of our Network company the VDI environment is accessible, but the Pairing can never be made.

 

This is impacting all our users randomly and the confidence is somehow being lost with the product.

Everything was functioning pretty well with Lync when it was first installed on all our computers.

And it stills works fine on our physical computers But since the beginning of the year, we have been migrating all our company into a VMware VDI Horizon environment. The Problem has begun to happen.

 

Just to clarify We have already opened a Microsoft Ticket incident.

The MS engineers have already been working more than 30 hours without success so far.

The problem has been escalated to the highest level in MS Support or at least we have been told so.

Until now, we have provided MS at multiple times a lot of Lync logs and network captures and have seen no real solution until today!

 

Now I give you some details about our Infrastructure

 

A VDI Environment that is not Citrix but WMWare !

The VMware VCenter 6.0.0, 2776511 (is configured to work in conjunction with Unidesk and Norskale for confort in creation of Software Layers

 

We have a multisite Network all routed through MPLS Links

The Physical sites are all in private ranges 192.168.xxx.yyy

The Datacenter Hosting the VDI infrastructure is located on a Network Range 172.16.16.xxx

All the traffic is routed correctly for all the different ranges. And When it was only on physical computers we never had problems.

The Lync Server is version 2013 ans is hosted on Premises. We mainly use enterprise Licensing

3 Frontends load balanced with a Netscaler 1WAC 2 Edges.

The Lync Infrastructure has been checked by an expert and has been proven to be correctly configured.

 

Now we are using VMWare Horizon Clients to connect to our VDI environment.

On the Physical Computers the Microsoft Lync VDI Plugin 2013 (15.0.4569.1506) is installed.

All Microsoft updates have been done and system is uptodate.

On the VDI environment Microsoft 2013 (15.0.4849.100 and MSO 15.0.4849.1000) is installed

Even when these were the last versions, the problem occurred so… I think it’s something else than just upgrade to the last version

VMWare environment (running version 6) is certified by Microsoft for running Lync 2013 in VDI.

 

We can provide more details on request….

 

By Opening this thread, we wanted to know if:

Someone else has been experiencing the same behaviour ?

Did you manage to solve this Issue ?

If Yes How ?

If NO, what was the workaround ?

 

Any comments or ideas that might give us some new leads for resolving this issue are welcome !

 

Thanks all for your help

 

Christian VEGA

1 Reply

Hi Christian,

 

We have also been having pairing problems in our VMWare VDI environment since we started using it last year.

 

Our VMWare View environment is version 6.1.4 and local client 6.1.2, but despite several upgrades and tweaks suggested by VMWare and Microsoft, users still have issues where the pairing will randomly just drop - sometimes restarting the SfB client will fix it, other times either the VDI or local endpoint needs to be rebooted.

 

What OS are you using? We are running Win7 on the endpoints and 8.1 in the VDI clients (persistent desktops).

 

Unfortunately nobody seems to know where the problem is, and Microsoft apparently has no plans to upgrade the VDI plugin according to https://technet.microsoft.com/en-us/library/mt740144.aspx. 

 

At this point we more or less have no option except to put up with it - the users who really need a stable phone connection are now using Polycom SIP phones rather than USB headsets.

 

Interested to know if you get anywhere with Microsoft as we certainly haven't been able to!

 

Miriam