Compaq t5725 HP Device Manager User Manual - Page 129

Remote Execution of Windows Scripts, Execute After Reboot, Save As, Wscript.exe, C:\windows\system32

Page 129 highlights

6. In the Execute After Reboot column, select Yes if the device should reboot before executing the command you specify. Select No if you want the command to execute without the need to reboot the device. 7. In the Wait column, select Yes if the given command has to wait for the previous command to finish before processing, or set to No for simultaneous execution of commands. 8. If you want to specify more commands, click Add to continue. 9. Click OK when you have finished. 10. Click Save As to save the template under a new name. 11. Drag and drop the template on the devices where you want the commands to run. Remote Execution of Windows Scripts Windows Scripting Host is a comprehensive scripting infrastructure for the Microsoft Windows platform, provides script engines, Visual Basic Scripting Edition and Microsoft JScript, which can be embedded into Windows applications and an extensive array of supporting technologies that make it easier for script users to script Windows applications. For more information on how to write Windows scripts, see: http://www.msdn.microsoft.com Enter "windows script" as search keywords. To run windows scripts as a command from HP Device Manager, you need to add wscript before the script name you want to run. Wscript.exe is in the C:\windows\system32 directory. Remote Command Execution 119

  • 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
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255

6.
In the
Execute After Reboot
column, select
Yes
if the device should reboot before executing the
command you specify. Select
No
if you want the command to execute without the need to reboot
the device.
7.
In the
Wait
column, select
Yes
if the given command has to wait for the previous command to finish
before processing, or set to
No
for simultaneous execution of commands.
8.
If you want to specify more commands, click
Add
to continue.
9.
Click
OK
when you have finished.
10.
Click
Save As
to save the template under a new name.
11.
Drag and drop the template on the devices where you want the commands to run.
Remote Execution of Windows Scripts
Windows Scripting Host is a comprehensive scripting infrastructure for the Microsoft Windows platform,
provides script engines, Visual Basic Scripting Edition and Microsoft JScript, which can be embedded
into Windows applications and an extensive array of supporting technologies that make it easier for
script users to script Windows applications.
For more information on how to write Windows scripts, see:
Enter “
windows script
” as search keywords.
To run windows scripts as a command from HP Device Manager, you need to add
wscript
before the
script name you want to run.
Wscript.exe
is in the
C:\windows\system32
directory.
Remote Command Execution
119