Microsoft Teams Rooms update 4.0.76.0 going live today

SSleeper thank you for both the kind words and especially for betting on Microsoft Teams Rooms!

Ilya Bukshteyn Thank you for the quick updates.  I'm loving how engaged eveyone here is to take care of this issue.  Makes me feel a little more reassured with the decision to go with Teams for a meeting room platform.  I know its not perfect yet but having engaged resources goes a long way to making this a great platform.

Having the same issue as Steve_Esposito - Updated to 4.0.76.0 on Saturday at 2am. It automatically signs into the Skype account and gets stuck at a blue window. If you close the blue window, it attempts to reload but gets stuck again.

The program Microsoft.SkypeRoomSystem.exe version 4.0.76.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 22cc
 Start Time: 01d4d81dba12cb23
 Termination Time: 4294967295
 Application Path: C:\Program Files\WindowsApps\Microsoft.SkypeRoomSystem_4.0.76.0_x64__8wekyb3d8bbwe\Microsoft.SkypeRoomSystem.exe
 Report Id: 747c8451-1426-4a30-8c08-4f6c21ff9cf5
 Faulting package full name: Microsoft.SkypeRoomSystem_4.0.76.0_x64__8wekyb3d8bbwe
 Faulting package-relative application ID: App

Application: DesktopAPIService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.UnauthorizedAccessException
   at System.StubHelpers.StubHelpers.GetWinRTFactoryObject(IntPtr)
   at Microsoft.SkypeTeam.NativeUtils.RRegistryHelper..ctor()
   at DesktopAPIService.DesktopAPIService+<ThreadProc>d__10.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

Faulting application name: DesktopAPIService.exe, version: 4.0.76.0, time stamp: 0x5c795d8d
Faulting module name: KERNELBASE.dll, version: 10.0.15063.1478, time stamp: 0x7789680f
Exception code: 0xe0434352
Fault offset: 0x0000000000065a98
Faulting process id: 0x2b5c
Faulting application start time: 0x01d4d81f41b707df
Faulting application path: C:\Program Files\WindowsApps\Microsoft.SkypeRoomSystem_4.0.76.0_x64__8wekyb3d8bbwe\DesktopAPIService\DesktopAPIService.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: e264aa21-5244-41f9-bd4b-01070d59684f
Faulting package full name: Microsoft.SkypeRoomSystem_4.0.76.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Ilya BukshteynThank you for the quick update, I look forward to that feature being implemented so I can remove the physical phone from the table in my rooms. 

Keith Knowles  SSleeper  I was incorrect above. The DTMF feature and video pin / unpin are both dependent on a cloud service change / feature flag. We're checking now on where that is in terms of getting enabled.  Should be very soon and we'll post here when confirmed.

Steve_Esposito we're investigating your report. What does "skype splash screen" mean exactly?  Is that the splash screen when the MTR app is starting up?  

Ilya Bukshteyn SSleeper  @Sohail Tariq I can also confirm that I have no dial pad after connecting to a phone call which is required for entering conference PINs or similar. 

Since moving to 4.0.76.0 I also have a number of rooms that have disappeared from OMS and are stuck on the Skype splash screen.  Do we know what is causing the issue?  Is there a team working on a resolve?  I have 167 units that upgraded recently.  I need to understand what has caused the issue and how best to resolve it.  Any assistance would be greatly appreciated.

SSleeper Ben Dodson There is no UX change on the console screen. In our MTRs internally we use the purple theme once devices are enabled for Microsoft Teams; theme settings are also under Settings on the console.  You will see the Teams meetings UX once the MTR joins a Teams meeting.

SSleeper you should be seeing the dialpad now in Teams default mode. Can you please follow up with support and/or Sohail_Tariq on my team?

SSleeper I think from Ilya Bukshteyn’s original post it is waiting for it to be enabled on the cloud service side. Hopefully this happens soon as it is the only thing holding us back from changing to Teams mode. 

Guido Peter  I think the actual front screen UI is the same, just if you start a meeting/call it will be Teams-based.