Managing HP drivers in SCCM and MDT.

Everybody that is working with deployment loves drivers and new computer models.
One good thing is that more and more PC manufacture is making it easier to handle drivers for their models.

To manage drivers for HP you can use HP SoftPaq Download Manager and HP System Software Manager.

* SoftPaqs = Applications and Drivers for HP Computers and Servers.

How does SDM and SSM work together?

  1. HP SDM connects to Internet to download the desired SoftPaqs for the computers.
  2. The SoftPaqs are saved in a shared folder on for example the server where you have your deployment share.
  3. SSM connects to the shared folder and checks for available SoftPaqs for the system that is being deployed and Installs the SoftPaqs.

 

HP SoftPaq Download Manager (SDM) – Lets you easy download drivers from HP.
http://www.hp.com/go/SDM

 

HP System Software Manager (SSM)– Installs the drivers on your computer during the Task Sequences.
http://www.hp.com/go/SSM

 

Configure SSM.

To run and setup SSM in admin mode, perform the following steps:

  1. Navigate to Hewlett-Packard\SSM in the Program Files directory (or Program Files (x86) if running 64-bit Windows), and then run SSM.exe
  2. When prompted for the location of the file share, navigate to the SDM download directory. Type the name you want to use for the file share, and then click Next.
  3. If you are presented with a message about SSM.CAB being missing, double-click on the specified text to copy the file to the file store, and then click Next until you reach client options.
  4. Select Reboot client upon completion of upgrades, and then click Next.
  5. Click Next until you reach the Build Database window.
  6. Select Check ftp.hp.com for CVA file updates first. This causes SSM to update the specification file for each SoftPaq, which may include bug fixes and expanded coverage.
  7. Click Build Database, and wait for the build process to finish.
  8. Click Finish to complete the process.
  9. Copy ssm.exe to the root of the SDM download directory. This allows easier execution of SSM from the network.

Configure SSM for use with a Task Sequences.

  1. Create a new application in MDT. Select Application without source files …..
  2. Enter HP SSM for application name.
  3. Enter the Command line \\server-name\share\ssm.exe . /install
  4. Press next a couple of times.
  5. Go to your Task Sequence and take properties.
  6. Add the application HP SSM

When HP SSM is executed it will check in the drivers folder for missing drivers and applications for the machine.

 

For more information you can read the following white papers from HP.

http://www.compit.se/download/deployment/system_software_mgr.pdf

http://www.compit.se/download/deployment/HP_drivers_MDT_SDM_SSM.pdf

This entry was posted in Deployment and tagged , , , , . Bookmark the permalink.

4 Responses to Managing HP drivers in SCCM and MDT.

  1. Smithman says:

    I am trying to get HP SSM working with MDT2012. When the tasksequence gets to the HP SSM install task, it starts installing de softpaqs, but somewhere in the middle, the system reboots. When the tasksequence tries to resume the installation, I get the error that the installation is in an unespected state and asks if the installation should be resumed or restarted.

    My guess is that the HP SSM reboots the system wich confuses MDT. Is there a way to prevent the HP SMM from rebooting the system?

  2. Hans says:

    Hi,
    I too got the same result as Smithman.
    The solution was to remove the HideShell=YES.
    Apperantly the application install and HideShell aren’t very compatible.

  3. gold price says:

    The SoftPaq from HP consists of both drivers and an application all wrapped up in a single installer. My first attempt was to extract the drivers and then import them into the MDT database. This worked and the drivers installed during setup and I have no yellow bangs in device manager. However only some of the hotkeys worked. My next attempt was to keep the drivers loaded in the MDT database and I would run a silent install after Windows was installed to install the supporting application to control the keys. The installer is MSI based so I thought this would be easy. Make the application default in MDT based on these specific manufacturer and models and I would be golden. Clean, simple, and automated.

  4. Zay says:

    Has anyone tried this on an offline media, or will it only work for network share?

Leave a Reply

Your email address will not be published. Required fields are marked *