Surface Hub Reverts to Skype Mode

%3CLINGO-SUB%20id%3D%22lingo-sub-325559%22%20slang%3D%22en-US%22%3ESurface%20Hub%20Reverts%20to%20Skype%20Mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325559%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20three%20Surface%20Hubs%20that%20we%20have%20provisioned%20via%20Intune%20to%20be%20in%20Teams%20Mode%20only.%26nbsp%3B%20A%20lot%20of%20times%20in%20the%20morning%20when%20someone%20first%20uses%20a%20hub%20it%20has%20reverted%20back%20to%20Skype%20Mode%20and%20does%20not%20show%20the%20Teams%20icon.%26nbsp%3B%20To%20fix%20this%20we%20usually%20have%20to%20restart%20the%20hub.%26nbsp%3B%20I%20believe%20this%20is%20happening%20because%20our%20hubs%20go%20through%20Cisco%20ISE%20on%20our%20network%20here%20at%20work%20for%20authentication%20and%20they%20are%20losing%20their%20network%20connection%20overnight%20when%20they%20are%20sitting%20there%20not%20being%20used%20and%20going%20back%20to%20Skype%20until%20it%20has%20to%20be%20restarted%20and%20re-authenticated%20on%20the%20network.%26nbsp%3B%20Has%20anyone%20ever%20run%20into%20an%20issue%20like%20this%20and%20is%20there%20a%20way%20to%20resolve%20this%20on%20the%20Hub%20side%20or%20do%20you%20think%20this%20is%20more%20of%20a%20network%2Fauthentication%20issue%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20You%2C%3C%2FP%3E%3CP%3EDamon%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-338515%22%20slang%3D%22en-US%22%3ERe%3A%20Surface%20Hub%20Reverts%20to%20Skype%20Mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-338515%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20device%20shouldn't%20revert%20to%20Skype%20mode%2C%20even%20if%20it%20cannot%20connect%20to%20Teams%20on%20Office%20365.%3C%2FP%3E%0A%3CP%3ERegardless%2C%20there's%20a%20daily%20maintenance%20window%20that%20should%20reboot%20the%20device%20overnight.%3C%2FP%3E%0A%3CP%3EIf%20this%20is%20something%20you're%20experiencing%20with%20only%20one%20Hub%20I%20suggest%20to%20log%20a%20ticket%20with%20Microsoft%20Services%20so%20they%20can%20look%20at%20the%20logs.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1757992%22%20slang%3D%22en-US%22%3ERe%3A%20Surface%20Hub%20Reverts%20to%20Skype%20Mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1757992%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F218115%22%20target%3D%22_blank%22%3E%40Damon%20Tyler%3C%2FA%3E%26nbsp%3Bwe%20have%20the%20exact%20same%20issue%20with%203%20Surface%20Hub%202s's.%20Configured%20via%20Intune%2C%20randomly%20revert%20to%20Skype.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1764097%22%20slang%3D%22en-US%22%3ERe%3A%20Surface%20Hub%20Reverts%20to%20Skype%20Mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1764097%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESame%20issue%20here.%20We%20have%2030%20Surface%20Hub%202s%20and%20randomly%2C%20some%20Surface%20Hubs%20revert%20back%20to%20Skype.%20Sometimes%20we%20can%20fix%20it%20by%20just%20rebooting%20the%20device%2C%20sometimes%20not.%20Our%20Surface%20Hubs%20are%20all%20managed%20in%20Intune%2C%20On%20premise%20AD%20joined%2C%20Teams%20preferred%20mode%20and%20connected%20to%20the%20network%20by%20Wifi%20WPA2%20enterprise.%20We%20are%20running%20these%20hubs%20since%20few%20month%20and%20we%20never%20had%20this%20issue%20before%20around%20the%2028th%20september.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20see%20this%20in%20the%20event%20viewer%20%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EActivation%20of%20application%20Microsoft.MicrosoftTeamsforSurfaceHub_8wekyb3d8bbwe!Teams%20failed%20with%20error%3A%20-2147009284%20See%20the%20Microsoft-Windows-TWinUI%2FOperational%20log%20for%20additional%20information.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eand%20in%20the%20TWinUI%2FOperational%20log%20%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft.MicrosoftTeamsforSurfaceHub_8wekyb3d8bbwe!Teams%20for%20the%20Windows.Launch%20contract%20failed%20with%20The%20deployment%20operation%20failed%20because%20the%20specified%20application%20needs%20to%20be%20registered%20first..%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EActivation%20for%20Microsoft.MicrosoftTeamsforSurfaceHub_8wekyb3d8bbwe!Teams%20failed.%20Error%20code%3A%20The%20operation%20completed%20successfully..%20Activation%20phase%3A%20-2147009265%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECyrille%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1764103%22%20slang%3D%22en-US%22%3ERe%3A%20Surface%20Hub%20Reverts%20to%20Skype%20Mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1764103%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F826375%22%20target%3D%22_blank%22%3E%40Cyrille_D%3C%2FA%3E%26nbsp%3Bwe%20had%20another%20one%20do%20this%2C%20and%20going%20into%20Apps%20Teams%20was%20greyed%20out%2C%20and%20clicking%20on%20it%20said%20it%20had%20to%20be%20reset%20(which%20did%20nothing).%20We%20just%20uninstalled%20it%20and%20reinstalled%20and%20that%20fixed%20it.%20This%20happened%20in%20the%20CEO's%20office%2C%20so%20to%20say%20he%20was%20unimpressed%20that%20the%20one%20thing%20the%20Hub%20is%20supposed%20to%20do%20well%20(Teams)%20didn't%20work%20is%20an%20understatement.%3C%2FP%3E%3CP%3EConsidering%20how%20much%20these%20things%20cost%2C%20they%20should%20be%20far%20more%20reliable.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1764112%22%20slang%3D%22en-US%22%3ERe%3A%20Surface%20Hub%20Reverts%20to%20Skype%20Mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1764112%22%20slang%3D%22en-US%22%3ESure%2C%20I%20have%20a%20ticket%20opened%20at%20Microsoft%20(premier%20support)%20since%20few%20days%20regarding%20this%20issue%20and%20still%20waiting%20for%20a%20feedback...%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1764280%22%20slang%3D%22en-US%22%3ERe%3A%20Surface%20Hub%20Reverts%20to%20Skype%20Mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1764280%22%20slang%3D%22en-US%22%3EThis%20behavior%20can%20be%20observed%20when%20Teams%20is%20trying%20to%20connect%20to%20Office%20365%20but%20unable%20to%20do%20so.%20You'll%20usually%20see%20this%20when%20the%20device%20wakes%20up%20from%20sleep%20if%20getting%20back%20on%20the%20network%20is%20slower%20than%20the%20Teams%20app%20attempt%20to%20sign%20in.%3CBR%20%2F%3ETo%20work%20around%20this%20behavior%2C%20you%20can%20switch%20to%20Teams%20Mode%202%2C%20or%20update%20to%20the%20Windows%2010%20Team%202020%20Update%20where%20this%20behavior%20doesn't%20exist.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1764398%22%20slang%3D%22en-US%22%3ERe%3A%20Surface%20Hub%20Reverts%20to%20Skype%20Mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1764398%22%20slang%3D%22en-US%22%3EThank%20you%20for%20the%20update%2C%20we'll%20probably%20switch%20to%20mode%202%20if%20the%20problem%20doesn't%20exists%20in%20this%20mode.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1764417%22%20slang%3D%22en-US%22%3ERe%3A%20Surface%20Hub%20Reverts%20to%20Skype%20Mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1764417%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F826375%22%20target%3D%22_blank%22%3E%40Cyrille_D%3C%2FA%3E%26nbsp%3Bwe%20have%20the%20issue%20in%20mode%202%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2182588%22%20slang%3D%22en-US%22%3ERe%3A%20Surface%20Hub%20Reverts%20to%20Skype%20Mode%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2182588%22%20slang%3D%22en-US%22%3EAnyone%20have%20insight%20on%20a%20resolution%20for%20this%3F%20Just%20discovered%20this%20is%20happening%20on%20some%20of%20my%20SH1%20devices.%20Going%20through%20Cisco%20ISE.%20Using%20Mode%201.%20A%20reboot%2C%20and%20they%20are%20back%20to%20using%20Teams.%20Since%20the%20office%20is%20so%20empty%20I%20haven't%20even%20checked%20if%20they%20revert%20by%20the%20end%20of%20the%20business%20day%2C%20or%20if%20it%20is%20happening%20overnight.%3C%2FLINGO-BODY%3E
Occasional Contributor

