vScope can use WMI (Windows Management Instrumentation) to discover information from Windows operating systems. Using the protocol can result in latency issues and slow down the Discovery in vScope. To not stall the Discovery, WMI has in vScope a timeout of 15 minutes. This means that if the WMI discovery of a resource is not finished after 15 minutes, vScope will stop Discovering this unit and throw:

Partial_OK

In the Discovery log.

This is how to solve this.

1. WinRM

The best way to improve the Discovery performance, avoid latency and Partial_OK is to enable WinRM discovery. That is done in both vScope and on the target machine(s) (if not enabled by default). The performance wins can be enormous since the number of rountrips of WMI requests are minimized. Eg.

Using regular WMI: 300 roundtrips * 100 ms (latency) = 30 seconds

WMI via WinRM: 1 roundtrip * 100 ms (latency) = 0,1 seconds.

Read more

• How to enable WinRM on Windows servers & clients

2. Increase the default timeout on WMI probe

If WinRM is not an option, you can also change the default timeout on the WMI probe.

1. Locate ..\vScopeData\configuration\config.ini 

2. Add a row specifying the new WMI timeout time in seconds. Default = 900 seconds = 15 minutes discovery.probe.wmi.timeout=1800