HP Neoware e90 ezRemote Manager 3.0 User Manual - Page 41

Cloned connection settings, What about other configuration settings?, Why clone connections? - thin client setup

Page 41 highlights

Connection Manager Connection Manager Connection Manager Cloned connection settings What about other configuration settings? dows XPe/NTe appliances, see "XPe/NTe software cloning" on page 35.) The following are examples of settings copied and cloned in Connection Manager (when the source or template appliance has any of these connections defined): • ICA connections: all configuration settings for each defined con- nection • RDP connections: all configuration settings for each defined con- nection • TeemTalk terminal emulation connections (if installed on source or template appliance): all configuration settings for each defined connection • Web browser connections: all configuration settings for each defined Web browser • PPP connections: all configuration settings for each defined PPP connection Other appliance configuration settings, such as printer setup, screen resolution, and global ICA settings are cloned through Properties Manager.(See "CHAPTER 7 Properties Manager" on page 49.) Why clone connections? Save time configuring thin client appliances Individual thin client appliances can be configured at the desktop when installed or whenever network resources change. This configuration usually includes initially defining 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 connection configurations on more than a few thin client devices can consume a lot of administrator resources. Connections Why clone connections? 41

  • 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

Connection Manager
Why clone connections?
41
Connections
Connection Manager
Connection Manager
dows XPe/NTe appliances, see “XPe/NTe software cloning” on page
35.)
Cloned connection
settings
The following are examples of settings copied and cloned in Con-
nection Manager (when the source or template appliance has any of
these connections defined):
ICA connections: all configuration settings for each defined con-
nection
RDP connections: all configuration settings for each defined con-
nection
TeemTalk terminal emulation connections (if installed on source
or template appliance): all configuration settings for each defined
connection
Web browser connections: all configuration settings for each
defined Web browser
PPP connections: all configuration settings for each defined PPP
connection
What about other
configuration
settings?
Other appliance configuration settings, such as printer setup, screen
resolution, and global ICA settings are cloned through Properties
Manager.(See “CHAPTER 7 Properties Manager” on page 49.)
Why clone connections?
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 defining 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 connection configurations on
more than a few thin client devices can consume a lot of administra-
tor resources.