fleetdm
Add Microsoft Word and Excel to Windows FMA
Goal
| User story |
|---|
| As an IT admin, |
| I want to be able to add installer packages for MS Word and Excel via Fleet-maintained apps |
| so that I can easily patch and update the software on the hosts I manage. |
Key result
Patch software without writing custom policies.
Original requests
#22369
Context
- Product Designer: @eugkuo
- Engineering support: @mostlikelee
Changes
Product
- [ ] UI changes: Add Microsoft Word and Excel to Windows FMA
- [ ] CLI (fleetctl) usage changes: No changes
- [ ] YAML changes: No changes
- [ ] REST API changes: No changes
- [ ] Fleet's agent (fleetd) changes: No changes
- [ ] GitOps mode changes: No changes
- [ ] Activity changes: No changes
- [ ] Permissions changes: No changes
- [ ] Changes to paid features or tiers: No changes
- [ ] Transparency changes: No changes
- [ ] First draft of test plan added
- [ ] Other reference documentation changes: No changes
- [ ] Once shipped, requester has been notified
- [ ] Once shipped, dogfooding issue has been filed
Engineering
- [ ] Test plan is finalized
- [ ] Contributor API changes: TODO
- [ ] Feature guide changes: TODO
- [ ] Database schema migrations: TODO
- [ ] Load testing: TODO
ℹ️ Please read this issue carefully and understand it. Pay special attention to UI wireframes, especially "dev notes".
QA
Risk assessment
- Requires load testing: TODO
- Risk level: Low / High TODO
- Risk description: TODO
Test plan
Standard FMA (un)install test scope.
Testing notes
Confirmation
- [ ] Engineer: Added comment to user story confirming successful completion of test plan.
- [ ] QA: Added comment to user story confirming successful completion of test plan.
As a heads-up here, a prerequisite for offering auto-install for these three titles is getting inventory working for these three titles. We'll be looking into Teams not showing up in #27199, but Word and Excel have the same problem.
In addition, we'll need to decide how to ingest these titles, as for Office the WinGet option doesn't seem to fit (@mostlikelee can share more detail), and for Teams the package format is msix, so TBD whether we can successfully pull that into Fleet even if we bypass package metadata extraction (#24831).
So while this probably requires low design effort (we already have the icons for these three, and they'll slot in when we have them added), it would be useful to have a timeboxed engineering research task in the 4.67 eng sprint to help figure out what we need to do for inventory (tweaks to software detail queries or maybe osquery changes), and where we're going to pull the packages from.
@mostlikelee Are there any product changes that need done? I think the answer is no, but I wanted to double check with you before filling out all those items with No changes.
Thanks!
Word and Excel add, Easier updates take flight, Patch with no dread, glad.
