HP OfficeJet, LaserJet printer setup (Windows Server 2016, 2012, 2008, 2003)

Review guidelines and steps for enterprise administrators on customizing HP printer installations.

This document applies to Windows Server 2016 (64 bit), 2012 (64 bit), 2008 R2 (64 bit), 2008 (32, 64 bit), 2003 R2 (32, 64 bit), 2003 (32 bit -SP1 or greater).

Customize the installation

Set up the driver and software install, create a command to select features and customize the installation, and connect client computers to the printer.

Before you begin the installation

Gather the following information before starting the install.

• Type of Windows operating system (Windows 2003, Windows 2008, or Windows 2012)

• Operating system version (32 or 64-bit)

• Language of the operating system where the printer is installed

• Connection type of the installed printer (USB or network)

Copy the driver and software files

Use the CD or download the print driver and software from HP Customer Support.

1. Insert the setup disk that shipped with the printer, create a folder on your system, and then copy the setup files into the folder.

   NOTE:

   If you do not have the disk, continue with these steps to download the driver.

2. Go to HP Software and Driver Downloads, and then enter and select your printer to go to the software and drivers page for your model.

3. Next to Detected operating system, click Choose a different OS, select your server operating system, and then click Change.

4. Select Full Feature Software and Driver or EasyStart Printer Setup Software–Offline Use Only.

5. Review the download options and information, and then click Download.

6. Click Save, and then browse to the location on your computer where you want to save the file.

7. Click Save to download the software.

8. Extract the executable file through a decompression program such as 7-Zip into a folder that you created.

To install the software that supports the printer, install the appropriate MSI. The MSI installs all supporting software, and then preinstalls the drivers for the printer. The drivers are available when you plug the printer into the computer or a network printer is installed.

There are two MSIs at the root of the CD image. One has an x86 suffix and one has an x64 suffix. The printer model number is in the MSI names (for example A910nx86.msi and A910nx64.msi). Install the x86 MSI on 32-bit Windows versions. Install the x64 MSI on x64 versions.

Create a command to select features and customize the installation

Use Msiexec to install an MSI. Review command properties and language IDs that turn certain features off or on in the software when installing the MSI.

NOTE:

For a more thorough documentation of msiexec and for additional questions, go to Microsoft Documentation - Msiexec (command-line options). If anything described in this section conflicts with the Microsoft documentation, assume that Microsoft documentation is correct.

Use your favorite tool to install the MSI onto the client computers. However, if you choose to use msiexec.exe, common command parameters might be helpful. Installing an MSI can be done by passing the path to siexec with the /i parameter:

msiexec.exe /i D:\A910nx86.msi (where D is the path to the msiexec file)

COMMAND PROPERTIES

Property Name	Values	Description	Default Value
CONNECT_NEW_PRINTER_ SHORTCUT	YES NO	Install the Start menu shortcut to add a new printer.	YES
ENTERPRISE	YES NO	Install the full software (NO) or the minimum software (YES) for enterprise applications.	NO
FAX	YES NO	Install the print-to-fax driver or not. If FAX=YES and ENTERPRISE=NO, the fax software is also installed. Otherwise, fax software is not installed.	YES
IGNORE_SERIALNUM	YES NO	Windows should or should not ignore the serial number when installing the printer via plug and play.	NO
MULTICAST	YES NO	Enable or disable multicast discovery to rediscover installed printers.	NO
REBOOT	Force Suppress ReallySuppress	Setting for when Windows Installer requires a reboot to complete the install.	(none)
SCANTOPC Not applicable for single function printers, Officejet 6500A, 6600/6700, 7500A, Officejet Pro 8500A, 8600	YES NO	Option to activate the scan-to-computer software is hidden (YES). Users must initiate scans from the computer instead of the printer. If set to anything other than NO, the option to activate the scan-to-pc software displays. If the property is not set, the printer displays the option.	YES
TRANSFORMS	Transform file name, ex: A910nx86_1055.mst	Filename or path to the transform file that is to be applied.	(none)
UNINSTALL_SHORTCUT	YES NO	Select to display the shortcut on the Start menu to uninstall the software.	YES

Languages and language IDs

Most installed files support MUI and include all language resources. However, the installed shortcuts are language-specific. By default, the shortcuts are installed in English. To change the language, find the language ID in the following table. Include the ID on the command line when installing the MSI. The transforms use the same filename as the MSI followed by an underscore and the language ID.

For example, to change the language to Spanish, use msiexec.exe /i A910nx86.msi /qn TRANSFORMS=A910nx86_1034.mst.

