Can you provide the script to collect trace logging whilst we had to provide a Fiddler trace from the client side as well

Suleman Fasasi 0 Reputation points
2025-12-11T10:14:01.0066667+00:00

Can you provide the script to collect trace logging whilst we had to provide a Fiddler trace from the client side as well.


Moved from: Community Center | Not monitored

Windows for business | Windows Client for IT Pros | Devices and deployment | Other
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Q&A Assist
    2025-12-11T10:14:14.4266667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    To collect trace logging while also providing a Fiddler trace from the client side, you can use the TroubleShootingScript (TSS) toolset in PowerShell. Here’s a basic script to enable trace logging:

    # Enable a scenario trace
    .\TSS.ps1 -Scenario <ScenarioName>
    
    # Enable component traces
    .\TSS.ps1 <-ComponentName> <-ComponentName> ...
    
    # Start traces with no-wait mode
    .\TSS.ps1 -StartNoWait -Scenario <ScenarioName>
    # Stop the trace when needed
    .\TSS.ps1 -Stop
    

    Make sure to replace <ScenarioName> and <ComponentName> with the appropriate names for your specific scenario. You can list supported scenarios and components using the following cmdlets:

    .\TSS.ps1 -ListSupportedScenarioTrace
    .\TSS.ps1 -ListSupportedTrace
    

    Additionally, ensure Fiddler is set up to capture the necessary traffic by enabling HTTPS decryption and capturing traffic as outlined in the Fiddler documentation.


    References:

    0 comments No comments

  2. Quinnie Quoc 7,625 Reputation points Independent Advisor
    2025-12-11T12:43:11.1166667+00:00

    Hello Suleman Fasasi,

    Thank you for your question regarding how to collect trace logging in addition to the Fiddler trace you already gathered from the client side. While Microsoft does not provide a single universal script for all scenarios, the recommended approach is to use the built‑in Microsoft Support Diagnostic Logging tools such as Collect‑Logs.ps1, which can capture network traces, event logs, and application‑level diagnostics in one package. You can run this PowerShell script from an elevated session to gather the required logs, and it will automatically bundle the output into a compressed folder for review. If you are troubleshooting a specific Microsoft service or application, you may also enable targeted logging through the corresponding module (for example, MSAL, Teams, or Office 365 connectivity logging).

    Combining these logs with your Fiddler capture will give a complete view of both client‑side traffic and system‑level behavior, which is extremely helpful for deeper analysis.

    I hope this guidance helps you move forward with your investigation. If this answers your question, please consider clicking “Accept the Answer” so that others in the community can benefit from the solution as well.

    Thank you so much!!!

    Best regards,

    QQ.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.