Jump to content

HP Officejet Pro 8600 Plus e-All-in-One Printer - N911g support

Installing the Printer Software on Windows Server 2003 or 2008

  • PrintPrint

Introduction

This document provides enterprise administrators information about customizing the installation of HP Officejet and Officejet Pro printers. It includes how to select a printer, what features and drivers are installed, and how to deploy the printer to target computers using a script to control the installation process. It also includes instructions for reducing the size of the deployed package, information about firewall requirements, and other technical details.
This document applies to the following editions of the Windows 2003 and 2008 Server:
  • Windows Server 2003 - 32 bit (SP1 or greater)
  • Windows Server 2003 R2 - 32 and 64 bit
  • Windows Server 2008 – 32 and 64 bit
  • Windows Server 2008 R2 - 64 bit
  • HP Officejet 6100 Printer Series (H611)
  • HP Officejet 6500A e-All-in-One Printer Series (E710)
  • HP Officejet 6600 e-All-in-One Printer Series (H711)
  • HP Officejet 6700 Premium e-All-in-One Printer Series (H711)
  • HP Officejet 6810 e-All-in-One Printer Series
  • HP Officejet 7110 Wide Format ePrinter series (H812)
  • HP Officejet 7500A Wide Format e-All-in-One Printer Series (E910)
  • HP Officejet 7610 Wide Format e-All-in-One Printer Series (H912)
  • HP Officejet Pro 6230 ePrinter series
  • HP Officejet Pro 6830 e-All-in-One Printer Series
  • HP Officejet Pro 8100 ePrinter Series (N811)
  • HP Officejet Pro 8500A e-All-in-One Printer Series (A910)
  • HP Officejet Pro 8600 e-All-in-One Printer Series (N911)
  • HP Officejet Pro 8610 e-All-in-One Printer Series

Before the installation

Before starting the installation, gather the following information:
  • Type of Windows operating system (Windows 2003 or Windows 2008)
  • Operating system version (32- or 64-bit)
  • Language of the operating system where the printer is installed (English or others)
  • Connection type of the installed printer (USB or network)
Follow these steps to customize the installation for the HP Officejet and Officejet Pro printers:
  1. Copy the driver and software files.
  2. Create a command to select features and customize the installation.
  3. Collect the files for distribution.
  4. Install the software and drivers on the client computers.
  5. Connect the client computers to the printer.

Step one: Copy the driver and software files

Copy the driver and software files using either of these methods:
Follow these steps to copy the files from the setup disk.
  1. Insert the setup disk that comes with the printer.
  2. Create a folder on your system and copy the files in the setup disk into the folder.
Follow these steps to copy the files from the web pack.
  1. Browse to the Get Software and Drivers page: Get Software and Drivers
  2. Check the instructions on the page, and then click the plus sign () next to the correct heading for additional instructions:
  3. Select the HP Officejet or Officejet Pro Full Feature Software and Driver.
  4. Review the download options and information, and then click Download.
    NOTE: Click the View directions link for step-by-step instructions on downloading and installing the software.
  5. Click Save, and then browse to the location on your computer where you want to save the file.
  6. Click Save. The software downloads to your computer.
  7. Extract the executable file through decompression programs 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, so that 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 with an x86 suffix and one with an x64 suffix. The MSI includes the printer’s model number in its name, for example A910nx86.msi and A910nx64.msi. Install the x86 MSI on 32-bit versions of Windows. Install the x64 MSI on x64 versions of Windows.

Step two: Create a command to select features and customize the installation

This section describes properties that can be set when installing the MSI that turn off certain features in the software. To see parameters that make it easier to configure the installation of the HP MSIs, see the Script examples .

Using Msiexec to install an MSI

Use your favorite tool to install the MSI onto the client computers. However, if you choose to use msiexec.exe, we have provided common command parameters that might be helpful. Installing an MSI can be done by passing the path to msiexec with the /i parameter:
msiexec.exe /i D:\A910nx86.msi (where D is the path to the msiexec file)
NOTE:Enable some required Windows services prior to installation. See Installing on Windows servers . To set the language of the installed software to something other than English, see Languages and language IDs . To turn off certain software features, see Feature selection .

Command properties

Property NameValuesDescriptionDefault Value
CONNECT_NEW_PRINTER_ SHORTCUTYES

NO
Selects whether to install the Start menu shortcut to add a new printer.YES
ENTERPRISEYES

