Skip to content

Commit a76fec7

Browse files
v-liannav-lianna
authored
AB#6402 11 articles (#9247)
* AB#6402 11 articles * updates * editing review * updates * updates * update msdate and reviewer
1 parent ca342b4 commit a76fec7

12 files changed

+929
-0
lines changed

‎support/windows-client/toc.yml‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1389,6 +1389,28 @@ items:
13891389
items:
13901390
- name: Introduction to TroubleShootingScript toolset (TSS)
13911391
href: ./windows-tss/introduction-to-troubleshootingscript-toolset-tss.md
1392+
- name: Collect data to analyze and troubleshoot Active Directory scenarios
1393+
href: ./windows-tss/collect-data-analyze-troubleshoot-active-directory-scenarios.md
1394+
- name: Collect data to analyze and troubleshoot application management scenarios
1395+
href: ./windows-tss/collect-data-analyze-troubleshoot-application-management-scenarios.md
1396+
- name: Collect data to analyze and troubleshoot clustering and high availability scenarios
1397+
href: ./windows-tss/collect-data-analyze-troubleshoot-windows-clustering-scenarios.md
1398+
- name: Collect data to analyze and troubleshoot Group Policy scenarios
1399+
href: ./windows-tss/collect-data-analyze-troubleshoot-group-policy-scenarios.md
1400+
- name: Collect data to analyze and troubleshoot licensing and activation scenarios
1401+
href: ./windows-tss/collect-data-analyze-troubleshoot-licensing-activation-scenarios.md
1402+
- name: Collect data to analyze and troubleshoot Windows networking scenarios
1403+
href: ./windows-tss/collect-data-analyze-troubleshoot-windows-networking-scenarios.md
1404+
- name: Collect data to analyze and troubleshoot performance scenarios
1405+
href: ./windows-tss/collect-data-analyze-troubleshoot-performance-scenarios.md
1406+
- name: Collect data to analyze and troubleshoot Remote Desktop Services scenarios
1407+
href: ./windows-tss/collect-data-analyze-troubleshoot-remote-desktop-services-scenarios.md
1408+
- name: Collect data to analyze and troubleshoot Shell experience scenarios
1409+
href: ./windows-tss/collect-data-analyze-troubleshoot-shell-experiences-scenarios.md
1410+
- name: Collect data to analyze and troubleshoot system management components scenarios
1411+
href: ./windows-tss/collect-data-analyze-troubleshoot-sys-management-components-scenarios.md
1412+
- name: Collect data to analyze and troubleshoot Windows servicing, Updates, and Features on Demand scenarios
1413+
href: ./windows-tss/collect-data-analyze-troubleshoot-windows-servicing-scenarios.md
13921414
- name: Gather information for Active Directory replication issues
13931415
href: ./windows-tss/gather-information-using-tss-ad-replication.md
13941416
- name: Gather information for deployment-related issues

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

