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.44.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 now allows IT administrators to execute scripts on hosts, irrespective of their online or offline status. This enhancement allows for a more flexible script execution process, catering to various operational scenarios. Administrators can now schedule and run scripts on any host, regardless of connectivity status, and track the script's execution.
Additionally, this feature provides a comprehensive view of past and upcoming activities related to script execution for a host. IT admins can see a chronological list of actions, including both executed and scheduled scripts, offering clear visibility into the timing and sequence of these activities. This capability is particularly beneficial for ensuring that essential scripts are run in an orderly and timely manner, enhancing the overall management and maintenance of the fleet.
IT administrators can now activate profiles for hosts based on specific labels, enabling more dynamic and attribute-based profile management. This functionality is particularly useful for tailoring configurations and policies to hosts that meet certain criteria, such as operating system versions. For example, an IT admin can now set a profile only to be applied to macOS hosts at or above macOS version 13.3. This approach facilitates a more granular and efficient management of host settings, ensuring that profiles are applied in a manner that aligns with each host's characteristics and requirements while also maintaining a consistent baseline across the fleet.
Host expiry settings can now be customized for each team. This feature addresses the diverse requirements of different groups of devices within an organization, such as servers and workstations. With this new functionality, endpoint engineers can set varied expiry durations based on the specific needs of each team. For instance, a shorter expiry period, like 1 day, can be configured for teams of servers, whereas a longer duration, such as 30 days, can be applied to your workstation teams. This flexibility ensures that each team's expiry settings are tailored to their operational tempo and requirements, providing a more efficient and effective management of device lifecycles within Fleet.
Fleet's latest update addresses a crucial security concern by altering how the fleetd
enroll secret is stored on macOS and Windows hosts. In response to the need for heightened security measures, fleetd
will now store the enroll secret in Keychain Access on macOS hosts and in Credentials Manager on Windows hosts rather than on the filesystem. This change significantly enhances security by safeguarding the enroll secret from unauthorized access, thus preventing bad actors from enrolling unauthorized hosts into Fleet.
This update includes a migration process for existing macOS and Windows installations where the enroll secret will be moved from the filesystem to the respective secure storage systems - Keychain Access for macOS and Credentials Manager for Windows. However, Linux hosts will continue to store the enroll secret on the filesystem. This improvement demonstrates Fleet's commitment to providing robust security features, ensuring that sensitive information like enroll secrets is securely managed and less susceptible to unauthorized access.
Endpoint operations:
/api/fleet/orbit/ping
and /api/fleet/device/ping
endpoints.pack_delimiter
in agent settings.fleetctl
for macOS as a universal binary (native support for both amd64 and arm64 architectures).fleetctl package --type=msi
on macOS using arm64 processor.host_count_updated_at
to policy API responses.GET /api/v1/fleet/hosts/:id
endpoint so that failing policies are listed first.Device management (MDM):
GET /api/v1/fleet/mdm/manual_enrollment_profile
and scripts related endpoints (/hosts/:id/activity
, /hosts/:id/activity/upcoming
).labels
object to MDM profiles response payload.configuration_web_url
values in DEP profile.Vulnerability management:
resolved_in_version
for vulnerabilities./api/fleet/orbit/device_token
and other endpoints.fleetctl
where --context
and --debug
flags were not allowed after certain commands."w"
prefix.fleetctl
and fleetd
to prevent errors for 204 responses.fleetd
or OSQuery.software/titles
and software/versions
endpoints, the
browser
property is no longer included in the response when empty.Visit our Upgrade guide in the Fleet docs for instructions on updating to Fleet 4.44.0.