Improve troubleshooting workflow for Windows custom MDM commands and profiles

[marko-lisica]

Goal

User story
As an IT admin using the fleetctl mdm-command-results or on the Host details > OS settings page in the UI,
I want to know which part of a Windows MDM command or profile didn't work
so that I can resolve the issue.

Changes

Product

• [x] UI changes: Figma link
• [x] CLI usage changes: Figma link
• [x] API changes: #16408

Engineering

• [ ] Database schema migrations: TODO
• [ ] Load testing: TODO

ℹ️  Please read this issue carefully and understand it. Pay special attention to UI wireframes, especially "dev notes".

Context

• Requestor(s): _____

QA

Risk assessment

• Requires load testing: TODO
• Risk level: Low / High TODO
• Risk description: TODO

Manual testing steps

1. Step 1
2. Step 2
3. Step 3

Testing notes

Confirmation

1. [ ] Engineer (@____): Added comment to user story confirming successful completion of QA.
2. [ ] QA (@____): Added comment to user story confirming successful completion of QA.

[marko-lisica]

Problem

Troubleshooting for Windows MDM commands is hard. Currently the only way to make relation between status and command is via CmdID / CmdRef which is either generated or overwritten by Fleet so user can't compare profile/command and raw XML output.

Potential solutions

Some of potential solutions are in the slack thread here.

[georgekarrv]

Hey team! Please add your planning poker estimate with Zenhub @jahzielv @roperzh @gillespi314

[noahtalerman]

• [ ] API changes: TODO

Hey @marko-lisica passed this issue back to you for API design.

[georgekarrv]

Initial estimate of 5 before API design. Will revisit after that is scoped

[noahtalerman]

@georgekarrv API design for this story is done. We moved the issue over to specified so we can revisit during sprint kickoff.

[sabrinabuckets]

[noahtalerman]

C&C: No customers to notify

[fleet-release]

Windows faults revealed, Like dewdrops on glass city, Troubleshoot with ease.