NO
Selects whether to install the full software (NO) or the minimum software (YES) for enterprise applications.NO
FAXYES

NO
Selects whether to 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_SERIALNUMYES

NO
Selects whether Windows should ignore the serial number when installing the printer via plug and play.NO
MULTICASTYES

NO
Sets whether multicast discovery is used to rediscover installed printers. (See the Multicast discovery section).NO
REBOOTForce

Suppress

ReallySuppress
Sets the behavior for when Windows Installer requires a reboot to complete the install.(none)
SCANTOPC

Not applicable for:

  • Single Function Printers
  • Officejet 6500A
  • Officejet 6600/6700
  • Officejet 7500A
  • Officejet Pro 8500A
  • Officejet Pro 8600
YES

NO
If this property is YES, the option to activate the scan-to-computer software is hidden and users must initiate scans from their computers instead of from the printer. If the option is set to anything other than NO, the option to activate the scan-to-pc software is displayed. If the property is not set, the printer displays the option.YES
TRANSFORMSTransform file name, ex: A910nx86_1055.mstThis is the filename or path to the transform file that is to be applied.(none)
UNINSTALL_SHORTCUTYES

NO
Selects whether to display the shortcut on the Start menu to uninstall the software.YES
The following Microsoft website provides more thorough documentation of msiexec: http://technet.microsoft.com/en-us/library/cc759262(WS.10).aspx . Refer to the Microsoft documentation if you have additional questions. In the event that anything described in this section conflicts with the Microsoft documentation, assume that the Microsoft documentation is correct.

Languages and language IDs

Almost all of the installed files support MUI and therefore 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, and then include it 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
Refer to the following table for languages and language IDs.
LanguageLanguage ID
Arabic1025
Traditional Chinese1028
Czech1029
Danish1030
German1031
Greek1032
English1033
Spanish1034
Finnish1035
French1036
Hebrew1037
Hungarian1038
Italian1040
Japanese1041
Korean1042
Dutch1043
Norwegian1044
Polish1045
Portuguese1046
Russian1049
Swedish1053
Turkish1055
Simplified Chinese2052

Step three: Collect the files for distribution

The following tables contain 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 FilesDescription
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_*.gpdPrint driver file
HPMACRONAMES.gpdPrint driver file
Hpvpl04.infPrint driver file
Hpvpl04.iniPrint driver file
Hpvpl04.catPrint driver file
Hpvplargb.iccPrint driver file
Locale.gpdPrint driver file
Pl.bmpPrint driver file
STDNAMES.gpd Print driver file
Drivers\Scanner (folder) Folder containing scan driver files
HPScanMiniDrv_*.infScan driver file
HPScanMiniDrv_*.catScan driver file
Drivers\Fax (folder)Folder containing fax drivers (required if installing fax)
HP*_fax.infFax driver file (required if installing fax)
HP*_fax*.catFax driver file (required if installing fax)
HP*_nullfax.infReplacement driver for Fax (required if NOT installing fax)
HP*_nullfax*.catReplacement driver for Fax (required if NOT installing fax)

Software installer (MSI)

NameDescription
Utils (folder)Folder containing required utilities
HP (folder)Folder containing Solution Center packages (required if installing full software and/or installing on Windows XP or Vista)
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].cabSoftware 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

NameDescription
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.msiMarketsplash installer
Readme.chmReadme documentation
Setup.exeInstaller (not required when installing the MSI without UI)
HP-DQEX5.exeInstaller (not required when installing the MSI without UI)

Step four: 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
This script will:
  • 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
This script will:
  • 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 Connect New Printer shortcut in 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

Step five: Connect client computers to the printer

Click your connection type for more information.
Connecting a printer to a USB port 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.
  1. Make sure that the software package (MSI) has been installed on the client computer.
  2. Make sure that the printer you want to install is already on the network and has a valid IP address. For WiFi printers, use the Wireless Wizard on the front panel; or use the Embedded Web Server (EWS) with an Ethernet cable plugged into the printer.
  3. Write down the IP address or hostname of the network printer that you want to install.
  4. Using an administrator account, run the following command on the target computer to start the network 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.
    This starts a process that uses the specified IP address or hostname to find and install the network printer. The entire process is done silently without displaying any UI. If the install is successful, it returns a value of 0. Otherwise, it returns a non-zero error code.