LANGUAGE IDS

Language	Language ID
Arabic	1025
Traditional Chinese	1028
Czech	1029
Danish	1030
German	1031
Greek	1032
English	1033
Spanish	1034
Finnish	1035
French	1036
Hebrew	1037
Hungarian	1038
Italian	1040
Japanese	1041
Korean	1042
Dutch	1043
Norwegian	1044
Polish	1045
Portuguese	1046
Russian	1049
Swedish	1053
Turkish	1055
Simplified Chinese	2052

Collect the files for distribution

Review the files on the CD image and when they are required. Administrators should refer to this table to set up an image that contains only the files necessary for the specified installation.

DRIVER FILES

Driver Files	Description
i386 (folder)	Folder containing 32-bit print driver files (required for installations on all 32-bit and 64-bit computers)
AMD64 (folder)	Folder containing 64-bit print driver files (required for installations on all 32-bit and 64-bit computers)
Hp_*.gpd	Print driver file
HPMACRONAMES.gpd	Print driver file
Hpvpl04.inf	Print driver file
Hpvpl04.ini	Print driver file
Hpvpl04.cat	Print driver file
Hpvplargb.icc	Print driver file
Locale.gpd	Print driver file
Pl.bmp	Print driver file
STDNAMES.gpd	Print driver file
Drivers\Scanner (folder)	Folder containing scan driver files
HPScanMiniDrv_*.inf	Scan driver file
HPScanMiniDrv_*.cat	Scan driver file
Drivers\Fax (folder)	Folder containing fax drivers (required if installing fax)
HP*_fax.inf	Fax driver file (required if installing fax)
HP*_fax*.cat	Fax driver file (required if installing fax)
HP*_nullfax.inf	Replacement driver for Fax (required if NOT installing fax)
HP*_nullfax*.cat	Replacement driver for Fax (required if NOT installing fax)

SOFTWARE INSTALLER (MSI)

Name	Description
Utils (folder)	Folder containing required utilities
Microsoft (folder)	Folder containing Device Stage packages (only required if installing full software)
[Model number][x86|x64].msi [Model number][x86|x64].cab [Model number][x86|x64]_*.mst	Software installer MSI, cab, and language transforms (x86 for 32-bit versions of Windows; and x64 for x64 versions of Windows)
Full_[x86|x64].cab	Software install cab file for full solution (only required if installing full software) (x86 for 32-bit versions of Windows; and x64 for x64 versions of Windows)
ErrorReporter.exe HPCommunication.dll HPCommunication.X.manifest HPeDiag.dll HPeDiag.X.manifest HPeSupport.dll HPeSupport.X.manifest HPScripting.dll HPScripting.X.manifest InstallMetrics.dll InstallMetrics.X.manifest InternetUtil.dll InternetUtil.X.manifest RulesEngine.dll RulesEngine.X.manifest	Required utility files

OPTIONAL FILES

Name	Description
Toolbar (folder)	Folder containing the Microsoft Live Toolbar installer
Required\lp[Model Number]*	Installer for Product Help
Optional\[Model Number]U[x86|x64]*	"Product Improvement Study"‖ MSI, cab, and language transforms (x86 is 32-bit version, x64 is 64-bit version)
Optional\HP Update*	HP Update MSI, cab, and language transforms
Optional\Data1.cab
Optional\IrisOCR*	Optical character recognition software (for scanning text)
Optional\Marketsplash_setup.msi	Marketsplash installer
Readme.chm	Readme documentation
Setup.exe	Installer (not required when installing the MSI without UI)
HP-DQEX5.exe	Installer (not required when installing the MSI without UI)

Install the software and drivers on client computers

Create a zipped script and the files to deploy to client computers. Enter the script into a command prompt.

Script example 1: msiexec.exe /i A910nx86.msi /qn /l*v C:\A910_Install.log ENTERPRISE=YES FAX=NO SCANTOPC=NO REBOOT=ReallySuppress

• Suppress the UI and all prompts (/qn)

• Create an install log file at C:\A910_Install.log

• Install a minimum set of software and drivers (ENTERPRISE=YES)

• Does not create fax printers (FAX=NO)

• Hide the Scan-to-PC option

• Suppress all reboot requests (REBOOT=ReallySuppress)

Script example 2: msiexec.exe /i A910nx86.msi /qn TRANSFORMS=A910nx86_2052.mst ENTERPRISE=YES CONNECT_NEW_PRINTER_SHORTCUT=NO UNINSTALL_SHORTCUT=NO

