Hi y’all! I noticed that

fleetctl

packages are installed with the name “Fleet osquery” on Windows and that the name was last changed in Nov 2021. Given the recent visibility of Fleet Desktop e.g. menu bar indicators, I was wondering if y’all have thought about changing the package name to “Fleet Desktop” or maybe “Fleet Desktop - osquery” if it’s important to include that in the name?

fleetctl

is an admin binary for Fleet and only needs to be installed on admin devices for generating packages or interacting with the API. This is not something that needs to be deployed to end users. Fleet Desktop on the other hand is what end users have for interacting with Fleet -- seeing device health, self-service, etc.

Sorry, I phrased the first part of my question poorly. Lemme make sure I’m not conflating things. Q1: I have to run

fleetctl package

to make a package for users to install on their hosts, right? Is there any other way to add users? https://fleetdm.com/guides/enroll-hosts Q2: If yes, when

fleetctl package

makes a Windows package, how does it set the name that the package gets installed under? I mean the name that appears in “Add & Remove Programs”. I think it comes from here but I’m not an expert/Fleet dev: https://github.com/fleetdm/fleet/commit/b65c61cb1203a2b05174df2f2658708caba6af25 Q3: If that’s the correct spot and it’s currently being named “Fleet osquery”, have y’all considered it being named “Fleet Desktop” given the recent focus on visibility to the end user of what’s installed on their host device?

No worries! I follow what you're saying now. 1. There is not a way to add users. Our approach is to enroll the entire host so

fleetctl

just generates a package with an enrollment secret that gets deployed to a host, not a specific user. 2. N/A 3. Not every customer deploys Fleet with the desktop enabled. For example, if you look at the command for adding hosts, you can remove

--fleet-desktop

and it will deploy Fleet in such a way that you can do everything possible with Fleet but there is no end user experience on the device. Because of this, and because Fleet desktop is just a menubar or systray app and not a full blown app, it might not make sense to call it "Fleet Desktop" but I definitely understand an argument for dropping the "osquery" part of the name since to your point, its potentially more than just the osquery features of Fleet when Desktop is also installed. 🤔

Ah right I forgot that Fleet Desktop is optional 🤦🏻

I definitely understand an argument for dropping the “osquery” part of the name since to your point

Sure sure. I was more curious if it had come up. Thanks for your help!

Thank you! Really appreciate you opening that with the additional context.