Appearance
Support Bundles
Support bundles collect diagnostics into a ZIP file for investigating a problem. Use Administration → Support Bundles with the Platform Admin role.
First use Audit And History to identify the affected endpoint, job, service, and time range. Create a bundle for that scope and download it when collection finishes.
Bundle types
| Bundle | When to use it |
|---|---|
| Server | Connection, platform, or server errors that affect multiple resources. |
| Service-client logs | Enrollment, connection, or execution problems with a selected service. |
| Job | Failed or stalled tasks, unexpected job outcomes, or missing artifacts. Select an endpoint to narrow the investigation. |
| Endpoint | A device that stays busy, cannot receive work, or has an enrollment, update, or Intel AMT problem. |
Bundles include the available logs and context for the selected scope. Live logs depend on the endpoint or service being reachable. A partial bundle can still be useful; review its collection warnings before assuming that all sources were included.
Infrastructure run journal output is excluded. If needed, download it separately from the run details.
Security
Treat bundles as sensitive operational data. They can contain device identities, user names, job configuration, and log excerpts. Ordyn excludes plaintext secrets, but the remaining context still needs protection.
Retention
Keep bundles only as long as needed for the investigation. Ordyn removes expired bundles automatically; delete downloaded copies when the support case is closed.