HP Neoware e90 ezRemote Manager 3.0 User Manual - Page 88

Instruction Set B, ezUpdate Server Configuration, ystem.rev, properties.rgy, connections.rgy

Page 88 highlights

Where X is the contents of the system.rev file. 4 If you have any registry files, most commonly the properties.rgy and connections.rgy created by ezRemote Manager, these will be added to the config.txt file next. For example: PROPERTIES "November 20, 2002" UPDATE_REGISTRY Properties.rgy CONNECTIONS "November 20, 2002" UPDATE_REGISTRY /REBOOT Connections.rgy There can be many additional registry files, and the date format is unimportant. However, prior to Neoware Rel. 6.0.3 there is a size limit of 64 KB per registry file. If the connections.rgy file, for instance, is 80K, it is possible to manually separate it into a 40K file connections1.rgy and a 40K connections2.rgy and modify the config.txt: PROPERTIES "November 20, 2002" UPDATE_REGISTRY Properties.rgy CONNECTIONS1 "November 20, 2002" UPDATE_REGISTRY / REBOOT Connections1.rgy CONNECTIONS2 "November 20, 2002" UPDATE_REGISTRY / REBOOT Connections2.rgy Instruction Set B To synchronize ezUpdate's behavior for Neoware Releases 6.0, 6.0.1, 6.02, and 6.0.3, an extra update process is necessary. 1 In the "(ftproot)/Neoware" folder on the ezUpdate server, create a folder with the name "3000." 2 In the "(ftproot)/Neoware" directory also place a config.txt file with the text: SYSTEM "X" LOAD_AND_RUN /REBOOT install.exe 3000 Where the value of "X" will be explained in step 3. Note: If you have a mixed environment with 5.3, 5.3.1, or 5.3.2 units, this extra update MUST contain a full update of that software. 88 ezUpdate Server Configuration

  • 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

88
ezUpdate Server Configuration
Where X is the contents of the s
ystem.rev
file.
4
If you have any registry files, most commonly the
properties.rgy
and
connections.rgy
created by ezRemote Manager, these will be
added to the
config.txt
file next. For example:
PROPERTIES “November 20, 2002" UPDATE_REGISTRY Proper-
ties.rgy
CONNECTIONS “November 20, 2002" UPDATE_REGISTRY /REBOOT
Connections.rgy
There can be many additional registry files, and the date format is
unimportant. However, prior to Neoware Rel. 6.0.3 there is a size
limit of 64 KB per registry file. If the
connections.rgy
file, for
instance, is 80K, it is possible to manually separate it into a 40K
file
connections1.rgy
and a 40K
connections2.rgy
and modify the
config.txt
:
PROPERTIES “November 20, 2002" UPDATE_REGISTRY Proper-
ties.rgy
CONNECTIONS1 “November 20, 2002" UPDATE_REGISTRY /
REBOOT Connections1.rgy
CONNECTIONS2 “November 20, 2002" UPDATE_REGISTRY /
REBOOT Connections2.rgy
Instruction Set B
To synchronize ezUpdate’s behavior for Neoware Releases 6.0,
6.0.1, 6.02, and 6.0.3, an extra update process is necessary.
1
In the “(ftproot)/Neoware” folder on the ezUpdate server, create a
folder with the name “3000.”
2
In the “(ftproot)/Neoware” directory also place a config.txt file
with the text:
SYSTEM “X” LOAD_AND_RUN /REBOOT install.exe 3000
Where the value of “X” will be explained in step 3.
Note: If you have a mixed environment with 5.3, 5.3.1, or 5.3.2
units, this extra update MUST contain a full update of that soft-
ware.