I installed gateway with NAT between PC and network. User of PC can chat via Lync client but can't call or join conference. What ports should be mapped via NAT for Lync client to use all Lync facilities? Updated: the question actually is about NAT port mapping of Lync client.
The VDI plugin for Lync 2013 allows using Lync 2013 (which automatically becomes SFB after some updates are installed) over a remote desktop connection without performance penalties, by offloading the audio/video processing to the RDP client.
But what to do if you are using Office 2016 and Skype For Business 2016 on your virtual desktops / terminal servers?
We currently have a Lync 2010 deployment, and are migrating to Skype for Business 2015.
From my reading, there is no way you can upgrade the clients direct from Lync 2010 to Skype for Business 2015/2016, and have to upgrade to Lync 2013 first, then apply the windows updates to update to S4B.
Looking for anyone who has some experience in this process, and essentially the best way to handle this transition.
I've stumbled upon a bizarre problem with Skype for Business 2015 (the client application, previously known as Lync 2013 but automatically upgraded to SfB 2015 by some Office update); maybe I'm missing something, but I'm unable to find a solution, hence this question.
The issue: someone invites you to a meeting, but you don't have a Lync/SfB account, thus you need to join the meeting as an external guest by clicking on the meeting link you received; however, the application is actually installed on your computer, as part of the Office 2013 package; in this scenario, clicking the meeting link will automatically launch the application, but then it will get stuck on asking you for sign in information, which you don't have. It looks like there is no way to avoid launching the application if it's actually installed, or to sign in as a guest.
How can you join a Lync 2013 / Skype for Business meeting as a guest when the application is installed on your computer but you don't have any account you can use?
We have in a quite large Organization Lync 2010 deployed. Also we use for software and updates distribution System Center Configuration Manager.
Our problem we face is that, if we distribute the Lync 2010 client updates through SCCM’s update service, and the update gets applied the Lync 2010 client silently quits. Whatever someone for example is in a Call, IM, Conference … Of course you can think this not so good if the Manager is in an important call and suddenly the Lync client quits.
We surely could distribute the update late at night or in the night, but then we have the problem that not all client are power up since most users shut down their PC after they leave the office, and let me say “Wake On Lan” isn’t really an options there.
So I’m curios how others handle Lync Client Updates in their organization? Or what are the best practices in distributing them...
Thanks.
Martin.