
●
Export conguration templates: Export a conguration template to a le and then import it into a dierent
instance of HP Web Jetadmin running on a dierent server (Export and Import Device Conguration
Templates on page 99).
●
Import conguration templates: After a conguration template has been exported, you can then import it
to use it on a dierent instance of HP Web Jetadmin running on a dierent server (Export and Import
Device Conguration Templates on page 99).
Volatile Conguration and HP Web Jetadmin Conguration Templates
Some actions performed remotely on devices can cause the device to automatically power cycle or change in
some other way that can impact the success of further conguration. Consider the case where you are
attempting to congure several device parameters, including one parameter that causes the device to reset
itself, which also causes HP Web Jetadmin to lose communication with the device for a time. Changing a device's
IP parameters is a good example. The device (in many cases) re-initializes and stops communicating for a time.
HP Web Jetadmin has several conguration elements that are known to cause device interrupts and, therefore,
cause a conguration to become volatile or unstable. These items are programmatically marked in such a way
that HP Web Jetadmin always uses them last in a conguration. These conguration items are:
●
Security > LDAP - Accessing the Server
●
Digital Sending > Activity Log
●
Fax > Fax Reports and Logs (print or clear activity log)
●
Security > Disable Direct Ports
●
Network > Protocol Stacks
●
Network > IPv4 Information, which includes Subnet Mask and Gateway (both single and batch
congurations)
●
Wireless > 802.11 a/b/g
●
Network > Link Setting
●
File System > File System Password
●
Security > Get Community Name
●
Security > Set Community Name
●
Security > SNMP Version Access Control
In any conguration, whether it is performed for a single device, for multiple devices, or with a conguration
template, these settings are always sent to the device last to improve the chance of successful congurations.
The following considerations should be made with these settings:
●
The chances of a conguration failure increase when these settings are used in the same conguration.
●
HP Web Jetadmin only marks these items to run last. HP Web Jetadmin does not put these items in any
order relative to the other items listed here.
●
Device behaviors, while sometimes predictable, are not fully documented with these known conguration
items.
In summary, not all of the HP Web Jetadmin congurations can guarantee a positive and stable result at the
physical device. You might need to test individual conguration options to understand the eects on various
HP device models and determine if an HP Web Jetadmin conguration is successful. HP will continue best eort
practices in documenting these and other known conguration characteristics.
ENWW Conguration 181
Komentarze do niniejszej Instrukcji