HP Neoware e90 ezRemote Manager 3.0 User Manual - Page 113

Snap-ins for XPe ezUpdate, install the required snap-inss.

Get HP Neoware e90 - Thin Client PDF manuals and user guides View all HP Neoware e90 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 113 highlights

image file, otherwise each XPe thin client with the "callcenter" profile name will load new software on every reboot. Snap-ins for XPe ezUpdate The snapins.txt file is a plain text file (empty by default) that is used to describe the list of snap-ins that are to be installed on each ezUpdate-managed XPe thin client appliance. If a snap-in is listed in snapins.txt but not installed in the ezUpdate-enabled appliance, at boot-up the ezUpdate service attempts to perform the snap-in installation from \neoware\xpe\shared\snapins, in a folder with the name of the not-installed snap-in. snapins.txt: Snap-in names should appear one per line, exactly the same as the folder name in the \neoware\xpe\shared\snapins directory. Commas are illegal characters in the ezUpdate snap-in names. Function of snap-ins for XPe ezUpdate • When checking to see if any snap-ins need to be installed/ updated, the ezUpdate server's snapins.txt file is compared to the XPe thin client appliance's registry containing Uninstall information: the DisplayName key. • If snapins.txt contains new or updated items, ezUpdate will install the required snap-ins(s). • If any of the snap-ins requires a reboot, the ezUpdate service will wait until all required snap-ins are installed before rebooting. • If Enhanced Write Filter is enabled on the thin client appliance(s), the changes will be committed prior to rebooting. For example, if the snapins.txt file contains a single line of "RDP52," and "RDP52" is not found in the XPe appliance's Uninstall registry keys, then the ezUpdate service will attempt to access ftp://servername/neoware/xpe/shared/snapins/RDP52 and execute the snap-in script file install.2do. List View XPe ezUpdate Advanced Topics 113

  • 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
XPe ezUpdate Advanced Topics
113
List View
image file, otherwise each XPe thin client with the “callcenter” pro-
file name will load new software on every reboot.
Snap-ins for XPe
ezUpdate
The
snapins.txt
file is a plain text file (empty by default) that is used
to describe the list of snap-ins that are to be installed on each ezUp-
date-managed XPe thin client appliance. If a snap-in is listed in
snapins.txt
but not installed in the ezUpdate-enabled appliance, at
boot-up the ezUpdate service attempts to perform the snap-in instal-
lation from
\neoware\xpe\shared\snapins
, in a folder with the name
of the not-installed snap-in.
snapins.txt:
Snap-in names should appear one per line, exactly the
same as the folder name in the
\neoware\xpe\shared\snapins
direc-
tory.
Commas are illegal characters in the ezUpdate snap-in names.
Function of snap-ins for XPe ezUpdate
•
When checking to see if any snap-ins need to be installed/
updated, the ezUpdate server’s snapins.txt file is compared to the
XPe thin client appliance’s registry containing Uninstall informa-
tion: the DisplayName key.
•
If snapins.txt contains new or updated items, ezUpdate will
install the required snap-ins(s).
•
If any of the snap-ins requires a reboot, the ezUpdate service will
wait until all required snap-ins are installed before rebooting.
•
If Enhanced Write Filter is enabled on the thin client appli-
ance(s), the changes will be committed prior to rebooting.
For example, if the
snapins.txt
file contains a single line of
“RDP52,” and “RDP52” is not found in the XPe appliance’s Unin-
stall registry keys, then the ezUpdate service will attempt to access
ftp://servername/neoware/xpe/shared/snapins/RDP52
and execute the
snap-in script file
install.2do
.