would otherwise have to be configured one device at a time. CSV files can easily be created by exporting data from a spreadsheet or word processing program.
Here is an example of a device configuration scenario:
●30 devices exist:
●Asset number assignments are required:
●Assignments are made respective to IP address sequence
A file can be created to represent the configuration desired. Here is a quick look at an example file:
Table 3-6 Example of a Configuration File
IP Addr | Port | Asset Number |
|
|
|
16.24.1.26 | 1 | Abc10040 |
|
|
|
16.24.1.27 | 1 | Abc10041 |
|
|
|
16.24.1.28 | 1 | Abc10042 |
|
|
|
16.24.1.29 | 1 | Abc10043 |
|
|
|
16.24.1.30 | 1 | Abc10044 |
|
|
|
NOTE: The first column is always the device identification, which can be an IP address, MAC address, or IP hostname. The second column is always the port. For HP devices, the port is 1, unless a device is attached to a multiport print server. For
Once the file is created and stored to disk on the client desktop; the user can import the file contents into HP Web Jetadmin using Configure Devices.
The CSV file contains header text for each device property to be configured. Once the user has browsed and uploaded the file a Map Headers control appears. The customer specific header text can be matched with the corresponding device property.
The first two columns are used to identify the devices to be configured. These devices must have already been discovered in HP Web Jetadmin prior to importing the file, or they will not be configured:
Table 3-7 Column Headers for Columns 1 through 3 for a CSV File
Column 1: Device Identifier (either IP address, hardware address (MAC address), or IP hostname)
Column 2: Port (always just “Port”)
Column 3+: selected by the user
Table 3-8 Importable Device Settings for Columns 3+ for a CSV File
Access Control List
Asset Number
Company Name
Default Copier Copies
Default Printer Copies
160 Chapter 3 Device Management | ENWW |
