How to Set Up IT Asset Management in Freshservice
What Will This Guide Cover?
Before diving into the setup steps, here is a quick summary of what this article walks through:
- Why IT asset management matters before you start configuring anything
- How Freshservice ITSM Software relates to setting up and maintaining an accurate asset inventory
- The core setup steps: configuring the CMDB, choosing discovery tools, and importing existing assets
- How to keep asset data accurate over time through automation and lifecycle workflows
- Common setup mistakes to avoid
- Answers to frequently asked questions about IT asset management in Freshservice
How Does Freshservice Relate to IT Asset Management Setup?
Freshservice ITSM Software includes a built-in Configuration Management Database, or CMDB, along with discovery tools that automatically detect hardware and software across an organization’s network. Because these features come built into the platform, setting up IT asset management does not require a separate discovery tool or a manually maintained spreadsheet; instead, administrators configure Freshservice’s native modules to build an accurate, continuously updated inventory.
This matters directly for anyone starting from scratch, since Freshservice reveals its value most clearly during the setup phase itself. Rather than importing static data once and letting it grow stale, Freshservice combines automated discovery, CSV imports, and mobile barcode scanning so that IT teams can build a foundation that stays accurate well after the initial configuration is complete.
Why Does Getting Asset Management Setup Right Matter From the Start?
Before jumping into configuration steps, it helps to understand why a careful setup process pays off later.
What Happens If the CMDB Starts With Inaccurate Data?
An inaccurate CMDB creates problems that ripple through every other ITSM process. Incident resolution slows down when agents cannot see which assets are actually affected, and change management becomes riskier when nobody can confirm real dependencies between systems. Getting discovery and imports right at the start avoids the far more time-consuming task of cleaning up bad data later.
Cleaning up a neglected CMDB after the fact often takes far longer than setting it up correctly from the beginning, since incorrect records tend to multiply as more tickets and automations reference them. Consequently, investing extra time upfront to verify discovery settings and import accuracy pays for itself many times over compared with correcting widespread data issues months down the line.
How Does Accurate Asset Data Support Other ITSM Processes?
A well-maintained CMDB feeds directly into incident, change, and problem management, since every ticket can link back to the specific hardware or software involved. This connection helps IT teams assess the impact of a change before it goes live, rather than discovering dependencies only after something breaks.
What Are the Core Steps to Set Up IT Asset Management in Freshservice?
Setting up asset management in Freshservice generally follows a logical sequence: configure the CMDB structure, choose a discovery method, import existing assets, and then maintain the data going forward.
How Do You Access and Configure the CMDB?
The CMDB lives under the Freshservice sidebar, where administrators can view and organize every Configuration Item, or CI, in the network. To begin, navigate to the CMDB module and review the default CI types, such as hardware, software, and network devices, adjusting them to match your organization’s actual asset categories. Establishing clear CI types early makes it much easier to filter, report, and automate workflows later.
Which Discovery Tools Should You Choose First?
Freshservice offers two main discovery tools for automatically populating the CMDB:
| Discovery Tool | Best For | How It Works |
|---|---|---|
| Discovery Agent | Laptops and roaming devices | Lightweight software installed on Windows, Mac, or Linux machines; reports data even off the network |
| Discovery Probe | Servers, printers, and stationary network devices | Installed on a server; scans IP ranges or domains to detect assets automatically |
Many organizations deploy both tools together, since the Discovery Agent tracks devices that move between locations, such as employee laptops, while the Discovery Probe covers fixed infrastructure like servers and network printers that stay within a defined IP range.
How Do You Install the Discovery Agent?
To configure the Discovery Agent, go to Admin, then Global Settings, then Asset Management, and select Discovery Hub. From there, click Configure Agent and Probe, choose the appropriate operating system, and download the installer. Installing the agent during device provisioning, rather than after devices are already deployed, helps ensure every new machine reports into the CMDB from day one.
How Do You Set Up the Discovery Probe?
The Discovery Probe requires installation on a server within the organization’s network. Once installed, a configuration wizard guides administrators through scanning parameters, including domain or IP range settings and the credentials needed to collect detailed data from devices using protocols like WMI for Windows or SSH for Linux. The Probe can also integrate directly with Microsoft SCCM if the organization already uses it, which simplifies data collection for existing SCCM-managed environments.
Additionally, the Discovery Probe can connect to Active Directory to synchronize user information alongside asset data. This matters because linking assets to specific users from the start makes it far easier to track ownership and accountability later, rather than trying to reconstruct that mapping manually after assets have already been imported into the CMDB.
How Do You Import Assets That Discovery Tools Cannot Reach?
For assets that discovery tools cannot detect automatically, Freshservice supports a few additional import methods:
- CSV import: Upload a spreadsheet of asset details directly into the CMDB, selecting the correct CI type before importing.
- Mobile barcode scanning: Use the Freshservice mobile app to scan an asset’s barcode, automatically pulling its information into the system.
- API integrations: Connect Freshservice with directory services such as Azure AD, or with platforms like Intune, to synchronize asset information automatically.
Combining these methods with automated discovery ensures that even assets outside the network, such as SaaS licenses or mobile devices, get captured in the CMDB. For organizations managing a mix of cloud subscriptions and physical hardware, this combination often provides the most complete picture, since no single method covers every asset type on its own.
How Do You Keep Asset Data Accurate After the Initial Setup?
Building the CMDB is only the first step. Freshservice also provides tools to keep that data current as the organization’s IT environment changes.
How Should Organizations Schedule Ongoing Discovery Scans?
Rather than treating discovery as a one-time event, administrators should schedule periodic scans through the Discovery Probe to catch new or changed assets automatically. Meanwhile, the Discovery Agent continues reporting hardware and software changes in real time from any device it is installed on, which keeps laptop and workstation data fresh without requiring manual scans.
How Can Automation Reduce Manual Asset Maintenance?
Freshservice allows administrators to build automation rules based on asset data, such as automatically flagging software licenses that have gone unused for a set period so they can be reassigned. This kind of automation reduces the manual auditing work IT teams previously handled through spreadsheets, freeing up time for higher-value tasks.
Beyond license management, automation rules can also trigger alerts when a warranty is about to expire or when a device has not reported data through the Discovery Agent for an unusually long time, which may signal a lost or decommissioned asset that needs follow-up. Building these rules early, right alongside the initial CMDB setup, helps organizations catch small issues before they accumulate into larger data quality problems.
How Does Freshservice Support Asset Retirement and Disposal?
When an asset reaches the end of its lifecycle, Freshservice can guide it through a standardized retirement workflow rather than relying on an informal checklist. This process typically includes generating a ticket to retrieve the physical device, creating a task to wipe data according to organizational standards, and updating the CMDB automatically once disposal is confirmed. Building this workflow during initial setup helps ensure consistent, auditable asset retirement from the start rather than adding it as an afterthought.
What Common Mistakes Should You Avoid During Setup?
A few recurring mistakes tend to undermine otherwise solid asset management setups.
Why Does Skipping Discovery Agent Deployment Cause Problems Later?
Organizations that import assets manually without deploying the Discovery Agent often end up with outdated records within weeks, since laptops and workstations change configurations frequently. Deploying the agent during device provisioning avoids this gap entirely, rather than trying to catch up later once data has already gone stale.
How Does Inconsistent CI Typing Create Reporting Issues?
If different team members categorize similar assets under inconsistent CI types, reporting and automation rules become far less reliable. Establishing clear naming conventions and CI type standards before importing large volumes of data prevents this kind of fragmentation, and documenting these standards in a shared reference makes it easier to onboard new IT staff without reintroducing the same inconsistencies later.
Why Should You Avoid Treating the CMDB as a One-Time Project?
Some organizations invest heavily in the initial CMDB setup, then stop reviewing or maintaining it afterward. Since IT environments change constantly, asset management works best as an ongoing process supported by scheduled scans, automation rules, and periodic manual audits rather than a single setup task considered finished once complete.
Conclusion
Setting up IT asset management in Freshservice starts with configuring the CMDB structure, choosing the right combination of Discovery Agent and Discovery Probe tools, and importing any remaining assets through CSV files, barcode scanning, or API integrations. From there, Freshservice supports ongoing accuracy through scheduled scans, automation rules, and standardized retirement workflows, which together prevent the CMDB from becoming outdated the way many manually maintained spreadsheets eventually do.
Organizations that take the time to plan CI types, deploy discovery tools consistently, and set up automation rules early tend to avoid the costly cleanup work that comes from letting asset data drift for months without review. Ultimately, the strength of an organization’s asset management program depends on treating setup as the beginning of an ongoing process rather than a single project to complete and forget. Freshservice ITSM Software gives IT teams the tools needed to build that foundation correctly from day one and maintain it reliably as the organization’s technology environment continues to grow and change.
Frequently Asked Questions
Most organizations benefit from deploying both, but if you need to choose one first, prioritize the Discovery Agent for laptops and other roaming devices, since it continues reporting data even when a device leaves the network. Add the Discovery Probe afterward to cover stationary assets like servers and printers within your internal network.
Yes. Freshservice supports CSV file imports and mobile barcode scanning for assets that discovery tools cannot detect automatically, such as older equipment or devices that rarely connect to the corporate network.
While the Discovery Agent reports changes in real time, the Discovery Probe should run on a regular schedule, such as weekly or biweekly, to catch new or modified assets across the network. Organizations with frequently changing environments may benefit from more frequent scans to keep the CMDB consistently accurate.
