HP 4650 HP Color LaserJet 4650 - Software Technical Reference (External) - Page 43

HP Driver Preconfiguration

Page 43 highlights

Table 2-2. Enterprise Autoconfiguration availability in Novell Netware environments Method Connection type Novell Netware 4.x Netware 5.x Bindery queue NDS queue Bindery queue NT 4.0 Installer Direct connect Universal serial bus (USB) Parallel Network Jetdirect TCP/IP x x x x IPX/SPX Standard TCP/IP (HP) TCP/IP (MS1) IPX/SPX (HP) 1 Bidirectional functionality is supported only with the client software from Novell. It is not supported with Microsoft (MS) Client Service for NetWare. HP Driver Preconfiguration HP Driver Preconfiguration is a software architecture and set of tools that permits HP printing-system software to be customized and distributed in managed corporate printing environments. Using HP Driver Preconfiguration, information technology (IT) administrators in corporate and enterprise environments can preconfigure the printing and device defaults for HP print drivers before installing the drivers in the network environment. HP Driver Preconfiguration is most beneficial when configuring print drivers for multiple workstations or print servers for print queues that share the same configuration. Two types of features can be configured: device settings and printing-preferences settings. The driver is configured to match the product hardware so that gaining access to all of the product accessories through the driver is enabled correctly (for example, for duplexing units and additional input trays). Most driver feature settings can also be configured. HP Preconfiguration configures the driver to match the accessories installed on the printer, or to match the settings that IT administrators make in the configuration (.CFG) file (for example, optional trays, total amount of memory, job storage settings, mopier settings). The preconfiguration process consists of three basic steps: driver acquisition, driver preconfiguration, and driver installation and deployment. These steps can be accomplished in different ways, depending on the tool that is being used to define the configuration. EN Chapter 2 Software description 23

  • 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
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309

Table 2-2. Enterprise Autoconfiguration availability in Novell Netware environments
Method
Connection type
Novell
Netware 4.x
Netware 5.x
Bindery
queue
NDS queue
Bindery
queue
NT 4.0
Installer
Direct
connect
Universal serial bus (USB)
Parallel
Network
Jetdirect
TCP/IP
x
x
x
x
IPX/SPX
Standard
TCP/IP (HP)
TCP/IP
(MS
1
)
IPX/SPX
(HP)
1
Bidirectional functionality is supported only with the client software from Novell. It is not supported with Microsoft
(MS) Client Service for NetWare.
HP Driver Preconfiguration
HP Driver Preconfiguration is a software architecture and set of tools that permits HP
printing-system software to be customized and distributed in managed corporate printing
environments. Using HP Driver Preconfiguration, information technology (IT) administrators
in corporate and enterprise environments can preconfigure the printing and device defaults
for HP print drivers before installing the drivers in the network environment.
HP Driver Preconfiguration is most beneficial when configuring print drivers for multiple
workstations or print servers for print queues that share the same configuration. Two types
of features can be configured: device settings and printing-preferences settings. The driver is
configured to match the product hardware so that gaining access to all of the product
accessories through the driver is enabled correctly (for example, for duplexing units and
additional input trays). Most driver feature settings can also be configured.
HP Preconfiguration configures the driver to match the accessories installed on the printer,
or to match the settings that IT administrators make in the configuration (.CFG) file (for
example, optional trays, total amount of memory, job storage settings, mopier settings).
The preconfiguration process consists of three basic steps: driver acquisition, driver
preconfiguration, and driver installation and deployment. These steps can be accomplished
in different ways, depending on the tool that is being used to define the configuration.
EN
Chapter 2 Software description
23