Option to automatically migrate Windows workstations

[noahtalerman]

Goal

User story
As an IT admin,
I want to migrate my Windows workstations from my old MDM solution to Fleet
so that I can use Fleet to enforce disk encryption, OS updates, and other OS settings on these hosts.

Objective

Customer promises + renewal requests

Original request

• 13667

Context

• Product designer: @rachaelshaw

Changes

Product

• [ ] UI changes: Figma
• [ ] CLI (fleetctl) usage changes: N/A
• [ ] YAML changes: PR
• [ ] REST API changes: PR (old PR with 1st draft here, for reference)
• [ ] Fleet's agent (fleetd) changes: N/A
• [ ] Activity changes: Draft PR
• [ ] Permissions changes: N/A
• [ ] Changes to paid features or tiers: Fleet Premium
  • @noahtalerman: Pricing page language: An "on" button in Fleet so you have control over when Windows workstations switch.
• [ ] Other reference documentation changes: N/A
• [ ] Once shipped, requester has been notified

Engineering

• [ ] 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

Manual testing steps

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

Testing notes

@noahtalerman:

Edge cases to consider:

• What about offline hosts?
• What happens in between toggling?
• What about the folks that have ‘Windows MDM turned on’
• What happens to those fleetd enrolled Windows hosts?
• What does the reporting look like? (status of hosts that have not transitioned yet, and which have. What if some never check in? How will I know which have and which haven't?)

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.

[noahtalerman]

Moving this out of the issue description. This was used during design process. Please see the Figma in the issue description for the latest UI changes.

Flip this behavior:

[noahtalerman]

Hey @zayhanlon heads up, this user story didn't make it into the upcoming engineering sprint because we didn't get it estimated in time.

It's still prioritized. We left it on the drafting board so that it can be pulled into the next engineering sprint.

[noahtalerman]

Hey @georgekarrv just giving you a reminder that this story is ready to spec. Please let us know if we can help get this ready for estimation :)

cc @marko-lisica

[noahtalerman]

Hey @georgekarrv just giving you a ping! as a reminder that this story is ready to spec. Please let us know if we can help get this ready for estimation.

[noahtalerman]

Hey @lukeheath I think let's give this user story that's tied to a customer promise a P2 so that we try to ship it next sprint.

[lukeheath]

@noahtalerman Agreed, thanks.