Understanding the home screen

The following lets you navigate and use DDU:

Understanding the workflows

Adding printers

1. From DDU, click Add New .

2. Type the deployment name and description.

3. Click Edit Device List .

4. Do either of the following:

   Note:  To skip adding printers, click Cancel . If this task is skipped, you are prompted to add them before creating a workflow. For more information on adding devices after creating a workflow, see Adding printers after creating a deployment workflow .

   Add devices manually

   1. Select Add a device .

   2. In the "Add a device" field, type the IP addresses or host names of the devices, and then click .

      Use the following formats to add IP addresses:

      • 10.195.*.* (wildcards for only the last two octets)

      • 10.195. y . yy (single IP address)

      • 10.195.1.3-10.195.1.255 (IP address range)

      • printerHostname.company.com (host name)

      • 2001:db8:0:0:0:0:2:1 (single full IPv6 address; wildcards are not supported)

      Note:  To remove an IP address or host name, select the IP address or host name in the "Discovered devices" list, and then click .

   Add devices using the CSV file

   1. Select CSV File .

   2. Browse to the CSV input file.

      Note:  The default file name is DduInput.csv . For information on creating a CSV file, see Creating CSV files .

5. If necessary, select Secured Device to prompt the user to type the authentication credentials used to access secured devices when deploying the workflow.

6. Click OK .

After a printer is added, DDU checks if the printer is online. If it is not, then a Discovery Failed error message appears.

Adding packages

1. From DDU, do either of the following:

   • Click Add New > Add Package .

   • Click Add Package .

2. Select Package Builders Package or Custom Package .

   Note:  When creating a custom package, printer information such as the serial number is not required.

   If Package Builder Package is selected, then do the following:

   1. Create a PkgBldrInput.csv file. For more information, see Creating CSV files .

   2. Access the Package Builder application.

   3. From the application, upload the PkgBldrInput.csv file.

   Note:  For more information, see the Package Builder User's Guide .

3. Specify the location of the package file.

4. Click OK .

Adding settings files (.ucf)

1. From DDU, do either of the following:

   • Click Add New > Add Settings Files(.ucf) .

   • Click Add Settings Files(.ucf) .

2. Select either of the following:

   • Settings file

   • Settings file (Scan to Network) —Add a settings file for Scan to Network.

3. Select either of the following:

   • Standard UCF File —Deploy a settings file with the same settings to printers.

   • Variable UCF File —Deploy a settings file with different settings to printers.

4. Do either of the following:

   • If Standard UCF File is selected, then in the Settings File field, specify the location of the updated settings file.

   • If Variable UCF File is selected, then do the following:

     1. If you have already created the variable settings file based on the template manually, then in the Settings File field, specify its location. If you do not have a variable settings file, then click Create Template File to create the file using DDU.

     2. If you have already created the lookup .csv file with different values for the variable setting names based on the template, then in the Lookup File field, specify its location. If you do not have a lookup .csv file, then click Create Lookup CSV File to create the file using DDU.

     Notes:

     • For more information on creating a variable configuration file and lookup .csv file using DDU, see Creating a variable configuration .ucf or .xml file and a lookup .csv file using DDU .
     • For more information on creating a variable configuration file and lookup .csv file manually, see Creating a variable configuration .ucf or .xml file and a lookup .csv file manually .

5. Click OK .

Adding certificates

Printer certificates are unique identifiers that are used to authenticate the following:

• HTTPS

• SSL

• TLS

• IPSec

• 802.11 connections

1. From DDU, do either of the following:

   • Click Add New > Add Certificates .

   • Click Add Certificates .

2. Do either of the following:

   Add a CA certificate

   1. Click Add CA Certificate .

   2. Specify the location of the certificate.

   Add a signed device certificate

   1. Click Add Signed Device Certificate .

   2. Specify the directory of the signed certificate.

   Add a PKCS certificate

   1. Click Add PKCS Certificate .

   2. Specify the location of the certificate.

   3. Type a friendly name for the certificate.

   4. Type the password for the PKCS file.

      Notes:

      • Check the Do hostname validation checkbox to validate hostname with common name of the certificate. By default, it is checked.
      • PKCS file deployment from DDU is only supported in devices with latest version of firmware.

