A support case opened on the appliance stalls because the support agent's first request is a system health collection, nobody on staff knows how one is generated or delivered, and the team ends up improvising a 2 GB upload through a laptop balanced on a rack rail. What post-deployment configuration would have made attaching health data to the case routine?

The supported pattern for health collections is automation established before the incident: the appliance can be configured to generate periodic diagnostic collections and transmit them to the vendor's support infrastructure over the support channel, and cases are then served by data that already exists upstream. With that configured, the support request is satisfied by pointing the case at recent collections. A self-made cron email to a generic mailbox is not a support workflow - it has no case linkage, no validation, and no ownership on the vendor side, and these platforms route automated data through dedicated support channels rather than inboxes. The wiki procedure is better than nothing but still assumes a knowledgeable responder, working portal access, and available bandwidth during an outage; the whole point of the automated configuration is that the routine does not depend on heroics. Raising verbosity and local retention makes later collections richer but delivers nothing anywhere - the data still sits on the appliance, and higher verbosity quietly consumes the same capacity you are busy monitoring. Exam caveat: automated submission requires the support entitlement and connectivity that the vendor-cloud monitoring features also need, and content policies should be reviewed if collections leave your custody. Operational check: on the next case, before support even asks, verify the most recent auto-collection timestamp and attach it to the case record.