IT Asset Management (ITAM) for MSPs: From Chaos to Complete Visibility

Introduction: The Hidden Cost of Unknown Assets

Most organizations know they have an IT asset problem. What they do not know is how expensive it is.

Consider what happens in a typical organization without structured IT asset management:

• Software license compliance violations: A company running 150 seats of an application they have purchased 100 licenses for is at risk of a software audit that could cost tens of thousands in back-licensing fees.
• Shadow IT: Employees sign up for SaaS tools on corporate cards without IT knowledge. These tools process company data, have no security review, and accumulate $50–$200/month each until someone looks at the credit card statement.
• Forgotten warranties and renewals: A server fails, and only then does the team discover the warranty expired 8 months ago. Emergency hardware replacement at double the planned budget.
• Security blind spots: An unmonitored laptop with an unpatched OS becomes the entry point for ransomware.
• Inefficient procurement: Without knowing what you have, you buy new when you should be redeploying existing assets.

For MSPs, their clients' ITAM problems are directly their problems — both as a service delivery challenge and as a business opportunity.

What Is IT Asset Management?

IT Asset Management (ITAM) is the set of business practices that join financial, contractual, and inventory functions to support the lifecycle management of IT assets.

The scope of ITAM includes:

Hardware assets: Physical devices — laptops, desktops, servers, network equipment, mobile devices, printers, and peripherals. Each with purchase date, warranty, location, assigned user, and end-of-life date.

Software assets: Installed applications, their license entitlements, actual usage, and compliance status.

SaaS and cloud assets: Cloud subscriptions, SaaS tools, cloud infrastructure resources — often the fastest-growing and most neglected category.

Contracts and licenses: EULAs, maintenance agreements, software assurance, support contracts.

The Asset Lifecycle: Five Stages

Effective ITAM manages assets across their complete lifecycle:

Stage 1: Planning and Procurement

Asset management begins before purchase. Questions to answer:

• What is the standard hardware configuration for each role type?
• What is the expected useful life of each asset class? (Laptops: 3–4 years; Servers: 5–7 years; Network switches: 7–10 years)
• What is the procurement process and approval threshold?
• What vendors are preferred and why?
• What lease vs. buy analysis applies?

Standardization dramatically reduces ITAM complexity. An organization with 5 approved laptop models is much easier to manage than one where every procurement is a different brand and model.

Stage 2: Deployment and Registration

When a new asset arrives:

• Assign a unique asset ID and label it physically
• Register in the ITAM system: serial number, model, purchase date, purchase price, warranty end date, assigned user/location
• Configure to organizational baseline (imaging, software deployment, security agent installation)
• Link to the purchase record and warranty documentation

Most RMM agents perform hardware inventory automatically — capturing serial numbers, model numbers, BIOS versions, and hardware specifications from the OS. This automated discovery dramatically reduces the manual work of asset registration.

Stage 3: In-Life Management

During the asset's active life:

• Track location and reassignment when assets move between users
• Monitor hardware health (SMART data, temperature, fan speeds)
• Manage software installed on the asset
• Track warranty status and flag assets approaching warranty end
• Manage contract renewals associated with the asset

Stage 4: Refresh Planning

Assets approaching end-of-life require proactive replacement planning. Create a hardware refresh report quarterly showing:

• Assets by age (> 3 years for laptops, > 5 years for servers)
• Assets by warranty status (expired, expiring within 6 months)
• Assets by health indicators (SMART data, repair history, performance degradation)

This converts emergency hardware failures into planned budget line items.

Stage 5: Retirement and Disposal

End-of-life asset management is often overlooked:

• Secure data destruction before any hardware leaves the organization (certificate of destruction for auditable environments)
• Process for charitable donation vs. resale vs. e-waste recycling
• License reclamation (return licenses to the pool when hardware is retired)
• Asset register update (mark as retired, do not just remove the record)

Automated Asset Discovery with RMM

