SOLVED

Teams Room Systems, no sign in with KB4565351

%3CLINGO-SUB%20id%3D%22lingo-sub-1587005%22%20slang%3D%22en-US%22%3ETeams%20Room%20Systems%2C%20no%20sign%20in%20with%20KB4565351%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1587005%22%20slang%3D%22en-US%22%3E%3CP%3EDear%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eyesterday%2C%20on%20our%20Teams%20Room%20Systems%20KB4565351%20was%20installed%2C%20now%20they%20can't%20sign%20in.%20If%20we%20remove%26nbsp%3BKB4565351%2C%20it%20works%20fine.%20Here%20are%20some%20details%3A%3C%2FP%3E%3CP%3EHardware%3A%20Lenovo%20ThinkSmart%20Hub%20500%3C%2FP%3E%3CP%3EWindows%3A%26nbsp%3BWindows%20Release%2018363.1016%3C%2FP%3E%3CP%3ERoom%20System%3A%204.5.35.0%3C%2FP%3E%3CP%3EUser%20(Skype)%20is%20located%20on%20premise%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20of%20our%20Room%20Systems%20have%20the%20problem%2C%20not%20only%20a%20single%20device.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20idea%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBye%2C%3C%2FP%3E%3CP%3EChristian%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1587005%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ERoom%20System%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1587338%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Systems%2C%20no%20sign%20in%20with%20KB4565351%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1587338%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20company%20experienced%20this%20same%20issue%20this%20morning.%20Conference%20room%20tablets%20were%20unable%20to%20connect%20to%20Skype%2C%20displaying%20the%20error%20message%20%22%3CSPAN%20class%3D%22fieldWidget%20roWidget%22%3E%3CSPAN%20class%3D%22F10746%20ControlStyle%20rofld%22%3ESign%20in%20failed.%20We%20couldn't%20sign%20you%20in.%20There%20might%20be%20a%20problem%20with%20your%20credentials.%20Please%20contact%20your%20support%20team.%3C%2FSPAN%3E%3C%2FSPAN%3E%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20a%20long%20period%20of%20investigation%2C%20we%20were%20able%20to%20determine%20that%20uninstalling%20update%20KB4565351%20resolves%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1587430%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Systems%2C%20no%20sign%20in%20with%20KB4565351%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1587430%22%20slang%3D%22en-US%22%3EWe're%20seeing%20the%20same%20issues%20with%20all%20our%20systems%20today.%3CBR%20%2F%3E%3CBR%20%2F%3E50%2B%20Conferencing%20systems%20offline%20in%20these%20Corona-days%20generates%20quite%20some%20noise%20internaly%20with%20the%20top%20executives%20in%20the%20company.%3CBR%20%2F%3EAnd%20we're%20about%20to%20start%20spending%20%24300.000%20more%20for%20these%20Teams-systems.%3CBR%20%2F%3E%3CBR%20%2F%3EThey%20really%20should%20test%20Patchreleases%20with%20Teams-Roomsystems.%3CBR%20%2F%3EThis%20isn't%20the%20first%20time%20an%20update%20does%20%22bad%20things%22%20to%20the%20Team%2FSkyperoomsystems.%3CBR%20%2F%3E%3CBR%20%2F%3EStatus%3A%3CBR%20%2F%3EAll%20Logitech%20Smartdocks%3A%20Teams%20OK%2FSfB%20Onprem%20fail%20login%20to%20SfB%20Onprem.%3CBR%20%2F%3EAll%20Logitech%20Taps%20with%20NUC%3A%20Teams%20OK%2FSfB%20Onprem%20fail%20login%20to%20SfB%20Onprem.%3CBR%20%2F%3E%3CBR%20%2F%3EAnd%20as%20Andrew%20and%20Chris%20have%20confirmed.%20Removing%20KB4565351%20fixes%20the%20issue%20until%20it%20hits%20the%20system%20at%20next%20patch-update.%3CBR%20%2F%3E%3CBR%20%2F%3EVidar%20Thomassen%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1589361%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Systems%2C%20no%20sign%20in%20with%20KB4565351%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1589361%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20also%20seeing%20this%20issue%20across%20our%20fleet%20of%20MTRs%20(~500).%26nbsp%3B%20We%20believe%20~140%20have%20installed%20the%20KB%20at%20this%20point%2C%20and%20are%20expecting%20the%20others%20to%20join%20them%20soon.%26nbsp%3B%20We're%20attempting%20to%20escalate%20with%20MS%2C%20but%20figured%20we%20would%20post%20and%20confirm%20what%20other%20are%20seeing.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1589385%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Systems%2C%20no%20sign%20in%20with%20KB4565351%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1589385%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F247906%22%20target%3D%22_blank%22%3E%40Chris82%3C%2FA%3E%26nbsp%3BThis%20is%20an%20issue%20for%20us%20as%20well.%26nbsp%3B%20Removing%20the%20KB%20did%20the%20trick%20for%20now.%26nbsp%3B%20Thanks%20for%20posting%20this!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1592230%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20Systems%2C%20no%20sign%20in%20with%20KB4565351%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1592230%22%20slang%3D%22en-US%22%3E%3CP%3ELooks%20like%20the%20problem%20was%20solved%20with%20MTR%204.5.37%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Dear all,

 

yesterday, on our Teams Room Systems KB4565351 was installed, now they can't sign in. If we remove KB4565351, it works fine. Here are some details:

Hardware: Lenovo ThinkSmart Hub 500

Windows: Windows Release 18363.1016

Room System: 4.5.35.0

User (Skype) is located on premise

 

All of our Room Systems have the problem, not only a single device.

 

Any idea?

 

Bye,

Christian

5 Replies
Highlighted
Best Response confirmed by ThereseSolimeno (Microsoft)
Solution

My company experienced this same issue this morning. Conference room tablets were unable to connect to Skype, displaying the error message "Sign in failed. We couldn't sign you in. There might be a problem with your credentials. Please contact your support team."

 

After a long period of investigation, we were able to determine that uninstalling update KB4565351 resolves the issue.

Highlighted
We're seeing the same issues with all our systems today.

50+ Conferencing systems offline in these Corona-days generates quite some noise internaly with the top executives in the company.
And we're about to start spending $300.000 more for these Teams-systems.

They really should test Patchreleases with Teams-Roomsystems.
This isn't the first time an update does "bad things" to the Team/Skyperoomsystems.

Status:
All Logitech Smartdocks: Teams OK/SfB Onprem fail login to SfB Onprem.
All Logitech Taps with NUC: Teams OK/SfB Onprem fail login to SfB Onprem.

And as Andrew and Chris have confirmed. Removing KB4565351 fixes the issue until it hits the system at next patch-update.

Vidar Thomassen
Highlighted

We are also seeing this issue across our fleet of MTRs (~500).  We believe ~140 have installed the KB at this point, and are expecting the others to join them soon.  We're attempting to escalate with MS, but figured we would post and confirm what other are seeing.

Highlighted

@Chris82 This is an issue for us as well.  Removing the KB did the trick for now.  Thanks for posting this!

Highlighted

Looks like the problem was solved with MTR 4.5.37