- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2022 06:51 AM
Hi all, could you please share your experience with troubleshooting missing "running processes" for Win servers after discovery. Any advice for a starting point would be appreciated.
Thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2022 09:15 AM
You can check the Windows - ADM probe and see if active processes section is displaying any error.
Also you can login to the MID Server and try to fetch below information from the MID Server through the discovery user to review if there are any errors displayed.
Get-WmiObject -class Win32_Process -ComputerName <IP-Address-of-the-Target> | Select -first 10 Name, Caption, Description, CreationDate, CommandLine, ExecutablePath, ParentProcessId, ProcessId, Priority
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2022 09:15 AM
You can check the Windows - ADM probe and see if active processes section is displaying any error.
Also you can login to the MID Server and try to fetch below information from the MID Server through the discovery user to review if there are any errors displayed.
Get-WmiObject -class Win32_Process -ComputerName <IP-Address-of-the-Target> | Select -first 10 Name, Caption, Description, CreationDate, CommandLine, ExecutablePath, ParentProcessId, ProcessId, Priority
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2022 09:16 AM
Thanks, just finished some ADM probe testing.
Appreciate the information provided.
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2022 09:49 AM
You are welcome @Mark Todorov