BMC Discovery Outpost system requirements

For detailed discovery of your datacenter or services in your public cloud, BMC Discovery uses an Outpost, that is installed on any suitable Windows computer in the target environment. The BMC Discovery Outpost can be a physical or virtual server, and it can use an existing infrastructure server. Multiple Outposts can be deployed to handle segmented networks, and these can all communicate with a single BMC Discovery appliance. Similarly, the Outpost can be registered with multiple appliances and receive work from those appliances. Outposts must be registered with one or more BMC Discovery appliances, they cannot be registered with other Outposts.

The following are the minimum recommended specifications for the Discovery Outpost host:

To avoid any impact during resource-intensive periods of discovery, we recommend not to install the BMC Discovery Outpost on any host supporting other business services. This is true even if the minimum specification is exceeded, since the Outpost attempts to use whatever resources are available, to optimize scan throughput.

If you are scanning from a large cluster or you have multiple BMC Discovery instances connected to an Outpost, performance may be affected due to multiple concurrent requests on the Outpost. In this case, installing more than one Outpost may help.

For frequently asked questions about the BMC Discovery Outpost, see FAQs.