The General panel lets you provide information that identifies a Virtual Infrastructure Discovery Job and options for discovering, registering, and importing properties for virtual machines.
Choose from the following options:
Auto-Register Discovered ESX hosts/Virtual Systems — Selecting this option automatically registers any discovered virtual machines that are not currently being managed by BMC Server Automation. This option connects to the targets selected in the job (the vCenter servers, global zones, IBM frame server) and retrieves all the virtual systems, non-Global Zones, or LPARs. It then compares the discovered systems to the list of BMC Server Automation enrolled servers and registers the systems in BMC Server Automation if they are not already registered. Selecting this option also sets the IS_VIRTUAL
job property to True for all virtual machines and zones which are registered by the Virtual Infrastructure Discovery Job.
The Virtual Infrastructure Discovery Job registers discovered servers with the server name, even if the server is registered with the IP address under the Server workspace.
Discover Unregistered Virtual Systems (VMware platforms only) — Select this option to discover any virtual machines that are not registered in the vCenter or BMC Server Automation. Selecting this option enables the Auto Remediate Unregistered Virtual Systems option, which moves the unregistered virtual machines to a vCenter server that you specify.
Ensure that the name of the vCenter (enrolled in BMC Server Automation) matches the name of the CONNECTION_URL
property specified when the vCenter server was added to BMC Server Automation.
The Import Lifecycle Properties option imports the server lifecycle properties for a virtual system from a pre-defined mapping file. The selected XML file contains a list of mappings for the targets and VMware vCenter servers against which the Virtual Infrastructure Discovery Job is run.
Selecting this option imports only the three supported lifecycle properties (OWNER
, EXPIRY_DATE
, LOCATION
) for all registered virtual machines (lifecycle properties are not imported for ESX Hosts).
The life cycle properties can be imported in one of the following scenarios: