Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to automatically migrate Windows workstations #22075

Open
14 tasks
noahtalerman opened this issue Sep 13, 2024 · 0 comments
Open
14 tasks

Option to automatically migrate Windows workstations #22075

noahtalerman opened this issue Sep 13, 2024 · 0 comments
Assignees
Labels
customer-preston #g-endpoint-ops Endpoint ops product group :product Product Design department (shows up on 🦢 Drafting board) story A user story defining an entire feature

Comments

@noahtalerman
Copy link
Member

noahtalerman commented Sep 13, 2024

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.

Context

Pricing page language: An "on" button in Fleet so you have control over when Windows workstations switch.

Flip this behavior:
Screenshot 2024-09-13 at 10 30 16 AM

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?)

Changes

Product

  • Reference documentation changes: TODO
  • UI changes: Figma
  • CLI (fleetctl) usage changes: TODO
  • YAML changes: TODO
  • REST API changes: TODO
  • Fleet's agent (fleetd) changes: TODO
  • Activity changes: TODO
  • Permissions changes: TODO
  • Changes to paid features or tiers: TODO

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

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 noahtalerman added story A user story defining an entire feature :product Product Design department (shows up on 🦢 Drafting board) labels Sep 13, 2024
@rachaelshaw rachaelshaw added the #g-endpoint-ops Endpoint ops product group label Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-preston #g-endpoint-ops Endpoint ops product group :product Product Design department (shows up on 🦢 Drafting board) story A user story defining an entire feature
Development

No branches or pull requests

3 participants