Scanning via Remote WMI

When Movere scans a device using the Remote WMI option, which credential(s) are used?

At least one set of credentials must be entered into the Movere Console before any scanning can be performed.  Movere will only leverage the credentials entered into the console for both .NET and WMI based scans, in the order they are entered.  The credentials used to log into the device the Movere Console is run from will not be used to access targeted endpoints unless they are also entered into the Movere Console.  Once Movere accesses the targeted endpoint, scanning will be performed using the credentials that permitted access.  If the targeted endpoint also has SQL installed then Movere will attempt to access SQL using the same credentials that permitted access to the device.  If those credentials do not permit access to SQL, then Movere will attempt to access SQL using any other credentials added to the Movere Console, again in the order they are entered. 

We have decided to complete all scans using the ‘Remote (WMI) only’ option, but the scanning is progressing at a slower pace, is this normal?

The Remote (WMI) option completes all scans across the network.  As a result, scan time is dependent on network speed, the age and speed of the device being scanned, and the resources available on the device the Movere Console is being run from.  While a .NET scan typically completes in less than 30 seconds, WMI scans can take 3-5 minutes to complete.  We have on occasion scanned very old devices with very limited resources.  To avoid scanning devices like these indefinitely, there is a 30 minutes timeout set in the configuration file which can be configured as needed.