Users Guide
Table Of Contents
- Dell Lifecycle Controller Integration Version 3.3 for Microsoft System Center Configuration Manager User's Guide
- Introduction to Dell Lifecycle Controller Integration (DLCI) for Microsoft System Center Configuration Manager
- Use case scenarios
- Common prerequisites
- Editing and exporting the BIOS configuration profile of a system
- Comparing and updating the firmware inventory
- Creating, editing, and saving a RAID profile of a system
- Deploying operating system on collection
- Exporting server profile to iDRAC vFlash card or network share
- Importing server profile from iDRAC vFlash card or network share
- Viewing and exporting Lifecycle Controller logs
- Working With NIC or CNA Profiles
- Working with Fibre Channel profiles
- Selecting Fibre Channel storage area network in boot sequence
- Using Dell Lifecycle Controller Integration
- Licensing for DLCI
- Dell Deployment ToolKit
- Dell Driver CAB files
- Configuring target systems
- Auto-discovery and handshake
- Applying Drivers from the task sequence
- Creating a task sequence
- Creating a Dell specific task sequence
- Creating a custom task sequence
- Editing a task sequence
- Configuring the task sequence steps to apply operating system image and driver package
- Applying the operating system image
- Adding Dell driver packages
- Deploying a task sequence
- Creating a task sequence media bootable ISO
- System Viewer utility
- Configuration utility
- Launching the integrated Dell Remote Access Controller console
- Task Viewer
- Additional tasks you can perform with Dell Lifecycle Controller Integration
- Configuring security
- Validating a Dell factory-issued Client Certificate on the Integrated Dell Remote Access Controller for auto-discovery
- Pre-authorizing systems for auto-discovery
- Changing the administrative credentials used by Dell Lifecycle Controller Integration for Configuration Manager
- Using the Graphical User Interface
- Using the Array Builder
- Using the Configuration Utility
- Creating a Lifecycle Controller boot media
- Configuring hardware and deploying the operating system
- Deploying operating systems
- Hardware configuration and OS deployment workflow
- Updating firmware during OS deployment
- Configuring hardware during OS deployment
- Configuring RAID
- Applying a NIC or CNA profile on a collection
- Applying FC HBA profiles and FC SAN boot attributes on a collection
- Applying an integrated Dell Remote Access Controller profile on a collection
- Exporting the system profiles before and after hardware configuration
- Comparing and updating firmware inventory for systems in a collection
- Viewing the hardware inventory
- Verifying Communication with Lifecycle Controller
- Viewing and exporting Lifecycle Controller logs for a collection
- Modifying credentials on Lifecycle Controllers
- Platform restore for a collection
- Comparing NIC or CNA profiles against systems in a collection
- Using the Import Server Utility
- Using the System Viewer Utility
- Viewing and editing BIOS configuration
- Viewing and configuring RAID
- Configuring iDRAC profiles for a system
- Configuring NICs and CNAs for a system
- Configuring FC HBA cards for a system
- Comparing and updating firmware inventory
- Comparing hardware configuration profile
- Viewing Lifecycle Controller logs
- Viewing the hardware inventory for the system
- Platform restore for a system
- Comparing FC HBA profile against a target system
- Troubleshooting
- Configuring Dell provisioning web services on IIS
- Dell auto-discovery network setup specification
- Troubleshooting the viewing and exporting of Lifecycle Controller logs
- Deploying the operating system on Dell’s 13th generation of PowerEdge servers using WinPE 3.0
- Issues and resolutions
- ESXi or RHEL deployment on Windows systems moves to ESXi or RHEL collection, but not removed from Windows Managed Collection
- Related documentation and resources

Deleting a variable condition
About this task
To delete a variable condition:
Steps
1. Select the variable condition and click Variables → Delete Variable Condition.
A message that all the attached arrays and disks will be deleted is displayed.
2. Click Yes to delete or No to cancel.
Arrays
Array nodes include both RAID arrays and non-RAID disk groups that are indicated by the different icons for RAID arrays and non-
RAID disks. By default, a non-RAID disk group is created when a controller is created. If the controller configuration specifies the
number of disks required, the same number of disks is added to the non-RAID group.
Arrays can be added, modified or deleted depending on the controller configuration and number of disks available.
Array elements contain logical drives and physical disks.
Adding a new array
About this task
To add a new array:
Steps
1. Under a variable condition, select a variable condition and click Arrays → New Array.
The Array Settings window is displayed.
2. Set the required RAID level from the Desired RAID Level drop-down menu.
3. On RAID levels 50 and 60, enter the span length of the array.
4. Click OK to apply the array, or Cancel to return to Array Builder.
Editing an array
About this task
To edit an array:
Steps
1. Select the array and click Arrays → Edit Array.
The Array Settings window is displayed. You can select a different RAID level for the array.
2. Click OK to apply the changes, or Cancel to return to Array Builder.
Deleting an array
About this task
To delete an array:
Steps
1. Select the array and click Arrays → Delete Array.
A message is displayed that all the attached disks will be deleted.
2. Click Yes to delete or No to cancel.
Logical drives also known as virtual disks
Logical drives can be present on RAID arrays and non-RAID groups. You can configure them by specifying the size (in GB) or
consume all available (or remaining) space in the array. By default, a single logical drive is created for all new arrays and is set to use
all the available space.
When specific-size logical drives are defined, the using all remaining space logical drive will consume any remaining space after
other logical drive(s) have allocated their space on the array.
32