
11
• HTTP proxy user and password settings
• XTP tickets
• OXPd Repository items (available under Tools > Options > Device Management >
Configuration)
• Templates that contain encrypted data
Device passwords and configuration templates that contain passwords are encrypted to secure
any passwords that might be stored. To unlock the encryption, a key that is applicable only on the
machine where it was created must be used. Passwords are too important to not be protected as
securely as possible. Therefore, items that pertain to passwords in configuration file templates are
present in the HP Web Jetadmin database, but can no longer be decrypted and are unusable
after the clone operation. For templates that contain passwords and security settings, all of the
passwords and security settings, such as the SNMP Set Community Name, are removed from the
template. All of the other settings, such as the system location, remain the same. These templates
must be edited or re-created on the new HP Web Jetadmin installation.
Workaround: It is possible to export templates that contain passwords by using HP Web
Jetadmin. For instructions, see steps 2 and 5 in Method 1 for cloning
.
• If discoveries have been scheduled on the machine that is being cloned, those same
discoveries occur on the new HP Web Jetadmin installation at the exact same time. These
duplicate discoveries result in twice the network traffic. It might be more beneficial to
synchronize the cache on the new installation with the previous installation. For more
information, see Data synchronization
.
• If reports were run on the machine that is being cloned, data collections are scheduled to
occur at a particular time and frequency. Cloning causes duplicate collections to occur on the
same devices and increases network traffic.
DATA SYNCHRONIZATION
Multiple installations of HP Web Jetadmin can share their device information with each other to
eliminate unnecessary network traffic and improve the redundancy of device information in each
installation. This synchronization feature also helps to ensure an accurate central repository of devices
on a single HP Web Jetadmin instance with the flexibility of having the satellite installations perform
local discoveries and report the device information back to the master HP Web Jetadmin installation.
This synchronization feature is not a full cloning of one HP Web Jetadmin installation to another.
Rather, this synchronization feature merely shares the list of discovered devices from one installation
with another.
To initiate data synchronization for multiple HP Web Jetadmin installations, go to Tools > Data
Synchronization. The Data Synchronization window lists all of the discovered HP Web Jetadmin
servers on the network that are available for synchronization. If this list is empty, go to the Application
Management navigation pane, expand HP Web Jetadmin Management, select HP Web Jetadmin
Installations, and then click Discover. WS discovery is the most reliable discovery method. Only
similar versions can be synchronized. Values of the user-defined fields can only be synchronized if the
user-defined fields have been exported from Server A and imported on Server B before data
synchronization. For more information, see Exporting/importing user-defined settings
.
Note If the list shows the wrong version, go to the Application Management navigation pane,
expand HP Web Jetadmin Management, select HP Web Jetadmin Installations, and then
select and delete the entry for the HP Web Jetadmin installation. Then rediscover the HP Web
Jetadmin installation.
Comentários a estes Manuais