Hello,

 

We have three Surface Hubs that we have provisioned via Intune to be in Teams Mode only.  A lot of times in the morning when someone first uses a hub it has reverted back to Skype Mode and does not show the Teams icon.  To fix this we usually have to restart the hub.  I believe this is happening because our hubs go through Cisco ISE on our network here at work for authentication and they are losing their network connection overnight when they are sitting there not being used and going back to Skype until it has to be restarted and re-authenticated on the network.  Has anyone ever run into an issue like this and is there a way to resolve this on the Hub side or do you think this is more of a network/authentication issue?

 

Thank You,

Damon

11 Replies

Hi, 

 

The device shouldn't revert to Skype mode, even if it cannot connect to Teams on Office 365.

Regardless, there's a daily maintenance window that should reboot the device overnight.

If this is something you're experiencing with only one Hub I suggest to log a ticket with Microsoft Services so they can look at the logs.

@Damon Tyler we have the exact same issue with 3 Surface Hub 2s's. Configured via Intune, randomly revert to Skype. 

Hi,

 

Same issue here. We have 30 Surface Hub 2s and randomly, some Surface Hubs revert back to Skype. Sometimes we can fix it by just rebooting the device, sometimes not. Our Surface Hubs are all managed in Intune, On premise AD joined, Teams preferred mode and connected to the network by Wifi WPA2 enterprise. We are running these hubs since few month and we never had this issue before around the 28th september.

 

