Hi @Deepanshu Grov1 ,
When you see CIs discovered by ACC‑Visibility without the OS Build Version, it’s not a bug so much as a limitation of what that source collects. ACC‑Visibility is designed to give you broad inventory and visibility, but it doesn’t always pull in detailed attributes like the OS build number.
What’s collected: ACC‑Visibility usually brings in basics like hostname, IP, OS type, and version. The build number isn’t part of its default payload.
Discovery patterns: The patterns used for ACC‑Visibility don’t query the OS build field. Unless you extend them, that data won’t be captured.
Mapping rules: Even if the data were collected, you’d need to make sure the Identification and Reconciliation rules map it into the `os_build_version` field.
Access level: ACC‑Visibility often runs without deep credentials, so it can’t query detailed OS info. Credential‑based discovery (like WMI for Windows or `uname` for Linux) is what normally provides build numbers.
ACC‑Visibility doesn’t populate OS build out of the box. To get that detail, you’ll need to either extend the discovery patterns or run credential‑based discovery alongside ACC‑Visibility.
Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for
Kind Regards,
Pavani P