Lines changed: 97 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,97 @@
1+
---
2+
title: Collect Data to Analyze and Troubleshoot Active Directory Scenarios
3+
description: Helps gather information about your issue by using the TroubleShootingScript (TSS) toolset and learn what data to collect based on Active Directory scenarios.
4+
ms.date: 07/22/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika, traceytu, takarasz, v-lianna，raviks, warrenw
9+
ms.custom: sap:Support Tools\TSS, csstroubleshoot
10+
---
11+
# Collect data to analyze and troubleshoot Active Directory scenarios
12+
13+
This article helps you gather information about your issue by using the TroubleShootingScript (TSS) toolset before contacting Microsoft support.
14+
15+
## Prerequisites
16+
17+
Refer to [Introduction to TroubleShootingScript toolset (TSS)](introduction-to-troubleshootingscript-toolset-tss.md#prerequisites) for prerequisites for the toolset to run properly.
18+
19+
## Scenario: Active Directory replication and topology
20+
21+
### TSS cmdlet
22+
23+
Client:
24+
25+
```powershell
26+
.\TSS.ps1 -Scenario ADS_AuthEx
27+
```
28+
29+
Server (domain controller (DC)):
30+
31+
```powershell
32+
.\TSS.ps1 -Scenario ADS_Auth
33+
```
34+
35+
### TSS cmdlet description
36+
37+
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`.
38+
39+
## Scenario: Active Directory Certificate Services (ADCS)
40+
41+
### TSS cmdlet
42+
43+
Client:
44+
45+
```powershell
46+
.\TSS.ps1 -Scenario ADS_AuthEx
47+
```
48+
49+
Server:
50+
51+
```powershell
52+
.\TSS.ps1 -Start -ADS_ADCS
53+
```
54+
55+
### TSS cmdlet description
56+
57+
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.
58+
59+
## Scenario: Authentication issues (Kerberos and New Technology LAN Manager (NTLM))
60+
61+
### TSS cmdlet
62+
63+
Client:
64+
65+
```powershell
66+
.\TSS.ps1 -Scenario ADS_AuthEx
67+
```
68+
69+
Server:
70+
71+
```powershell
72+
.\TSS.ps1 -Scenario ADS_Auth
73+
```
74+
75+
### TSS cmdlet description
76+
77+
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.
78+
79+
## Scenario: Domain join
80+
81+
### TSS cmdlet
82+
83+
Client:
84+
85+
```powershell
86+
.\TSS.ps1 -Scenario ADS_AuthEx
87+
```
88+
89+
Server:
90+
91+
```powershell
92+
.\TSS.ps1 -Scenario ADS_Auth
93+
```
94+
95+
### TSS cmdlet description
96+
97+
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‎

Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,89 @@
1+
---
2+
title: Collect Data to Analyze and Troubleshoot Application Management Scenarios
3+
description: Helps gather information about your issue by using the TroubleShootingScript (TSS) toolset and learn what data to collect based on application management scenarios.
4+
ms.date: 07/22/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika, traceytu, takarasz, v-lianna, raviks, warrenw
9+
ms.custom: sap:Support Tools\TSS, csstroubleshoot
10+
---
11+
# Collect data to analyze and troubleshoot application management scenarios
12+
13+
This article helps gather information about your issue by using the TroubleShootingScript (TSS) toolset before contacting Microsoft support.
14+
15+
## Prerequisites
16+
17+
Refer to [Introduction to TroubleShootingScript toolset (TSS)](introduction-to-troubleshootingscript-toolset-tss.md#prerequisites) for prerequisites for the toolset to run properly.
18+
19+
## Scenario: Modern, Inbox, and Microsoft Store apps
20+
21+
### TSS cmdlet
22+
23+
```powershell
24+
.\TSS.ps1 -Scenario PRF_UWP
25+
```
26+
27+
### TSS cmdlet description
28+
29+
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.
30+
31+
## Scenario: Microsoft Store
32+
33+
### TSS cmdlet
34+
35+
```powershell
36+
.\TSS.ps1 -Scenario PRF_Store
37+
```
38+
39+
### TSS cmdlet description
40+
41+
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.
42+
43+
## Scenario: WinGet
44+
45+
### TSS cmdlet
46+
47+
```powershell
48+
.\TSS.ps1 -Scenario PRF_WinGet
49+
```
50+
51+
### TSS cmdlet description
52+
53+
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.
54+
55+
## Scenario: Photos app
56+
57+
### TSS cmdlet
58+
59+
```powershell
60+
.\TSS.ps1 -Scenario PRF_Photo
61+
```
62+
63+
### TSS cmdlet description
64+
65+
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.
66+
67+
## Scenario: Clipboard and copy/paste
68+
69+
### TSS cmdlet
70+
71+
```powershell
72+
.\TSS.ps1 -Scenario PRF_Clipboard
73+
```
74+
75+
### TSS cmdlet description
76+
77+
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).
78+
79+
## Scenario: Camera problems
80+
81+
### TSS cmdlet
82+
83+
```powershell
84+
.\TSS.ps1 -Scenario PRF_MediaCamera
85+
```
86+
87+
### TSS cmdlet description
88+
89+
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‎

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
title: Collect Data to Analyze and Troubleshoot Group Policy Scenarios
3+
description: Helps gather information about your issue by using the TroubleShootingScript (TSS) toolset and learn what data to collect based on Group Policy scenarios.
4+
ms.date: 07/22/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika, traceytu, takarasz, v-lianna, raviks, warrenw
9+
ms.custom: sap:Support Tools\TSS, csstroubleshoot
10+
---
11+
# Collect data to analyze and troubleshoot Group Policy scenarios
12+
13+
This article helps gather information about your issue by using the TroubleShootingScript (TSS) toolset before contacting Microsoft support.
14+
15+
## Prerequisites
16+
17+
Refer to [Introduction to TroubleShootingScript toolset (TSS)](introduction-to-troubleshootingscript-toolset-tss.md#prerequisites) for prerequisites for the toolset to run properly.
18+
19+
## Scenario: Issues applying Group Policy
20+
21+
### TSS cmdlet
22+
23+
Client:
24+
25+
```powershell
26+
.\TSS.ps1 -Scenario ADS_AuthEx
27+
```
28+
29+
Server (domain controller):
30+
31+
```powershell
32+
.\TSS.ps1 -Scenario ADS_Auth
33+
```
34+
35+
### TSS cmdlet description
36+
37+
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.

‎support/windows-client/windows-tss/collect-data-analyze-troubleshoot-licensing-activation-scenarios.md‎

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
title: Collect Data to Analyze and Troubleshoot Licensing and Activation Scenarios
3+
description: Helps gather information about your issue by using the TroubleShootingScript (TSS) toolset and learn what data to collect based on licensing and activation scenarios.
4+
ms.date: 07/22/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika, traceytu, takarasz, v-lianna, raviks, warrenw
9+
ms.custom: sap:Support Tools\TSS, csstroubleshoot
10+
---
11+
# Collect data to analyze and troubleshoot licensing and activation scenarios
12+
13+
This article helps gather information about your issue by using the TroubleShootingScript (TSS) toolset before contacting Microsoft support.
14+
15+
## Prerequisites
16+
17+
Refer to [Introduction to TroubleShootingScript toolset (TSS)](introduction-to-troubleshootingscript-toolset-tss.md#prerequisites) for prerequisites for the toolset to run properly.
18+
19+
## Scenario: Windows volume activation
20+
21+
### TSS cmdlet
22+
23+
```powershell
24+
.\TSS.ps1 -CollectLog DND_SETUPReport
25+
```
26+
27+
### TSS cmdlet description
28+
29+
Use this scenario when Windows fails to activate. Run this cmdlet on the machine that is experiencing the activation failure. The `DND_SETUPReport` collects detailed logs including component-based servicing (CBS), Windows Update, and servicing logs to help identify root causes such as component corruption, servicing stack issues, or policy misconfigurations.

0 commit comments

Comments
 (0)