This list displays the available HP configuration. It represents the types of major activities used by to configure ProLiant servers, such as configuring the BIOS, array controller, iLO and boot order. Details of the HP Configuration Actions are described in HP Custom Configuration Actions.

This list displays the available options for the selection configuration action type, which is either Get or Set, or both. With each configuration type, you can apply a configuration to the targeted machine ("Set") or you can capture a configuration from a reference machine ("Get") using a single task step. Some configuration types enable only one option, and in that instance, only one is available to select. Once you select an available action, additional controls become visible and/or enabled.

Based on the Configuration Action Type you are performing, the command needed by the utility is either the name of a file or a command line parameter. This control enables you to enter the appropriate parameters or configuration file for the task. The information that appears and options available follow these general rules:

This checkbox enables or disables the Additional Command Line control. It is checked manually by you or can be checked (and optionally not-modifiable) programmatically based on the requirements of the selected configuration type. Some configuration types might not require additional command line parameters. In this instance, the checkbox does not appear.

This checkbox controls the use of the timeout value control. If checked, the timeout value control is enabled and you can specify an integer value (limit to between 5 and 100) for the timeout value. The task is marked as failed if the status is not returned within the timeout value.

When you need a variable that is not initialized or has a blank value to remain blank, you must select this option. This causes the processing of the task on the clients side to continue if any variable is undefined or blank.

In some instances, if variables are intended to be replaced but are not found within the environment, the action is left in an unusable or misconfigured state. If an environment variable is not set or is set to null, an invalid value is returned. When this checkbox is selected, any failure to retrieve a valid variable value results in the action being marked as failed. This feature enables you to see what is wrong with the action rather than trying to debug a failed command line or a misconfigured system.

This setting enables the client-side script to search for and replace variables in the command line or within the files specified. The variables are replaced with values found in the task sequence environment or the Windows® system environment. If you do not have any variables in the command line or in files specified, leaving this checkbox unchecked provides for greater performance of the action since it does not have to search for the variables in every file.

In some instances, configuring a hardware component requires the use of a password. Rather than embedding the password in plain text within the XML or visible on the command line, you can utilize this option to store the password hidden from you and used within the action on the client as a task sequence variable. Checking this box enables the two password textboxes. Two textboxes are used to ensure you confirm the password entered since the password text does not appear.

You might have to set additional variables on the system prior to a task running. This might be because the utility or script being run needs to have specific variables defined to direct it to a specific path, other utilities, or to define options for program execution. This data grid enables you to define an unlimited number of additional variables for this task, which is set prior to the start of the command that runs the associated utility.

Each variable must have a name, but the value can remain empty if you need to create a null variable. Each variable can be set as a system, task sequence, or machine variable. To remove a variable, click the X button on the appropriate row. A variable's value can contain another variable. This is useful in the instance that an existing variable holds the value you need, but the program needs to access that information from a different variable name.

When a task sequence runs, Configuration Manager tracks and logs command execution through the SMSTS.LOG file stored in the local path on the client (for example, on the X: drive in WinPE). This log file contains valuable debugging information, yet when using WinPE, the log is lost at each reboot. This checkbox enables the SMSTS.LOG file to be sent back to a designated location specified previously in a "Connect to Network Drive" action.

After the command executes, the client gathers the SMSTS.LOG file and pushes it back to the mapped network location specified in the Drive Letter list and the Path textbox. If the path does not exist, it is created before the log file is placed there. If a filename is specified in the path, the SMSTS.LOG file is saved as that file. If the file already exists, the file name is modified with an incremental value and then saved.

Enable extended/debug logging

By default, a limited amount of information regarding the task execution by the script appears in the SMSTS.LOG file. By enabling debug-level logging, a much greater amount of information is included in the log file, which might assist with troubleshooting a failure in the task sequence. This setting only affects the logging by the custom action script and not the logging by the task sequence client itself.

For information about logging debug information about the Admin UI components of the custom action, see the Debugging UI Issues section in the troubleshooting assistant.

Retain network folder settings checkbox

If you have an extensive task sequence with many of these custom actions, rather than require you to enter the same network path and login information in each task step, this checkbox enables you to copy the settings from a previous step that sets these network settings.

	NOTE: Since network settings are not retained across a reboot, checking the box only copies the settings from a prior task if there are no reboots between them. If there is a reboot after the previous task with network settings and before this task, an error message displays and you are required to re-enter the network settings.

The log path enables the log file to be stored in a location other than the root directory of the mapped drive. If a path is specified, the log is stored there. If the directory does not exist, it is created if possible. If a filename is specified at the end of the path, the log file is saved as that file name. If the file name already exists, then an incremental value is added to the name so the file can be saved without overwriting an existing file.

The domain and account name to be used to access the above path.

The password associated with the account name. The password is stored and transmitted in encrypted form.

The map a drive checkbox enables the list for mapping a drive. A mapped drive is not necessary to store files on a network share (a UNC path can be used), but HP recommends mapping a drive. A mapped drive is required for accessing any batch files (.CMD or .BAT).

The mapped drive list contains drive letters that are used to store the log file or the captured settings file from the Get action. This drive needs to already have been mapped using a Connect to Network Folder action prior to this task step.

The Import File Button menu item enables you to search for and import an existing text-based file. The contents appear in the form.

By selecting the Save to Package checkbox, the configuration is exported to a file when you click OK on the page. The starting directory is the package directory where the other toolkit configuration files exist. The package must be updated to distribution points before any changes are available to task sequences.

Save to a Variable

If you do not choose to save the configuration to the package, the configuration is saved as a string within the task sequence and sent as a variable to the target server during deployment. When this occurs, it is noted in the custom action with the configuration parameter text "[Configuration saved as a variable]". The configuration can be saved as a file in the package instead by re-opening the editor, checking the box on the left and clicking OK, and then selecting the file to save.

If you attempt to apply a very specific set of configuration rules to target servers, the configuration might fail when one of the rules does not match a controller in the system. To apply a large blanket set of rules to all servers, the configuration might fail only when none of the rules match any controller. This setting enables you to control these actions.

There are three available error handling rules:

The following is the definition of the rules associated with the different elements in the dialog. The rules define what actions can or cannot be performed on the various elements, which in turn drives the activation or deactivation of the various controls (menu buttons) on the dialog or results in warnings. For example, if moving an array upward in the list causes an invalid configuration, the "Move Up" control is disabled or a warning dialog appears.