Skip to content

Commit 49571a8

Browse files
Merge pull request #9850 from MicrosoftDocs/main
Auto Publish – main to live - 2025-10-08 02:00 UTC
2 parents 0206bc6 + 0eb4f90 commit 49571a8

File tree

4 files changed

+55
-1
lines changed

4 files changed

+55
-1
lines changed

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ appliesto:
2222
- Microsoft Teams
2323
search.appverid:
2424
- MET150
25-
ms.date: 10/02/2025
25+
ms.date: 10/07/2025
2626
---
2727
# Known issues with Teams Rooms on Windows
2828

@@ -49,6 +49,7 @@ ms.date: 10/02/2025
4949
| --- | --- | --- |
5050
|During a Coordinated meeting, when the meeting volume is changed by using a room remote, the speaker on a Surface Hub or Teams Rooms device turns on.|For a trusted device such as a Surface Hub or Teams Rooms device that is set up to automatically join a Coordinated meeting when the primary device joins, the speaker turns on when a room remote is used to change the meeting volume. This issue occurs even though the audio settings on the device are turned off, and whether they're enabled or disabled.|Turn off proximity join and room remote capabilities on the trusted devices that automatically join a Coordinated meeting.|
5151
|The central part of the console on a Teams Rooms device doesn't respond to touch and mouse input.|On some Microsoft Teams Rooms devices such as the Crestron Dell Optiplex 7080 that use a 4k monitor connected as the front-of-room display, the central portion of the display intermittently stops responding to touch and mouse controls.<br/><br/>Despite this issue, the Teams Rooms app is functional and accepts inputs from a connected keyboard.|Contact Microsoft Support for assistance to work around this issue.|
52+
|Poor audio quality from a Teams Rooms device.|You might experience any of the following audio quality issues from a USB microphone or speaker that's connected to your Teams Rooms device: <ul><li> - Echo sent to remote participants on the call.</li><li> - Low audio quality sent to remote participants on the call.</li><li> - Decrease in audio quality as the call progresses.</li><li> - Low volume in speakers within the room.</li></ul><br/>This issue might be caused when a setting in the audio driver configuration to enhance audio quality is enabled.|To fix the audio quality issue, disable the audio enhancement setting for the attached Teams-certified USB audio device by using the following steps:<ol><li>Select **Settings** on the Teams Rooms device console.</li><li>Select **Windows Settings**, and sign in to the Teams Rooms device as an administrator.</li><li>Open **Control Panel**.</li><li>Select **Hardware and Sound** > **Sound**.</li><li>On the **Playback** tab, select the affected audio device and then select **Properties**.</li><li>Select the **Advanced** tab.</li><li>In the **Signal Enhancements** section, uncheck **Enable audio enhancements**, and then select **OK**.</li><li>Select the **Recording** tab and repeat steps 5, 6 & 7 for the same audio device </li><li>Select **OK** and then close **Control Panel.</li><li>Restart the Teams Rooms device.</li></ol>
5253

5354
## Limitations
5455

support/windows-client/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1081,6 +1081,8 @@ items:
10811081
items:
10821082
- name: Can't install OpenSSH features
10831083
href: ../windows-server/system-management-components/cant-install-openssh-features.md?context=/troubleshoot/windows-client/context/context
1084+
- name: Enable OpenSSH verbose logging
1085+
href: ../windows-server/system-management-components/enable-openssh-verbose-logging.md?context=/troubleshoot/windows-client/context/context
10841086
- name: OpenSSH client can't connect to a server via SSH
10851087
href: ../windows-server/system-management-components/open-client-can-not-connect-server.md?context=/troubleshoot/windows-client/context/context
10861088
- name: PowerShell
Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
---
2+
title: How to Enable OpenSSH Verbose Logging
3+
description: Explains how to enable verbose logging for the OpenSSH service.
4+
ms.date: 10/07/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika, warrenw, v-appelgatet
9+
ms.custom:
10+
- sap:system management components\openssh (including sftp)
11+
- pcy:WinComm User Experience
12+
appliesto:
13+
- ✅ <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
14+
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
15+
---
16+
# How to enable OpenSSH verbose logging
17+
18+
To enable logging verbose logging for the OpenSSH Server service, modify the sshd_config file, and restart the OpenSSH Server service. Follow these steps:
19+
20+
1. Use an administrator-level account to open a text editor, and then open **%ProgramData%\ssh\sshd_config**. The default text of the "Logging" section should resemble the following excerpt:
21+
22+
```output
23+
# Logging
24+
#SyslogFacility AUTH
25+
#LogLevel INFO
26+
```
27+
28+
1. To enable verbose logging, edit the text to resemble the following excerpt:
29+
30+
```output
31+
# Logging
32+
SyslogFacility AUTH
33+
LogLevel VERBOSE
34+
```
35+
36+
> [!NOTE]
37+
> By default, the OpenSSH Server service sends logs to Windows Event Viewer. To record a log file instead, use `SyslogFacility LOCAL0` instead of `SyslogFacility AUTH` in sshd_config. The OpenSSH service records log files in %ProgramData%\ssh\logs.
38+
39+
1. Save and close the sshd_config file.
40+
41+
1. To restart the OpenSSH Server service, open a Windows Command Prompt window, and then run the following command:
42+
43+
```console
44+
NET STOP "OpenSSH SSH Server" && NET START "OpenSSH SSH Server"
45+
```
46+
47+
After the service restarts, it generates verbose log data.
48+
49+
For more information about how to configure OpenSSH, see the [Windows configurations in sshd_config](/windows-server/administration/OpenSSH/openssh-server-configuration#windows-configurations-in-sshd_config) section of "OpenSSH Server configuration for Windows Server and Windows."

support/windows-server/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2598,6 +2598,8 @@ items:
25982598
items:
25992599
- name: Can't install OpenSSH Features
26002600
href: ./system-management-components/cant-install-openssh-features.md
2601+
- name: Enable OpenSSH verbose logging
2602+
href: ./system-management-components/enable-openssh-verbose-logging.md
26012603
- name: OpenSSH client can't connect to a server via SSH
26022604
href: ./system-management-components/open-client-can-not-connect-server.md
26032605
- name: PowerShell

0 commit comments

Comments
 (0)