• Suppress the UI and all prompts (/qn)

• Install a Simplified Chinese version of the printer software (TRANSFORMS=A910nx86_2052.mst)

• Install a minimum set of software and drivers (ENTERPRISE=YES)

• Does not create a Connect New Printer shortcut in the Start menu

• Does not create an uninstall shortcut in the Start menu

• Suppress all reboot requests (REBOOT=ReallySuppress)

Installing on Windows Servers

Make sure that the following are enabled for Windows Server 2003 and 2008.

• On Windows Server 2003, the Windows Image Acquisition (WIA) service is installed but is disabled by default. For scanning to work, enable the WIA service.

• On Windows Server 2003 R2, the Windows Image Acquisition (WIA) service is installed but is disabled by default. For scanning to work, enable the WIA service.

• On Windows Server 2008, the Windows Image Acquisition (WIA) service is not installed by default. For scanning to work you must install the Desktop Experience Feature. The WIA service will then be enabled by default.

• On Windows Server 2008 R2, the Desktop Experience feature must be installed before plug and playing a USB.

Log files for DeviceSetup.exe

• DeviceSetup.exe is the application that sets up and maintains the information about installed printers.

• DeviceSetup.exe can run from a command line or be scripted.

• Each execution of DeviceSetup.exe generates a new log file. These logs pertain to everything DeviceSetup does, so they can be useful for troubleshooting.

• For Windows Vista and Windows 7, the log file is located at:

  C:\Users\[NTUserAccount]\AppData\Local\HP\AtInstall\[execution#]\DeviceSetup.log

• For Windows XP, the log file is located at:

  C:\Documents and Settings\[NTUserAccount]\Local Settings\Application Data\HP\AtInstall\[execution#]\DeviceSetup.log

Connect client computers to the printer

Set up a USB or network connection to the printer, and review potential issues with a network install.

Connecting a USB printer is relatively straightforward. After the driver is installed, connect the printer to a USB port, and then turn on the printer to start Plug and Play.

For network connections, use the following steps.

1. Make sure that the software package (MSI) has been installed on the client computer.

2. Make sure that the printer is already on the network and has a valid IP address. For a Wi-Fi connection, use the Wireless Setup Wizard on the front panel. For a wired network connection, use the Embedded Web Server (EWS) with an Ethernet cable connected to the printer.

3. Note the IP address or hostname of the printer.

4. Using an administrator account, run the following command on the target computer to start the install process: START /WAIT /D―C:\Program Files\HP\[Product Name]\Bin‖ DeviceSetup.exe /networkaddress [ip address or hostname]

   NOTE:

   On Windows Vista and Windows 7 computers, run this command from an elevated process when UAC is enabled.

   The setup process begins using the IP address or hostname to find and install the printer. The entire process is done silently without displaying any UI. If the install is successful, it returns a value of 0. Otherwise, a non-zero error code returns.

Potential issues during network installation

• The hostname might not be resolving to a valid IP address. If you are using the printer hostname to install, make sure that a name resolution service (for example, DNS, WINS) that can resolve the hostname to a valid IP address is running on the network.

• Make sure the IP address or hostname is correct in the command line.

• Turn on the printer and make sure it is in a ready state during the install.

• Check the connection to the network. If the printer is connected with an Ethernet cable, check the cable and its connection. If the printer is connected to Wi-Fi, make sure that the printer is still connected to the network.

• DeviceSetup.exe may fail on Windows Vista and Windows 7 due to UAC. Make sure to run DeviceSetup.exe in elevated mode when UAC is enabled.

Firewall issues and requirements

A firewall installed on the target computer can block the installer from communicating with the network printer.

Make sure the firewall allows the installer process (DeviceSetup.exe) to establish a TCP connection to the network printer.

If the firewall is interfering with printer communication, add rules to any firewall software to allow the following applications to communicate with printers on the local subnet:

{Program Files}\HP\{Model Name}\bin\HPNetworkCommunicator.exe

Most of the data transfer between the computer and the printer is done over HTTP (typically port 80 or port 8080). Printing also uses a TCP connection on ports 3910 and 9100. In most cases, the firewall allows this type of traffic without any problems. If your firewall software does not allow this type of traffic, create a rule for the HP software to communicate with the printer.

HP uses Web Services Discovery to find and establish communication with HP printers. Other parts of the HP solution communicate with the printer via HTTPS (usually port 443 or 8443). In most cases, firewalls allow this type of traffic. The applications not affected if this traffic is blocked are:

• {Program Files}\HP\{Model Name}\bin\DigitalFaxWizard.exe (if using print to fax)

• {Program Files}\HP\{Model Name}\bin\ScanToFolderWizard.exe

• {Program Files}\HP\{Model Name}\bin\ScanToEmailWizard.exe

Multicast discovery

The normal behavior for HP printer software is that it discovers (and rediscovers) printers on the network using Web Services Discovery, which sends multicast UDP packets. In the enterprise release, the software uses only unicast UDP or TCP packets to try to relocate the printer after installation. This enables the software to function properly on a network where multicast is disabled. This also results in the software being unable to find and use the printer if the IP address changes and the printer hostname do not resolve the IP address. Multicast rediscovery can be re-enabled in the software by changing the config.ini file that installs to C:\Program Files\HP\[Model Name]\config.ini. This file contains a section similar to the following:

[Discovery] Multicast=false

Changing the multicast value to "true" enables the software to relocate the printer whenever the IP address changes by using multicast discovery. However, the software no longer functions on a network when multicast is disabled or if a firewall is blocking outgoing multicast packets or incoming responses.

At installation, this value can be changed by setting the MULTICAST property to YES (the default is NO).

Off-subnet printers

The process to install a network printer is the same for a printer on a different subnet than the computer it is being installed on. Follow those instructions to install such a printer. When on a different subnet, the client computer cannot rediscover the printer if the IP address or hostname of the printer changes.

Update the software to use a new IP address

The network printer IP address or host name can change after the printer is installed on the computer. In the case of an off-subnet printer, the software cannot always detect the new IP address or host name.

1. Click Start, and then click All Programs > HP.

2. Click the HP printer name, and then click Update IP Address.

   If multiple instances of the printer are installed, click the printer you want to update. Another dialog box opens.

3. Type the IP address in the field to enable the Search button, and then click the Search button to make sure the IP address is correct.

4. Click Save.

   NOTE:

   Searching does not update the IP address. Click Save to update the IP address.

Command line tool to update the installed printer IP address

Instead of launching the Start menu shortcut and using the UI to update the installed printer IP address, run DeviceSetup.exe from a command line or script.

Using an administrator account, run the following command on the target computer to change the IP address of a network installed printer: START /WAIT /D C:\Program Files\HP\[Product Name]\Bin DeviceSetup.exe /serialnumber [printer serial number] /changeip [new ip address]

NOTE:

On Windows Vista and Windows 7 computers, run this command from an elevated process when UAC is enabled.

This starts a process that uses the specified IP address or hostname to find and install the network printer. The process is done silently without displaying any UI. If the install is successful, a value of 0 returns. Otherwise, it returns a non-zero error code.

Command line tool to update the installed printer hostname

Use an administrator account to change the hostname of a network installed printer.

Run the following command on the target computer: START /WAIT /D C:\Program Files\HP\[Product Name]\Bin DeviceSetup.exe /serialnumber [printer serial number] /changehostname [new hostname].

NOTE:

On Windows Vista and Windows 7 computers, run this command from an elevated process when UAC is enabled.

This starts a process that attempts to find the printer with the given serial number, and then change it to use the new hostname. The process is done silently without displaying any UI. If the install is successful, a value of 0 returns. Otherwise, it returns a non-zero error code.

Potential issues that can cause a failed update

• DeviceSetup.exe could be failing on Windows Vista or Windows 7 due to UAC. Make sure that you run DeviceSetup.exe in elevated mode when UAC is enabled.

• You might have entered an incorrect serial number. Make sure to specify the correct serial number for the network printer in the command line.

Technical details

Review additional technical details for printer setups with Windows Server.

Web Services Discovery (WSD)

HPNetworkCommunicator.exe uses Web Services Discovery (WSD) to communicate with HP printers during and after installation. When searching for a printer, HP sends either multicast or unicast UDP packets. After the printer receives the probe, it responds to the software in a Microsoft Windows ephemeral port range 49152-65535 with pertinent information.

Search protocols (UDP/TCP)

When searching for a list of printers, WSD initiates a multicast (UDP) probe to IP 239.255.255.250 at port 3702. After the printer is installed and before every printer operation (for example, print, scan, or fax), HP checks if communication can be established. HP calls this action 'rediscovery' To perform rediscovery, WSD sends a multicast UDP packet to resolve the IP address of the printer. When searching for a printer using the IP address, WSD creates a TCP socket over port 80. This is usually done under specific circumstances.

Windows XP users

Windows XP does not support the standard WSD protocol. HP developed an internal solution that operates almost identically to how it is implemented for Windows Vista and Windows 7. The main difference is during a search for a printer by IP address. An IP address-initiated search sends out unicast UDP probes.

Installing by providing an IP address

If you are installing the software via the command line and provide an IP address to the command line, HP uses the IP address to find your printer. However, for rediscovery purposes, HP attempts a unicast UDP probe or a TCP connection (to port 80).

Your firewall software might block this type of activity. If so, create a rule for HPNetworkCommunicator.exe to establish communication. When installing with the graphical user interface and the printer is not discovered through the multicast probe method, you can install with the printer IP address. If you get the IP option, either your firewall is blocking the traffic or your network does not support multicasting. From the software perspective, it is the same. If it is a firewall issue and the printer is on the same subnet as the computer, HP recommends creating rules in the firewall software to allow for multicast probes from HPNetworkCommunicator.exe.

Compatibility with the full software solution

The software solution for enterprises is simply a configuration of the full software, where the installer behaves as if the enterprise software is the same as the normal software solution. If either version is already installed, the software acts as though it is already installed.

SOFTWARE SCENARIOS AND ACTIONS

Scenario	Actions Taken	Outcome
Installing Enterprise First	Install Enterprise v2.0 Run software CD v2.0 or earlier (v1.0)	The software CD tells the user that the software is already installed. Any other MSI packages that are not yet installed (Help, Customer Experience Program, MS Toolbar) are offered to the user.
Upgrading to Full Solution	Install Enterprise v2.0 Run software CD v3.0	The software CD enables the user to upgrade the solution and installs the full software solution.
Installing Full Solution First	Install full software from CD v2.0 Run Enterprise install v2.0 (assume simply running msiexec /i [MSI])	The Enterprise install is successful and does not change what was installed (the full solution remains installed).
Attempting to Install Older Enterprise Release	Install full software from CD v2.0 Run enterprise install v1.0 (assume simply running msiexec /i [MSI])	The Enterprise install fails because a newer version is already installed.
Upgrading to Enterprise Solution	Install full software from CD v2.0 Run Enterprise install v3.0 (assume simply running msiexec /i [MSI])	The Enterprise install successfully upgrades the software, removes the full solution, and then installs only what is configured for the enterprise.

Create a smaller install image

Describes how to remove files from the release image and create a batch file in your development system to do the customization.

The easiest way is to copy the script, paste it into a file, and then name the file custom.bat. Open a command prompt to the folder containing the release image, and then run the batch file from that directory. The batch file asks several questions, and then deletes any unnecessary files.

@echo off

echo Creating Enterprise Release

echo This will delete files in the current directory to create the release.

echo Press Ctrl+C now if this is not what you want to do

pause

SET /P FAX="Include FAX? [Y|N] "

SET /P PLATFORM="32 bit, 64 bit, or Both? [32|64|Both] "

SET /P LANGUAGE="Specify Language ID or All? [{LanguageID}|All] "

rmdir /Q /S Optional

rmdir /Q /S HP

rmdir /Q /S Microsoft

rmdir /Q /S Toolbar

rmdir /Q /S Required

rmdir /Q /S licensing

del /F /Q Full_*.cab

del /F Setup.exe

del /F HP-DQEX5.exe

del /F autorun.inf

del /F ReadMe.chm if "%FAX%"=="N" (

pushd Drivers

rmdir /Q /S Fax

popd

del /F /Q HP*_fax.inf

del /F /Q HP*_fax*.cat

) ELSE (

REM The nullfax driver might be inside of the MSI in K3.5/K4, but we'll try to remove it anyway

del /F /Q HP*_nullfax*.inf

del /F /Q HP*_nullfax*.cat

)

if "%PLATFORM%"=="32" (

del /F /Q *x64.msi

del /F /Q *x64.cab

del /F /Q *x64_*.mst

)

if "%PLATFORM%"=="64" (

del /F /Q *x86.msi

del /F /Q *x86.cab

del /F /Q *x86_*.mst

)

if "%LANGUAGE%"=="All" GOTO :SKIP_LANGUAGES

FOR %%F in (*%LANGUAGE%*.mst) DO ren "%%F" "%%~nF._mst"

del /F /Q *.mst

FOR %%F in (*._mst) DO ren "%%F" "%%~nF.mst"

:SKIP_LANGUAGES

echo All Done!

https://support.hp.com/