Windows server taking too much time to discover through Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2022 03:35 AM
We are facing issue with windows server discovery. Windows schedule taking too long time to discover the CI's (One IP taking more than 20+ minutes, attached screenshot of time performance).
- We have noted during some of the network tracing we have completed that the windows discovery tries to communicate on port 5986 which is not open on the target windows devices. This in for WinRM_ssl which is a secure port. We have set the MID server parameters to use WMI only as WinRM causes security issues – this is set on the existing MID servers and the new MID server.
We can see from the discovery timeline logs that the ‘WMI: Classify’ and ‘Windows OS – Servers’ Patterns are what is taking the time. MID server processing time has been observed at 11 mins. Probe execution time can be ~700 seconds.
Can anyone please provide the solution as soon as possible.
Thanks in advance
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2022 05:48 AM
I'd recommend checking the Pattern Log for your Windows Server Discovery runs. There is likely a Shared Library section which is performing something overly extensive, like gathering volumes for mapped network drives or numerous NICs.
From here, you may be able to elect to skip collecting this information with a precondition.
Open the Pattern in a Debug Mode for a problematic target device & click through the steps to identify where within the Pattern you're having slowness.
