Components Tab Data Consistency After Normal Scan

After a Normal Scan on Windows machines, several component tabs previously displayed inconsistent or missing data across the Installed Software, Network Adapters, Peripheral Devices, Services, and IP Connections tabs. End-to-end handling of Agent Normal Scan results between the Discovery Agent, Discovery Server, and the Components UI has been improved. Every component row now resolves its asset linkage correctly, install metadata captured by the agent is persisted through to the UI, and grid totals are computed from the same dataset that drives paging.

Issues addressed

The fix resolves the following inconsistencies in component data:

Component tab Previous issue
Installed Software Blank Asset Name values and missing Software Install Date for entries such as Microsoft 365 Apps, Microsoft Teams Meeting Add-in, and Microsoft OneDrive.
Network Adapters Adapter names were missing and the adapter count did not match what was detected on the machine.
Peripheral Devices and Services Record counts were incorrect and did not reflect the actual device or service count from the scan.
Services Asset Name was missing from all service entries.
IP Connections Pagination showed invalid totals (for example, "Showing 101-101 of 101") while still offering a page 2 navigation link.

Where the fix appears

The corrected component data is visible in the following locations:

Location What changed
CMDB > Windows Host CI > Installed Software tab Asset Name is populated correctly, and Software Install Date is available for entries including Microsoft 365 Apps, Teams, and OneDrive.
CMDB > Windows Host CI > Network Adapters tab Adapter names display correctly, and the count matches what the agent detected on the machine.
CMDB > Windows Host CI > Peripheral Devices and Services tabs Record counts accurately reflect the actual number detected during the scan.
CMDB > Windows Host CI > Services tab Asset Name is populated for all service entries.
CMDB > Windows Host CI > IP Connections tab Pagination totals match the true record count. No more invalid trailing pages.

Procedure

Complete the following step after upgrading to v6.1.2 to repopulate component data for existing Windows hosts.

  1. Re-run the Agent Normal Scan.

    Trigger a new Normal Scan on affected Windows hosts to repopulate component data with the corrected values. No configuration changes are needed; the fix takes effect automatically.


Copyright © 2026 Virima, Inc. All rights reserved. v6.1