HP Web Jetadmin - Creating Reports and Exporting Data

10
Device Utilization by User data collection—a special case
Device Utilization by User data collection is a data collection type that collects Personal Identifiable
Information (PII). This data collection type attempts to capture the name of each user sending each
print job to the device along with the associated job information, such as printed pages (Color, Mono,
Simplex, and Duplex Pages, plus Media Size), Copy Pages, Digital Send Pages, Incoming Fax Pages,
and the application used (Adobe PDF, Microsoft Excel, Microsoft PowerPoint, Microsoft Word, and
Web Pages). Users and administrators should understand their own policies on PII before enabling
Device Utilization by User data collection on their devices.
Using Device Utilization by User data collection to capture the print job’s user name is only supported
with HP printing devices and only in Windows environments. In addition, the print driver must be
either the device model’s specific Windows driver from HP (not from Microsoft) or the HP UPD. The
user name captured is the Windows user logon name in the format “DOMAIN\USER”. In all other
operating system environments and Windows environments not using one of the supported print
drivers, the user name is captured under the name “Anonymous”.
For a Device Utilization by User
data collection to be successful,
the device must also have a Job
Information Table (to hold the job
information over time) and an
SNMP Trap Destination Table
(Figure 11).
To summarize, the requirements
for a successful Device Utilization
by User data collection are:
 Windows environment
 Use of HP print driver or
HP UPD
 A device that supports Job
Information Table (not
supported on all HP printing
devices)
 A device that supports SNMP
Trap Destination Table (not
supported on all HP printing
devices)
 A device with the ability to
send an end-of-job trap (not supported on all HP printing devices)
With these requirements in place, Device Utilization by User data collection is the one type of data
collection that does not depend on a regularly scheduled interval to collect data. HP Web Jetadmin
must rely on gathering this data from the device’s job information table. Because different device
models have different sized job information tables and because HP Web Jetadmin does not know the
length of each table, data must be collected after each print job. This is to help minimize the loss of
any data as it rotates through the job table (the table has a “first-in, first-out” algorithm) before
HP Web Jetadmin can capture it. Lost job information can still occur due to a spike in network traffic,
when the device receives many print jobs in a very short period of time.
Figure 11—Config tab showing SNMP Trap Destination Table