Movere uses the .NET framework to scan each targeted endpoint locally. This provides two key benefits. The first is minimal network traffic. By scanning devices locally, communication between the Movere Console and each targeted endpoint is limited to delivery of the Movere scanning engine (< 4MB) and the return of the encrypted output file (typically < 8KB). The second is memory utilization. The Movere scanning engine only uses resources that are available and does not de-prioritize any existing running application.
For example, if a scan starts and the targeted endpoint is currently sitting at 80% CPU utilization, Movere will be limited to a maximum of ~10% of the systems total resources (Windows uses a complex algorithm to ensure that it keeps resources available for the operating system itself). If the device has more resources available, then Movere will take advantage of the additional resources, but the .NET framework will make this decision, not Movere. In addition to this we also need to consider total scan time per device. Movere is able to scans most devices within 30 seconds, which means with only 10% CPU Movere will still be able to complete its scanning in <1 minute, with >10% scan time is reduced even further. Ultimately, all this also depends on what Microsoft products are installed, i.e. a device with SQL Server installed will take longer to inventory than a device without SQL, etc.
If enough resources are not available to complete the scan then Movere will show the following error messages that are explained below:
- Insufficient memory to continue the execution of the program:Movere leverages the .NET framework, which controls the resources it receives and the priority in which they are given. When the target endpoint has insufficient resources, instead of placing the endpoint under further strain, Movere terminates itself.
- Insufficient system resources exist to complete the requested service:Similar to the insufficient memory error, this typically means that the targeted endpoint has insufficient processing power to perform the requested tasks. Once again, Movere will terminate itself to avoid placing further strain on the system.