3. Click OK .

Adding configuration files (.zip)

1. From DDU, do either of the following:

   • Click Add New > Add Configuration Files(.zip) .

   • Click Add Configuration Files(.zip) .

2. Select either of the following:

   • Standard Configuration File —Deploy a configuration file with the same settings to printers.

   • Variable Configuration File —Deploy a configuration file with different settings to printers.

3. Do either of the following:

   • If Standard Configuration File is selected, then in the Configuration File field, specify the location of the updated configuration file.

   • If Variable Configuration File is selected, then do the following:

     1. If you have already created the variable settings file based on the template manually, then in the Settings File field, specify its location. If you do not have a variable settings file, then click Create Template File to create the file using DDU.

     2. If you have already created the lookup .csv file with different values for the variable setting names based on the template, then in the Lookup File field, specify its location. If you do not have a lookup .csv file, then click Create Lookup CSV File to create the file using DDU.

     Notes:

     • For more information on creating a variable configuration file and lookup .csv file using DDU, see Creating a variable configuration .ucf or .xml file and a lookup .csv file using DDU .
     • For more information on creating a variable configuration file and lookup .csv file manually, see Creating a variable configuration .ucf or .xml file and a lookup .csv file manually .

4. Click OK .

Adding npa files (.npa)

1. From DDU, do either of the following:

   • Click Add New > Add NPA Files(.npa) .

   • Click Add NPA Files(.npa) .

2. Do either of the following:

   1. Click Select NPA File (*.npa) .

   2. Specify the location of the file.

3. Select the NPA Port.

   Note:  The default port number is 9500.

4. Click OK .

Adding licenses

This feature lets you add licenses for eSF applications.

1. From DDU, do either of the following:

   • Click Add New > Add License .

   • Click Add License .

2. Select the license type.

   Notes:

   • If eSF 1.x,2.x and 3.x licenses is selected, then select the application where you want to deploy the license. Select this option when using printers running on eSF version 3 or earlier.
   • Printers running on eSF version 4 or later support only licenses with the .zip format.
   • Printers running on eSF version 3 or earlier support only licenses with the .lic format.
   • For information on checking the eSF version of your printer, see the help information documentation .

3. Specify the location of the license file.

4. Click OK .

Adding a firmware or flash file

Use this feature when deploying firmware files, application flash files, or engine codes and scanner codes.

1. From DDU, do either of the following:

   • Click Add New > Add Firmware or Flash Files(*.fls) .

   • Click Add Firmware or Flash Files(*.fls) .

2. Specify the location of the flash file.

3. Select one of the following:

   • Firmware File —Deploy a firmware flash file.

     Notes:

     • If Save File Path Only is selected, then make sure that the file is located and accessible in the specified file path during the deployment. This setting does not include the firmware file in the workflow. Clearing this setting compresses the file and saves it in the workflow.
     • If the firmware version in the file is later than the firmware version on the printer, then the firmware on the printer is upgraded. Otherwise, it is downgraded. If the firmware version in the file is the same as the version on the printer, then the firmware is not deployed. To deploy the firmware without checking the firmware version of the printer, select Force Deployment .
     • You can add only one firmware file in a workflow.
     • The firmware file is the first in the installation sequence by default. For example, if you add a firmware file in the fifth sequence, then it moves to the first sequence automatically. However, the sequence of the firmware task can be altered.

   • Application file —Deploy application .fls files.

   • Others —Deploy engine codes, scanner codes, or other flash files. The Others option does not validate the flash file.

     Warning—Potential Damage:  Deploying inappropriate flash files may damage the printer.

4. Click OK .

Adding tasks

This feature lets you add multiple tasks to a workflow.

1. From DDU, do either of the following:

   • Click Add New > Add Task .

   • Click Add Task .

