The endpoint baseline profile

Cadence checks every managed endpoint against a baseline profile at deployment and on every agent cycle. Drift is reported, not silently corrected — remediation is always a separate, gated action.

Checks

Check	Severity	Why
print.default-driver-class	critical	The default printer must use a modern Microsoft class driver. QuickBooks builds a printer device context to lay out invoices; a legacy virtual-PDF default produces an invalid one and takes the process down.
print.no-label-printer-default	critical	Invoice geometry cannot be computed against a 2-inch thermal label page.
print.xps-services-enabled	high	Required for Save-as-PDF and emailed invoices.
print.addprinter-failure-rate	high	The leading indicator. Crash volume tracks this number.
print.legacy-pdf-conflicts	medium	Legacy virtual PDF drivers compete with QuickBooks’ own print path.
print.printer-count-sane	low	Large or stale printer lists slow form open and add failure surface.
qb.build-pinned	high	Mixed maintenance builds against one company file is an unsupported multi-user configuration.
qb.crash-telemetry-enabled	medium	Without local dumps, a crash leaves no evidence and every support case restarts from a screenshot.
os.v3-driver-exposure	info	Microsoft is deprecating v3 print drivers; Windows Protected Print Mode blocks them. Inventory now, plan replacements.

Why these and not a generic OS baseline

Every check here came out of a real failure in a real QuickBooks environment. The print-stack checks in particular exist because a fleet was updated to the current release, cleared of network faults, and kept crashing — until the default printer turned out to be the cause.

See Why QuickBooks crashes for the full investigation.