Dell Lifecycle Controller Integration Version 3.3 for Microsoft System Center Configuration Manager User's Guide

Hardware configuration and OS deployment workflow

1. In Configuration Manager Version 1610, Configuration Manager 2012 SP2, Configuration Manager 2012 R2 SP1, Configuration Manager 2012 R2, Configuration Manager 2012 SP1, or Configuration Manager 2012, in Device Collections, right-click any appropriate Dell collection and select Dell Lifecycle Controller > Launch Config Utility.
2. From the Dell Lifecycle Controller Configuration Utility, select Hardware Configuration and Operating System Deployment.
3. Click Next.
4. Select Update Firmware from a Dell Repository if you want to update the Firmware on the collection. For more information, see Updating firmware during OS deployment.
5. Click Next.
6. In BIOS Configuration, select BIOS or UEFI and click Browse, to select the path where the BIOS or UEFI profile is saved. Click Next.
   Select Continue on Error to continue the deployment, even if there is an error.
7. Select Configure Hardware if you want to change the hardware settings. For more information, see Configuring hardware during OS deployment.
8. Click Next.
9. Select Configure FC HBA if you want to apply an FC HBA profile and FC SAN boot attributes to a collection.
   1. Select the FC adapter profile check box to apply an FC HBA profile to a collection. For more information, see Applying a FC HBA profile on a collection.
      and
   2. Select the SAN boot settings check box to apply FC SAN boot attributes to a collection. For more information, see Applying FC SAN boot attributes on a collection.
   Select Continue on Error to continue the deployment, even if there is an error.
10. Select Configure RAID to configure RAID on the servers. For more information, see Configuring RAID.
11. Click Next.
12. Select Configure network adapter if you want to apply a Network adapter profile to the collection. For more information, see Applying a NIC or CNA profile on a collection.
13. Click Next.
14. Select Configure iDRAC if you want to apply an iDRAC profile to the collection. For more information, see Applying an integrated Dell Remote Access Controller profile on a collection.
15. Select Export hardware configuration to create a backup of the system profiles and export it to an iDRAC vFlash Card or a Network share. For more information, see Exporting the system profiles before and after hardware configuration.
    NOTE Always ensure to select at least one hardware profile to enable the Export hardware configuration page.
16. Select Do not deploy operating system in the advertisement screen if you want to skip deploying the operating system on the collection.
    In this case, the Next button is disabled and you can directly click Reboot targeted collection. The hardware configuration tasks are submitted based on the selections you made in the previous steps and you can view the status of tasks on Task Viewer.

    NOTE If you select a server to boot from a SAN device, you should skip deploying the operating system on a collection from the Configuration Utility.
17. If you want to deploy the operating system:
    • To deploy Windows operating systems: Select Windows Operating System, then select the advertisement to advertise the task sequence to the collection, and the operating system for deployment on the collection.
    • To deploy non-Windows operating systems: Select Non-Windows Operating System, select the operating system, provide details, and then click Next.
    • Other option to the Boot, Credentials, and Browse button are disabled for Non-windows deployment in Select ISO Image.
18. Under Select Lifecycle Controller bootable media, select one of the following options:
    • Boot to Network ISO — Reboots specified ISO.
    • Stage ISO to vFlash and Reboot — Downloads the ISO to vFlash and reboots.
    • Reboot to vFlash (ISO Must be present on vFlash) — Reboots to vFlash. Ensure that the ISO is present in the vFlash.
      NOTE To use the Reboot to vFlash (ISO Must be present on vFlash) option, the label name of the partition created on vFlash must be ISOIMG.
    • Select the Use Network ISO as Fallback check box if you want the network ISO to be a fallback step.
    • Click Browse and select the path where the Dell Lifecycle Controller bootable media is saved.

    NOTE If you have set a default share location for the Lifecycle Controller boot media, the default location populates automatically. For more information, see Setting a default share location for the Lifecycle Controller boot media.
19. Type the user name and password for accessing the share where the Dell Lifecycle Controller bootable media is located.
20. Click Reboot Targeted Collection. This selection sends the jobs for each system in the collection to the Task Viewer. To view the current tasks in the queue and their status, open the Task Viewer by clicking the Dell icon on the task bar. For more information on Task Viewer, see Task Viewer.

    After a system with iDRAC receives the WS-MAN command, it reboots to Windows PE and runs the advertised task sequence. It then automatically boots to the Lifecycle Controller boot media, depending on the boot order you created in the task sequence.

    NOTE If you want to update a system after you deploy the operating system, and the system services are still unavailable, then you can reset the iDRAC using the iDRAC web-based interface. For more information, see the Dell Lifecycle Controller Remote Services User’s Guide available at Dell.com/support/home.

    NOTE If a yellow bang appears under device manager after you deploy Windows 2016 operating system, then download and install appropriate drivers from Dell.com/support/home.

    After the deployment is successful, the system with iDRAC moves to the Managed Dell Lifecycle Controller (OS Deployed) collection under All Dell Lifecycle Controller Servers.

    NOTE If you change the host name of the target systems after you deploy the operating system, the system continues to appear under the Managed Dell Lifecycle Controller (OS Deployed) collection on the Configuration Manager console. You do not need to re-discover the system when you change the host name.