The terms ‘agent’ and ‘bot’ are used interchangeably, but there are diverse types of agents/bots on the market. The best way to define the Movere bot is to reference its lifespan, which is temporary, or non-persistent. A persistent agent must be installed, could require a system reboot, and, if no longer required, must be instructed to uninstall itself. A non-persistent bot attempts to complete its assigned task(s) and whether its successful or not, then self-terminates/dissolves. This is exactly what Movere bots do. Movere leverages the .NET framework to determine if there are enough system resources to run. If there aren’t, Movere sends a message to the user informing them that the system has insufficient resources, then it self-terminates/dissolves. If there are sufficient resources, Movere will only use what is granted by the .NET framework and will not de-prioritize any existing workloads.
This technique avoids requiring any changes to the environment being scanned, facilitates organization-wide deployment with ease, avoids the need to deploy central administration servers and collection points, avoids moving externally collected data back into the organization, and allows for updates to be delivered directly from the Movere portal.
Note: If the user does not want to deploy the Movere bots, then Movere can be run in remote WMI mode. With WMI, nothing is deployed to the endpoints being scanned. However, without the .NET framework, there is no resource management. Everything is moved across the network, generating a far greater level of traffic than deploying as a service or local executable.