Deploying a Scout

Asset Manager Scouts are deployed by users in the same manner as Command Centers. The license keys, which Asset Manager creates using a component's UUID, determine whether the virtual machine OVA template will unpack to a Scout or to a Command Center.  

The OVA intended for use in deploying Scouts allocates fewer system resources because Scouts are small. The one intended for use in deploying Command Centers is relatively large.  It is configured to allocate an appropriate level of resources to discover and index your organization's network.

You may install an unlimited number of virtual Scouts by reusing the OVA template and you may connect however many Scouts you need to your Command Center. You will need to input a unique license key from Asset Manager, however, for each Scout you install. This is because the UUID changes every time the OVA is applied to a different virtual machine.

Each Command Center deploys with its own onboard Scout that cannot be disabled or deleted. This onboard Scout is referred to as "local" or "onboard" on the Asset Manager GUI and in this documentation.

Once deployed, Scouts are smaller, have a minimal GUI, and require fewer system resources.  When you browse to a Scout's IP address, you'll see three tabs of device identifiers about it.  For more on these identifiers, plus the procedure to add, remove, and upgrade Scouts, see Managing Asset Manager Systems.