Skip to content

Commit 896e206

Browse files
committed
Merge remote-tracking branch 'upstream/main' into AB#7246-Troubleshooting-and-Adjusting-Concurrent-Connection-Limits-in-SSH
2 parents f551a15 + 7ea43c9 commit 896e206

18 files changed

+84
-352
lines changed

.openpublishing.redirection.json

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,35 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "support/windows-client/windows-tss/gather-information-using-tss-user-experience.md",
5+
"redirect_url": "/troubleshoot/windows-client/windows-tss/collect-data-analyze-troubleshoot-sys-management-components-scenarios",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path": "support/windows-client/windows-tss/gather-information-using-tss-windows-failover-cluster-issues.md",
10+
"redirect_url": "/troubleshoot/windows-client/windows-tss/collect-data-analyze-troubleshoot-windows-clustering-scenarios",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path": "support/windows-client/windows-tss/gather-information-using-tss-wufb-reports.md",
15+
"redirect_url": "/troubleshoot/windows-client/windows-tss/collect-data-analyze-troubleshoot-windows-servicing-scenarios",
16+
"redirect_document_id": false
17+
},
18+
{
19+
"source_path": "support/windows-client/windows-tss/gather-information-using-tss-group-policy.md",
20+
"redirect_url": "/troubleshoot/windows-client/windows-tss/collect-data-analyze-troubleshoot-group-policy-scenarios",
21+
"redirect_document_id": false
22+
},
23+
{
24+
"source_path": "support/windows-client/windows-tss/gather-information-using-tss-deployment.md",
25+
"redirect_url": "/troubleshoot/windows-client/windows-tss/collect-data-analyze-troubleshoot-windows-servicing-scenarios",
26+
"redirect_document_id": false
27+
},
28+
{
29+
"source_path": "support/windows-client/windows-tss/gather-information-using-tss-ad-replication.md",
30+
"redirect_url": "/troubleshoot/windows-client/windows-tss/collect-data-analyze-troubleshoot-active-directory-scenarios#scenario-active-directory-replication-and-topology",
31+
"redirect_document_id": false
32+
},
333
{
434
"source_path": "support/windows-client/setup-upgrade-and-drivers/prevent-users-connect-usb.md",
535
"redirect_url": "https://gpsearch.azurewebsites.net/#173",

Microsoft365/purview/purview/audit-logs/mailbox-audit-logs.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: How to use mailbox audit logs in Microsoft 365
2+
title: Use mailbox audit logs in Microsoft 365
33
description: Describes how to use mailbox audit logs to determine when a mailbox was updated unexpectedly or whether items are missing in Microsoft 365 dedicated.
44
author: Cloud-Writer
55
ms.author: meerak
@@ -18,20 +18,18 @@ search.appverid: MET150
1818
ms.date: 05/05/2025
1919
---
2020

21-
# How to use mailbox audit logs in Microsoft 365
21+
# Use mailbox audit logs in Microsoft 365
2222

23-
In Microsoft 365, you can run mailbox audit logs to determine when a mailbox was updated unexpectedly or whether items are missing from a mailbox. For example, you may have to do this if items are moved or if they're deleted unexpectedly or incorrectly.
23+
In Microsoft 365, you can run [mailbox audit logs](/purview/audit-mailboxes) to determine when a mailbox was updated unexpectedly or whether items are missing from a mailbox. For example, you may have to do this if items are moved or if they're deleted unexpectedly or incorrectly.
2424

2525
**Note**: For the vNext environment, by default, mailbox audit logs aren't enabled. The feature must be turned on in order for a user to begin a search.
2626

27-
## How to run and check mailbox audit logs
27+
## Run mailbox audit logs
2828

2929
Mailbox audit logging lets users obtain information about actions that are performed by non-owners and administrators. Mailbox audit logging is available to members of the Audit Reporting Mailbox self-service group only by using Windows Remote PowerShell.
3030

3131
> [!NOTE]
32-
>
33-
> - By default, only non-owner mailbox audit logging is enabled, and owner mailbox audit logging is disabled. If you have to perform owner mailbox audit logging to investigate a specific issue, you can temporarily enable the process for two weeks.
34-
> - Some organizations might not allow you to use mailbox audit logging. In this case, the feature will be turned off for you.
32+
> Some organizations might not allow you to use mailbox audit logging. In this case, the feature will be turned off for you.
3533
3634
To investigate this issue, create and use a Windows PowerShell script by using the sample script that's provided in Step 1 in this section, and then customize a search. By default, you can investigate actions that are performed by non-owners and administrators. This script exports content in a simplified, comma-separated values (.csv) file to help you troubleshoot reports about items that are missing or that were updated unexpectedly.
3735

@@ -205,7 +203,7 @@ The most useful columns of the .csv file are exported. Some of these columns are
205203
|OperationResult|Status of the operation</br></br>**Note** Operation results include the following: </br>- Failed </br>- PartiallySucceeded </br>- Succeeded |
206204
|CrossMailboxOperation|Information about whether the operation that's logged is a cross-mailbox operation (for example, copying or moving messages among mailboxes) |
207205
208-
### More information about mailbox audit logging
206+
### Use Windows Remote PowerShell
209207
210208
- The **Search-MailboxAuditLog** cmdlet is used in the sample script in Step 1 to search a single mailbox synchronously. You can do this also by running the cmdlet in Windows Remote PowerShell.
211209

Teams/meetings/teams-meeting-with-shared-mailboxes.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,14 +12,17 @@ appliesto:
1212
- Microsoft Teams
1313
search.appverid:
1414
- MET150
15-
ms.date: 06/23/2025
15+
ms.date: 10/08/2025
1616
---
1717
# Teams meeting features for shared mailboxes
1818

1919
For Microsoft Teams meetings that are managed by using a shared mailbox, only a limited number of features are available. The following table lists the details of each feature.
2020

2121
> [!NOTE]
22-
> Shared mailboxes aren't intended for direct login. Keep the shared mailbox account in the **Disabled** state, and avoid resetting its password or signing in by using the shared mailbox user account.
22+
23+
> - Keep the shared mailbox account in the **Disabled** state, and avoid resetting its password.
24+
> - Don't sign in by using the credentials of the shared mailbox user account. Only users that the shared mailbox is shared with can log in with their user credentials.
25+
> - To create a Teams meeting in a shared mailbox calendar, a valid Teams license must be assigned either to the shared mailbox or to the user who is logged in to the shared mailbox.
2326
2427
|Available feature|Details|
2528
|----------|-----------|

support/azure/app-service/temporary-storage-for-azure-app-service.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ If an application is reporting high resource consumption, the source of the prob
1313

1414
This video demonstrates how to narrow the scope of your troubleshooting to temporary storage, and the next steps for investigating and troubleshooting performance issues.
1515

16-
> [!VIDEO <https://www.youtube.com/embed/bk8h-VYaIXs>]
16+
> [!VIDEO https://www.youtube.com/embed/bk8h-VYaIXs]
1717
1818
## Related content
1919

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-cloud-tiering.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -328,6 +328,19 @@ This option doesn't require removing the server endpoint but requires sufficient
328328
3. Use the *OrphanTieredFiles.txt* output file to identify orphaned tiered files on the server.
329329
4. Overwrite the orphaned tiered files by copying the full file from the Azure file share to the Windows Server.
330330
331+
## How to identify files that are excluded from File Sync
332+
1. Open a PowerShell window as administrator.
333+
2. Navigate to the folder. Replace `<volume letter>` and `<syncShare>` with the volume letter and sync share names.
334+
```powershell
335+
cd <volume letter>\ <syncShare>\
336+
```
337+
3. Run this command:
338+
```powershell
339+
dir desktop.ini,thumbs.db,ehthumbs.db,~$*.*,*.laccdb,*.tmp -Recurse -Force -File -ErrorAction Ignore
340+
```
341+
342+
Alternatively, you may use the TreeSize tool. The same list of exclusions can be put into the TreeSize 'filters' configuration to count excluded content. The advantage of this approach is that the content which the administrator does not have access to in case of the former approach will be accessible by TreeSize because it uses the backup/restore permissions when scanning content.
343+
331344
## How to troubleshoot files unexpectedly recalled on a server
332345
333346
Antivirus, backup, and other applications that read large numbers of files cause unintended recalls unless they respect the skip offline attribute and skip reading the content of those files. Skipping offline files for products that support this option helps avoid unintended recalls during operations like antivirus scans or backup jobs.

support/windows-client/toc.yml

Lines changed: 13 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1417,6 +1417,16 @@ items:
14171417
href: ./windows-troubleshooters/active-and-retired-troubleshooters-windows-10.md
14181418
- name: Support Tools
14191419
items:
1420+
- name: Performance Monitoring Tools
1421+
items:
1422+
- name: Using Performance Monitor
1423+
href: ../windows-server/support-tools/troubleshoot-issues-performance-monitor.md?context=/troubleshoot/windows-client/context/context
1424+
- name: Using Process Explorer
1425+
href: ../windows-server/support-tools/troubleshoot-issues-process-explorer.md?context=/troubleshoot/windows-client/context/context
1426+
- name: Using Task Manager
1427+
href: ../windows-server/support-tools/support-tools-task-manager.md?context=/troubleshoot/windows-client/context/context
1428+
- name: Using WPR, WPA, or Xperf
1429+
href: ../windows-server/support-tools/support-tools-xperf-wpa-wpr.md?context=/troubleshoot/windows-client/context/context
14201430
- name: TroubleShootingScript toolset (TSS)
14211431
items:
14221432
- name: Introduction to TroubleShootingScript toolset (TSS)
@@ -1437,37 +1447,15 @@ items:
14371447
href: ./windows-tss/collect-data-analyze-troubleshoot-performance-scenarios.md
14381448
- name: Collect data to analyze and troubleshoot Remote Desktop Services scenarios
14391449
href: ./windows-tss/collect-data-analyze-troubleshoot-remote-desktop-services-scenarios.md
1440-
- name: Collect data to analyze and troubleshoot Shell experience scenarios
1450+
- name: Collect data to analyze and troubleshoot shell experience scenarios
14411451
href: ./windows-tss/collect-data-analyze-troubleshoot-shell-experiences-scenarios.md
1452+
- name: Collect data to analyze and troubleshoot Windows servicing, updates, and Features on Demand scenarios
1453+
href: ./windows-tss/collect-data-analyze-troubleshoot-windows-servicing-scenarios.md
14421454
- name: Collect data to analyze and troubleshoot system management components scenarios
14431455
href: ./windows-tss/collect-data-analyze-troubleshoot-sys-management-components-scenarios.md
1444-
- name: Collect data to analyze and troubleshoot Windows servicing, Updates, and Features on Demand scenarios
1445-
href: ./windows-tss/collect-data-analyze-troubleshoot-windows-servicing-scenarios.md
1446-
- name: Gather information for Active Directory replication issues
1447-
href: ./windows-tss/gather-information-using-tss-ad-replication.md
1448-
- name: Gather information for deployment-related issues
1449-
href: ./windows-tss/gather-information-using-tss-deployment.md
1450-
- name: Gather information for Group Policy issues
1451-
href: ./windows-tss/gather-information-using-tss-group-policy.md
14521456
- name: Gather information for Hyper-V related issues
14531457
href: ./windows-tss/gather-information-using-tss-hyper-v-issues.md
14541458
- name: Gather information for SQL cluster (AG/FCI) related issues
14551459
href: ./windows-tss/gather-information-using-tss-sql-cluster-ag-fci-issues.md
1456-
- name: Gather information for user experience-related issues
1457-
href: ./windows-tss/gather-information-using-tss-user-experience.md
1458-
- name: Gather information for Windows failover cluster related issues
1459-
href: ./windows-tss/gather-information-using-tss-windows-failover-cluster-issues.md
1460-
- name: Gather information for Windows Update for Business reports-related issues
1461-
href: ./windows-tss/gather-information-using-tss-wufb-reports.md
14621460
- name: Use the xray feature of TSS
14631461
href: ./windows-tss/use-the-xray-feature-of-tss-to-identify-known-issues.md
1464-
- name: Performance Monitoring Tools
1465-
items:
1466-
- name: Using Performance Monitor
1467-
href: ../windows-server/support-tools/troubleshoot-issues-performance-monitor.md?context=/troubleshoot/windows-client/context/context
1468-
- name: Using Process Explorer
1469-
href: ../windows-server/support-tools/troubleshoot-issues-process-explorer.md?context=/troubleshoot/windows-client/context/context
1470-
- name: Using Task Manager
1471-
href: ../windows-server/support-tools/support-tools-task-manager.md?context=/troubleshoot/windows-client/context/context
1472-
- name: Using WPR, WPA, or Xperf
1473-
href: ../windows-server/support-tools/support-tools-xperf-wpa-wpr.md?context=/troubleshoot/windows-client/context/context

support/windows-client/windows-tss/collect-data-analyze-troubleshoot-active-directory-scenarios.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,7 @@ ms.reviewer: kaushika, traceytu, takarasz, v-lianna,raviks, warrenw
99
ms.custom: sap:Support Tools\TSS, csstroubleshoot
1010
appliesto:
1111
- <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
12+
- <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
1213
---
1314
# Collect data to analyze and troubleshoot Active Directory scenarios
1415

support/windows-client/windows-tss/collect-data-analyze-troubleshoot-group-policy-scenarios.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,7 @@ ms.reviewer: kaushika, traceytu, takarasz, v-lianna, raviks, warrenw
99
ms.custom: sap:Support Tools\TSS, csstroubleshoot
1010
appliesto:
1111
- <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
12+
- <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
1213
---
1314
# Collect data to analyze and troubleshoot Group Policy scenarios
1415

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,7 @@ ms.reviewer: kaushika, traceytu, takarasz, v-lianna, raviks, warrenw
99
ms.custom: sap:Support Tools\TSS, csstroubleshoot
1010
appliesto:
1111
- <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
12+
- <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
1213
---
1314
# Collect data to analyze and troubleshoot system management components scenarios
1415

support/windows-client/windows-tss/collect-data-analyze-troubleshoot-windows-clustering-scenarios.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,7 @@ ms.reviewer: kaushika, traceytu, takarasz, v-lianna, raviks, warrenw
99
ms.custom: sap:Support Tools\TSS, csstroubleshoot
1010
appliesto:
1111
- <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
12+
- <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
1213
---
1314
# Collect data to analyze and troubleshoot clustering and high availability scenarios
1415

0 commit comments

Comments
 (0)