Export configuration and collect a bounded debug log#

When to use this procedure#

Use this when configuration or runtime sequencing must be reviewed.

This procedure applies to WinSyslog.

Use an account that can read the product configuration and Windows diagnostic state.
Replace angle-bracket placeholders with values from the affected system.

Disable debug logging immediately after the bounded capture.
Remove credentials, private keys, license material, and unrelated customer data before sharing.

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

Export settings as a text registry file, then enable the minimum debug level that reproduces the problem.

Expected result: The affected object and its effective settings are identified.

If it fails: Return to the complete Event Log detail and configuration export before changing settings.
Run the native Windows checks below from the affected product host.
```
Get-Item -LiteralPath '<CONFIG_EXPORT>' | Format-List FullName,Length,LastWriteTime
Get-Item -LiteralPath '<DEBUG_LOG>' | Format-List FullName,Length,LastWriteTime
```
Expected result: Both files exist, are readable, and cover the recorded reproduction interval.

If it fails: Verify the service account can write the debug directory and restart only if the setting requires it.
Perform one uniquely identifiable product test through the same service, rule, or action.

Expected result: The intended destination records the test exactly once.

If it fails: Collect the first new product event and bounded debug output; do not change unrelated settings.

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

The complete Event Log entry and neighboring product events with timestamps.
The command output, relevant configuration export, and bounded debug log from the same interval.