HP LaserJet Pro 100 HP LaserJet Pro 100 Color MFP M175 - Software Technical Re - Page 80

HP Driver Deployment Utility, The HP DDU can be used with the Universal Print Driver installer

Get HP LaserJet Pro 100 PDF manuals and user guides View all HP LaserJet Pro 100 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 80 highlights

HP Driver Deployment Utility The HP Driver Deployment Utility (HP DDU) was created to simplify the deployment of print 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 HP DDU works with print drivers that can be installed by an .INF file. It is designed to work with print drivers that have their files contained in one directory structure. Because this utility is generic, it does not detect how specific print drivers are packaged. It packages all files in the directory (and subdirectories) where the print driver .INF file is found. The print driver must be expanded so that the HP DDU can process the .INF file. If you download an .EXE file with the print-driver files, you need to run it first to unpack all of the files. Then, run the HP DDU to package it for deployment on the client system. HP DDU can be used to pre-configure a print driver for deployment. When the package is run on the client computer, the new configuration file is used to configure the print driver after it is installed. This does not break WHQL certification. If the print driver was WHQL certified, and the print-driver files are organized within one directory structure, then HP DDU will not break WHQL certification. HP 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 print 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 Universal Print Driver installer may be a better choice as an install tool. The Universal Print Driver installer allows the configuration of settings from the command line. The HP DDU can be used with the Universal Print Driver installer, but the Universal Print Driver command line will not be accessible. The HP DDU is designed to package and stage/install print drivers. Print-driver specific features, like those found in the Universal Print Driver installer, are specific to the Universal Print Driver installer and not supported by the HP DDU. The HP DDU installer could be used with the Universal Print Drivers 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 print driver and create the printer object. Supported operating systems ● Microsoft Windows XP ● Microsoft Windows XP 64-Bit Edition ● Microsoft Windows Server 2003 ● Microsoft Windows Server 2003 64-Bit Edition ● Microsoft Windows Server 2008 62 Chapter 2 Windows software description 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
HP Driver Deployment Utility
The HP Driver Deployment Utility (HP DDU) was created to simplify the deployment of print 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 HP DDU works with print drivers that can be installed by an .INF file. It is designed to work with
print drivers that have their files contained in one directory structure. Because this utility is generic, it
does not detect how specific print drivers are packaged. It packages all files in the directory (and
subdirectories) where the print driver .INF file is found. The print driver must be expanded so that the
HP DDU can process the .INF file. If you download an .EXE file with the print-driver files, you need to
run it first to unpack all of the files. Then, run the HP DDU to package it for deployment on the client
system.
HP DDU can be used to pre-configure a print driver for deployment. When the package is run on the
client computer, the new configuration file is used to configure the print driver after it is installed. This
does not break WHQL certification.
If the print driver was WHQL certified, and the print-driver files are organized within one directory
structure, then HP DDU will not break WHQL certification. HP 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 print 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 Universal
Print Driver installer may be a better choice as an install tool. The Universal Print Driver installer allows
the configuration of settings from the command line.
The HP DDU can be used with the Universal Print Driver installer, but the Universal Print Driver
command line will not be accessible. The HP DDU is designed to package and stage/install print
drivers. Print-driver specific features, like those found in the Universal Print Driver installer, are specific
to the Universal Print Driver installer and not supported by the HP DDU.
The HP DDU installer could be used with the Universal Print Drivers 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 print driver and create the printer object.
Supported operating systems
●
Microsoft Windows XP
●
Microsoft Windows XP 64-Bit Edition
●
Microsoft Windows Server 2003
●
Microsoft Windows Server 2003 64-Bit Edition
●
Microsoft Windows Server 2008
62
Chapter 2
Windows software description
ENWW