Users Guide

This feature is disabled by default. To enable this authorization check, run the following command:

C:\Program Files (x86)\Dell\DPS\ProvisionWS\bin\import.exe –CheckAuthorization false.

Changing The Administrative Credentials Used By Dell Lifecycle Controller Integration For

Configuration Manager

Use the following commands to change the administrative credentials for Configuration Manager used by Dell Lifecycle

Controller Integration:

To set the user name:

C:\Program Files (x86)\Dell\DPS\ProvisionWS\bin\import.exe –CIuserID [New

Console Integration Admin User ID]

To set the password:

C:\Program Files (x86)\Dell\DPS\ProvisionWS\bin\import.exe -CIpassword [New

Console Integration Admin Password]

Using the Graphical User Interface

You can also use the Graphical User Interface (GUI) to change the security configurations.

Use the following command to open the GUI screen:

C:\Program Files (x86)\Dell\DPS\ProvisionWS\bin\import.exe -DisplayUI

Using Import.exe To Update Target System Information

If you have discovered systems with Dell Lifecycle Controller Integration for Configuration Manager version 1.0 or 1.1

and updated the firmware after upgrading to version 1.2 or later, then you must re-discover the systems if you have

changed their hostname during operating system deployment.

To avoid re-discovering the systems and avail the hostname change functionality:

1. Launch the command prompt on the target system.

2. Navigate to C:\Program Files (x86)\Dell\DPS\ProvisionWS\bin folder.

3. Type the command: import.exe -Servers .

The Configuration Manager database is updated with the latest firmware information from the target systems. You can

verify if the information of all the systems is correctly updated by viewing the import.log file in the Program Files\Dell

\DPS\Logs folder.

Using the Array Builder

The Array Builder allows you to define arrays and disk sets with all available RAID settings, logical drives or virtual disks

of varying sizes or use all available space, and assign hot spares to individual arrays or assign global hot spares to the

controller.

When a controller is created, a default variable condition, array and disk(s) are created to ensure a valid configuration.

You can choose to leave the controller un-configured with disks set to non-RAID, or you can add arrays or perform other

actions.