HP UPD - Driver Configuration Support Guide

HP DDU Frequently Asked Questions
Does HP DDU support driver preconfiguration?
Yes, the DDU can be used to pre-configure a driver for deployment. When the package is run on the
client PC, the new configuration file is used to configure the driver after it is installed. This does not
break WHQL certification.
How do I use the HP DDU to deploy a direct connect driver with
preconfiguration?
If you load multiple pdls for one printer, the OS will determine which one satisfies the Plug and Play
event. The OS will create one printer object for that pdl.
1. Run hpddu.exe to create the package.
2. From Package Source section:
a. Select the driver to package by browsing to an INF file in the directory.
b. Select the Preconfiguration checkbox. This checkbox is enabled only for drivers that
support preconfiguration.
c. Select the Silently preload the driver Install Type.
d. Select the Show a prompt to connect the printer checkbox if you want to prompt the user
after the files are copied
3. From Package Target section:
●
Three files will be written here: an .exe, a .cab and an .xml with information about the
package created.
4. From Create Package section:
a. If you want to suppress any error messages select the Suppress all end user error
messages checkbox.
b. Select the Create Package button
c. The configuration dialog will open and allow you to set configuration details for this driver.
After accepting the configuration changes, the package will be created.
5. Run the new .exe from the client machine. You must have administrator rights to run the exe
because it will be copying files into the Windows driver store. Now the driver files are on the
system, and any user can connect the printer to trigger the plug and play event.
NOTE: The printer object isn’t created until the printer is connected.
NOTE: If you deploy multiple direct connect preconfigured drivers, they all use a configuration file
with the same name, the first one connected will be the only one configured properly. This might
happen if you deploy the PCL6 and PCL5 drivers for the same printer. This is because the
configuration file is copied to the \3 directory awaiting for the printer to connect. Each deployment will
just copy over the same configuration file since they all use the same name. Once the printer is
connected, this configuration file gets consumed and deleted. Future Plug and Play events will not
have the configuration file available.
ENWW HP DDU Frequently Asked Questions 17