The Dell Client Configuration Utility is an ad-hoc configuration tool to modify Dell BIOS settings on workstation class systems(Precision, OptiPlex & Latitude). It does not require the permanent installation of a management agent on the target systems. The tool consists of a simple web-based interface that allows you to select and configure a multitude of settings. It will compile an executable that you can then deploy to the systems that need the modifications.

About the Dell Client Configuration Utility
Download DCCU 3.1.1055 (current as of 3/4/2011)

The installation of the DCCU requires the Microsoft .NET Framework.

Determining available values

In order to populate the dropdown values in DCCU it is necessary to perform an initial "get values" operation that will create an XML file that we can then import back into the tool.

1. Start DCCU
2. Navigate to the Get Values tab
3. Choose the Select All checkbox
4. Choose Create Package, make note of the location where the tool saves the executable, name the file anyting that you want e.g. GETVALUES.EXE.
5. Go to the folder where the executable was saved and run it.
6. In the DCCU interface choose Open Output File
7. Browse to the folder that your executable was saved to and choose DCCUResults.xml

The values in the tool should now be populated with your current configuration.

Modifying a Value

You can now modify any of the available values. Go to the Set Values tab and find the value you wish to modify. The below example shows setting the Wake-on-LAN configuration to 6 (enabled for All nics).



After you have selected the settings that you want applied you simply choose the Create Package button to create the compiled exe. Make sure you save it as a name that is easily attributed to the settings it is changing.

Deploying the Settings

You can now copy this simple executable to your deployment tool and send the configuration to your clients. There are a few items to be aware of when deploying:

• The executable will delete itself from the location where it was run. It will only leave behind the XML files that contain the status of the change. If you need to run the settings multiple times for some reason then you might copy the exe to temp directory and execute it there.
• This tool will issue a zero exit code if it was successful but it does not provide definitive inventory on the state of the BIOS setting.
• While a reboot will not occur, some settings may not be viable until after a reboot. You will need to test that scenario for your custom settings. In most cases you can avoid an immeadiate reboot and wait for the next user initiated reboot.

Dennis Abbott