Merge pull request #9384 from MicrosoftDocs/main

Auto push to live 2025-07-22 02:40:29

Author: Simonx Xu

Microsoft365/purview/ediscovery/resolve-ediscovery-issues.md

@@ -46,7 +46,7 @@ When you view the search result statistics in the *Export Summary \<timestamp\>.
 
 An estimate of the search results is just that: It's an estimate and not an actual count of items that meet the search query criteria. For more information about why estimated and downloaded search results can differ, see [Differences between estimated and actual eDiscovery search results](/microsoft-365/compliance/ediscovery-differences-between-estimated-and-actual-search-results).
 
-[Back to top](#resolve-search-errors-in-ediscovery-standard)
+[Back to top](#resolve-search-errors-in-ediscovery)
 
 ## Search error: "Location is ambiguous"
 
@@ -58,7 +58,7 @@ When you run an [eDiscovery search](/microsoft-365/compliance/ediscovery-search-
 
 ### Cause
 
-The locations specified in the error message are invalid. The mailbox identifier for each invalid location is used by duplicate or conflicting objects in Exchange Online Protection (EOP).
+The locations that are specified in the error message are invalid. The mailbox identifier for each invalid location is used by duplicate or conflicting objects in Exchange Online Protection (EOP).
 
 ### Resolution
 
@@ -74,7 +74,7 @@ For each invalid location, follow these steps:
 
 3. Remove the duplicate or conflicting object.
 
-[Back to top](#resolve-search-errors-in-ediscovery-standard)
+[Back to top](#resolve-search-errors-in-ediscovery)
 
 ## Search error: "Recipient not found"
 
@@ -100,7 +100,7 @@ The system can't find one of the [recipients](/powershell/module/exchange/new-ma
 
 4. After you verify that the recipient is synced in EOP, retry your search.
 
-[Back to top](#resolve-search-errors-in-ediscovery-standard)
+[Back to top](#resolve-search-errors-in-ediscovery)
 
 ## Search error: CS007
 
@@ -134,7 +134,7 @@ Your [eDiscovery search](/microsoft-365/compliance/ediscovery-search-for-content
 
 Retry your search. If your search still fails, split your search into smaller searches. For example, use date ranges or limit the number of search locations to return smaller result sets.
 
-[Back to top](#resolve-search-errors-in-ediscovery-standard)
+[Back to top](#resolve-search-errors-in-ediscovery)
 
 ## Search or export error: "Maximum number of jobs for your organization are currently running"
 
@@ -187,7 +187,7 @@ To resolve the error, use the following procedure:
 
 2. Retry your search or export operation.
 
-[Back to top](#resolve-search-errors-in-ediscovery-standard)
+[Back to top](#resolve-search-errors-in-ediscovery)
 
 ## Export error: "Item has been moved or deleted" or "Unable to retrieve item due to timeout"
 
@@ -207,7 +207,7 @@ These "FailedToExportItem" error messages indicate that the system didn't export
 
 Wait for the system to retrieve and export the original mailbox items that are associated with the temporary backups.
 
-[Back to top](#resolve-search-errors-in-ediscovery-standard)
+[Back to top](#resolve-search-errors-in-ediscovery)
 
 ## Export error: "File wasn't exported because it doesn't exist" or "File not found"
 
@@ -227,7 +227,7 @@ You might see this error message if the eDiscovery search includes Microsoft Sha
 
 To resolve the issue, reindex the SharePoint Online or OneDrive for Business location by using one of the procedures that are provided in [Manually request crawling and reindexing of a site, a library or a list](/sharepoint/crawl-site-content). If you want the search results to include the renamed or moved files, rerun the eDiscovery search.
 
-[Back to top](#resolve-search-errors-in-ediscovery-standard)
+[Back to top](#resolve-search-errors-in-ediscovery)
 
 ## Export download issue: eDiscovery export doesn't download any files
 
@@ -247,7 +247,7 @@ The issue can occur for any of the following reasons:
 
 If you're experiencing issues that affect the download, see [Best practices for downloading export packages](/purview/edisc-search-export).
 
-[Back to top](#resolve-search-errors-in-ediscovery-standard)
+[Back to top](#resolve-search-errors-in-ediscovery)
 
 ## Export download error: "Search result was not downloaded as it is a folder"
 
@@ -265,4 +265,4 @@ You might see this error message if your search includes Microsoft SharePoint On
 
 No resolution is required. You can safely ignore the error message.
 
-[Back to top](#resolve-search-errors-in-ediscovery-standard)
+[Back to top](#resolve-search-errors-in-ediscovery)

support/power-platform/power-automate/desktop-flows/office-automation/excel/troubleshoot-excel-errors.md

@@ -1,14 +1,15 @@
 ---
-title: Errors when running desktop flows including Excel actions
+title: Errors when running desktop flows that include Excel actions
 description: Provides mitigation steps for errors generated by Excel actions in desktop flows.
 ms.author: iomavrid
 author: yiannismavridis
-ms.date: 07/21/2025
+ms.reviewer: amitrou, nimoutzo
+ms.date: 07/22/2025
 ms.custom: sap:Desktop flows\Office automation
 ---
-# Errors when running desktop flows, including Excel actions
+# Errors when running desktop flows that include Excel actions
 
-This article provides mitigation steps for errors generated by [Excel actions](/power-automate/desktop-flows/actions-reference/excel) in desktop flows. Most errors occur in the context of multiple Excel actions, and there's no strict mapping between them.
+This article outlines steps to mitigate errors that might occur when using [Excel actions](/power-automate/desktop-flows/actions-reference/excel) in Power Automate desktop flows. Some of these errors might occur when you try to open a blank or existing Excel file using the **Launch Excel** action. Most errors occur in the context of multiple Excel actions, and there's no one-to-one mapping between specific errors and actions.
 
 ## More information
 

support/power-platform/power-automate/toc.yml

@@ -74,7 +74,7 @@
       items:
         - name: Excel
           items:
-            - name: Errors when running desktop flows including Excel actions
+            - name: Errors when running desktop flows that include Excel actions
               href: desktop-flows/office-automation/excel/troubleshoot-excel-errors.md
         - name: Outlook
           items:

support/windows-client/toc.yml

@@ -1389,6 +1389,28 @@ items:
     items:
     - name: Introduction to TroubleShootingScript toolset (TSS)
       href: ./windows-tss/introduction-to-troubleshootingscript-toolset-tss.md
+    - name: Collect data to analyze and troubleshoot Active Directory scenarios
+      href: ./windows-tss/collect-data-analyze-troubleshoot-active-directory-scenarios.md
+    - name: Collect data to analyze and troubleshoot application management scenarios
+      href: ./windows-tss/collect-data-analyze-troubleshoot-application-management-scenarios.md
+    - name: Collect data to analyze and troubleshoot clustering and high availability scenarios
+      href: ./windows-tss/collect-data-analyze-troubleshoot-windows-clustering-scenarios.md
+    - name: Collect data to analyze and troubleshoot Group Policy scenarios
+      href: ./windows-tss/collect-data-analyze-troubleshoot-group-policy-scenarios.md
+    - name: Collect data to analyze and troubleshoot licensing and activation scenarios
+      href: ./windows-tss/collect-data-analyze-troubleshoot-licensing-activation-scenarios.md
+    - name: Collect data to analyze and troubleshoot Windows networking scenarios
+      href: ./windows-tss/collect-data-analyze-troubleshoot-windows-networking-scenarios.md
+    - name: Collect data to analyze and troubleshoot performance scenarios
+      href: ./windows-tss/collect-data-analyze-troubleshoot-performance-scenarios.md
+    - name: Collect data to analyze and troubleshoot Remote Desktop Services scenarios
+      href: ./windows-tss/collect-data-analyze-troubleshoot-remote-desktop-services-scenarios.md
+    - name: Collect data to analyze and troubleshoot Shell experience scenarios
+      href: ./windows-tss/collect-data-analyze-troubleshoot-shell-experiences-scenarios.md
+    - name: Collect data to analyze and troubleshoot system management components scenarios
+      href: ./windows-tss/collect-data-analyze-troubleshoot-sys-management-components-scenarios.md
+    - name: Collect data to analyze and troubleshoot Windows servicing, Updates, and Features on Demand scenarios
+      href: ./windows-tss/collect-data-analyze-troubleshoot-windows-servicing-scenarios.md
     - name: Gather information for Active Directory replication issues
       href: ./windows-tss/gather-information-using-tss-ad-replication.md
     - name: Gather information for deployment-related issues

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

@@ -0,0 +1,97 @@
+---
+title: Collect Data to Analyze and Troubleshoot Active Directory Scenarios
+description: Helps gather information about your issue by using the TroubleShootingScript (TSS) toolset and learn what data to collect based on Active Directory scenarios.
+ms.date: 07/22/2025
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika, traceytu, takarasz, v-lianna，raviks, warrenw
+ms.custom: sap:Support Tools\TSS, csstroubleshoot
+---
+# Collect data to analyze and troubleshoot Active Directory scenarios
+
+This article helps you gather information about your issue by using the TroubleShootingScript (TSS) toolset before contacting Microsoft support.
+
+## Prerequisites
+
+Refer to [Introduction to TroubleShootingScript toolset (TSS)](introduction-to-troubleshootingscript-toolset-tss.md#prerequisites) for prerequisites for the toolset to run properly.
+
+## Scenario: Active Directory replication and topology
+
+### TSS cmdlet
+
+Client:
+
+```powershell
+.\TSS.ps1 -Scenario ADS_AuthEx
+```
+
+Server (domain controller (DC)):
+
+```powershell
+.\TSS.ps1 -Scenario ADS_Auth
+```
+
+### TSS cmdlet description
+
+Run this cmdlet on both the source and destination DCs to gather data at the same time. Begin logging on both DCs using the TSS cmdlet and reproduce the issue by initiating replication with the [repadmin /replicate](/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/cc742152(v=ws.11)) cmdlet. For example, `repadmin /replicate dest-dc01 source-dc01 DC=contoso,DC=com`.
+
+## Scenario: Active Directory Certificate Services (ADCS)
+
+### TSS cmdlet
+
+Client:
+
+```powershell
+.\TSS.ps1 -Scenario ADS_AuthEx
+```
+
+Server:
+
+```powershell
+.\TSS.ps1 -Start -ADS_ADCS
+```
+
+### TSS cmdlet description
+
+Depending on the issue or scenario, you can run this cmdlet only on the ADCS server, the client, or both. Begin logging using the TSS cmdlet and reproduce the issue.
+
+## Scenario: Authentication issues (Kerberos and New Technology LAN Manager (NTLM))
+
+### TSS cmdlet
+
+Client:
+
+```powershell
+.\TSS.ps1 -Scenario ADS_AuthEx
+```
+
+Server:
+
+```powershell
+.\TSS.ps1 -Scenario ADS_Auth
+```
+
+### TSS cmdlet description
+
+Depending on the specific issue or scenario, you might need to gather data from the client, the server, and the DC, or from all three sources. For thorough troubleshooting, it's important to obtain data from all three sources. However, if you can't retrieve logs from the DC, you can continue logging on the client and server with the TSS cmdlet, and reproduce the issue.
+
+## Scenario: Domain join
+
+### TSS cmdlet
+
+Client:
+
+```powershell
+.\TSS.ps1 -Scenario ADS_AuthEx
+```
+
+Server:
+
+```powershell
+.\TSS.ps1 -Scenario ADS_Auth
+```
+
+### TSS cmdlet description
+
+Depending on the specific issue or scenario, you might need to gather data from the client and the DC. However, if you can't retrieve logs from the DC, you can continue logging on the client with the TSS cmdlet, and reproduce the issue.

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

@@ -0,0 +1,89 @@
+---
+title: Collect Data to Analyze and Troubleshoot Application Management Scenarios
+description: Helps gather information about your issue by using the TroubleShootingScript (TSS) toolset and learn what data to collect based on application management scenarios.
+ms.date: 07/22/2025
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika, traceytu, takarasz, v-lianna, raviks, warrenw
+ms.custom: sap:Support Tools\TSS, csstroubleshoot
+---
+# Collect data to analyze and troubleshoot application management scenarios
+
+This article helps gather information about your issue by using the TroubleShootingScript (TSS) toolset before contacting Microsoft support.
+
+## Prerequisites
+
+Refer to [Introduction to TroubleShootingScript toolset (TSS)](introduction-to-troubleshootingscript-toolset-tss.md#prerequisites) for prerequisites for the toolset to run properly.
+
+## Scenario: Modern, Inbox, and Microsoft Store apps
+
+### TSS cmdlet
+
+```powershell
+.\TSS.ps1 -Scenario PRF_UWP
+```
+
+### TSS cmdlet description
+
+The `PRF_UWP` scenario is useful for troubleshooting problems with Inbox applications (Appx or Modern apps), the Start menu, and the Shell. For example, Universal Windows Platform (UWP) apps (such as Settings, Calculator, and Microsoft Store) don't launch or crash. This scenario also applies to issues where AppX package registration fails, or UWP apps are slow or unresponsive.
+
+## Scenario: Microsoft Store
+
+### TSS cmdlet
+
+```powershell
+.\TSS.ps1 -Scenario PRF_Store
+```
+
+### TSS cmdlet description
+
+The `PRF_Store` scenario is useful for troubleshooting installation problems with Inbox applications (Appx or Modern apps). For example, Microsoft Store doesn't open, crashes, hangs, or fails to install or update apps. This scenario also applies to issues where app deployments that rely on the Microsoft Store infrastructure fail, or where Microsoft Store apps don't appear in the Start menu or Company Portal.
+
+## Scenario: WinGet
+
+### TSS cmdlet
+
+```powershell
+.\TSS.ps1 -Scenario PRF_WinGet
+```
+
+### TSS cmdlet description
+
+The `PRF_WinGet` scenario is useful for troubleshooting issues with WinGet cmdlets failing or hanging. This scenario also applies to issues where the installating or upgrading apps via WinGet isn't working, or issues with the Microsoft Store integration in WinGet.
+
+## Scenario: Photos app
+
+### TSS cmdlet
+
+```powershell
+.\TSS.ps1 -Scenario PRF_Photo
+```
+
+### TSS cmdlet description
+
+The `PRF_Photo` scenario is useful for troubleshooting problems such as the Photos app not opening, crashing, or freezing. It also applies to issues where images fail to render or load slowly, or issues with editing, saving, or sharing photos.
+
+## Scenario: Clipboard and copy/paste
+
+### TSS cmdlet
+
+```powershell
+.\TSS.ps1 -Scenario PRF_Clipboard
+```
+
+### TSS cmdlet description
+
+The `PRF_Clipboard` scenario can help diagnose issues where the clipboard functionality is degraded or broken. Examples include copy/paste failing intermittently or stopping working entirely. This scenario also applies to issues where clipboard operations are slow or hang (for example, Snipping Tool delays).
+
+## Scenario: Camera problems
+
+### TSS cmdlet
+
+```powershell
+.\TSS.ps1 -Scenario PRF_MediaCamera
+```
+
+### TSS cmdlet description
+
+The `PRF_MediaCamera` scenario is useful for troubleshooting problems such as the camera not being detected or not working in apps like Teams, Zoom, or Camera. You might see a message like "No camera found" or an error code when launching the Camera app, or encounter a black screen or frozen video feed during video calls.

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

@@ -0,0 +1,37 @@
+---
+title: Collect Data to Analyze and Troubleshoot Group Policy Scenarios
+description: Helps gather information about your issue by using the TroubleShootingScript (TSS) toolset and learn what data to collect based on Group Policy scenarios.
+ms.date: 07/22/2025
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika, traceytu, takarasz, v-lianna, raviks, warrenw
+ms.custom: sap:Support Tools\TSS, csstroubleshoot
+---
+# Collect data to analyze and troubleshoot Group Policy scenarios
+
+This article helps gather information about your issue by using the TroubleShootingScript (TSS) toolset before contacting Microsoft support.
+
+## Prerequisites
+
+Refer to [Introduction to TroubleShootingScript toolset (TSS)](introduction-to-troubleshootingscript-toolset-tss.md#prerequisites) for prerequisites for the toolset to run properly.
+
+## Scenario: Issues applying Group Policy
+
+### TSS cmdlet
+
+Client:
+
+```powershell
+.\TSS.ps1 -Scenario ADS_AuthEx
+```
+
+Server (domain controller):
+
+```powershell
+.\TSS.ps1 -Scenario ADS_Auth
+```
+
+### TSS cmdlet description
+
+Depending on the specific issue or scenario, you might need to gather data from the client and the domain controller. However, if you can't retrieve logs from the domain controller, you can continue logging on the client with the TSS cmdlet and reproduce the issue.