Course Preview

Fleet Management

Fleet management is the coordinated inventory, configuration, updating, security, support, and retirement of an organization's computers and mobile devices. A central service keeps many endpoints in a known state while each device reports what actually happened.

itInfrastructure and operations | OpenSkills.info

Course pathWalk it in order

Look it upDip in anytime

Go furtherLeaves this page

Don't Panic: Fleet Management

A fleet is a collection of endpoints that has stopped being small enough to manage by memory, spreadsheets, or a hopeful look at the office. Computers, phones, tablets, kiosks, and other devices each have their own habits. Fleet management turns that unruly collection into a control loop: identify, enroll, declare, observe, reconcile.

First comes inventory, which is less a list than a polite argument between several lists. Procurement knows hardware was acquired. The asset register knows custody. A directory knows identities. Network discovery knows what answered. The management service knows what reported recently. None gets the whole story, so the useful work is finding where they disagree.

Then comes enrollment, the trusted relationship between an endpoint and the management service. Organization-owned hardware can take broad device controls. Personal hardware needs a narrower work boundary. This is where the word policy becomes slightly mischievous: the same label on two platforms does not promise the same enforcement. The platform decides what control exists.

A policy declares the state a device should maintain: encryption, credentials, an application, a certificate, or an update target. Assignment is only intent. Delivery is not execution, and execution is not verification. A console can be very pleased with itself while an offline device, a conflict, low storage, or a pending restart has other plans. Fresh observed state is the evidence that settles the argument.

Changes travel through rings because a fleet is not one giant test device wearing several hats. A lab checks installation and rollback. An IT ring finds operational impact. A representative pilot includes the old hardware, remote networks, applications, and operating-system combinations that are waiting to be awkward in production. Then measured waves expand the change, with stop conditions and exceptions kept visible.

The lifecycle continues after a device stops being useful. Offboarding reaches accounts, tokens, managed data, hardware custody, automated enrollment, credentials, and disposal evidence. Removing one console record is a neat administrative gesture, not proof that those handoffs happened.

Read the Intro for the whole control loop and its boundaries. Use Slides when the relationships need a map. Keep the Cheatsheet nearby when tracing a rollout, a stale record, or an offboarding handoff. Field Notes carries the operational traps that make a correct-looking fleet less correct than it appears.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources