DRIVER CONFIGURATION Support Guide
HP Driver Pre-Configuration and Deployment Guide Support Guide
Copyright and License Trademark Credits © 2013 Copyright Hewlett-Packard Development Company, L.P. AMD is a trademark of Advanced Micro Devices, Inc. Intel® is a trademark of Intel Corporation in the U.S. and other countries. Microsoft®, Windows®, Windows® XP, Windows Vista®, Windows® 8, Windows® 2008, and Windows® 2008R2 are U.S. registered trademarks of Microsoft Corporation.
Table of contents 1 Introduction ....................................................................................................................................................... 1 2 HP Driver Configuration Utility .......................................................................................................................... 3 Driver acquisition ..................................................................................................................................
What does the HP DDU do on the client system? ............................................................. 19 How do I reuse a package I created? ................................................................................ 19 Common Problems ............................................................................................................ 19 I get a “Multiple Drivers Found” warning when I select the driver .....................
1 Introduction The HP Driver Pre-Configuration and Deployment Guide describes the HP printer management software used to configure and deploy HP drivers. Three separate tools for configuring and deploying HP drivers are described in detail. ● HP Driver Configuration Utility (DCU) ● HP Driver Deployment Utility (DDU) ● HP Web Jetadmin (WJA) NOTE: The System Administrator Guide (SAG) provides detailed instructions for other installation methods and can be downloaded from http://www.hp.com/go/upd.
The process for driver preconfiguration can be accomplished using either the HP Driver Configuration Utility or the HP Driver Deployment Utility. Both are designed with the same basic UI controls for interacting with the hpcpu*.cfg or [filename].cfm file, but are packaged differently, to support established printer installation workflows or to leave the deployment and installation of the driver entirely up to the user.
2 HP Driver Configuration Utility The HP Driver Configuration Utility is a small Windows application used to edit the configuration file associated with a particular driver. The configuration file controls the print driver settings and takes effect when the driver is installed for both dynamic and traditional mode installation methods. NOTE: Windows requires a user to have Administrator rights to install a printer driver.
Access/installation HP DCU is included with the HP Printer Administrator’s Resource Kit (HP PARK) and can be downloaded at: www.hp.com/go/upd Driver pre-configuration The process of configuring drivers and other software occurs before installation. This allows the driver to be configured once and installed on any number of server or client systems. The driver configuration is stored in a configuration file named hpcpu*.cf_. For example, the configuration file for HP UPD 5.5 would be named hpcpu130.cfg.
Utilization requires that the .cfm reside on the local machine's driver installation directory before the HP UPD installation. When the HP UPD installation is launched, the settings defined in the *.cfm file become the installed defaults. If a *.cf_ or *.cfg file exist along with a *.cfm file, the *.cfm file on the local machine's driver installation directory will take priority. Following the installation, the hpcpu*.cfm changes to hpcpu*.
Creating cfm files After download, the HP Driver Configuration Utility compressed package can be expanded into a local or network directory. No formal installation process is required. Double-click the HPBCFGAP.EXE file in the destination directory to launch the HP DCU. NOTE: The HP DCU is included with the HP Printer Administrator's Resource Kit (PARK). To download the PARK, go to the HP website, www.hp.com/go/upd.
Configuration file *.cfm: The *.cfm file is not deployed as part of the standard driver installation package. This restricts its use to local installations. Utilization requires that the .cfm reside on the local machine's driver installation directory before the HP UPD's installation. When the HP UPD installation is launched, the settings defined in the *.cfm file become the installed defaults. If both a *.cf_ or *.cfg and a *.cfm file exist, the *.
When copying the cfm file to the local machine driver directory, the cfm file name must have the format hpcpuxxx.cfm, where xxx matches the number of the cfg file. For example, hpcpu130.cfg would be named hpcpu130.cfm. When using UPD 5.2 or later (excluding 5.4), you can use any file name, as long as it uses the extension .cfm, and the install.exe is used with the /gcfm option to install the printer. For example, install /gcfm”c:\temp\duplex.
Lockable features Each HP printer model defines the feature set available for preconfiguration. In general, most driver features are supported, meaning that device settings and printing preferences can be customized prior to installation. Additionally, some features can be locked to a particular state if an IT administrator desires control over device usage. Features that are defined under custom shortcuts cannot be locked.
10 Chapter 2 HP Driver Configuration Utility ENWW
3 HP Driver Deployment Utility The HP Driver Deployment Utility (HP DDU) was created to simplify the deployment of printer drivers onto a client PC. It is a simple utility that packages the driver files and the code needed to deploy them into an *.EXE and *.CAB file. These files are run on the client PC to copy the driver files to the Windows driver store and for network packages, to install the printer. NOTE: Windows requires a user to have administrator rights to install a printer driver.
Install and run the HP Driver Deployment Utility Download the most current version of the HP Driver Deployment Utility from www.hp.com/go/upd NOTE: The HP Driver Deployment Utility is included with the PARK. To download the PARK, which includes the HP DDU software and this guide (HP Driver Configuration and Deployment Support Guide), go to the above URL, click the Documentation tab, and then click HP Printer Administrator's Resource Kit from the Universal Print Driver Tools section.
Use the HP Driver Deployment Utility The HP Driver Deployment Utility user interface is divided into 3 sections: ● Package Source ● Package Target ● Create Package Package Source The following describes the package type and driver location to create. Driver Directory—Use the Select Driver button to enter the directory where your driver resides by browsing or typing it in.
The following network settings are additional. You may accept the default values or change any of them. ● Port Name: This is the network port name that will be created. If the name already exists, a number will be appended to make it unique. ● Printer Name: This is the printer name that will appear in the printers’ folder. If the name already exists, a number will be appended to make it unique.
New features The following new features have been added to the HP DDU: ● Progress dialog—The HP DDU has been modified to display a progress dialog while the driver is being installed on the client. The progress dialog does not require user interaction and can be disabled to provide a completely silent install at runtime. To disable the progress dialog, run the deployment package with the /q command line InstallPackage.exe /q.
Table 3-2 HP DDU command line options for network connect packages (continued) Option Description /hn Use the specified hostname to identify the printer; for example/hn Myhostname. The hostname cannot be longer than 255 chars and can only contain the following characters: A-Z, a-z, 0-9 and the dash (-). In Dynamic mode, the HP UPD provides the ability for a user to search the network for installed devices.
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.
How do I use the HP DDU to deploy a network printer with preconfiguration? 1. Run hpddu.exe to create the package. 2. From Package Source section: 3. 4. 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 create network port and install driver Install Type. d. Select the Network Settings button to enter the network settings.
structure without modifying them. If driver pre-configuration is done, the new configuration file is used to configure the driver after it is installed. This does not break WHQL certification. When should I use the UPD installer instead of HP DDU? The HP UPD installer has many unique settings that can be configured on the command line. If you need any of these unique items, you should use the UPD installer instead of DDU.
I get a “Please select the driver directory before configuring network settings” error when I try to open the “Network Settings” dialog Select a driver before opening the Network Settings dialog. This allows the printer name field to be auto-filled based on the driver name. The Create Package button is not enabled This button will not be enabled until you have: 1. Selected the driver. 2. If network connect – filled out one of the required network settings. 3. Selected the Save as name and directory.
4 Print queue and print driver management using HP Web Jetadmin V10 Introduction HP Web Jetadmin V10 (referred to hereafter as HP Web Jetadmin) is a software application for managing print queues and print drivers on remote servers and workstations. Administrators can create, edit and delete print queues and install or update print drivers by using the Print Management features in HP Web Jetadmin. HP Web Jetadmin can act as a driver repository for deploying new HP drivers on remote systems.
Create a print queue Local administrator credentials are required on hosts managed by HP Web Jetadmin Print Management features. You can establish these rights in a number of ways. ● You are a domain administrator. ● Your user domain account exists in the local Administrator group on the remote host. ● You belong to a domain group that exists in the local Administrator group on the remote host. NOTE: File and printer sharing must be enabled at the remote host where the print queue is to be created. 1.
2. Select a device from the list (only one device can be selected). Click Next. The Select server page appears. Figure 4-2 Select server page 3. Select a server name and a domain. Select Add (more than one computer name can be selected). Click Next. The Select driver page appears. Figure 4-3 Select driver page ENWW 4.
● Universal Print Driver - an embedded INF installer for the HP Universal Print Driver is a resident part of the Print Management solution. The HP Universal Print Driver Post Script is available here as an installed feature. ● Known Drivers - drivers that are already installed on the remote host or drivers that exist on the HP Web Jetadmin server (INF driver install base). These drivers, when identified for use with the print queue, are added to the queue as it is being installed.
1. Open the Create Queue wizard by either right-clicking in the Print Management tree or by selecting Create Print Queue from the Print Management - Common Tasks task module. 2. Select a device from either a group or the All devices listing. Only one device selection is possible. Click Next. 3. Select one or more remote hosts using the Select Server screen. 4. Select the driver and preconfiguration if it exists. 5. Enter a name for the queue and supply any necessary share information. 6.
3. Click Next. The Confirm page appears. 4. Click Next. The Results page appears. Click Done to view the Print Management page. Driver management HP Web Jetadmin facilitates driver management. Drivers can be added to the HP Web Jetadmin host which acts as a driver repository. These drivers are installed on remote hosts where queue management is being performed. The drivers can be removed when they are no longer the latest revision or no longer needed.
2. ENWW Select the driver and click Next. The Specify Configuration Options page appears.
3. Configure the driver settings and name the preconfiguration for the driver; notice that some settings might be locked in which cases you cannot edit them. Click Next. The Confirm page appears. 4. Click Save Configuration. The Results page appears. 5. Click Done. The Print Management page appears. The new preconfiguration and the default configuration now exist and can either be exported to an INF driver install file set or used in managing print queues.
Default or any previously stored preconfiguration. This preconfiguration is applied to the host where print queue management is targeted. HP Universal Print Driver (HP UPD) The HP Universal Print Driver Postscript (HP UPD-PS) is bundled with HP Web Jetadmin software and can be installed from any create or edit queue interface. The HP Universal Print Driver has preconfiguration capabilities which allow you to specify print defaults such as duplex or grayscale.
30 Chapter 4 Print queue and print driver management using HP Web Jetadmin V10 ENWW
5 Appendix A The hpcpu*.cf_ (available in HP UPD 5.0.3 and earlier releases) are compressed configuration files compressed in the driver package supplied with the drive. It can only be edited using DCU. When the DCU is used to preconfigure driver settings, the driver's default configuration file is copied outside the compressed driver package allowing the contents of the configuration file to be modified with administrator-defined settings.
32 Chapter 5 Appendix A ENWW
