HP Neoware e90 ezRemote Manager 3.0 User Manual - Page 109

How XPe ezUpdate functions, Boot time check for updated software, ezUpdate, User Manual

Page 109 highlights

How XPe ezUpdate functions List View Boot time check for updated software When an ezUpdate-enabled XPe thin client appliance boots up (whether a soft reboot or a power cycle), an ezUpdate service runs in the appliance. ezUpdate is enabled as the default. • The ezUpdate service runs even if no user is logged in. • If DHCP has provided the XPe appliance with an ezUpdate FTP server name in tag 137 (see "DHCP tag 137" on page 104), then the ezUpdate service uses that server name. • If the XPe appliance has been configured to ignore tag 137 and has been configured with a server name using the ezUpdate Control Panel applet, then the ezUpdate uses that server name. • If no server name is provided, the ezUpdate service exits. • For more information about the ezUpdate Control Panel applet, see "ezUpdate Control Panel" on page 33 of the User Manual for Thin Client Appliances with Microsoft Windows XP Embedded Operating System, Rel. 1.2. • The ezUpdate service uses the following to create a query to the ezUpdate server: • The ezUpdate server name (or IP address) • The Flash disk size (in megabytes) • The profile name (by default, "factory") • For example, for a 256 MB Flash disk device accessing the ezUpdate server named "EZSERVER" with default ezUpdate settings in the thin client appliance, the service attempts to access ftp://EZSERVER/neoware/xpe/256/factory/image.dd • If an image.dd file is found, then the ezUpdate service attempts to access a version file matching its Update Version setting. For the Update Version setting of "1" (the default), the service attempts to access ftp://EZSERVER/neoware/xpe/256/factory/1. If the matching version file name is not found, then ezUpdate initiates a software update using the image.dd file located in the folder. How XPe ezUpdate functions 109

  • 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

How XPe ezUpdate functions
109
List View
How XPe ezUpdate functions
Boot time check for
updated software
When an ezUpdate-enabled XPe thin client appliance boots up
(whether a soft reboot or a power cycle), an
ezUpdate
service runs in
the appliance. ezUpdate is enabled as the default.
The ezUpdate service runs even if no user is logged in.
If DHCP has provided the XPe appliance with an ezUpdate FTP
server name in tag 137 (see “DHCP tag 137” on page 104), then
the ezUpdate service uses that server name.
If the XPe appliance has been configured to ignore tag 137 and
has been configured with a server name using the ezUpdate Con-
trol Panel applet, then the ezUpdate uses that server name.
If no server name is provided, the ezUpdate service exits.
For more information about the ezUpdate Control Panel applet,
see “ezUpdate Control Panel” on page 33 of the
User Manual for
Thin Client Appliances with Microsoft Windows XP Embedded
Operating System, Rel. 1.2.
The ezUpdate service uses the following to create a query to the
ezUpdate server:
The ezUpdate server name (or IP address)
The Flash disk size (in megabytes)
The profile name (by default, “factory”)
For example, for a 256 MB Flash disk device accessing the
ezUpdate server named “EZSERVER” with default ezUpdate
settings in the thin client appliance, the service attempts to
access
ftp://EZSERVER/neoware/xpe/256/factory/image.dd
If an
image.dd
file is found, then the ezUpdate service attempts to
access a version file matching its Update Version setting. For the
Update Version setting of “1” (the default), the service attempts
to access
ftp://EZSERVER/neoware/xpe/256/factory/1
. If the match-
ing version file name is not found, then ezUpdate initiates a soft-
ware update using the
image.dd
file located in the folder.