I can see this in the event viewer :

 

Activation of application Microsoft.MicrosoftTeamsforSurfaceHub_8wekyb3d8bbwe!Teams failed with error: -2147009284 See the Microsoft-Windows-TWinUI/Operational log for additional information.

 

and in the TWinUI/Operational log :

 

Microsoft.MicrosoftTeamsforSurfaceHub_8wekyb3d8bbwe!Teams for the Windows.Launch contract failed with The deployment operation failed because the specified application needs to be registered first..

 

Activation for Microsoft.MicrosoftTeamsforSurfaceHub_8wekyb3d8bbwe!Teams failed. Error code: The operation completed successfully.. Activation phase: -2147009265

 

Best regards,

 

Cyrille

 

@Cyrille_D we had another one do this, and going into Apps Teams was greyed out, and clicking on it said it had to be reset (which did nothing). We just uninstalled it and reinstalled and that fixed it. This happened in the CEO's office, so to say he was unimpressed that the one thing the Hub is supposed to do well (Teams) didn't work is an understatement.

Considering how much these things cost, they should be far more reliable.

Sure, I have a ticket opened at Microsoft (premier support) since few days regarding this issue and still waiting for a feedback...
This behavior can be observed when Teams is trying to connect to Office 365 but unable to do so. You'll usually see this when the device wakes up from sleep if getting back on the network is slower than the Teams app attempt to sign in.
To work around this behavior, you can switch to Teams Mode 2, or update to the Windows 10 Team 2020 Update where this behavior doesn't exist.
Thank you for the update, we'll probably switch to mode 2 if the problem doesn't exists in this mode.

@Cyrille_D we have the issue in mode 2

Anyone have insight on a resolution for this? Just discovered this is happening on some of my SH1 devices. Going through Cisco ISE. Using Mode 1. A reboot, and they are back to using Teams. Since the office is so empty I haven't even checked if they revert by the end of the business day, or if it is happening overnight.
This should be fixed in the 20H2 update, we had no issue since the update but as you said, our offices are also empty.

@Cyrille_D 

Thank you so much for the reply! 

I had tried the 20H2 update about two weeks ago to pre-emptively move to Modern Auth. But I was having trouble with my accounts disconnecting after setup. So I rolled those devices back. I have no idea if they were doing this before, and maybe I'm just noticing since they are more visible to me?

 

I'm new to SH devices so we'll try 20H2 again soon on a test device.