Assessments - 0, GPA: 0
(
)
)
|
por este dispositivo também tem outras instruções :
Facilidade de uso
determined that a clone can indeed succeed following these steps, but there is NO GUARANTEE that
it will work in any particular environment.
Cloning an installation of HP Web Jetadmin involves a number of steps that should be followed in
precise order to increase the chances of success. The following steps assume that the new HP Web
Jetadmin installation (clone) will be running on the same drive letter as the original installation (as
well as the same directory on that drive letter). The drive letters MUST match as there are many
references in the files that are being copied to the new machine that point to the drive letter in use on
the old machine.
1) Perform a backup of the original HP Web Jetadmin installation following the backup.bat
procedure outlined earlier in this document.
2) Install a fresh copy of THE SAME VERSION of HP Web Jetadmin on the new (clone) machine
that existed on the original machine if a true clone is desired. If the versions don’t match, the
Settings directory files would not match when attempting to restore, thus causing
abnormalities. It is still possible to restore an old copy of an HP Web Jetadmin database on
a newer installation as the database tables would be updated for the new version. However,
ths would not be a true clone as the Settings directory files would not be cloned.
3) Once the fresh installation of HP Web Jetadmin is complete on the new clone machine,
restore the original HP Web Jetadmin files and directory using the restore.bat procedure
outlined earlier in this document.
Limitations of Cloning
Cloning simply cannot duplicate every single item from the original machine. Tthe following
limitations will exist with a cloned machine:
• If alerts had been configured on the original machine that involve traps, while the alerts settings
will be copied to the new machine during cloning, nothing has instructed the printers to start
sending traps to the new HP Web Jetadmin installation. If it is desired to have the new HP Web
Jetadmin installation process the alerts, the entries in the trap destination lists of each printer
would have to be modified. Fortunately, HP Web Jetadmin allows for modifying a device trap
destination list in both single and multiple configuration modes.
• Reports that display information pertaining to which user printed documents will not be processed
for the same reason as the alerts issue. By User reports rely on traps being sent from the device
after each print job. Since HP Web Jetadmin is now running on a new machine, new entries
must be made in the trap tables of all devices to send traps to the new machine. The
recommendation is to resubscribe to By User collections on the new HP Web Jetadmin machine
(which will write entries to the trap tables).
• When restoring settings store and database information to the HP Web Jetadmin host, encrypted
data will no longer function if the host or Windows OS instance is different from that which was
used to process the original file-set. In these cases, the encrypted data can be restored manually
through the HP Web Jetadmin user interface. A few examples of encrypted data include device
passwords, SMTP user/password settings, HTTP proxy user/password settings, etc. Credential
store passwords and saved configuration file templates are encrypted to secure any passwords
that may be stored. To unlock the encryption, a key must be used that is only applicable to the
machine where it was created. Passwords are too important not to protect as securely as
possible. Therefore, items pertaining to passwords in configuration file templates will have to be
recreated on the new HP Web Jetadmin installation as the old files cannot be unlocked or
unencrypted on the new machine if they are manually copied there.
• If discoveries have been scheduled on the machine that is being cloned, those same discoveries
will occur on the new HP Web Jetadmin installation at the exact same time, meaning twice the
8
...