The foundation of scalable ITAM is automated discovery. Manual asset audits are point-in-time snapshots that are outdated the moment they are complete. RMM agent-based continuous discovery provides live, always-current asset data.

What RMM agents discover automatically:

• Hardware: Make, model, serial number, CPU, RAM, storage drives, network adapters, display adapters
• Operating system: Version, build, last boot time, activation status
• Installed software: All applications with version numbers, install date, publisher
• Network: MAC addresses, IP addresses, hostname
• BIOS/firmware: Version numbers (critical for security vulnerability tracking)
• Hardware health: SMART data for drives, temperature sensors, battery health for laptops

Building an asset database from RMM data:

Most RMM platforms expose hardware inventory data via API. You can export this to:

• A spreadsheet for smaller environments
• Your PSA's asset management module (ConnectWise, Autotask, HaloPSA)
• A dedicated ITAM platform (Asset Panda, Snipe-IT, Lansweeper, NinjaIT's built-in asset inventory)

The key advantage of RMM-driven discovery: every device with an agent is automatically discovered and kept current. No manual scanning required.

Data Mammoth(opens in new tab), which manages hosting infrastructure for hundreds of clients, uses automated ITAM discovery to maintain accurate server inventory across their entire fleet — enabling proactive warranty management and capacity planning at scale.

Software License Management: Where Money Leaks

Software license management is the most financially impactful component of ITAM for most organizations. Two problems dominate:

Over-licensing: Paying for more licenses than you use. Common causes: headcount reductions without license optimization, mergers that create duplicate tools, SaaS tools purchased by departments independently.

Under-licensing: Running more instances than you are licensed for. Risk: vendor audit, back-licensing fees, and potential legal action.

Software License Categories

Understanding license types is essential for compliance:

Per-device: One license per physical device. The license follows the device, not the user.

Per-user: One license per named user. The user can install on multiple devices (typically 2–5) per the license terms.

Concurrent: N users can use the application simultaneously, regardless of total installed count. Popular for ERP and CAD applications.

Subscription (SaaS): Monthly or annual subscription, typically per user. Usually includes the right to use current versions only.

OEM (Original Equipment Manufacturer): Bundled with hardware purchase. Tied to the original device; typically non-transferable.

Volume Licensing: Enterprise agreements (Microsoft EA, Google Workspace Business) that cover a defined organization. Typically include deployment rights, upgrade rights, and Software Assurance.

Software License Audit Process

Run a quarterly software license audit:

1. Inventory what is installed: Export the full software inventory from your RMM for all managed devices
2. Map to purchased licenses: Match installed software to your license purchase records
3. Identify gaps: Software installed without corresponding purchased licenses
4. Identify waste: Licenses purchased but unused or underused
5. Remediate: Purchase missing licenses, reclaim unused licenses, uninstall unauthorized software
6. Document: Update the license register

SaaS Governance

SaaS is the fastest-growing and most chaotic asset category. Without governance, organizations accumulate dozens of SaaS subscriptions paying on corporate cards, many of which:

• Are used by only 1–2 people
• Process sensitive data without security review
• Have overlapping functionality with already-licensed tools
• Continue charging after the person who signed up has left the company

Building a SaaS inventory:

1. Review corporate credit card statements for recurring SaaS charges
2. Review accounts payable for annual SaaS renewals
3. Survey department heads for tools their teams use
4. Check browser extension lists on managed devices (browser extensions often indicate SaaS usage)
5. Review identity provider (Okta, Azure AD, Google Workspace) for connected apps

A practical SaaS management process:

• Require IT approval before new SaaS tools are purchased
• Assign an owner to each SaaS tool (the person responsible for managing access)
• Quarterly review: who is using each tool? Is it still providing value?
• Offboarding process: when an employee leaves, deprovision their SaaS access immediately

The ITAM Governance Framework

Without governance, ITAM degrades. Define clear policies and responsibilities.

Roles and Responsibilities (RACI Matrix)

R = Responsible, A = Accountable, C = Consulted, I = Informed

The Minimum Viable Asset Record (MVAR)

Not every asset needs 50 data fields. Define the minimum dataset you will capture for each asset class:

Hardware devices:

• Asset ID (internal)
• Asset type (laptop, desktop, server, etc.)
• Make and model
• Serial number
• Purchase date
• Warranty end date
• Assigned user/location
• Operating system and version
• Monitoring status (in RMM yes/no)

Software licenses:

• Software name and version
• Vendor
• License type (per-device, per-user, concurrent, subscription)
• License count (purchased)
• License count (deployed)
• Renewal date
• Annual cost
• Contract/purchase order reference

ITAM for Compliance

IT asset management directly supports multiple compliance frameworks:

SOC 2 CC6.1 and CC6.2: Require that access is restricted to authorized personnel and that asset configurations are maintained. An accurate asset inventory is evidence for both.

ISO 27001 A.8: "Asset Management" is a dedicated ISO 27001 domain requiring an asset inventory, asset ownership, and acceptable use policies.

CMMC Level 2 (3.4.1): "Establish and maintain baseline configurations and inventories of organizational systems." Your ITAM system is the direct evidence for this control.

CIS Control 1 and 2: The first two CIS Controls are "Inventory and Control of Enterprise Assets" and "Inventory and Control of Software Assets" — ITAM is the literal implementation of the two most fundamental security controls.

ITAM as an MSP Service Offering

For MSPs, ITAM is both an internal operational requirement and a service you can sell to clients.

What clients get from managed ITAM:

• Accurate, always-current hardware inventory
• Warranty tracking with proactive renewal alerts
• Software license compliance monitoring
• SaaS governance and cost optimization
• Hardware refresh planning reports for budget conversations
• Compliance evidence for audits

Packaging ITAM services:

• Include basic asset discovery (via RMM) in your standard managed services package
• Offer enhanced ITAM as an add-on: $2–$5/device/month for full lifecycle management, license management, and SaaS governance
• Annual ITAM audits as project work: $3,000–$8,000 for a comprehensive license compliance audit and cleanup

NinjaIT's device management and reporting includes hardware inventory discovery, software inventory, and warranty tracking out of the box — giving MSPs the foundation for ITAM-as-a-service without additional tooling.

Frequently Asked Questions

What is the difference between ITAM and ITSM? ITAM (IT Asset Management) focuses on the financial and lifecycle management of IT assets. ITSM (IT Service Management) focuses on the delivery and support of IT services. They overlap in the Configuration Management Database (CMDB) — ITSM needs to know what assets exist to manage them as configuration items. Your RMM can serve as the discovery source for both.

Should I use a dedicated ITAM tool or integrate with my RMM? For most MSPs, the RMM is the best source of hardware and software inventory data. A dedicated ITAM tool adds value when you need: formal contract management, financial depreciation tracking, advanced license compliance analytics, or hardware refresh forecasting. Evaluate dedicated ITAM when your managed endpoint count exceeds 2,000 or when you are selling ITAM as a premium service.

How often should I run a software license audit? Quarterly for high-cost software (Microsoft, Adobe, AutoCAD). Monthly for SaaS subscription review. Annual comprehensive audit that includes all installed software across the entire environment.

What is a software audit from a vendor, and how do I handle it? Vendors (Microsoft, Oracle, SAP, Adobe) have the right to audit software usage under most enterprise agreements. If you receive an audit notice: immediately engage legal counsel familiar with software licensing, do not respond with discovery data until you understand the scope, conduct your own internal audit first to understand your position, and negotiate — first audit findings are almost always a starting point, not a final demand.

Conclusion

IT asset management is the operational foundation that makes everything else in IT management more effective. You cannot patch what you do not know exists. You cannot secure what you cannot inventory. You cannot budget for hardware replacement without lifecycle data.

The investment in building proper ITAM practices — automated discovery, lifecycle tracking, license management — pays dividends in security, compliance, and cost optimization.

For MSPs, ITAM is also a service differentiation opportunity. Clients who have experienced the chaos of poor asset management appreciate the structured visibility that good ITAM provides — and are willing to pay for it.

Start with automated RMM discovery, build your asset register, and add license management as your second step. Related reading: what is RMM, infrastructure metrics to monitor, and MSP client onboarding guide.

Hardware Lifecycle Planning: The Budget Conversation Tool

One of the most valuable outputs of mature ITAM is a hardware refresh forecast — a report that shows clients their aging hardware and the projected cost to replace it on a schedule.

Building a Hardware Refresh Report

A hardware refresh report answers three questions:

1. What do we have that is end-of-life or approaching it?
2. What will it cost to replace, and on what timeline?
3. What is the risk of not replacing on schedule?

Step 1: Age the asset inventory

Export your full hardware inventory with purchase dates. Calculate device age. Flag:

• Laptops > 3.5 years
• Desktops > 4 years
• Servers > 5 years
• Network switches and routers > 7 years
• UPS/battery backup > 5 years

Step 2: Layer warranty status

Devices outside warranty have three risk categories:

• At risk: Warranty expired in the past 12 months. Operating with no hardware support.
• Urgent: Warranty expired > 12 months ago. Hardware failure requires emergency procurement.
• Critical: More than 2 years out of warranty. Ongoing operations on legacy hardware with no support.

Step 3: Build the replacement cost estimate

For each aging device, list the replacement cost at current pricing. Be specific: "14 HP EliteBook 840 G7 laptops at $1,200 each = $16,800" is more compelling than "laptops need replacement."

Step 4: Recommend a replacement timeline

Spreading hardware refresh across 2–3 budget years is more financially realistic for most clients than replacing everything at once. Create a phased schedule:

• Year 1: Critical servers and end-of-warranty workstations
• Year 2: At-risk laptops and aging network equipment
• Year 3: Remaining desktop refresh

This becomes the technology roadmap presented at each QBR, making hardware spending predictable and budgetable for clients instead of a series of emergency expenditures.

The Business Case for Proactive Hardware Refresh

Clients who understand the cost of reactive hardware management invest in proactive refresh. The business case:

Emergency procurement premium: Hardware purchased in an emergency (failed server with production data at risk) costs 15–30% more than planned hardware procured through normal channels, because you need immediate delivery and have limited negotiating leverage.

Lost productivity during failure: A server failure that takes 8 hours to resolve costs a 20-person company roughly 160 person-hours of lost productivity at $50/hour average fully-loaded labor cost = $8,000 in lost productivity, plus the emergency hardware and labor cost.

Data loss risk: Aging drives have higher failure rates. ITAM data on drive age and SMART status lets you replace drives proactively before they fail — preventing data loss that is orders of magnitude more expensive than the drive replacement.

For clients who are hesitant to invest in hardware refresh, this business case — quantified with their actual data — is often compelling.

Cloud and Virtual Asset Management

As organizations move workloads to cloud, the asset management challenge shifts from physical to virtual and subscription-based. Modern ITAM must cover:

IaaS and PaaS Resource Tracking

Infrastructure-as-a-service (AWS EC2, Azure VMs, Google Compute Engine) and platform-as-a-service resources are assets just like physical servers, with their own lifecycle management requirements:

Cloud resource inventory: What VMs, containers, databases, and storage resources exist? In multi-cloud environments, visibility requires dedicated cloud management tools or cloud-native services (AWS Config, Azure Resource Graph, GCP Cloud Asset Inventory).

Cost allocation: Cloud resources generate costs by usage. Without tagging and cost allocation policies, cloud spending becomes a black box. Implement resource tags that map to clients, projects, and cost centers.

Right-sizing: Cloud resources are frequently over-provisioned. A quarterly right-sizing analysis — comparing actual resource utilization to provisioned capacity — typically identifies 20–35% cost reduction opportunities without performance impact. See our cloud cost optimization guide for detailed methodology.

Idle resource identification: Cloud environments frequently accumulate idle resources: stopped VMs still incurring storage costs, unattached storage volumes, orphaned snapshots, unused load balancers. An ITAM discipline for cloud means regularly auditing for and terminating idle resources.

Microsoft 365 and Google Workspace License Management

These are among the most commonly over-licensed tools in any organization. The lifecycle management process:

Provisioning: When a new employee joins, assign the appropriate license tier (Business Basic vs. Business Standard vs. Business Premium in M365 terms). Not every employee needs the same tier — field workers may need only mobile email while knowledge workers need the full suite.

Deprovisioning: When an employee leaves, immediately deprovision their license. In Microsoft 365, you can convert the account to a shared mailbox (which doesn't require a paid license) for 30 days while preserving their email access for handover. Then fully remove.

License tier optimization: Quarterly, review who has which license tier and whether they are actually using the features of their tier. An employee with a Business Premium license ($22/month) who only uses email could be downgraded to Business Basic ($6/month), saving $16/user/month.

Benchmark: Most MSPs find 15–25% license cost reduction opportunities in their first M365 license audit for a client. This finding pays for the cost of the ITAM service and creates goodwill.

Endpoint Management for Remote and Hybrid Workforces

The shift to remote and hybrid work has made endpoint ITAM more complex. Physical location of assets is now distributed — home offices, coffee shops, client sites — making physical inventory impractical. RMM agent-based inventory is the only scalable solution.

Additional considerations for distributed workforces:

Device ownership policies: Company-owned vs. BYOD (Bring Your Own Device) requires different ITAM approaches. BYOD devices should appear in the asset inventory but may be excluded from certain management policies.

Home network security: Endpoints on home networks are exposed to different risk profiles than office endpoints. ITAM data on network configuration and VPN connectivity helps security teams assess exposure.

Physical asset recovery: When remote employees leave, you need a documented process for recovering company hardware. The ITAM record should include the device's assigned user and last known location to facilitate recovery.

ITAM Tooling: An Honest Comparison

Choosing the right ITAM tool depends on your scale, budget, and requirements. Here is an honest assessment of the options:

RMM-Native Asset Management

Best for: MSPs who want a unified platform without additional tooling.

NinjaIT: Strong hardware inventory, software inventory, and warranty tracking integrated with monitoring and patching. Best for MSPs who want a single pane of glass.

ConnectWise Automate: Mature hardware and software inventory with deep PSA integration. Best for larger MSPs on the ConnectWise stack.

Datto RMM: Good inventory with Autotask integration. Best for existing Kaseya/Datto customers.

Limitations: RMM-native tools typically lack financial tracking (depreciation, total cost of ownership) and formal contract management. For MSPs needing these features, supplement with a dedicated tool.

Dedicated ITAM Platforms

Snipe-IT (open source): Excellent free option for basic hardware lifecycle management. Active development, strong community. Requires self-hosting. No license management.

Asset Panda: Purpose-built ITAM with mobile check-in/check-out, barcode scanning, contract management, and warranty tracking. Good for MSPs managing physical assets in multiple client locations.

Lansweeper: Network discovery plus asset management. Strong IT and non-IT asset tracking. Popular for CMDB-style asset management.

ServiceNow ITAM (for enterprise): The de facto standard for enterprise ITAM, but expensive ($50,000+/year) and complex. Only relevant for MSPs managing very large enterprise environments.

ITSM Platforms with Asset Management

Freshservice: ITSM with integrated ITAM. Auto-discovery, contract management, and strong reporting. Good mid-market option.

HaloPSA: MSP-focused ITSM with asset management built in. Best for MSPs who want PSA + asset management + ticketing in one platform.

Jira Service Management (Assets): For MSPs already on the Atlassian stack. Complex but flexible.

Selection Criteria

When evaluating ITAM tools, prioritize:

1. Integration with your RMM (bidirectional sync, not just export)
2. Software license management capabilities (not just hardware)
3. Reporting flexibility (can you generate the reports your clients need?)
4. Automation (auto-import from RMM discovery, not manual entry)
5. Multi-tenant support (critical for MSPs managing multiple client environments)

ITAM Program Maturity Model

Building a mature ITAM program is a journey, not an event. Most MSPs progress through three maturity levels:

Level 1: Foundational (Months 1–3)

What you have:

• RMM agent deployed on all managed devices
• Automated hardware inventory in the RMM
• Basic software inventory visible per device
• Physical assets tagged and logged in a spreadsheet or PSA

What you can do:

• Know what you have (approximately)
• Identify unmanaged devices
• Answer basic audit questions

What you cannot do:

• License compliance analysis
• Accurate warranty tracking at scale
• Proactive hardware refresh planning

Level 2: Operational (Months 3–9)

What you add:

• Structured asset register with warranty dates
• Software license tracking linked to purchase records
• Maintenance schedules tied to asset records
• Monthly reporting on asset status per client

What you can do:

• Track warranty expiration proactively
• Identify obvious license compliance gaps
• Generate hardware refresh reports for QBRs
• Recover assets when employees leave (deprovisioning checklist)

Level 3: Optimized (Months 9–18)

What you add:

• Full software license reconciliation (installed vs. licensed)
• SaaS inventory and governance process
• Cloud resource tracking and cost allocation
• Compliance mapping (which assets cover which controls)
• ITAM data integrated with security tooling (vulnerability scanner knows asset inventory)

What you can do:

• Pass software audits with confidence
• Identify license optimization opportunities that save clients money
• Support compliance audits with documented asset evidence
• Forecast total IT spend 2–3 years forward

Practical ITAM Workflows for MSPs

New Employee Onboarding

When a new employee joins a client:

1. Ticket created: Onboarding request received 5+ business days before start date
2. Asset selection: Pull from asset register — is there a suitable device in stock? If not, initiate procurement with the lead time the hardware refresh planning has budgeted for.
3. Device preparation: Image or configure the device to the role-based standard. Log in RMM (verify agent install).
4. Software licensing: Check software license inventory before installing licensed software. Confirm a license is available. If not, initiate purchase before installation.
5. SaaS provisioning: Against a role-based SaaS access list, provision the employee in each tool. Log provisioning in the ITAM system (owned by this user).
6. Asset assignment: Update asset record: assigned to [Employee Name], [Department], [Location], start date.
7. Documentation: Update IT Glue/Hudu with the new employee's asset details.

Employee Offboarding

When an employee leaves a client:

1. Advance notice: Receive notice from HR (or IT contact) of departure date. This is the ideal; in practice, you may receive same-day notice.
2. Account deprovisioning: On the last day, disable Active Directory/Entra account, revoke SSO, disable MFA. Do not delete immediately — retain for 30 days for data recovery requests.
3. SaaS deprovisioning: Against the ITAM record for this user, disable access in every SaaS tool they were provisioned for. This step is commonly missed and creates security and compliance risk.
4. License reclamation: Return reclaimed software licenses to the available pool in the license inventory.
5. Asset recovery: Coordinate physical return of company hardware. Update asset record: unassigned, location = [storage room/IT closet].
6. Data retrieval: Before wiping the device, export any data that needs to be preserved (per the client's data retention policy).
7. Device preparation for redeployment: Wipe and re-image, or prepare for retirement if beyond useful life.

CyberXper(opens in new tab) provides cybersecurity expertise for complex offboarding scenarios, including forensic data extraction from corporate devices when employees depart under sensitive circumstances.

ITAM and Cybersecurity: The Intersection

IT asset management and cybersecurity are deeply interconnected. You cannot secure what you do not know you have.

Asset Inventory as the Security Baseline

CIS Control 1 ("Inventory and Control of Enterprise Assets") and CIS Control 2 ("Inventory and Control of Software Assets") are the first two controls for a reason: every other security control depends on knowing your asset inventory.

You cannot:

• Patch what you do not know exists
• Monitor devices that are not in your monitoring tool
• Apply endpoint protection to unknown endpoints
• Restrict network access to known devices without an accurate device list

Your RMM asset inventory is your security perimeter. Unmanaged devices — laptops, personal phones accessing corporate email, IoT devices on the corporate network — represent blind spots that attackers exploit.

Shadow device detection: Configure your RMM and/or network monitoring to detect devices on the corporate network that do not have a management agent. These are the unmanaged endpoints that need to be either brought under management or explicitly excluded.

Software Inventory and Vulnerability Management

When your vulnerability scanner (Tenable, Qualys, Rapid7) identifies a critical vulnerability in "Apache Log4j version 2.14," your ITAM software inventory answers the critical triage question: "Which of our managed devices have Apache Log4j installed, and which version?"

Without a software inventory, this question requires manual investigation across every device — taking hours or days. With an accurate software inventory, you query the database and have an answer in seconds.

This is why software inventory is not just a license management tool — it is a security response accelerator.

End-of-Life Software as a Security Control

Unsupported software — Windows 7, Windows Server 2008, Internet Explorer, Adobe Flash — is a security liability because vendors no longer release security patches for it. Without a software inventory and lifecycle tracking, end-of-life software persists in environments long after it should have been retired.

ITAM provides the visibility to identify and prioritize end-of-life software remediation: upgrade the OS, replace the application, or isolate the device from the network if immediate replacement is not possible.

Conclusion: ITAM as a Strategic Service

The most successful MSPs treat ITAM not as overhead — an operational necessity they try to keep cost-efficient — but as a strategic service they actively sell and continuously improve.

Clients who have experienced the pain of a failed server outside warranty, an unexpected software audit, or the discovery that 20 former employees still have active SaaS accounts are motivated buyers of structured ITAM services.

Your pitch is simple: "We know exactly what you have, what condition it is in, what it costs you, and when it needs to be replaced. You never get surprised by hardware failures, compliance audits, or unexpected license costs."

That is the value of mature ITAM — and it is a compelling value proposition for any organization that has experienced the chaos of managing IT without it.

Frequently Asked Questions About IT Asset Management

What is the minimum viable ITAM program for a 50-person company?

Minimum viable: (1) a hardware inventory spreadsheet or simple ITAM tool updated whenever devices are added, modified, or retired; (2) RMM-based software inventory showing installed applications per device; (3) a license register tracking purchased vs. deployed counts for your 5 most expensive software titles; (4) a calendar alert 90 days before warranty expiry for all servers. This provides 80% of the security and financial benefit of mature ITAM at 20% of the effort. Expand from here as the organization grows.

How do I handle BYOD (Bring Your Own Device) in ITAM?

BYOD devices present a unique ITAM challenge: you need to know what devices are accessing corporate data (security requirement) without necessarily managing them as corporate assets (privacy and liability concern). Approach: implement Mobile Device Management (MDM) with a conditional access policy — only devices enrolled in MDM can access corporate email and apps. MDM enrollment creates an ITAM record for the device (device type, OS version, compliance status) without full management of personal apps or data. Track BYOD devices in a separate asset category with explicit "employee-owned" designation.

What happens to ITAM data when we change RMM platforms?

Historical RMM data (hardware specs, software inventory, performance history) typically does not migrate between platforms. The new platform starts building its own asset history from deployment. Mitigate this by: exporting key asset data (hardware specs, serial numbers, warranty dates, purchase records) to a spreadsheet or dedicated ITAM tool before migration. This core asset data is platform-independent and should survive platform changes. Performance history and monitoring history will be lost — accept this as the cost of migration and ensure the new platform starts building history from day one.

How should I handle assets that go missing or are stolen?

Document the missing asset report in your ITAM system immediately. If the device had full-disk encryption (it should), the data is protected. File a police report for stolen assets (required for insurance claims and some compliance frameworks). Remotely wipe the device via MDM if it is still online. Update the insurance policy if the asset value meets the reporting threshold. Conduct a root cause analysis: how did the asset go missing? Was it inadequate physical security, poor check-out procedures, or lack of asset tracking? Address the process gap to prevent recurrence.