Users Guide

For few attributes displayed under Attribute Name of Apply System Profile-Failure Details window is not same as
Attribute Name of the system profile when you click More Details.
To export the details to a .CSV file, in the right corner of the data grid, click .
4. To abort the deployment job, click the icon.
5. When the message is displayed, click Abort Job to abort, or to cancel, click Do Not Abort Job.
6. To display the Purge Deployment Job Queue window, click . Select the Older than date and job Status, and click
Apply.
The selected jobs are then cleared from the queue.
Deployment job timing
The provisioning and deploying of bare-metal servers can take between 30 minutes to several hours to complete, depending
on several factors. When starting a deployment job, it is recommended that you plan your deployment time according to
the guidelines provided. The amount of time it takes to complete provisioning and deployment varies with deployment type,
complexity, and number of deployment jobs running simultaneously. The following table provides the approximate time a
deployment job can take: The deployment jobs are run in batches of up to five concurrent servers to improve time for the
overall deployment job. The exact number of concurrent jobs depends on available resources.
Table 37. Approximate deployment time
Deployment type Approximate time per deployment
Hypervisor only Between 30 to 130 minutes
Hypervisor and hardware profiles 1–4 hours
System profile only 5–6 minutes
System profile and hypervisor profile 30–40 minutes
Server states within deployment sequence
When an inventory job is run, the auto/maually discovered bare-metal systems are classified in different states to help
determine if the server is new to the data center or has a pending deployment job scheduled. The administrators can use
these states to determine if a server should be included in a deployment job. The following are the states:
Table 38. Server states in the deployment sequence
Server state Description
Unconfigured The server has contacted OMIVV and is waiting to be
configured.
Configured The server is configured with all hardware information that is
required for a successful hypervisor deployment.
Downloading custom Dell EMC ISO images
The custom ESXi images that contain all Dell drivers are required for deployment.
1. Navigate to support.dell.com.
2. Click Choose from all products > Servers, Storage, & Networking..
3. Under Select a product, click PowerEdge.
4. Click a PowerEdge server model.
5. Click Drivers & Downloads page of the server model.
6. Click the Change OS link, and select an ESXi system you want.
7. Click Enterprise Solutions.
108
Deploying hypervisor