Windows 10 - Insights for the Enterprise Series (January)
Your SlideShare is downloading.
×
![DesktopAPIService
• Windows Update and App Store Interactions
• Event Log Entries
[5080][15][DesktopAPIService.cs:175:Conn...](https://image.slidesharecdn.com/presentationdeck-mtrtroubleshooting-final-200904214245/75/mtr-troubleshooting-20-2048.jpg?cb=1666064458)
Check these out next
Recommended
More Related Content
Slideshows for you (20)
Similar to MTR Troubleshooting (20)
More from Graham Walsh (20)
Recently uploaded (20)
MTR Troubleshooting
- 1. About the Speaker Technical Solutions Manager Lives in Minneapolis, MN Microsoft Certified Master Loves being a Member/Owner of Broken Clock Cooperative in Minneapolis Twitter: lkannel URI:lkannel@ucninjas.com
- 2. Advanced Microsoft Teams Room Troubleshooting Topics Prerequisites What’s new? HardwareTroubleshooting ServiceTroubleshooting Log file analysis CoolTools MTR OEMTools
- 3. Prerequisites • Experiencing creating, deploying, and troubleshooting Microsoft Teams Rooms • Experience with theTeams Admin Center • Skype for BusinessTroubleshootingTools like CQD, CLS, Snooper • WhenTroubleshooting: • Gather specific dates and times of issues/events • Clearly document what was expected to happen, and what actually happened
- 4. What’s New? • Embedded PS1 with MTR updater • WindowsVersion Support An ounce of prevention is worth a pound of cure
- 5. Embedded PS1 updater *Uses hashed binary application embedded in powershell script *Updates using appropriate user context (Skype) *Process takes up to 45 minutes (wait until complete!) – MTR settings screen will display 4.4.63.0 as of July 5th, 2020. https://support.microsoft.com/en-us/help/4565998/teams- rooms-application-does-not-start-after-update https://go.microsoft.com/fwlink/?linkid=2134015 From an elevated command prompt
- 6. WindowsVersion Support Windows 10 1903 Recommended Windows 10 1909Validated Windows 10 2004 Not Recommended
- 7. MTR Management inTeams Admin Center
- 8. HardwareTroubleshooting • OEM Devices • DriverVersions • Displays • MTR Logs and enumerated devices • Devices • DxDiag • MSInfo32 • Event Logs https://Bit.ly/MTRLogs
- 9. OEM Devices • Audio I/O • Microphones • Speakers • Camera(s) • Display(s) • Compute (Bios) Use the latest firmware recommended by OEM
- 10. Log Files • Log collection script
- 11. Devices.txt Device Description/Name Product ID/Vendor ID – helpful when working with OEMs troubleshooting specific device hardware/firmware issues
- 12. Dxdiag (DirectX) • Detailed System Info • Windows Build • CPU/Bios/Memory • System devices and driver builds/repository • Audio/Video Compressors • Windows Error Reporting (WER) events
- 13. Event Logs If its 68K-70K, its probably empty (no need to open/review Microsoft-Windows-Kernel-PnP_Configuration identifies USB device additions, removals, and configurations.
- 14. ServiceTroubleshooting • Exchange/Exchange Online • Skype for Business Server/Online • MicrosoftTeams
- 15. Exchange Retrieving the core credentials from the password vault Core credentials do exist. Attempting to autodiscover for demoroom1@mydemos.com with https://outlook.office365.com/autodiscover/autodiscove r.json/v1.0/demoroom1@mydemos?Protocol=ews Retrieving the core credentials from the password vault Core credentials do exist. Scenario_Name = AutodiscoverV2. Scenario_Reason = mydemos.com : Attempting to autodiscover. Scenario_Status = Success. Scenario_Step = Start. Scenario_TotalTime = 00:00:00. AppSkypeDesktopAPIService.txt AppSkypeSkypeRoomInit- • ConfigurationValues • Web Services connectivity AppMicrosoftTeamslogs.txt SkypeDownloadsMS Teams Diagnostic Logs *.txt Event Logs
- 16. AppSkypeDesktopAPIService.txt AppSkypeSkypeRoomInit-Version.log • ConfigurationValues • Web Services connectivity AppMicrosoftTeamslogs.txt SkypeDownloadsMS Teams Diagnostic Logs *.txt Event Logs Exchange
- 17. • AppSkypeDesktopAPIService.txt • AppSkypeSkypeRoomIni Version.log • ConfigurationValues • Web Services connectivity • AppMicrosoftTeamslogs.txt • SkypeDownloadsMSTeams Diagnostic Logs *.txt • Event Logs Exchange
- 18. MicrosoftTeams • Main Kiosk Application Log • Identifies User and hardware interactions AppSkypeDesktopAPIService.txt AppSkypeSkypeRoomInit-Version.log • ConfigurationValues AppMicrosoftTeamslogs.txt SkypeDownloadsMS Teams Diagnostic Logs *.txt
- 19. DesktopAPIService • Audio/Video Device Interactions • Display connectivity (left top)=(0 0) (w h)=1024w * 768h isPrimary=True name=.DISPL AY1 maxResolution=5120w * 2880h [2024][15][AudioDeviceHelper.cs:49:ChangeDevice] Attempting to change the default audio device eConsole eRender Echo Cancelling Speakerphone (Logi Rally Audio) [2024][15][AudioDeviceHelper.cs:53:ChangeDevice] DEVICE NOT FOUND! [2024][1][SystemWatcher.cs:185:WndProc] Received event type PBT_POWERSETTINGCHANGE [2024][1][SystemWatcher.cs:197:WndProc] System message: Display OFF [5080][1][SystemWatcher.cs:185:WndProc] Received event type PBT_POWERSETTINGCHANGE [5080][1][SystemWatcher.cs:201:WndProc] System message: Display ON
- 20. DesktopAPIService • Windows Update and App Store Interactions • Event Log Entries [5080][15][DesktopAPIService.cs:175:Connection_RequestReceived] Received request of type: GetRegIntValueInHklm with args: SOFTWAREPoliciesMicrosoftWindowsWindowsUpdate Received request of type: EventLog_WriteEntry with args: {"Description":"Heartbeat is healthy.","ResourceState":"Healthy","OperationName":"Heartbeat","OperationResult":"Pass","OS":"Windows 10","OSVersion":"10.0.18363.900","Alias":"logitech-srs-mn1@logidemos.com","DisplayName":"Logitech Tap Training Room 1","AppVersion":"4.4.63.0","IPv4Address":"192.168.1.105","IPv6Address":"","IPv4Address2":"172.18.64.1"}, 4, 2000
- 21. SkypeRoomInit • Configuration Settings at runtime Value of AudioCaptureCommunicationsDevice = Echo Cancelling Speakerphone (Logitech MeetUp Speakerphone) Value of AudioRenderCommunicationsDevice = Echo Cancelling Speakerphone (Logitech MeetUp Speakerphone) Value of AudioRenderDefaultDevice = Echo Cancelling Speakerphone (Logitech MeetUp Speakerphone) Value of AutoExitMeetingEnabled = True Value of AutoScreenSharing = True Value of BluetoothAdvertisementEnabled = True Value of ByomAutoAcceptEnabled = True Value of LastPasswordUpdate = 1/1/0001 12 Value of PasswordRotationEnabled = False Value of PasswordUpdateFrequencyInDays = 30 Value of TeamsMeetingsEnabled = True Value of WebexMeetingsEnabled = False Value of ZoomMeetingsEnabled = False Value of IsTeamsDefaultClient = True Value of TeamsRing = general Value of TeamsVersion = 1.3.00.8357 Value of ContentCameraId = Value of ContentCameraInverted = False Value of ContentCameraEnhancementEnabled = True Value of HideMeetingNames = False Value of Theme = Windows.Storage.ApplicationDataCompositeValue Creating new RigelTheme with #FF0874AA Default#FF0874AA.png True Default Value of Autodiscover = Windows.Storage.ApplicationDataCompositeValue Value of ModernAuthEnabled = True Value of NoOfFrontOfRoomDisplays = 1 Value of DisplayOrder = 1 Value of DuplicateIngestDefault = True Value of AdminEmailAddress = Value of AllowSendLogs = False Value of SystemId = ab91d9ec74c5001121ff7f579f87b43bcd032b16969620373ab7e9bbb306151b
- 22. SkypeRoom-Lync*.lynclog • Skype Login Info • Web Services information, SIP ladder flows (parsable via Snooper) • SDP/Media negotiation information
- 23. AppMicrosoftTeamslog.txt Bad password/MFA: Added AuthenticationFailed (current state: Unknown -> AuthenticationFailed) SSO: ssoerr - SSO failed. ErrorCode:invalid_grant Error Desc: Status: caa20003 Monitor Location: Saved window state to {"monitorId":2480450848,"x":0,"y":0,"width":1280,"height":800,"isM Maximized":false,"isFullScreen":true}
- 24. AppMicrosoftTeamslog.txt Bluetooth beaconing enabled: RIGEL-SERVICE: RigelService::UpdateBluetoothAdvertisementState BluetoothLE Desktop: ble:advertisement-start requested BluetoothLE Desktop: ble:publisher-status-changed 0 BluetoothLE Desktop: ble:publisher-status-changed 2 Bluetooth Advertisement State Update request received update bluetooth advertisement state, isAdvertising = true https://www.graham-walsh.com/add-this-room-to-your-microsoft-teams-meeting/
- 25. AppMicrosoftTeamslog.txt “My content is on the wrong display” RigelWindowService: Launching context view correlationId:4d24513d-fcf4-4631- 8cf0-faef1012c752 RigelHostedWindow windowType=GalleryAndContent log=Primary display id = 2480450848, and bounds = (x,y) = (0,0), (width,height) = (1280,800) RigelHostedWindow windowType=GalleryAndContent log=Found 1 secondary displays RigelHostedWindow windowType=GalleryAndContent log=Secondary display id = 2528732444, and bounds = (x,y) = (1280,0), (width,height) = (1281,720) RigelHostedWindow windowType=GalleryAndContent log=Selected display id:2528732444, index:0 in secondary displays list
- 26. CoolTools • MonitorInfoView • Snooper • Azure Log Analytics • USBDeview
- 27. MonitorInfoView Gathers detailed info about connected displays such as: • Manufacturer • Maximum Resolution • Refresh Rates • Low power state options (standby, suspend, low power) • EDIDVersion • Download
- 28. MonitorInfoView Gathers detailed info about connected displays such as: • Manufacturer • Maximum Resolution • Refresh Rates • Low power state options (standby, suspend, low power) • EDIDVersion • HTML Output
- 29. Snooper • Included in SfBS 2015/2019 debugging tools • 2015 • 2019
- 30. Azure Monitor
- 31. USBDeview https://www.nirsoft.net/utils/usb_devices_view.html Thank you MichaelTressler!
- 32. Advanced Microsoft Teams Room Troubleshooting Topics What’s new? HardwareTroubleshooting ServiceTroubleshooting Log file analysis CoolTools
- 33. Appendix
- 34. DesktopAPIService.txt
