Discovery in ITAM follows a workflow from preparing the Discovery Worker through reviewing discovered devices and mapping them to assets in ALM. Complete each stage in order so the worker can reach the targets, the job can authenticate successfully, and you can reconcile the resulting device records with the asset inventory.

Discovery workflow
1. Install the Discovery Worker
Install and configure a Discovery Worker in an environment that can connect to the ITAM Discovery service and the target devices. Complete the post-installation checks and confirm that the worker service is running before creating jobs.
For more information, see Discovery Worker Installation and Administration Guide.
2. Create accounts for the devices you want to discover
Create an active Discovery Account for each target type and authentication method in scope. For example, use WMI credentials for Windows devices, SSH credentials for Linux or Unix devices, and SNMP credentials for supported network devices. Other account types support cloud, database, hypervisor, container, API, and LDAP/AD discovery.
Test each account against a target through a Discovery Worker when the account form provides that option. The worker must be able to reach the target, and the account must have the permissions needed to collect discovery information.
For more information, see Discovery Accounts.
3. Create and run discovery jobs
Create a job for the device type or discovery source you want to scan. Configure its scope or target, select the appropriate active account, choose the scan and schedule settings, and assign an available Discovery Worker where required. Save and run the job, or activate its schedule to run it later.
The job sends work to the Discovery Worker. The worker connects to the configured targets, collects available inventory, and submits the results to ITAM as Discovered Devices.
For more information, see Discovery Jobs.
4. Review the discovered devices
After the job completes, open Discovered Devices and select the relevant department and device category. Confirm that the expected devices appear, then review their identity, discovery method, latest discovery time, status, and collected information. If expected devices are missing, check the job result, target scope, account status and permissions, connectivity, and worker availability.
For more information, refer, Discovered Devices.
5. Map discovered devices to ALM
Configure Asset Mapping for the relevant department, asset category, discovery type, and, when needed, discovery method. Set conditions to classify eligible devices and map discovery attributes to ALM asset attributes. Save the configuration, then select Run Sync to process eligible records when you want to run a manual sync. A successful discovery job can also start the synchronization process automatically.
Mapping matches discovered devices to existing assets or configuration items (CIs), or creates records when the configured rules allow it. See Asset Mapping for prerequisites, matching rules, and sync results.
For more information, refer Asset Mapping.
6. Verify mapping status
Return to Discovered Devices and review each device’s Mapping Status and Mapped Asset fields:
Mapped means the mapping process links the device to an existing asset or CI, or creates a new asset through the configured rules. The Mapped Asset field identifies the associated record.
Not mapped means the mapping process did not link the device to or create an asset or CI. Review the mapping configuration and sync results, then correct the rules or create the asset manually if appropriate.