2. Do any of the following:

   Add a task to start, stop, or uninstall an application

   1. Select a task.

   2. In the Application Id/Name menu, select an application.

      If the application is not on the list, then do either of the following:

      Update the app-id-version.txt file
      Note:  You can find the configuration file at DDUAppFolder \config , where DDUAppFolder is the location of the DDU folder.

      1. Using a text editor, open the app-id-version.txt file.

      2. Type AppID = AppName : ver1,ver2,ver3 , where AppName is the friendly name, AppID is the application ID, and ver1,ver2,ver3 are application versions separated by a comma.

      3. Save the file.

      Notes:

      • To show only the application ID in the menu, type AppID =: ver1,ver2,ver3 . Adding AppID using this method applies it on the entire session.
      • You can find the file in DDUAppFolder \Config\ , where DDUAppFolder is the location of the DDU folder.
      Type the application ID

      In the Application Id/Name menu, type the application ID.

      Note:  This option does not update the app-id-version.txt file. The added application ID is only available for the created workflow. Adding AppID using this method does not apply it on the entire session.

   3. If necessary, in the Version menu, select or type the version of the application that you selected.

      Note:  If Any is selected, then DDU starts, stops, or uninstalls any version of the application that is installed on the printer.

   4. Click OK .

   Note:  For more information on obtaining the application ID and version number, contact your solution provider.

   Add a task to restart the printers

   Select Reboot printer .

   Add a task to remove held print jobs

   Select Remove Held Jobs .

   Note:  The Remove Held Jobs option is applicable to printers running on eSF version 4 or earlier.

   Add a task to increase the interval between tasks

   1. Select Add Delay .

   2. Specify the interval in milliseconds.

   Add a task to update a device certificate

   Select Update Device Certificate .

   Add a task to delete device certificate

   Select Delete Device Certificate .

3. Click OK .

4. Type the deployment name and description.

5. Click Save .

Notes:

• The firmware file is the first in the installation sequence by default. For example, if you add a firmware file in the fifth sequence, then it moves to the first sequence automatically.
• To move tasks, click the up and down arrows.
• To stop a task, in the Stop Workflow On Failure column, select the task that stops the workflow when a failure occurs.
• You can edit and delete tasks.
• To add a printer, click Edit Device List . For more information, see Adding printers .
• To configure the deployment and discover settings, click . For more information on configuring DDU, see Configuring the utility .

Creating a variable configuration .ucf or .xml file and a lookup .csv file using DDU

Creating a variable configuration .ucf or .xml file

A variable configuration file contains the variable setting names based on the template of the original settings file or configuration file.

1. From DDU, add a settings file or a configuration file.

   Note:  For more information on adding a settings file, see Adding settings files (.ucf) . For more information on adding a configuration file, see Adding configuration files (.zip) .

2. Select Variable UCF File or Variable Configuration File .

3. Click Create Template File .

4. In the Base UCF Path or Base VCC Path field, specify the location of the settings file or configuration file of the standard configuration file.

5. Click .

6. On the left panel, select a file, and then click >> . The properties and values of all settings available in the file are shown in the right panel.

7. In the right panel, select the settings. Selecting a setting updates its current value to a variable, ${Var_ PropertyName } , where PropertyName is the name of the setting. For example, if you selected WS_SCAN_ENABLED , then the automatically generated variable is ${Var_WS_SCAN_ENABLED} .

   Notes:

   • To change the automatically generated variable name, double-click it.
   • When changing the automatically generated variable, make sure that the variable name format is ${ VariableName } , where VariableName is a unique property name. Variable names are used when creating the lookup .csv file.
   • To sort the settings alphabetically, double-click the Property column.

8. If necessary, repeat steps 6 and 7 to select multiple files.

9. Select either of the following:

   • Save All Settings —Create a variable configuration file that contains all the settings.

   • Save Changes Only —Create a variable configuration file that contains only the settings that you have updated. For example, if you have updated only two settings, then only those settings are included in the configuration file. Other settings are not copied.

   Note:  For the variable configuration file of Scan to Network, all settings are saved by default.

