HP Neoware e90 ezRemote Manager 3.0 User Manual - Page 52

Why clone properties?, Save time configuring thin client appliances

Page 52 highlights

Properties Manager Why clone properties? Save time configuring thin client appliances Save standard configurations as backups Create ezUpdate server configuration files Individual thin client appliances can be configured at the desktop when installed or whenever network resources change. This configuration usually includes initially setting up monitor resolution, the network, defining printers, and deciding to which servers, applications, and Web sites the thin client user may have access. While this configuration doesn't take much time for an individual appliance, initially configuring or changing the configurations on more than a few thin client devices can consume a lot of administrator resources. The alternative to individual client configuration is to configure a single appliance (the "template" appliance) with a standard configuration that other devices can use, and to then clone that configuration and copy it to the other thin client appliances. ezRemote Manager makes cloning and copying thin client configurations easy and quick. Saving the template configuration to file provides a way to archive and back up your thin client appliance configurations. Multiple configuration files can be saved for later access and restoration using ezRemote Manager. The property cloning mechanism used by ezRemote Manager to push new or updated configurations to target thin client appliances can also be used to create configuration files that can be pulled by same-model thin client appliances from ezUpdate servers. (For more information about setting up an ezUpdate server: see "Appendix B: ezUpdate for Windows CE Appliances" on page 83, or see "Appendix C: ezUpdate for NeoLinux Appliances" on page 93.) Setting up the template appliance Using ezRemote Manager to manage the appliance properties of your Neoware thin client devices is easy. The process begins at the appliance itself. 52 Why clone properties?

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118

Properties Manager
52
Why clone properties?
Why clone properties?
Save time
configuring thin
client appliances
Individual thin client appliances can be configured at the desktop
when installed or whenever network resources change. This configu-
ration usually includes initially setting up monitor resolution, the
network, defining printers, and deciding to which servers, applica-
tions, and Web sites the thin client user may have access. While this
configuration doesn’t take much time for an individual appliance,
initially configuring or changing the configurations on more than a
few thin client devices can consume a lot of administrator resources.
The alternative to individual client configuration is to configure a
single appliance (the “template” appliance) with a
standard
configu-
ration that other devices can use, and to then
clone
that configuration
and
copy
it to the other thin client appliances. ezRemote Manager
makes cloning and copying thin client configurations easy and
quick.
Save standard
configurations as
backups
Saving the template configuration to file provides a way to archive
and back up your thin client appliance configurations. Multiple con-
figuration files can be saved for later access and restoration using
ezRemote Manager.
Create ezUpdate
server
configuration files
The property cloning mechanism used by ezRemote Manager to
push
new or updated configurations to target thin client appliances
can also be used to create configuration files that can be
pulled
by
same-model thin client appliances from ezUpdate servers. (For more
information about setting up an ezUpdate server: see “Appendix B:
ezUpdate for Windows CE Appliances” on page 83, or see “Appen-
dix C: ezUpdate for NeoLinux Appliances” on page 93.)
Setting up the template appliance
Using ezRemote Manager to manage the appliance properties of
your Neoware thin client devices is easy. The process begins at the
appliance itself.