Discovering CI via OOTB Discovery.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2025 09:34 PM
We have our CIs created through Azure service graph connector. I tried to run discovery on them to identify if the fields we would like to pull through discovery are available OOB. (Computer class and its child, fields are IP address, Description, RAM, CPU Speed, Disk Space, firmware version, Serial Number).
However, I'm running into Below Issue, looks like it could be due to our discovery not configured yet.
1) The following protocols have been disabled via the Configuration Console and will not be scanned by Shazzam: wbem
2) Can't connect to target host via WinRM service, and this MID server is set to connect via WinRM only
Let me know if I should leverage discovery for pulling in those fields or If I can do this in Azure Service graph connector.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2025 11:32 PM
Hi @pardhiv ,
As per ServiceNow documentation following data will be populated
please refer the ServiceNow documentation:
CMDB classes targeted in Service Graph Connector for Microsoft Azure
If my response helped, please hit the 👍Thumb Icon and accept the solution so that it benefits future readers.
Regards,
Pratik