Solutions
Device management
Remotely manage, and protect laptops and mobile devices.
Orchestration
Automate tasks across devices, from app installs to scripts.
Software management
Inventory, patch, and manage installed software.
Extend Fleet
Integrate your favorite tools with Fleet.
Customers
Stripe + Fleet
Stripe consolidates multiple tools with Fleet.
Foursquare + Fleet
Foursquare quickly migrates to Fleet for device management.
What people are saying
Stories from the Fleet community.
More
JD Strong
JD Strong
Fleet 4.43.0 is live. Check out the full changelog or continue reading to get the highlights. For upgrade instructions, see our upgrade guide in the Fleet docs.
Fleet introduces a significant improvement regarding the management of user information. This update allows Fleet users to set the end-user email address directly within Fleet without depending on external sources like a Google Chrome profile or an Identity Provider (IdP). This enhancement simplifies and streamlines associating user email addresses with their respective devices. Administrators have greater flexibility and control over user data by enabling direct input and managing end-user email addresses within the Fleet platform. This feature represents Fleet's ongoing commitment to user-friendly and adaptable device management solutions.
A feature to fully disable remote script execution across an organization has been added in this release. This feature aligns with Fleet's value of ownership, as it gives administrators greater control over their Fleet environment. For organizations that want a "read-only" Fleet, this ensures they can tailor the platform to their organization's specific security policies and operational requirements.
Implementing disabling remote script execution reflects Fleet's commitment to adaptable and secure device management solutions. It acknowledges different organizations' diverse needs and security concerns, offering the flexibility to opt out of this capability if it doesn't align with their particular security posture or operational strategy. This update is a testament to Fleet's dedication to providing a versatile, user-centric platform that prioritizes its users' unique needs and preferences in a straightforward, no-frills manner.
Available in Fleet Premium
Administrators can now specify the version of osqueryd
, fleetd
, and Fleet desktop to be used on an endpoint, offering options such as "stable," "edge," or a specific version number. A fallback version can also be specified if the preferred version is unavailable. This provides greater flexibility and control over the deployment of Fleet and aligns with Fleet's commitment to delivering tailored and efficient device management solutions.
By enabling the specification of versions through server overrides, Fleet demonstrates its dedication to openness and ownership, empowering users with more personalized and adaptable tools. This feature is especially beneficial for organizations that require precise version control to meet specific security, compatibility, or testing needs. The ability to choose between stable releases, cutting-edge versions, or particular version numbers ensures that Fleet users can optimize their endpoint management strategies in alignment with their unique operational requirements.
Endpoint operations:
POST /api/v1/fleet/queries/:id/run
endpoint for synchronous live queries.PUT /api/fleet/orbit/device_mapping
and PUT /api/v1/fleet/hosts/{id}/device_mapping
endpoints for setting or replacing custom email addresses.--end-user-email
flag to fleetctl package
for .msi
installer bundling.host_count_updated_at
to policy API responses.gigs_total_disk_space
to host endpoint responses.fleetd
update channels in agent options (Fleet Premium only, requires fleetd
>= 1.20.0)./api/fleet/orbit/device_token
and other endpoints.Device management (MDM):
fleetd
auto-installs on Apple hosts enabling MDM features manually.fleetctl
.fleetctl
did not allow placement of --context
and --debug
flags following certain commands.overrides.platform
to be set to null
.fleetctl
issue with creating a new query when running a query by name.Visit our Upgrade guide in the Fleet docs for instructions on updating to Fleet 4.43.0.