Movere supports all three scanning mechanism:
On the device running the Movere Console, the Movere service can be installed and started as a persistent service. With this approach, the Movere Service can survive a system reboot if one should occur during a scan. The Movere service can also be configured to start on a predefined schedule.
On the targeted endpoint, Movere installs as a temporary service by default. If Movere cannot install itself as a service, Movere then attempts to scan the device as a local executable. Alternatively, if the user does not want Movere to install itself as a temporary service, then the local scanning option can be selected via the Movere Console. In this configuration, Movere will not attempt to install itself as a temporary service, and will only run as a local executable. The same data is collected irrespective of which technique is used to scan a Windows device. This option gives Movere customers greater control over the scanning process and prevents having to change existing configurations if temporary services or local scanning is prohibited by existing security products.
Movere has remote scanning capabilies via WMI. This scanning method is maintained to support the scanning of legacy Windows platforms (e.g. Windows 2000/2003/XP) and to support customers with systems that a Movere bot cannot be delivered to locally, primarily for contractual reasons. Using the remote scanning technique, nothing is deployed to the endpoint being scanned.