10. If necessary, specify the location where you want to save the new variable configuration file in Out Directory.

    Notes:

    • By default, the new file name contains the suffix _Var and is saved in the location of the original settings file or configuration file.
    • The file name of the new variable configuration file cannot be changed.

11. Click Save .

Creating a lookup .csv file

A .csv file contains different values for the variable setting names based on the template.

Notes:

• You can create or specify a lookup .csv file only after creating or specifying a variable configuration file.
• We recommend creating the .csv file using a spreadsheet that supports CSV file format.

1. From DDU, add a settings file or a configuration file.

   Note:  For more information on adding a settings file, see Adding settings files (.ucf) . For more information on adding a configuration file, see Adding configuration files (.zip) .

2. Select Variable UCF File or Variable Configuration File .

3. In the Settings File or Configuration File field, specify the location of the variable configuration file or create a template.

4. Click Create Lookup CSV File .

5. Depending on the identifier used when adding a printer, select either IP Address Header or Host Name Header .

   Notes:

   • For more information, see Adding printers .
   • Use the same identifier when adding a printer. For example, if you used the printer IP address when adding a printer, then use the same when creating the lookup .csv file.
   • The first row contains the identifier and the specified variable name in the configuration file.
   • The variable name in the first row appears only when the variable configuration file is created using DDU.

6. In the list, double-click on the fields to specify the values of the variable name for each printer.

7. If necessary, specify the location where you want to save the lookup .csv file in Out Directory.

   Notes:

   • By default, the file name contains the prefix CSV_ and is saved in the location of the original settings file or configuration file.
   • The file name of the new variable configuration file cannot be changed.

8. Click Save .

Understanding the files

Sample standard settings file

nvOemMfgLongName "Lexmark International"
HTTPSENABLE TRUE
LPDTIMEOUT 90
printTimeout "90"

Sample variable .ucf file

nvOemMfgLongName $(variable_1)
HTTPSENABLE $(variable_2)
LPDTIMEOUT $(variable_3)
printTimeout $(variable_4)

The lookup file contains the values of the variable names in the configuration file. These values are deployed to printers that are specified in the lookup file.

Understanding the lookup .csv file

The file contains the values for each variable defined in the variable configuration file. These values are deployed to the printers defined in the lookup file.

The following lookup file deploys the configuration file to three printers and retains the current value of printTimeout for the third printer:

Sample lookup file

IP_ADDRESS,variable_1,variable_2,variable_3,variable_4
192.168.1.1,"abc International",TRUE,60,"80"
192.168.1.2,"xyz International",FALSE,70,"60"
192.168.1.5,"mno International",FALSE,50,CUR_VAL

The first row contains the headers of the lookup file and the variable names defined in the variable configuration file. Use the same identifier when adding a printer. For example, if you used the printer IP address when adding a printer, then use the same when creating a lookup .csv file.

The succeeding rows are the printers where you want to deploy the configuration file and the values for each variable.

Notes:

• Make sure that the values of the variable names have the same format as the variable names in the original .ucf or .xml configuration files. For example, if the value in the original .ucf or .xml configuration file has double quotes, then add double quotes. If the value in the original .ucf or .xml configuration file is in capital letters, then use capital letters.
• If the value of a setting contains a back slash, then type another back slash before the first. For example, if the value is \\192.168.1.2\share , then enter \\\192.168.1.2\\share .
• If you do not want to update the current value of a variable setting, then set the value to CUR_VAL .

Creating a variable configuration .ucf or .xml file and a lookup .csv file manually

Creating a variable .ucf or .xml file

A variable file contains the variable setting names based on the template of the original settings file or configuration file.

1. Using a text editor, open the .ucf file.

2. From the setting that you want to have a variable value, change its value to ${ VariableName } , where VariableName is a unique variable name.

3. Save the file.

Notes:

• We recommend saving the .ucf file with a different name to distinguish it from the original file. For example, you can add the prefix Var_ to the file name.
• Take note of the variable names in the configuration file. These variable names are used when creating the lookup .csv file.

Sample standard settings file

