Interpretation
How do you interpret the customer's words?
The customer enforces Recovery Lock passwords and can't see the status across their fleet. They want the targeted filter they already get for disk encryption and configuration profiles.
What's Fleet missing?
Recovery Lock status is visible per host only. There's no host filter for it in the UI, no os_settings_recovery_lock parameter on List hosts alongside os_settings_disk_encryption, and no status counts that isolate it from other OS settings.
What does the customer's ideal workflow look like?
- Filter hosts by Recovery Lock status the same way they filter by disk encryption status.
- See counts per status to track coverage.
- Drill into failed hosts and read the failure detail.
- Pull the same breakdown from the API.
Interpretation
How do you interpret the customer's words?
The customer enforces Recovery Lock passwords and can't see the status across their fleet. They want the targeted filter they already get for disk encryption and configuration profiles.
What's Fleet missing?
Recovery Lock status is visible per host only. There's no host filter for it in the UI, no
os_settings_recovery_lockparameter on List hosts alongsideos_settings_disk_encryption, and no status counts that isolate it from other OS settings.What does the customer's ideal workflow look like?