16. CR 10406: When accessing the device conguration history, HP Web Jetadmin no longer fails with the error
message Exception: System.NullReferenceException.
17. CR 10409: When conguring the Access Control List conguration option for HP LaserJet 400 M401 devices
when SNMPv3 is enabled and SNMPv1 is set to read-only, HP Web Jetadmin no longer displays Not
supported on the Results page.
18. CR 10410: HP Web Jetadmin now successfully congures the Access Control List conguration option for
HP LaserJet 4250, HP Color LaserJet CP3525, and HP LaserJet P4015 devices when SNMPv3 is enabled
and SNMPv1 is set to read-only.
19. CR 10481: After changing the HP Embedded Web Server (EWS) password for an HP LaserJet 400 M401
device, all of the HP FutureSmart devices no longer have a status of Device Communication Error.
20. CR 10548: When receiving alerts, HP Web Jetadmin no longer shows null instead of the actual device data,
such as IP Hostname: null.
21. CR 10570: When creating device conguration templates, HP Web Jetadmin now accepts the characters 0
through 9 in the name of the outgoing server.
22. CR 10578: When conguring Windows Users and Groups for HP FutureSmart devices, HP Web Jetadmin
now accepts the hyphen (-) and backslash (\) as valid characters, which matches the behavior of the
HP Embedded Web Server (EWS).
23. REQ 6584: HP Web Jetadmin now sets the Include thumbnail option for the Fax Receive Settings and Fax
Send Settings conguration options on HP FutureSmart devices that have rmware version 3.4 or later.
24. REQ 5887: When applying a device conguration template that has a customized order dened for the
Quick Sets to multiple devices, the Quick Sets are now listed in the same order on all of the devices.
25. REQ 6563: HP Web Jetadmin can now delete PIN-protected jobs on HP legacy devices that have rmware
version 13.2 or later.
HP Web Jetadmin 10.3 SR8 (10.3.96073)
The following are the improvements and xes made in HP Web Jetadmin 10.3 SR8 (10.3.96073):
1. HP Web Jetadmin was changing the hostname of a device when the device was turned o. This was a
problem in environments with DHCP servers, which always registered hostnames even if the IP address
was not distributed. In some cases, HP Web Jetadmin was also changing the hostname if two devices
swapped their IP addresses after a DHCP renewal.
Implemented x:
First check the status of the device. If the device status is Device Communication Error, do not update the
hostname.
If the device status is not Device Communication Error and the hostname on the device is dierent from the
hostname in HP Web Jetadmin, check the device for the model number, model name, and serial number.
Update the hostname only if these three values on the device are the same as the values on
HP Web Jetadmin.
2. Scheduled exports of the IP hostname and default From email address are now completing as fast as
manual exports.
3. Data collection is now possible when the regional settings are set to Korean.
24 Chapter 1 Late Breaking News for HP Web Jetadmin 10.4 SR2 (Edition 29, 5/2017) ENWW
Kommentare zu diesen Handbüchern