Potential issues during network installation
The following is a list of potential issues that might cause the network installation to fail:
  • A firewall blocks the installer from communicating with the network printer. If the target computer is running a firewall, make sure that the firewall allows the installer process (DeviceSetup.exe) to establish a TCP connection to the network printer. See the Firewall Requirements section for processes that must be allowed access through a firewall.
  • 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 (e.g., DNS, WINS) that can resolve the hostname to a valid IP address is running on the network .
  • DeviceSetup.exe could be failing on Windows Vista and 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 IP address or hostname. Make sure that you specify the correct IP address or hostname in the command line.
  • The printer might be turned off, or is off the network. Make sure that the printer is plugged in and turned on. If the printer is connected to the network with an Ethernet cable, check the cable and its connection. If the printer is connected wirelessly, make sure that the printer is still connected to the network.
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 it has been installed. 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’s hostname does 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 described in the section to install a network printer is the same process used to install a printer on a different subnet than the computer on which it is being installed. Follow those instructions to install such a printer. However, since the printer is installed on a different subnet than the computer, the client computer cannot rediscover the printer if the IP address or hostname of the printer changes. The section below describes how to update the client computer if the IP or hostname of the printer is changed.
The IP address or host name of a network printer can change after the printer has been installed on the computer. In the case of an off-subnet printer, the software cannot always detect the printer's new IP address or host name.
Follow these steps to update the IP address or host name for an installed printer.
  1. Click Start (), click All Programs, click HP, 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 with a new IP address. Another dialog box opens.
  2. Type the IP address in the field to enable the Search button, and then click the Search button to make sure that the IP address is correct.
  3. The Save button is enabled after you enter an IP address. Click the Save button to save the IP address in the field.
    NOTE: Searching does not update the IP address. Click Save to actually update the IP address.
    The installed software uses the new IP address.
Instead of launching the shortcut from the Start menu and using the UI to update the IP address of an installed printer, 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 entire process is done silently without displaying any UI. If the install is successful, it returns a value of 0. Otherwise, it returns a non-zero error code.
Using an administrator account, run the following command on the target computer to change the host name of a network installed printer:
START /WAIT /D C:\Program Files\HP\[Product Name]\Bin DeviceSetup.exe /serialnumber [printer serial number] /changehostname [new hostname]
NOTE: In Microsoft Vista and Windows 7, run the command from an elevated process when UAC is enabled.
This starts a process that attempts to find the network installed printer with the given serial number, and then change it to use the new host name. The entire process is done silently without displaying any UI. If the operation is successful, it will return a value of 0. Otherwise, it will return a non-zero error code.

Potential issues

The following are potential issues that might cause the update to fail:
  • 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 that you specify the correct serial number for the network printer in the command line.
When installing a network printer, the HP software and drivers must communicate with the printer over the network. Firewall software might interfere with this communication. If so, 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
Read this section for additional technical details regarding the setup.

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 on a port in 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 to see if communication can be established. HP calls this action "rediscovery." To do the 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 the way it’s implemented for Windows Vista and Windows 7. The main difference is when you are searching for a printer by IP address. For an IP-address-initiated search under Windows XP, HP sends out unicast UDP probes.

Installing by providing an IP address

If you are installing the software via the command line and you 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. If you are installing via the graphical user interface and your printer cannot be discovered through the multicast probe method, you have the option to install the printer by providing the IP address. If you get the option of installing by IP, either your firewall is blocking the traffic, or your network does not support multicasting. From the software's perspective, it is the same. If it is a firewall issue, and your printer is on the same subnet as the computer, HP recommends creating rules in your firewall software to allow for multicast probes from HPNetworkCommunicator.exe. See Multicast Discovery for more information.

Compatibility with the full software solution

The software solution for enterprises is simply a configuration of the full software, so that the software installer behaves as if the enterprise software is the same as the normal software solution. If either software version is already installed, the software will act as though the software is already installed.
ScenarioActions Taken Outcome
Installing Enterprise First
  1. Install Enterprise v2.0
  2. 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
  1. Install Enterprise v2.0
  2. 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
  1. Install full software from CD v2.0
  2. 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
  1. Install full software from CD v2.0
  2. 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
  1. Install full software from CD v2.0
  2. 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.
This section describes how to remove files from the release image. 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 a few questions, and then deletes any files that are unnecessary.
@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!
©2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
HP Officejet Pro 8600 Plus e-All-in-One Printer - N911g

HP Support forums

Find solutions and collaborate with others on the HP Support Forum
HP.comHP on FacebookHP on TwitterHP on YouTubeHP on Linked InHP on FlickrHP on Google+