Discovery Scans return inconsistent results - Windows servers don' t respond to all port probes all the timeIssue A discovery schedule runs and every time it is executed on demand it returns a different result. e.g. Discovery Status DIS001234 has a source 1.2.3.4 which could not be classified. However when running a quick discovery on source 1.2.3.4, it gets discovered successfully. Because of this behaviour every time the discovery schedule is run, the list of sources which didn't get discovered, changes.CauseThere are 2 full networks being discovered in 1 schedule by 1 MID server When a MID server is on a slower network/overloaded, sometimes the port probes that are being sent out don't get returned in a timely manner, and therefore don't get reported back to the instance. ResolutionImplement discovery behaviours or limit the schedules to a smaller range of IP addresses. Implement one of the below options or combine them: (1) Split the Network to multiple discovery schedules and run them 1 after the other if you want to discover all devices in a particular range together (2) Create multiple schedules with Discovery Behaviours. This will create targeted probe scans and will limit the port probes we are sending. Today, we created a WMI only behaviour to only discover Windows Servers but you can customize this according to your needs. create-disco-behavior.html has more details on discovery behaviours.