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
Section titled “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. |
os.component-store-healthy |
medium | A quick read of Windows’ own corruption flags (no scan). Answers “is it the OS?” before a vendor asks. |
print.xps-writer-present |
medium | The XPS feature can be on while the printer object was deleted; QuickBooks needs the printer. |
av.qb-defender-exclusion |
low | Live-scanning a multi-GB company file on every write adds latency. Reads both the managed policy hive and local preferences, because an EDR that manages Defender strips local exclusions. |
qb.edition-single |
medium | An all-edition install forces an elevated “reconfigure your new edition” on every launch. A correct install carries exactly one. |
qb.edition-seated |
high | After a silent install, QuickBooks needs one elevated interactive launch to finish edition setup. Until then every user launch fails. |
qb.edition-expected |
high | The installed edition matches the edition your organisation set in Cadence. |
Profile version 1.1.0 (September 2026) added the last six, from a clean-machine rebuild and a fleet-wide maintenance pass. See How QuickBooks updates actually work for the edition and update-cache findings behind them.
Why these and not a generic OS baseline
Section titled “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.