osemeister.blogg.se - Remove cached skype for business login

The Decemsecurity update added a new ‘fallback/DNS-less autodiscover’. What impact does it had to your Lync on-premises environment?

Cloud Based Discovery, UPN Enforcement for OrgID, and SIP Autodetection from Azure for Skype for Business Client.

The issue is fixed by January 12, 2016, update for Lync 2013 (Skype for Business).The KB points two other two KB (also initially released on the same date): In this case, the new DNS-less discovery (also known as Cloud-based discovery) redirects you to the Microsoft Lync Online Discovery services in Office 365″

“This issue occurs because if Lync 2013 (Skype for Business) client fails to detect lyncdiscover and lyncdiscoverinternal services. “”The address type is not valid” error when you sign in to Lync 2013 (Skype for Business) by using domain\username format”. On the 12 of January, KB3114687 was published:

Uses SSO to autodetect SIP address and start sign in” – But no more details.

KB3114351 was later updated on – “This security update contains the following improvements: If you were an earlier adapter of the KB3114351 – security update for Lync 2013 (Skype for Business): Decem(this also applies to security update for Skype for Business 2016: KB3114372), you didn’t find by that time on one ‘functionality’ that was introduced. You will also get much more similar popup if you like to control/restrict the desktop trusted certificates on your environment (check the last paragraph on the blog) By now they probably are not having it anymore. If you have deployed on your organization a firewall/proxy with Deep Packet Inspection (DPI), some of your Lync (SfB) users might have questioned you about a certificate popup similar to picture on the right.