nvOemMfgLongName "Lexmark International"
HTTPSENABLE TRUE
LPDTIMEOUT 90
printTimeout "90"

Sample variable .ucf file

nvOemMfgLongName $(variable_1)
HTTPSENABLE $(variable_2)
LPDTIMEOUT $(variable_3)
printTimeout $(variable_4)

Creating a VCC variable configuration file bundle

1. Extract the .xml or .ucf files in the bundle that you want to have variable settings.

2. Using a text editor, open the .xml or .ucf files.

3. From the setting that you want to have a variable value, change the value to ${ VariableName } , where VariableName is a unique variable name.

4. Save the file.

5. Compress the updated .xml or .ucf files in another bundle.

Notes:

• We recommend saving the bundle with a different name to distinguish it from the original bundle. For example, you can add the prefix Var_ in the file name.
• When updating multiple configuration files, use unique variable names. A variable name used in an .xml or .ucf file must not be used in a different .xml or .ucf file contained in the VCC bundle.
• Take note of the variable names in the configuration file. These variable names are used when creating the lookup .csv file.

The following are updated configuration files in a VCC configuration file bundle:

Sample bundle.xml file

<?xml version="1.0" encoding="UTF-8"?>
<bundle>
<bundleInfo>
<name> Exported Bundle </name>
<description>
Settings exported on Mon May 30 02:54:47 2016
 : FW version 201604071044</description>
</bundleInfo>
<vcc:esfSettings xmlns:vcc="vcc">
    <esfSetting src="esf_settings.xml" />
</vcc:esfSettings>
...
<deviceSettings>
	<setting name="nvVNCEnabled">Off</setting>
	<setting name="mfp.general.settingsTimeout">${variable_1}</setting>
	<setting name="pcl.A4Width">198 mm</setting>
	<setting name="network.IPV6DHCPENABLE">${variable_2}</setting>
	<setting name="rgbColorReplace2.outputR">${variable_3}</setting>
</deviceSettings>
</bundle>

Creating a lookup .csv file

A .csv file contains different values for the variable setting names based on the template.

1. Using a spreadsheet, in the first row, type the headers.

   Note:  Headers contain the identifier for the printers where you want to deploy the configuration file and the variable names in the configuration file.

2. Depending on the identifier used when adding a printer, use either HOSTNAME or IP_ADDRESS as the printer identifier.

   Notes:

   • For example, if you want to use the printer IP address, and you have specified Var1, Var2, and Var3, then type IP_ADDRESS,Var1,Var2,Var3 as the header.
   • Use the same identifier when adding a printer. For example, if you used the printer IP address when adding a printer, then use the same when creating a lookup .csv file.

3. In the succeeding rows, type the printer host names or IP addresses, and the values of each variable for each printer.

   Sample lookup file

   IP_ADDRESS,variable_1,variable_2,variable_3,variable_4
   192.168.1.1,"abc International",TRUE,60,"80"
   192.168.1.2,"xyz International",FALSE,70,"60"
   192.168.1.5,"mno International",FALSE,50,CUR_VAL

   Notes:

   • When using a spreadsheet that supports CSV file format, the values for each variable line does not show a comma. The values are separated by column and cell.
   • Make sure that the values of the variable names have the same format as the variable names in the original .ucf or .xml configuration files. For example, if the value in the original .ucf or .xml configuration file has double quotes, then add double quotes. If the value in the original .ucf or .xml configuration file is in capital letters, then use capital letters.
   • If the value of a setting contains a back slash, then type another back slash before the first. For example, if the value is \\192.168.1.2\share , then enter \\\192.168.1.2\\share .
   • If you do not want to update the current value of a variable setting, then set the value to CUR_VAL .
   Note:  For more information on setting the values in the lookup .csv file, see Understanding the lookup .csv file .

4. Save the file.

• Make sure that the values of the variable names are the same as the values in the original .ucf or .xml configuration files.

• If the value of a setting contains a back slash, then type another back slash before the first. For example, if the value is \\192.168.1.2\share , then enter \\\192.168.1.2\\share .

