ACC-V Not Updating Existing CI with Discovery Source = ServiceNow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
8m ago
Hi Community,
We are testing ACC-V on an existing Windows Server CI.
Issue
The ACC agent is Up and Host Data Collection shows Collected, but the existing CI was not being updated.
The CI had: Discovery Source = ServiceNow
The agent also had only:
and Enhanced Discovery was not assigned.
Finding
The Enhanced Discovery Policy uses: sn_agent.disco_disable_ci_clobber_of_agentless_disco = true
When enabled, the policy filters for:
- AgentClientCollector
- ACC-Visibility
- ServiceNow DEX
Therefore, our CI with Discovery Source = ServiceNow was not getting qualified to trigger the Enhanced Discovery check.
Test
For testing only, I manually changed: ServiceNow → ACC-Visibility and triggered Collect Host Data again.
After this:
- Enhanced Discovery was assigned.
- Windows CI attributes were updated.
- MSFT SQL Instance and SQL Server Analysis Services were discovered.
- Related CMDB relationships were created.
Question
The documentation also mentions that this setting is ignored if Horizontal Discovery has not run within the configured threshold.
In our case, the last visible Horizontal Discovery update for this CI was more than 14 days before our ACC test, but Enhanced Discovery was still not assigned until we manually changed the Discovery Source to ACC-Visibility.
Existing IRE:
What is the recommended approach here? Should we set this property to false
Thanks!
