HP LaserJet M9040/M9050 HP LaserJet M9040/M9050 MFP - Software Technical Refer - Page 296

HP Driver Deployment Utility

Page 296 highlights

HP Driver Deployment Utility The HP Driver Deployment Utility (DDU) was created to simplify the deployment of printer drivers onto a client computer. It is a simple utility that packages the printer-driver files, and the code needed to deploy them, into 2 files: an .EXE file and a .CAB file. These files are run on the client computer to copy the printer-driver files to the Windows driver store, and for network packages, to install the product. The DDU will work with printer drivers that can be installed by an .INF file. It is designed to work with printer drivers that have their files contained in one directory structure. Because this utility is generic, it does not detect how specific printer drivers are packaged. It will package up all files in the directory (and subdirectories) where the printer driver .INF file was found. The printer driver must be expanded so that the DDU can process the .INF file. If you download an .EXE file with the printer-driver files, you will need to run it first to unpack all of the files. Then, run the DDU to package it for deployment on the client system. The DDU can be used to pre-configure a printer driver for deployment. When the package is run on the client computer, the new configuration file is used to configure the printer driver after it is installed. This does not break WHQL certification. If the printer driver was WHQL certified, and the printer driver files are organized within one directory structure, then DDU will not break WHQL certification. DDU packages all of the files found in the printerdriver directory structure without modifying them. If printer-driver pre-configuration is done, the new configuration file is used to configure the printer driver after it is installed. This does not break WHQL certification. NOTE: If you need the ability to configure unique settings for printer-driver deployment, the UPD installer may be a better choice as an install tool. The UPD installer allows the configuration of settings from the command line. The DDU can be used with the UPD installer, but the UPD command line will not be accessible. The DDU is designed to package and stage/install printer drivers. Printer-driver specific features, like those found in the UPD installer, are specific to the UPD installer and not supported by the DDU. Examples of where the DDU installer could be used are to deploy a direct connect driver in traditional mode or a network install in traditional mode. NOTE: Administrative rights are necessary on the client system where the install is being performed. For a direct connect, administrative rights are only required to run the .EXE package. The user can then connect the product without administrative rights. For a network connection, the .EXE package will copy files to the driver store, create the port, install the printer driver and create the printer object. ● Microsoft Windows 2000 Service Pack 4 ● Microsoft Windows XP ● Microsoft Windows XP 64-Bit Edition ● Microsoft Windows Server 2003 ● Microsoft Windows Server 2003 64-Bit Edition ● Microsoft Windows Vista ● Microsoft Windows Vista (64-bit) 278 Chapter 6 Engineering details ENWW

  • 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
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326

HP Driver Deployment Utility
The HP Driver Deployment Utility (DDU) was created to simplify the deployment of printer drivers onto
a client computer. It is a simple utility that packages the printer-driver files, and the code needed to
deploy them, into 2 files: an .EXE file and a .CAB file. These files are run on the client computer to copy
the printer-driver files to the Windows driver store, and for network packages, to install the product.
The DDU will work with printer drivers that can be installed by an .INF file. It is designed to work with
printer drivers that have their files contained in one directory structure. Because this utility is generic, it
does not detect how specific printer drivers are packaged. It will package up all files in the directory (and
subdirectories) where the printer driver .INF file was found. The printer driver must be expanded so that
the DDU can process the .INF file. If you download an .EXE file with the printer-driver files, you will need
to run it first to unpack all of the files. Then, run the DDU to package it for deployment on the client
system.
The DDU can be used to pre-configure a printer driver for deployment. When the package is run on the
client computer, the new configuration file is used to configure the printer driver after it is installed. This
does not break WHQL certification.
If the printer driver was WHQL certified, and the printer driver files are organized within one directory
structure, then DDU will not break WHQL certification. DDU packages all of the files found in the printer-
driver directory structure without modifying them. If printer-driver pre-configuration is done, the new
configuration file is used to configure the printer driver after it is installed. This does not break WHQL
certification.
NOTE:
If you need the ability to configure unique settings for printer-driver deployment, the UPD
installer may be a better choice as an install tool. The UPD installer allows the configuration of settings
from the command line.
The DDU can be used with the UPD installer, but the UPD command line will not be accessible. The
DDU is designed to package and stage/install printer drivers. Printer-driver specific features, like those
found in the UPD installer, are specific to the UPD installer and not supported by the DDU.
Examples of where the DDU installer could be used are to deploy a direct connect driver in traditional
mode or a network install in traditional mode.
NOTE:
Administrative rights are necessary on the client system where the install is being performed.
For a direct connect, administrative rights are only required to run the .EXE package. The user can then
connect the product without administrative rights. For a network connection, the .EXE package will copy
files to the driver store, create the port, install the printer driver and create the printer object.
Microsoft Windows 2000 Service Pack 4
Microsoft Windows XP
Microsoft Windows XP 64-Bit Edition
Microsoft Windows Server 2003
Microsoft Windows Server 2003 64-Bit Edition
Microsoft Windows Vista
Microsoft Windows Vista (64-bit)
278
Chapter 6
Engineering details
ENWW