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

Windows MDM feels like a dead end to new users #19017

Open
RachelElysia opened this issue May 15, 2024 · 8 comments
Open

Windows MDM feels like a dead end to new users #19017

RachelElysia opened this issue May 15, 2024 · 8 comments
Labels
~csa Issue was created by or deemed important by the Customer Solutions Architect. customer-mozartia customer-rocher ~dogfood Issue resulted from Fleet's product dogfooding.

Comments

@RachelElysia
Copy link
Member

RachelElysia commented May 15, 2024

Problem

I am clicking around the App and I found > Settings > Integrations > MDM > Turn on Windows MDM > Turn on
I click the turn on button and I get this error, "Please configure Fleet with a certificate and key pair first." but there's no link to where/how I'm suppose to do that.

Screen.Recording.2024-05-15.at.10.27.34.AM.mov

Potential solutions

  1. Link to further instructions?
@RachelElysia RachelElysia added :product Product Design department (shows up on 🦢 Drafting board) ~feature fest Will be reviewed at next Feature Fest labels May 15, 2024
@noahtalerman
Copy link
Member

@RachelElysia thanks for tracking this!

Soon we'll be generating some of the required certs for macOS MDM features. Story here: #10383

@roperzh do you think we can generate the WSTEP cert/key for the user? That way, a user trying to turn on Windows MDM features can click "Turn on" and that's it. They're done.

@noahtalerman noahtalerman added ~dogfood Issue resulted from Fleet's product dogfooding. and removed :product Product Design department (shows up on 🦢 Drafting board) labels May 16, 2024
@roperzh
Copy link
Contributor

roperzh commented May 16, 2024

@noahtalerman yes absolutely, makes sense!

@noahtalerman
Copy link
Member

This one could be a quick win if we don't have capacity for generating the certs: #19262

@nonpunctual nonpunctual added the ~csa Issue was created by or deemed important by the Customer Solutions Architect. label May 28, 2024
@noahtalerman noahtalerman removed the ~feature fest Will be reviewed at next Feature Fest label Jun 4, 2024
@nonpunctual
Copy link
Contributor

nonpunctual commented Aug 8, 2024

@RachelElysia @noahtalerman @roperzh @zayhanlon @dherder @ddribeiro what are the odds on making this "quick win" happen? Came up 2x on customer calls this week. Thanks!

@zayhanlon
Copy link
Contributor

@nonpunctual what happens next? they reach out to us, we point them to docs? what's the 'workaround'

@nonpunctual
Copy link
Contributor

@zayhanlon because I am referring to eval environments we can actually add the wstep certs for them to get Windows MDM evals rolling.

But, if these evals close, the production environments would need to be set up with private keypair requested from the customer like we used to have to do with Apple MDM server config. So, it would become an issue for someone on your team... Thanks.

@dherder
Copy link
Contributor

dherder commented Aug 8, 2024

@zayhanlon the workaround is very similar to what we used to do with the macOS certs, albeit a bit less effort. In an eval, we would generate the certs and pass them to infra for deployment. Seems like if we are generating those certs on the macos MDM side and we are tracking those internal to the Fleet server, we could just reuse the SCEP cert keypair like we used to before the certs were stored in the db.

@zayhanlon
Copy link
Contributor

thanks! we'll weight it out once i get a q4 tentative plan from noah @nonpunctual @dherder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
~csa Issue was created by or deemed important by the Customer Solutions Architect. customer-mozartia customer-rocher ~dogfood Issue resulted from Fleet's product dogfooding.
Development

No branches or pull requests

6 participants