Quick Start: Microsoft Product Support Reports Viewer for IT Pros

Microsoft Product Support Reports Viewer: Complete Guide & How to Use It

What it is

The Microsoft Product Support Reports Viewer (PSR Viewer) is a tool for viewing structured diagnostic and support reports generated by Microsoft products or support tooling. It consolidates logs, error details, configuration snapshots, and telemetry into readable sections so IT staff and support engineers can quickly identify issues and extract actionable data.

When to use it

• After a product error or crash to review collected diagnostics.
• When submitting data to Microsoft support so you can confirm what’s included.
• During troubleshooting to compare configuration and telemetry snapshots across systems.

Key features

• Structured report navigation: Sections for errors, events, configuration, installed components, and performance counters.
• Search and filter: Quickly find keywords, error codes, or timestamps.
• Export/Share: Save selected sections or full reports as files for sharing with support.
• Timestamps & correlation IDs: Enables correlating events across logs.
• Attachments view: Access included log files, dumps, or configuration snapshots.

How reports are generated (typical sources)

• Built-in diagnostic logging in Microsoft products (e.g., Windows, Exchange, SQL Server).
• Support diagnostics tools (e.g., Microsoft Support Diagnostic Tool, product-specific collectors).
• Telemetry exports from product portals or SaaS service diagnostic packages.

Installation & requirements

• Usually runs on Windows. Check product-specific prerequisites (framework versions, permissions).
• Requires read access to collected report files or the location where the diagnostic tool writes output.
• Some versions are included with support tools; others are downloadable as part of a diagnostics package.

Opening a report

1. Launch the Reports Viewer application.
2. Use File > Open (or the Import button) to load the report package (commonly .zip, .cab, or a tool-specific bundle).
3. Let the viewer index and parse the package; progress indicators show parsing status.

Navigating the interface

• Left pane: hierarchical sections (Overview, Errors, Events, Configuration, Performance).
• Center pane: detailed content for the selected section, with expandable items.
• Top toolbar: search, filter, export, and view settings.
• Bottom/status bar: parsing status, report timestamp, and correlation IDs.

Common workflows

1. Quick triage (5–10 minutes)

   • Open report and read the Overview/Executive Summary.
   • Check top error entries and most recent events.
   • Search for the error code or exception text.

2. Deep analysis (30–90 minutes)

   • Review sequence of events and correlate timestamps.
   • Inspect configuration differences and installed components.
   • Open attached logs or memory dumps if available; note recurring patterns.

3. Preparing for support case

   • Use export options to include only relevant sections (errors, events, config).
   • Attach correlation IDs and timestamps in your support request.
   • Optionally redact sensitive configuration entries before sharing.

Tips for effective troubleshooting

• Filter by time range around the incident window to reduce noise.
• Search error codes rather than full messages to find related occurrences.
• Note correlation IDs shown in multiple sections — they’re key to linking events.
• Compare configs from a working system if available to spot differences.
• Keep copies of original reports; export versions you send to support.

Common pitfalls

• Missing data: Diagnostic collectors may not capture everything if run after a reboot or if permissions are limited.
• Large attachments: Memory dumps can be huge; include only if requested.
• Sensitive data exposure: Redact credentials or personal data before sharing externally.

Exporting and sharing

• Use built-in export to produce a packaged file containing selected sections.
• Choose common formats (PDF for summaries, ZIP for full bundles).
• Verify exported package opens correctly before attaching to a support case.

Security and privacy considerations

• Treat reports as sensitive — they may contain configuration, usernames, or network details.
• Remove or obfuscate secrets and PII before sharing outside your organization