@marko-lisica: Do you still think we should have "fleetd first" as best practice for manual enrollment of macOS hosts? Thinking about how should we treat /enroll page on larger screens. To me this new flow is way simpler for IT admins and end-users. The only thing they need is to install profile and then fleetd is installed automatically.
@noahtalerman: Those are great points! In the short term, yes, let’s stick w/ “fleetd first”.
Most of our customers buy Fleet to enroll macOS, Windows, and Linux. Installing fleetd first let's there be one, cross-platform way to get all of your hosts enrolled.
As more of our customers become majority macOS, iOS, and iPadOS, I think that’s when we consider switching to "enrollment profile first".
@marko-lisica: Do you still think we should have "fleetd first" as best practice for manual enrollment of macOS hosts? Thinking about how should we treat /enroll page on larger screens. To me this new flow is way simpler for IT admins and end-users. The only thing they need is to install profile and then fleetd is installed automatically.
@noahtalerman: Those are great points! In the short term, yes, let’s stick w/ “fleetd first”.
Most of our customers buy Fleet to enroll macOS, Windows, and Linux. Installing fleetd first let's there be one, cross-platform way to get all of your hosts enrolled.
As more of our customers become majority macOS, iOS, and iPadOS, I think that’s when we consider switching to "enrollment profile first".