Merging changes synced from https://github.com/MicrosoftDocs/SupportArticles-docs-pr (branch live)

Author: Learn Build Service GitHub App

Teams/teams-rooms-and-devices/teams-rooms-known-issues-android.md

@@ -23,7 +23,7 @@ appliesto:
   - Microsoft Teams
 search.appverid: 
   - MET150
-ms.date: 09/24/2025
+ms.date: 10/06/2025
 ---
 # Known issues with Teams on Android devices
 
@@ -54,6 +54,7 @@ ms.date: 09/24/2025
 |Unable to assign speed dial to line keys on a sidecar|When you assign speed dial contacts to line keys on the sidecar that is connected to a touch phone device, they don't work.|No workaround is available for the speed dial contacts that you assigned by using the sidecar. However the speed dial contacts that're already set up and shared line delegates and other groups are automatically pinned on the sidecar.|
 |Speed dial line key doesn't transfer an active call.|In older Teams Phones versions, you could transfer an active call by selecting a line key that is configured as a speed dial for a specific contact.<br/><br/>Beginning with Teams Phones version 1.7.0 1449/1.0.94.2025165302, you're only able to make an outgoing call to the speed dial after you select it from the **Transfer** menu.|If you want to transfer active calls to specific contacts, configure line keys as speed dials for those contacts and assign the **Transfer** and **Consult Transfer** menu options to the appropriate line keys.|
 |The screen hangs on Yealink phones when the headset is picked up.|On Yealink MP56 phones that are running version 1449/1.0.94.2025248901 of the Teams for Android app, the screen hangs or crashes when you pick up the headset to make an outbound call.|No workaround is available at this time.|
+|Can't see line keys on the home screen.|After you update your Teams Phones to version 1449/1.0.94.2025264001 of the Teams for Android app, you don't see any assigned line keys on the home screen.<br/><br/>This behavior is seen on non-touch phones such as Poly CCX 350 that have either the CAP or Premium CAP licenses.|No workaround is available at this time.|
 
 ## Limitations
 

support/windows-client/windows-tss/collect-data-analyze-troubleshoot-sys-management-components-scenarios.md

@@ -54,5 +54,21 @@ Use this cmdlet when running a scheduled task that fails with an error, or when
 
 Use this cmdlet when having network printing errors occur, when the client fails to print, or when the printing is slow.
 
+## 
+
 > [!NOTE]
 > If the printing is slow, add the parameter `-procmon` to the end of the cmdlet.
+
+## Scenario: Windows Remote Management (WinRM)
+
+#### TSS cmdlet
+
+
+```powershell
+.\TSS.ps1 -Scenario UEX_WinRM
+```
+
+#### TSS cmdlet description
+
+Use this command to collect data for any WinRM scenario. Run on both source and destination 
+