Closed noahtalerman closed 1 year ago
Hey @marko-lisica and @marcosd4h below is my understand of the next steps that came out of our discussion during today's product design review.
What do you think? Am I missing anything?
TODO Marko: What should the information architecture (IA) look like in the Fleet UI for setting up Windows MDM?
TODO Marcos: Can we write Fleet information (URLs) into Azure programmatically? Are there APIs that allow for this?
TODO Marcos: How would we apply for a "Fleet" application showing up in Azure? What do we have to build? What do we have to build to support the "On premise" option?
@marko-lisica on the Automatic enrollment page in Fleet (linking to our dogfood instance here), we have Team (under Apple Business Manager), End user authentication, and End user license agreement.
I think we'll want to support this same functionality for Windows.
Also, on the Dashboard page (linking to our dogfood instance here) we have a report for hosts that are automatically enrolled v. manually enrolled.
For Windows in the Fleet UI, I think it makes sense to call user drive enrollment => “manual enrollment” and Autopilot enrollment => “automatic enrollment.” I think it's simpler for users for Mac and Windows to share enrollment language. I think to the user, they mean similar things on Mac and Windows.
I talk through the above in a Loom video here: https://www.loom.com/share/57896312112f4556a1ff415fd652a280
@marko-lisica on the Automatic enrollment page in Fleet (linking to our dogfood instance here), we have Team (under Apple Business Manager), End user authentication, and End user license agreement.
I think we'll want to support this same functionality for Windows.
Also, on the Dashboard page (linking to our dogfood instance here) we have a report for hosts that are automatically enrolled v. manually enrolled.
For Windows in the Fleet UI, I think it makes sense to call user drive enrollment => “manual enrollment” and Autopilot enrollment => “automatic enrollment.” I think it's simpler for users for Mac and Windows to share enrollment language. I think to the user, they mean similar things on Mac and Windows.
I talk through the above in a Loom video here: https://www.loom.com/share/57896312112f4556a1ff415fd652a280
I have some questions, regarding OS agnostic settings.
TODO Marcos: Can we write Fleet information (URLs) into Azure programmatically? Are there APIs that allow for this?
[Marcos] I've been looking into the Azure REST API reference here, and it seems this is not possible. I'm going to spend some more time today to keep looking to double check this
TODO Marcos: How would we apply for a "Fleet" application showing up in Azure? What do we have to build? What do we have to build to support the "On premise" option?
[Marcos] I'm going to look at this today
@marcosd4h @marko-lisica here's our Google doc w/ notes and action items we discussed during today's (2023-05-25 ) call: https://docs.google.com/document/d/1O7jMhRi3W-xwr_8wowwAKn_bzqESsedpknV64IxyiC8/edit#heading=h.fdn2a4gmpks0
The call was also recorded in Gong because I added the gong assistant. Here's the link: https://us-65885.app.gong.io/call?id=9145677102777577085
Hey folks, I tested the Windows automatic enrollment (non-Autopilot) experience and recorded several videos that you can find here in Loom: https://www.loom.com/spaces/All-Fleet-67132/folders/Intune-1db88dafed064975b4c5aaa18ba655d6
Some key findings and follow up research:
- End user sees the Fleet default end user license agreement (EULA) during the non-Autopilot flow
- Creating this default EULA is currently in progress. Tracked in GitHub here (internal)
- While building this feature you can use this sample EULA PDF here: https://drive.google.com/file/d/1U34XpQNV8JB5WPrgneH5wtG9hH4176Z_/view?usp=drive_link
- NOTE: We won't call this story done until the default EULA is added.
As noted above, we won't call this story done until the Fleet default EULA Is added. I added the above to the "requirements" section so that all folks on the team aligned on what we expect to ship.
cc @georgekarrv @marcosd4h
Requirements:
Noted in Noah's comment above that Win 11 Home was not supported. The device I am testing on came with Home, so I am upgrading to Pro and will retest.
After upgrading to Windows 11 Pro, I am still receiving an error on sign-in and am unable to complete the enrollment flow. It remains unclear whether the error is with my app configuration in Entra ID, or elsewhere. I will need to walk through the entire process with someone to verify where the breakdown is occurring.
Windows MDM setup, Seamless enrollment unfolds, Fleet's reach in clouds grows.
Reopening this because we don't have docs yet.
@sabrinabuckets @marcosd4h just checking, did this make it through QA? Looks like this was moved straight from the QA column to the closed column (skipped ready for release)
@noahtalerman we QA'd this on a call together with Gabe & Marcos. I didn't see it go back through the flow on the board though.
Confirm and celebrate: Needs docs.
Docs are in an open PR here: https://github.com/fleetdm/fleet/issues/11764
C&C: @noahtalerman to talk to Mike about docs.
C&C: @noahtalerman to work with JD to get the doc content into an article. Mike and I decided to put a freeze on committed learning docs. We still want to be able to point the user somewhere to learn.
C&C: @spokanemac can you please help me transform this PR into an article? https://github.com/fleetdm/fleet/pull/14566
C&C: @noahtalerman to rename "Entra" to "Azure" (old name) because the Fleet UI will use Azure for now.
C&C: "Entra" to "Azure" rename is done here: https://github.com/fleetdm/fleet/pull/14919
Windows, set to sail, Fleet enrolls, no track fails, Secure, without fail.
Goal
Requirements
Changes
UI
https://www.figma.com/file/hdALBDsrti77QuDNSzLdkx/%F0%9F%9A%A7-Fleet-EE-(dev-ready%2C-scratchpad)?type=design&node-id=17222-213545&mode=design