Discovery not populating the ServiceNow Running processes table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2018 06:20 AM
So i am running discovery on a device and i am trying to populate the running process table associated with that device. I know the ADM probe is the one that gets this information for me and once the probe runs the running processes information is returned back in the XML but for some reason it is not populating the running processes table, does any one know what is going on here? it works when i do it on windows servers but i am trying to get the running processes of a windows 10 device to get populated.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2018 08:12 AM
Are there any errors in the ecc queue response on the input for ADM? Check that first and see if there are any issues with it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2018 08:49 AM
No errors on the ecc queue for the ADM probe. It says it is processed but still will not populate the running process table. I can clearly see in the xml that is that the running processes are being returned, i just don't know why it is populating that table for servers but not for the windows 10 devices.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-06-2022 03:32 PM
Hi,
The probe Windows - Application Dependency Mapping is being invoked to collect the process data.
The decision to call this probe Windows - Application Dependency Mapping is governed by multiple parameters of which one is the value of target_powershell_access parameter in the wmi classify payload. A value of false means, that Discovery is unable to use PowerShell to collect the process data from target devices.
Hence, please "<parameter name="target_powershell_access" value="false"/>" it is returning of false or true.
If target_powershell_access is coming as false that means, the Powershell on the target device is not enabled for Discovery to run and collect the data. So enabling the PowerShell on the target device will resolve the issue.
- Please verify Point 4 in the below KB.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0549830 - Please refer to the below doc for more information on enabling remote Powershell.
https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/enable-psremoting?view=...
Regards,
Nayan
