Skip to content

Commit 05bc8a0

Browse files
v-tappelgatev-tappelgate
committed
Revert "Removed old files"
This reverts commit 05eb1bb.
1 parent 3034f76 commit 05bc8a0

6 files changed

Lines changed: 303 additions & 0 deletions

‎support/windows-client/windows-tss/gather-information-using-tss-ad-replication.md‎

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
title: Gather information by using TSS for Active Directory replication issues
3+
description: Introduces how to gather information by using the TroubleShootingScript (TSS) toolset for Active Directory replication issues.
4+
ms.date: 01/21/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika, warrenw, v-lianna
9+
ms.custom: sap:Support Tools\TSS DS, csstroubleshoot
10+
appliesto:
11+
- <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
12+
---
13+
# Gather information by using TSS for Active Directory replication issues
14+
15+
This article introduces how to gather information by using the TroubleShootingScript (TSS) toolset for Active Directory replication issues.
16+
17+
Before contacting Microsoft support, you can gather information about your issue.
18+
19+
## Prerequisites
20+
21+
Refer to [Introduction to TroubleShootingScript toolset (TSS)](introduction-to-troubleshootingscript-toolset-tss.md#prerequisites) for prerequisites for the toolset to run properly.
22+
23+
## Gather key information before contacting Microsoft support
24+
25+
1. Download [TSS](https://aka.ms/getTSS) and extract it in the *C:\\tss* folder.
26+
2. Open the *C:\\tss* folder from an elevated PowerShell command prompt.
27+
> [!NOTE]
28+
> Don't use the Windows PowerShell Integrated Scripting Environment (ISE).
29+
3. Run the following cmdlets:
30+
31+
```powershell
32+
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
33+
```
34+
35+
```powershell
36+
.\TSS.ps1 -Scenario ADS_Replication -noProcmon -noPSR -noVideo
37+
```
38+
39+
4. Enter *A* for "Yes to All" for the execution policy change.
40+
41+
> [!NOTE]
42+
>
43+
> - The traces are stored in a compressed file in the *C:\\MS_DATA* folder. After a support case is created, this file can be uploaded to the secure workspace for analysis.
44+
> - If you've downloaded this tool previously, we recommend downloading the latest version. It doesn't automatically update when running `-Scenario ADS_Replication -noProcmon -noPSR -noVideo`.

‎support/windows-client/windows-tss/gather-information-using-tss-deployment.md‎

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
title: Gather information by using TSS for deployment-related issues
3+
description: Introduces how to gather information by using the TroubleShootingScript (TSS) toolset for deployment-related issues.
4+
ms.date: 01/15/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika, warrenw, v-lianna
9+
ms.custom: sap:Support Tools\TSS DnD, csstroubleshoot
10+
appliesto:
11+
- <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
12+
---
13+
# Gather information by using TSS for deployment-related issues
14+
15+
This article introduces how to gather information by using the TroubleShootingScript (TSS) toolset for deployment-related issues.
16+
17+
Before contacting Microsoft support, you can gather information about your issue.
18+
19+
## Prerequisites
20+
21+
Refer to [Introduction to TroubleShootingScript toolset (TSS)](introduction-to-troubleshootingscript-toolset-tss.md#prerequisites) for prerequisites for the toolset to run properly.
22+
23+
## Gather key information before contacting Microsoft support
24+
25+
1. Download [TSS](https://aka.ms/getTSS) and extract it in the *C:\\tss* folder.
26+
2. Open the *C:\\tss* folder from an elevated PowerShell command prompt.
27+
> [!NOTE]
28+
> Don't use the Windows PowerShell Integrated Scripting Environment (ISE).
29+
3. Run the following cmdlets:
30+
31+
```powershell
32+
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
33+
```
34+
35+
```powershell
36+
.\TSS.ps1 -Collectlog DND_SetupReport
37+
```
38+
39+
4. Enter *A* for "Yes to All" for the execution policy change.
40+
41+
> [!NOTE]
42+
>
43+
> - The traces are stored in a compressed file in the *C:\\MS_DATA* folder. After a support case is created, this file can be uploaded to the secure workspace for analysis.
44+
> - If you've downloaded this tool previously, we recommend downloading the latest version. It doesn't automatically update when running `-Collectlog DND_SetupReport`.

‎support/windows-client/windows-tss/gather-information-using-tss-group-policy.md‎

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
title: Gather information by using TSS for Group Policy issues
3+
description: Introduces how to gather information by using the TroubleShootingScript (TSS) toolset for Group Policy issues.
4+
ms.date: 01/15/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika, warrenw, v-lianna
9+
ms.custom: sap:Support Tools\TSS DS, csstroubleshoot
10+
appliesto:
11+
- <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
12+
---
13+
# Gather information by using TSS for Group Policy issues
14+
15+
This article introduces how to gather information by using the TroubleShootingScript (TSS) toolset for Group Policy issues.
16+
17+
Before contacting Microsoft support, you can gather information about your issue.
18+
19+
## Prerequisites
20+
21+
Refer to [Introduction to TroubleShootingScript toolset (TSS)](introduction-to-troubleshootingscript-toolset-tss.md#prerequisites) for prerequisites for the toolset to run properly.
22+
23+
## Gather key information before contacting Microsoft support
24+
25+
1. Download [TSS](https://aka.ms/getTSS) and extract it in the *C:\\tss* folder.
26+
2. Open the *C:\\tss* folder from an elevated PowerShell command prompt.
27+
> [!NOTE]
28+
> Don't use the Windows PowerShell Integrated Scripting Environment (ISE).
29+
3. Run the following cmdlets:
30+
31+
```powershell
32+
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
33+
```
34+
35+
```powershell
36+
.\TSS.ps1 -Scenario ADS_GPOEx -ADS_GPedit -ADS_GPmgmt -ADS_GPO -ADS_GPsvc -GPresult Both
37+
```
38+
39+
4. Enter *A* for "Yes to All" for the execution policy change.
40+
41+
> [!NOTE]
42+
>
43+
> - The traces are stored in a compressed file in the *C:\\MS_DATA* folder. After a support case is created, this file can be uploaded to the secure workspace for analysis.
44+
> - If you've downloaded this tool previously, we recommend downloading the latest version. It doesn't automatically update when running.

‎support/windows-client/windows-tss/gather-information-using-tss-user-experience.md‎

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
title: Gather information by using TSS for user experience-related issues
3+
description: Introduces how to gather information by using the TroubleShootingScript (TSS) toolset for user experience-related issues.
4+
ms.date: 01/15/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika, warrenw, v-lianna
9+
ms.custom: sap:Support Tools\TSS UEX, csstroubleshoot
10+
appliesto:
11+
- <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
12+
---
13+
# Gather information by using TSS for user experience-related issues
14+
15+
This article introduces how to gather information by using the TroubleShootingScript (TSS) toolset for user experience-related issues.
16+
17+
Before contacting Microsoft support, you can gather information about your issue.
18+
19+
## Prerequisites
20+
21+
Refer to [Introduction to TroubleShootingScript toolset (TSS)](introduction-to-troubleshootingscript-toolset-tss.md#prerequisites) for prerequisites for the toolset to run properly.
22+
23+
## Gather key information before contacting Microsoft support
24+
25+
1. Download [TSS](https://aka.ms/getTSS) and extract it in the *C:\\tss* folder. If you've downloaded this tool previously, we recommend downloading the latest version. It doesn't automatically update when running.
26+
2. Open the *C:\\tss* folder from an elevated PowerShell command prompt.
27+
> [!NOTE]
28+
> Don't use the Windows PowerShell Integrated Scripting Environment (ISE).
29+
3. Run the following cmdlet and enter *A* for "Yes to All" for the execution policy change.
30+
31+
```powershell
32+
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
33+
```
34+
35+
Then, run the cmdlets that are listed in the following table according to your issue. The traces are stored in a compressed file in the *C:\\MS_DATA* folder. After a support case is created, this file can be uploaded to the secure workspace for analysis.
36+
37+
|Issues |Cmdlet(s) |
38+
|---------|---------|
39+
|<a id="remote-desktop-session"></a>Remote Desktop session issues |`.\TSS.ps1 -Scenario UEX_General -UEX_Auth -UEX_Logon` |
40+
|<a id="terminal-server-licensing"></a>Terminal Server licensing issues |`.\TSS.ps1 -UEX_RDS -Netsh -UEX_Logon -UEX_EVT -UEX_Auth -UEX_WMI -UEX_WinRM` |
41+
|<a id="remote-desktop-session-connectivity"></a>Remote Desktop Session (RDS) connectivity issues |`.\TSS.ps1 -UEX_RDS -Netsh -UEX_Logon -UEX_EVT -UEX_Auth` |
42+
|<a id="printing"></a>Printing issues |`.\TSS.ps1 -UEX_Print -Procmon -Netsh -PSR` |
43+
|<a id="remote-desktop-disconnection"></a>Remote Desktop disconnection issues |`.\TSS.ps1 -CollectLog UEX_EventLog`<br>`.\TSS.ps1 -Scenario UEX_General`|
44+
|<a id="remote-desktop-disconnection-configuration"></a>Remote Desktop connection configuration issues |`.\TSS.ps1 -Scenario UEX_ServerManager -UEX_WMI -UEX_RDS -UEX_ServerManager -UEX_WinRM` |
45+
|<a id="wmi"></a>WMI issues |`.\TSS.ps1 -Scenario UEX_WMIHighCPU` (with high CPU usage)<br>`.\TSS.ps1 -Scenario UEX_WMI` (without high CPU usage) |
46+
|<a id="remote-desktop-client-connection"></a>Remote Desktop Client connection issues |`.\TSS.ps1 -CollectLog -UEX_Basic -UEX_RDS -UEX_WinRM -UEX_WMI` |
47+
|<a id="winrm"></a>WinRM issues |`.\TSS.ps1 -Scenario UEX_WinRM` |
48+
|<a id="powershell"></a>PowerShell issues |`.\TSS.ps1 -Collectlog NET_PowerShell`<br>`.\TSS.ps1 -Scenario UEX_PowerShell`|

‎support/windows-client/windows-tss/gather-information-using-tss-windows-failover-cluster-issues.md‎

Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
---
2+
title: Gather information by using TSS for Windows failover cluster related issues
3+
description: Introduces how to gather information by using TSS for Windows failover cluster related issues.
4+
ms.date: 01/15/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika, warrenw, v-lianna
9+
ms.custom: sap:Support Tools\TSS SHA, csstroubleshoot
10+
appliesto:
11+
- <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
12+
---
13+
# Gather information by using TSS for Windows failover cluster related issues
14+
15+
This article introduces how to gather information by using the TroubleShootingScript (TSS) toolset for Windows failover cluster related issues.
16+
17+
Before contacting Microsoft support, you can gather information about your issue.
18+
19+
## Prerequisites
20+
21+
Refer to [Introduction to TroubleShootingScript toolset (TSS)](introduction-to-troubleshootingscript-toolset-tss.md#prerequisites) for prerequisites for the toolset to run properly.
22+
23+
## Gather key information before contacting Microsoft support
24+
25+
1. Download [TSS](https://aka.ms/getTSS) and extract it in the *C:\\tss* folder.
26+
2. Open the *C:\\tss* folder from an elevated PowerShell command prompt.
27+
> [!NOTE]
28+
> Don't use the Windows PowerShell Integrated Scripting Environment (ISE).
29+
3. Run the following cmdlets:
30+
31+
```powershell
32+
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
33+
```
34+
35+
```powershell
36+
.\TSS.ps1 -SDP Cluster
37+
```
38+
39+
4. Enter *A* for "Yes to All" for the execution policy change.
40+
41+
> [!NOTE]
42+
>
43+
> - The time to collect this script on a given system may vary. It depends on system speed, system size, the number of virtual machines, the amount of data in logs, and so on. Depending on these factors, the average collection time is between 30 and 90 minutes, or even longer, especially if no skip commands are used.
44+
> - The collection is stored in a compressed file in the *C:\\MS_DATA* folder. After a support case is created, this file can be uploaded to the secure workspace for analysis.
45+
46+
## Optional parameters
47+
48+
Some parameters are optional to perform a quicker and more streamlined collection, which may help the script finish successfully if a certain section stops responding.
49+
50+
- This cmdlet skips running the Best Practices Analyzer and makes the collection faster.
51+
52+
```powershell
53+
.\TSS.ps1 -SDP Cluster -SkipSDPList skipBPA
54+
```
55+
56+
- This cmdlet skips some small collection items that may fail in a regular collection and makes the script more reliable.
57+
58+
```powershell
59+
.\TSS.ps1 -SDP Cluster -SkipSDPList skipHang
60+
```
61+
62+
- This cmdlet skips some additional collection parameters that may not be needed.
63+
64+
```powershell
65+
.\TSS.ps1 -SDP Cluster -SkipSDPList skipTS
66+
```
67+
68+
- This cmdlet skips testing Server Message Block (SMB) connectivity to any Cluster Shared Volumes (CSVs) in the failover cluster.
69+
70+
```powershell
71+
.\TSS.ps1 -SDP Cluster -SkipSDPList skipCsvSMB
72+
```
73+
74+
> [!NOTE]
75+
> You can combine multiple skip parameters with comma-separated items, such as the following example:
76+
>
77+
> ```powershell
78+
> .\TSS.ps1 -SDP Cluster -SkipSDPList skipBPA,skipHang,skipTS,skipCsvSMB
79+
> ```

‎support/windows-client/windows-tss/gather-information-using-tss-wufb-reports.md‎

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
title: Gather information by using TSS for Windows Update for Business reports-related issues
3+
description: Introduces how to gather information by using the TroubleShootingScript (TSS) toolset for Windows Update for Business reports-related issues.
4+
ms.date: 01/15/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika, warrenw, v-lianna
9+
ms.custom: sap:Support Tools\TSS DnD, csstroubleshoot
10+
appliesto:
11+
- <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
12+
---
13+
# Gather information by using TSS for Windows Update for Business reports-related issues
14+
15+
This article introduces how to gather information by using the TroubleShootingScript (TSS) toolset for Windows Update for Business reports-related issues.
16+
17+
Before contacting Microsoft support, you can gather information about your issue.
18+
19+
## Prerequisites
20+
21+
Refer to [Introduction to TroubleShootingScript toolset (TSS)](introduction-to-troubleshootingscript-toolset-tss.md#prerequisites) for prerequisites for the toolset to run properly.
22+
23+
## Gather key information before contacting Microsoft support
24+
25+
1. Download [TSS](https://aka.ms/getTSS) and extract it in the *C:\\tss* folder.
26+
2. Open the *C:\\tss* folder from an elevated PowerShell command prompt.
27+
> [!NOTE]
28+
> Don't use the Windows PowerShell Integrated Scripting Environment (ISE).
29+
3. Run the following cmdlets:
30+
31+
```powershell
32+
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
33+
```
34+
35+
```powershell
36+
.\TSS.ps1 -Collectlog DND_WUfBReport
37+
```
38+
39+
4. Enter *A* for "Yes to All" for the execution policy change.
40+
41+
> [!NOTE]
42+
>
43+
> - The traces are stored in a compressed file in the *C:\\MS_DATA* folder. After a support case is created, this file can be uploaded to the secure workspace for analysis.
44+
> - If you've downloaded this tool previously, we recommend downloading the latest version. It doesn't automatically update when running `-Collectlog DND_WUfBReport`.

0 commit comments

Comments
 (0)