Lost laptops, surprise audits, and license overuse can turn a normal help desk day into damage control, especially when no one knows what the company owns or who has it. CompTIA A+ Core 2 (220-1202), Domain 4.1, Objective Asset management. This objective tests how well you can track devices and software so support stays fast, accurate, and accountable.
In plain terms, an asset is anything the company owns and must track, such as laptops, phones, printers, servers, or software licenses. When you manage assets well, you can answer basic questions quickly, what it is, where it is, who's using it, and whether it's covered under warranty or allowed by licensing terms.
This section explains the essentials you're expected to know for the exam and the job. You'll review inventory lists, asset tags and IDs, and why many teams use a configuration management database (CMDB). You'll also connect the procurement life cycle to real tasks, like assigning users, tracking warranty status, and spotting licensing risk before it becomes a compliance issue.
Asset Tracking
CompTIA A+ Core 2 (220-1202) Domain 4.1 Objective 4.1 (Asset management) treats asset management as a practical control, not paperwork. In support work, accurate records help you move from guessing to verifying, because you can link a device or service to an owner, a location, and a cost. It also reduces risk during audits, returns, and license checks, since you can show what the organization owns and how it gets used.
Assets you should track, beyond just laptops
In a real IT shop, assets include more than endpoints. You track anything that costs money, stores data, or affects uptime. A simple, job-based inventory usually includes:
- Desktops and laptops
- Monitors and printers
- Phones and tablets (plus personally owned devices, if allowed by policy)
- Network gear (switches, routers, wireless access points)
- Docks, chargers, and adapters
- Spare parts (RAM, SSDs, replacement keyboards)
- Removable media (USB drives, external hard drives)
- Virtual assets, such as software subscriptions and hosted tools
It also helps to separate what you track into three buckets:
- Hardware: A company laptop with an asset tag and a serial number.
- Software: A Microsoft 365 license assigned to a named user account.
- Cloud services: A SaaS ticketing system subscription tied to a tenant and billing plan.
Organizations often track accessories because they disappear easily and add up quickly. A missing dock can stall a new hire's setup, while repeated charger replacements quietly drain budget.
What good tracking looks like in daily support tickets
A user submits a ticket: their laptop powers on, but the screen stays black. First, the tech checks the asset record in the inventory list or CMDB. The record shows the asset tag, serial number, assigned user, and the device model. Next, the tech confirms the warranty status and sees it expires in three months. The record also lists the last known location, which helps if the user works across sites.
Because the record already ties the device to the user, the tech avoids basic back-and-forth like "Which laptop is it?" or "When did you get it?" Instead, the tech focuses on the fix. If the warranty covers the issue, the tech chooses repair and starts the vendor RMA process. If the device is out of warranty and near end of life, the tech may replace it and schedule data transfer.
This is also where chain of custody matters. In plain terms, it answers "who had it last" and "when it changed hands." That trail protects the user and the IT team, especially when equipment goes missing or returns arrive damaged.
Accurate Inventory Lists
CompTIA A+ Core 2 (220-1202) Domain 4.1 Objective 4.1 expects you to understand how inventory lists stay accurate over time, because support, audits, and licensing all depend on clean records. A good inventory list works like a library catalog: you can find the item fast, confirm who has it, and prove when it changed hands. If the list is unclear, every ticket takes longer and every audit turns into a scramble.
The minimum fields an inventory list should include
An inventory list should answer four basics: what it is, where it is, who has it, and what condition it's in. Keep fields consistent across teams, because consistency makes searching and auditing easier.
For hardware, include these minimum fields:
- Asset ID (unique tag number used internally)
- Serial number (vendor identifier)
- Model (helps with drivers, parts, and replacements)
- Device type (laptop, phone, printer, switch)
- Location (site, room, rack, or department)
- Status (in stock, deployed, repair, retired)
- Assigned user (or "unassigned" for spares)
- Purchase date (supports budget and refresh planning)
- Warranty end date (speeds up repair decisions)
- Notes (damage, accessories, exceptions, special configs)
For software, track rights and assignments, not just names. At minimum, add:
- License type (per-user, per-device, subscription)
- License count (purchased versus used)
- Renewal date (prevents surprise expirations)
- Assigned device or user (ties usage to a record you can verify)
A record you can't tie to a person, place, or proof (serial or license terms) won't hold up in an audit.
How inventory gets messy, and simple ways to prevent it
Inventory lists usually fall apart for predictable reasons. Shadow IT adds apps and devices outside the process. Devices get moved to another office with no notice. Spare gear gets handed out "just for today" and never comes back. In addition, teams sometimes create duplicated asset IDs, which breaks searches and audit trails. Finally, old records stay open, so retired or replaced devices still look active.
You can prevent most of this with a few habits that are easy to teach and repeat. First, run every new item through a basic intake process (tag it, record it, set status to in stock). Next, use a simple check-in and check-out form so every handoff creates a timestamp and an owner. Also, schedule spot checks (small samples beat rare, painful full counts). Most importantly, set a rule that every device change triggers an update, including moves, repairs, loaners, and retirements.
Use this short checklist before you claim "audit ready":
- Each asset ID is unique, with no duplicates.
- Status matches reality (in stock, deployed, repair, retired).
- Assigned user and location are filled in for deployed items.
- Warranty and purchase dates exist for supported hardware.
- Software counts reconcile (purchased, assigned, available).
Small, frequent updates keep the list trustworthy, which keeps your tickets and audits calm.
CMDB Basics
CompTIA A+ Core 2 (220-1202) Domain 4.1 Objective 4.1 (Asset management) expects you to understand why many teams move from a simple asset list to a CMDB. An inventory can tell you what you own, but a CMDB explains how systems fit together. That extra context matters during outages and planned changes, because you can predict impact instead of guessing.
In practice, a CMDB stores configuration items (CIs) (such as laptops, switches, servers, apps, and cloud services) and the relationships between them. Think of it like a map, not a checklist. When you can trace connections, you can find the true root cause faster and avoid breaking "unrelated" systems by accident.
Inventory list vs CMDB, when each one is enough
An inventory list answers "what and where." It tracks assets like laptops, printers, and switches, along with who has them and where they sit.