• Updating the new CSV file using a UTF text editor may result in an error.

Creating CSV files

A CSV file is used for deploying and creating packages. It contains the details of the supported printers on the network.

1. From DDU, click Create CSV File .

2. In the IP/Hostname field, type the IP address or host name of the devices, and then click .

   Use the following formats to add IP addresses:

   • 10.195.*.* (wildcards for only the last two octets)

   • 10.195.y.yy (single IP address)

   • 10.195.1.3-10.195.1.255 (IP address range)

   • printerHostname.company.com (host name)

   • 2001:db8:0:0:0:0:2:1 (single full IPv6 address; wildcards are not supported)

   Note:  To remove an IP address or host name, select it from the list, and then click .

3. If necessary, do the following:

   • To change the destination of the created CSV files, click Out Directory .

   • To configure device discovery settings, click Advanced Settings .

     Note:  To change the default file names of the generated CSV files, update the Ddu’s Input File Name and Package Builder’s Input File Name settings. For more information, see Understanding advanced settings .

4. Click Discover .

The following files are created in Out Directory:

• PkgBldrInput.csv —You can directly import this file to Package Builder for creating packages.

• DduInput.csv —You can use this file in DDU for deployment.

Notes:

• Only supported devices are added on the device lists.
• If the device lists are already created, and you want to create another device list, then make sure to update the file names. If you use the same file name as the existing device list, then DDU appends only the discovered supported devices.

Exporting device data

This feature lets you discover printers, and then export their certificate signing requests (CSR), all device settings, shortcuts, logs, and reports information.

1. From DDU, click Export Device Data .

2. Do any of the following:

   Export a device CSR

   1. Click Export Device CSR .

   2. Add printers. For more information, see Adding printers .

   3. From the Export Device CSR dialog, review the default path where the exported certificate files are stored.

      Note:  To change the default path, click Out Directory , and then browse to the correct directory.

   4. Click Export .

   Note:  To check the deployment status, click View Status .

   Export all device settings

   1. Click Export All Device Settings .

   2. Add printers. For more information, see Adding printers .

   3. From the Export All Device Settings dialog, review the default path where the exported files are stored in .zip format.

      Note:  To change the default path, click Out Directory , and then browse to the correct directory.

   4. Click Export .

   Note:  To check the deployment status, click View Status .

   Export device shortcuts

   1. Click Export Device Shortcuts .

   2. Add printers. For more information, see Adding printers .

   3. From the Export Device Shortcuts dialog, review the default path where the exported files are stored in .zip format.

      Note:  To change the default path, click Out Directory , and then browse to the correct directory.

   4. Click Export .

   Note:  To check the deployment status, click View Status .

   Export all device reports

   1. Click Export All Device Reports .

   2. Add printers. For more information, see Adding printers .

   3. From the Export All Device Reports dialog, review the default path where the exported files are stored in .zip format.

      Note:  To change the default path, click Out Directory , and then browse to the correct directory.

   4. Click Export .

   Note:  To check the deployment status, click View Status .

   Export logs

   1. Click Export Logs .

   2. Add printers. For more information, see Adding printers .

   3. From the Export Logs dialog, review the default path where the exported files are stored in .zip format.

      Note:  To change the default path, click Out Directory , and then browse to the correct directory.

   4. Click Export .

   Note:  To check the deployment status, click View Status .

Editing deployment workflows

1. From DDU, select a deployment workflow.

2. Click Edit .

3. Configure the items.

4. If necessary, click to configure the deployment workflow settings.

   Note:  For more information on configuring DDU, see Configuring the utility .

5. Click Save .

6. Do either of the following:

   • To update the package, click Overwrite workflow .

   • To create another package, click Save as new workflow .

Deleting deployment workflows

1. From DDU, select a deployment workflow.

2. Click .

Adding printers after creating a deployment workflow

You can add printers without editing the deployment workflow. Printers added using this process do not overwrite the printers added when creating a workflow.

1. From the home screen, click beside the deployment workflow.

2. Add printers. For more information, see Adding printers .

