Export configuration and collect a bounded debug log#

When to use this procedure#

Use this when configuration or runtime sequencing must be reviewed.

Applies to#

This procedure applies to EventReporter.

Prerequisites#

  • Use an account that can read the product configuration and Windows diagnostic state.

  • Replace angle-bracket placeholders with values from the affected system.

Safety#

  • Disable debug logging immediately after the bounded capture.

  • Remove credentials, private keys, license material, and unrelated customer data before sharing.

Configuration path#

Configuration Client > Computer > Export Settings to Registry File; then General > Debug.

Procedure#

  1. Before changing settings, use Computer > Export Settings to Registry File and save a pre-change text export in a protected working directory.

    Expected result: A readable pre-change export exists and its modification time precedes the troubleshooting change.

    If it fails: Do not continue with a state-changing repair until a readable pre-change export exists.

  2. Record the start time, enable only the debug output required to reproduce once, then record the end time and disable debugging immediately.

    $captureStart=Get-Date; $captureStart.ToString('o')
    Get-Item -LiteralPath '<CONFIG_EXPORT>' | Format-List FullName,Length,LastWriteTime
    Get-Item -LiteralPath '<DEBUG_LOG>' | Format-List FullName,Length,LastWriteTime
    $captureEnd=Get-Date; $captureEnd.ToString('o')
    

    Expected result: The export and debug log are readable, the log covers the recorded interval, and debug output is disabled after the reproduction.

    If it fails: Verify the configured debug path and service-account write access. Do not leave debugging enabled while investigating a missing log.

  3. Preserve only the bounded interval around one uniquely identifiable test, then create redacted copies for review.

    Expected result: The test and its outcome can be correlated across the redacted export, Event Log, and bounded debug interval.

    If it fails: Repeat only after correcting the capture window; do not collect an unbounded debug log.

Verify the result#

Repeat the affected operation, confirm its positive output, and verify that queues, collection positions, or remote delivery continue normally.

Evidence to collect#

  • The capture start and end timestamps, complete Event Log entry, and neighboring product events.

  • The pre-change configuration export and bounded debug log from the same interval.

  • Redacted review copies with credentials, license data, private keys, addresses, hostnames, paths, database identifiers, certificate identities, and environment-specific service, ruleset, and action names removed.