Notes:

• When adding or editing a printer list after creating a workflow, appears beside the workflow. If this icon does not appear, then the printer list saved with the workflow is used during deployment.
• To remove the updated printer list, click , remove all the printers or .csv files, and then click OK .

Deploying workflows

1. From DDU, select a deployment workflow.

2. Click .

3. If you are deploying a workflow on secured devices, then do the following:

   1. Select the authentication method used to access the secured printer.

      • Basic Authentication —Use a user name, user name and password, or PIN when accessing the printer.

      • Kerberos

      • LDAP

      • LDAP + GSSAPI

      Note:  For multiple secured devices, use the same authentication method and password.

   2. Type your authentication credentials.

   3. Click OK .

Notes:

• To check the deployment status, click Status .
• If you start another workflow while a workflow is still running, then the newly started workflow is queued and starts after the running workflow finishes.
• To stop deploying a workflow, click .

Enabling firmware updates access control

Before you deploy to secured printers, make sure that the Firmware Updates access control is enabled. Do the following:

1. Access the Embedded Web Server.

   1. Obtain the printer IP address. Do either of the following:

      • Locate the IP address on the printer home screen.

      • View the IP address in the Network Overview section or in the TCP/IP section of the Network/Ports menu.

   2. Open a web browser, and then type the printer IP address.

2. From the Embedded Web Server, depending on your printer model, do either of the following:

   • For eSF version 5:

     1. Click Settings > Security > Manage Groups/Permission > Edit Group > Access Controls > Device Management .

     2. Select Firmware Updates .

     3. Click Save .

   • For eSF version 4 or earlier:

     1. Click Settings > Security > Security Setup > Access Controls > Management .

     2. Set Firmware Updates to No Security .

     3. Click Submit .

Understanding the status panel and workflow logs

The status panel contains the following messaging structures:

• ALL —Shows the following:

  • IP addresses and their executed tasks

  • Summary overview of the executed tasks

  • Failed tasks and error messages

• Communication Errors —Shows the IP addresses with failed discovery tasks and their error messages.

• Deployment Errors —Shows the IP addresses with failed deployment tasks and their error messages.

• Successful Deployments —Shows the IP addresses with all successful tasks.

To change the default workflow logging settings, in the Advanced dialog, from the Logs section, configure either of the following:

• Clear Logs Interval (Days) —Specify the number of days before logs that are older than the specified value are removed.

  Notes:

  • The default value is 15 days.
  • This task occurs during the deployment of a workflow.

• Automatically Export Deployment Log —If set to true , then logs are automatically exported after the deployment of a workflow. If set to false , then the status panel shows an option to export the deployment log.

  Note:  The default value is true .

Accessing logs

The workflow deployment logs are located in the % DDUAppFolder %\bin\logs folder, where DDUAppFolder is the location of the DDU folder.

where:

DeploymentLog is the name of the deployment log.

TIMESTAMP is the log time.

The workflow deployment logs (.csv) contain any of the following:

• Successful deployments

• Communication errors

• Deployment errors

DDU uses the Apache Log4j ^TM software API to create the application and deployment logs. The configuration file for the logs can be found in DDUAppFolder \config\log4j-config.xml , where DDUAppFolder is the location of the DDU folder. For more information, see Configuring log settings .

By default, the log files are saved in the folder for the DDU executable files.

DDU creates the following logs:

• Application log (ddu.log) —If set to DEBUG , then this log file helps developers track each request and response between the device and the computer. Threads of requests and responses are classified according to device IP addresses.

• Deployment log —This log file helps users view device details and status of solutions and licenses being installed. The file also provides a message to confirm that deployment is successful. For easier sorting of device status, the log file is created in CSV format, with the IP address of the device as the first column.

  Checking for deployment errors

  1. Open the deployment.csv file. The log file can be found in DDUAppFolder \bin\log , where DDUAppFolder is the location of the DDU folder.

  2. Filter the log file for errors.

  Note:  If the log file is set to INFO , then the file contains the same messages as the status window does.