Anyone else working with HP SoftPaq-based driver files?
-
Friday, February 26, 2010 6:52 AMIf anyone else here is dealing with HP computers you know what I mean. They offer their drivers in the form of these little .EXE-based files called SoftPaqs. They tend to be named something like ""SPxxxxx.exe". I have been setting these up in the MDT as APPLICATIONS and I'm running a set of silent install commands on each one to get them installed. If anyone wants to know here's the supported command syntax:
- "SPxxxxx.exe is the SoftPaq to unpack
- "-pdf" is a runtime switch that overrides the build parameters
- "-f" is a runtime switch that overrides the default path set at build time
- "-s" instructs the package to unpack in silent mode, skipping the Welcome, License, and Directory screens
- "-e" instructs the package to extract only, that is, do not run the component installation program.
- -s -a -silent -reboot (Good for silent installs.)
My question is this:
Is anyone else doing this differently (specifically for HP SoftPaqs)?
I've read a few other posts and I've noticed that many people tend to go for a process that involves extracting drivers from vendors and getting them integrated into Out-Of-Box drivers. I'm just wondering if my method is the best. mainly because I need to associate a specific set of these drivers with specific task sequences and that is probing difficult when they are set up as Applications. Any thoughts/advice?
All Replies
-
Friday, February 26, 2010 12:57 PMyou may want to look into the HP System Software Manager (SSM). It is an application that has a local database to keep track which SPs apply to which models. It can be run as an "application" from the task sequence. I use it in conjunction with extracting the drivers from the SP exe and importing them into the workbench. Some "drivers" like QuickLaunch need to be installed, so I let SSM decide if that model needs the software.
-
Friday, February 26, 2010 2:00 PMI use a freeware product called Uniextract to open the EXE and get the necessary driver files. Works quite well most of the time.
http://legroom.net/software/uniextract -
Friday, February 26, 2010 2:53 PM The HP SSM utility is a great tool and can be easily integrated to work with MDT 2010.
1. Download and install the SSM Softpaq from www.hp.com/go/ssm
2. Create a folder structure on your deployment server that will be used as a file store for the SSM Source files.
3. Run the SSM Softpaq to extract the SSM Program and support files.
4. Copy the SSM.exe and SSM.cab to the root directory of the PC model (e.g. HP Elitebook 8530w)
5. Open a CMD promt as an administrator
6. Map a drive to the location of the PC model
7. Run the follow command: ssm.exe /am_bld_db
This will create a .mdb file and a .xml file
You can then take these files and create a script to copy them to C:\SSM and then another command to run the SSM.exe to install the apps.
It looks something like this: C:\\SSM\SSM.exe /install /a C:\SSM
Rich
http://deploywindows7.wordpress.com/- Proposed As Answer by Rich Coulter Friday, February 26, 2010 8:53 PM
- Marked As Answer by Tim MintnerModerator Tuesday, March 02, 2010 5:48 PM
-
Friday, February 26, 2010 5:36 PMThanks for all the responses guys! This SSM program sounds like the answer to all my issues. I'll give it a go!
-
Friday, February 26, 2010 8:53 PMLet me know if you have any issues. I'm actually working on blogging about this in the very near future with an MCS friend of mine.
Rich
http://deploywindows7.wordpress.com/ -
Friday, February 26, 2010 11:13 PM
Let me know if you have any issues. I'm actually working on blogging about this in the very near future with an MCS friend of mine.
Will do Rich! I just got it downloaded and came back to copy and paste your instructions into a TXT file. I'll let you know how I come out.
Rich
http://deploywindows7.wordpress.com/- Proposed As Answer by KristofferJones Tuesday, March 02, 2010 5:00 AM
-
Tuesday, March 02, 2010 5:02 AM
Zeus
I don’t know how you getting on with HP softpac stuff but when I visited this last year under SCCM it was a nightmare to script the HP quick launch in particular the wireless lan / wan “intelligent switching”
So with my introduction into MDT2010 Lite touch I have set out a find a way to pause the deploy and capture TS before the actual capture for some manual tweeking…. Yes yes yes I know I should script it but I am actually working on something far further down the line and have not the time at the moment to master all the lovely tools to automate this properly. It was not as easy as I thought it would be until I was pointed to LTIsuspend.wsf. Bang that into bing and hey prestoNow I’m off to build my lappy refrence machine – manually config the hp quicklaunch and capture the results. Never to darken the doors of the MDT forum again – Yeah right……………
You may wanna take a look at LTIsuspend.wsf.
Oh BTW I sneezed when and clicked propose instead of reply - sorry -
Tuesday, March 02, 2010 3:19 PMCombine SSM with the HP Softpaq Download Manager (http://h20331.www2.hp.com/Hpsub/cache/509658-0-0-225-121.html) and it can download the softpaqs directly to your SSM store. It all works pretty well together.
-
Friday, March 05, 2010 5:09 PM
Combine SSM with the HP Softpaq Download Manager (http://h20331.www2.hp.com/Hpsub/cache/509658-0-0-225-121.html ) and it can download the softpaqs directly to your SSM store. It all works pretty well together.
Thanks I'll look into that as well. -
Thursday, March 25, 2010 2:53 PMI've used SSM today and I managed to update 13 computers within more or less 90 min (bios, drivers, and two softwares)!!! it works greate! Now i'm going to use this with HP Softpaq Download Manager. I'm thinking about bios configuration too.
-
Saturday, March 27, 2010 1:27 AM
I've used SSM today and I managed to update 13 computers within more or less 90 min (bios, drivers, and two softwares)!!! it works greate! Now i'm going to use this with HP Softpaq Download Manager. I'm thinking about bios configuration too.
Care to share your process Tomek? -
Thursday, April 15, 2010 9:06 AM
1. download ssm :-)
2. create a folder to be sheared
3. copy ssm.exe and ssm.cab to the folder
4. create subfolder for softpaqs
5. download all softpaq you want to install and put them into this subfolder
6. start this copied ssm.exe to create and configure database files
a. if you want to update bios too you must set the password too (ie: 12345)
7. make sure sharing works well (in my case I were to configure sharing manually)
8. I created a .bat file and I put this into the sheared folder too. The file was:
\\ServerName\ShearedFolder\ssm.exe \\ServerName\ShearedFolder /A /CSPWD:”12345” /RB
/A – means accept
/CSPWD – password; this pass is set then up to the bios too! It must be the same with bios pass
/RB –restart after update9. Run .bat file from the computer you want to update (ie. Run it on 15 computers simultaneously)
And Voila :-) after that I was eating my second breakfast ;-).
Unfortunately i didn’t manage to make it work with HP sofpaq manager. I think this is because of different .xml files, but I’m not sure yet.
-
Thursday, June 17, 2010 7:47 PMExcellent. I got this to work in our TS. Thanks Tomek.S
-
Friday, June 18, 2010 7:04 AM
We get these as we have HP laptops.
I would suggest you extract them (usually they are self extracting) and apply the drivers into the standard driver pool using MDT.
However some of them do actually require the EXE to be executed. I don't quite know how to do this and I am very interested to see how to do it.
-
Friday, September 10, 2010 2:58 AM
Just as a final follow-up post to this thread:
I did try this and several other methods to manage the HP SoftPaq Drivers. Ultimately I opted to just work through *all* the SoftPaq files for each model we support and extract them using the /e switch. Once extracted I imported them into Out-of-Box drivers. The few I could not import I added as Applications with the appropriate unattended install commands. It was very tedious and time consuming but so far that method has been a tremendous success. its also very easy to mainitan and add new models. I guess the moral is to just suck it up, take the time and do it right the first time.
-
Friday, September 10, 2010 3:17 AM
We have been managing hundreds of HP laptops for years with MDT (BDD), and really have no issues... We use the SSM tool to update the bios, but just use the MDT driver store for everything else. There are a couple of things that require installers, but we use fat images in our environment, so its not a big deal - we have all our equipment on lease cycles - so everything is identical.
I will have to look at the possibility of using the ssm tool for everything though - sounds interesting...
-Dan
-
Friday, September 10, 2010 5:15 AM
You should be able to use 7-zip to open those EXE's and extract the drivers manually an skip the hoky installer.
Then use either the OOB driver function or a application that runs setup.exe. That's the way I do it, prefering the OOB drivers function
-
Monday, September 13, 2010 2:32 AM
Anything that is MSI based should install silently with /qn
As far as I can tell once you have extracted most of these Softpaqs you will get an MSI based installation.
Installshield is -s (may be case sensitive). WinDVD and Quick Launch Buttons installers are InstallShield based.
Lightscribe is a little tricker but if you start the LSSetup.exe installation then go to your Temp folder you can copy the extracted files from there. A command line like this (in a batch file) is supposed to automatically install the Lightscribe package. However my usual experience is that some kind of error code seems to be returned, maybe I need to check the last line:
@echo off
cd \
msiexec.exe /I \SWSETUP\LSHSI\LS_HSI.msi /qn UPDATE_SHELL_COMMAND="http://www.hp.com/go/techcenter/LightScribe/" SOURCELIST="%ProgramFiles%\HPQ\Lightscribe" SHOW_DESKTOP_ICON="0" LS_LAUNCHER_COMMAND="%ProgramFiles%\HPQ\LightScribe\PSG Getting Started.mht"
mkdir "%Programfiles%\HPQ\Lightscribe"
copy "\SWSETUP\LSHSI\US\PSG Getting Started.mht" "%ProgramFiles%\HPQ\LightScribe\"Roxio DVD Creator or variants thereof can be silently installed with something like the following:
Setup.exe /qn REBOOT=ReallySuppress /L*v C:\system.sav\logs\Roxio\Creator\SONIC_ROXIO_MSI_{ProductID}.log
-
Thursday, August 11, 2011 10:21 PM
Hi,
With Regards to SSM, I understood till the 7th Step. Could you please brief me on from the 8th step. I dont know on how to create .bat file. And when you say we need to run the .bat file, is that we need to run on all the client units? The reason why I m asking this is because I thought this software can be installed on one Server unit and it can run the update to all client units from here. Please help
-
Friday, August 12, 2011 7:30 AM
I also use ssm. At first I did have some issues with them. Mainly related to nvidia drivers.
1. Driver will not install since the ssm database is missing my new product number
2. Nvidia driver install reboot the machine, makeing ssm not complete.
3. Sometimes the found new hardware wizard was shown, causing the driver install not to continue.
For issue 1 I did edit nvidia .cva file and changed SysID5 to match my z400 workstation (0x0B4Ch)
For issue 2; I made a script that will add a runonce value run ssm at next windows start. When ssm is done the runonce value is removed. SSM detects if nvidia was installed and will not do that again if the machine reboots.
For issue 3; I made me a wizkilla.vbs that terminate the found new hardware wizard.
Install.cmd
@echo off pushd "%~dp0" start "" wscript wizkilla.vbs regedit /s .\add_runOnce.reg start "" /wait ".\SSM.EXE" . /install /DEBUG ping -n 30 localhost 1>nul regedit /s .\remove_runOnce.reg ping -n 30 localhost 1>nul
wizkilla.vbs
On Error Resume Next strComputer = "." Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2") Const maxloop = 1200 initloop = 1 Do While True If initloop > maxloop Then Exit Do Else initloop = initloop + 1 End If Set colItems = objWMIService.ExecQuery("Select * from Win32_Process Where Name = 'rundll32.exe'",,48) For Each objItem in colItems If InStr(1,objItem.CommandLine,"newdev.dll",vbTextCompare) Then 'tested for XP sp2 and win 7 objItem.Terminate() 'Bye bye "Found new Hardware wizard" End If Next WScript.Sleep 200 Loopadd_runOnce.reg
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\ssm0] "0"="C:\\Drivers\\Install.cmd"
Remove_runonce.reg
Windows Registry Editor Version 5.00 [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\ssm0]
Rebuild_SSM_DB.cmd
pushd "%~dp0" start "" /wait ".\SSM.EXE" /AM_BLD_DB /DEBUG pause
You can use Rebuild_SSM_DB.cmd when you have downloaded new SSM Compliant softpacks from HP.com
SSM.exe needs a ssm.bin file. You create this bin file by running ssm.exe without any command line switches.
-
Friday, March 16, 2012 7:17 PM
I'd just like to elaborate on what one of the posters above was stating for you guys. SSM is an excellent utility combined with SCCM and SOFTPAQ DOWNLOAD MANAGER. If you are downloading all these softpaqs for different models you are wasting your time. Get the sofpaq manager. Pick your machine models , OS and languages in the manager. Point it do download to your SSM share. Presto. It will pull down all the software for your machine and if it is the same sofpaq for multiple models it will only pull it once.
Deploy ssm and the cab file as a package and run "ssm \\[UNC path to SSM share]. SSM will sort through the downloaded softpaqs and install whatever is needed. Mltiple runs will be needed. If you leverage this with a generalized Win7 image and OSD you can build one task sequece and advertisement to deploy OS's to any piece of HP equipment you own. Much better than Dells way of doing it (driver packs for SCCM).
Sorry for the quick crude directions, but you can figure out the rest.
- Edited by Leon79 Friday, March 16, 2012 7:24 PM
-
Tuesday, April 03, 2012 1:41 PM
Hi
I get an error when I run ssm from the command line in Windows 7 that "The program is to big to fit in memory"
Any ideas?
-
Tuesday, April 03, 2012 9:36 PMWhat is your scratch space set to for PE?
-
Friday, November 30, 2012 6:03 PM
I'd just like to elaborate on what one of the posters above was stating for you guys. SSM is an excellent utility combined with SCCM and SOFTPAQ DOWNLOAD MANAGER. If you are downloading all these softpaqs for different models you are wasting your time. Get the sofpaq manager. Pick your machine models , OS and languages in the manager. Point it do download to your SSM share. Presto. It will pull down all the software for your machine and if it is the same sofpaq for multiple models it will only pull it once.
Deploy ssm and the cab file as a package and run "ssm \\[UNC path to SSM share]. SSM will sort through the downloaded softpaqs and install whatever is needed. Mltiple runs will be needed. If you leverage this with a generalized Win7 image and OSD you can build one task sequece and advertisement to deploy OS's to any piece of HP equipment you own. Much better than Dells way of doing it (driver packs for SCCM).
Sorry for the quick crude directions, but you can figure out the rest.
I have about a dozen HP laptops and desktops. I currently deploy using MDT 2012 and WDS. Each model has a task sequence which I choose when pxe booting, followed by a name. I am interested in simplifying the deployment process. I agree that downloading all softpaqs to a single directory and letting ssm figure out the best way to install is the way to go. I have a couple questions.
1. Do you just run the .bat file as an application for all models?
2. What options do you choose when extracting and configuring ssm? I have trouble with updates rebooting the system, regardless if clear the 'force reboot' checkbox.
3. At what point to you install this as an application? During the normal 'Install Applications' task in the sequence?
4. Do you only add network and storage drivers to the deployment share itself and let ssm install the rest?Thanks in advance!
-
Friday, November 30, 2012 6:11 PMI have a short guide abou the HP drivers, e-mail me, firstlast @ h0tm@il
-
Wednesday, January 16, 2013 9:56 AM
Hello,
I am using MDT 2012 Update 1 and SSM.
@ my situation, SSM is working OK with Windows 7, but NOT windows 8.
Do I need to customize something or is the combination MDT 2012/SSM/Windows 8 not working?
Anybody who have a working situation with Windows 8 (enterprise or pro?)
Thx
-
Wednesday, January 16, 2013 1:14 PM
Update:
Procedure is now working well for my HP 8200-desktop and HP 6560B with Windows7.
I also tried both systems and packages for Windows 8, but no packages are
installed during installation.I took the the softpaqs under "windows8 32bit" and "windows8 64bit", and
tried this for windows 8 PRO and Enterprise without result.When i check the log, the sections "possible updates" and " "updated
performaned" are empty (with windows 8)Anybody with the same problem or a solution for this issue?
Thx
-
Thursday, January 17, 2013 7:48 AMAnybody with an option for this issue with windows 8?
-
Wednesday, January 23, 2013 4:51 PMFor HP's newer systems (released in the last year or two) they now have driver packs available for the OS as well as WinPE. These are the flat driver files (.INF) and not executables or MSIs. Has certainly made my life easier (Dell has been doing this for a while as well). Should be available on their driver download page.
-
Wednesday, January 23, 2013 5:29 PM
Hello Darth,
this are new files from HP that were today released? Last week i didn`t find any files on the website!
-
Thursday, January 24, 2013 10:12 PM
I had the same problem. But HP release a new Version of SSM. http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=ch&prodTypeId=12454&prodSeriesId=5232845&prodNameId=5232846&swEnvOID=4132&swLang=13&mode=2&taskId=135&swItem=vc-114554-1 now it works ;-)
-
Friday, January 25, 2013 7:36 AM
thx for the link. i will test this!
Release notes:
Version 2.51.7.1
- Add support for softpaq dependencies by repeating install
loop up to 3 times.
Can be overridden by using /NOREPEAT argument on
commandline.
- Added /CHECKSIGN command. Will allow only signed softpaq's
to be installed. Unsigned softpaqs will be skipped.
SSM default behavior does
not require softpaqs to be signed.
Version 2.50.8.1 August 09, 2012
-
Initial Windows 8 support
- Included additional methods of reading device
list to include some devices missing in Win8.
- Fixed method which reads
client information on XP SP3 to return valid data.
- Updated SSM User Guide
to indicate removal of REPSET support in SSM.
- Fixed support for Windows 8.
- Disabled native BIOS flash support in SSM. BIOS updates require HPQFlash
utility to update successfully.
- Added support for Windows 8.
- Fixed
memory access issues while reading client information.
- Added support for
generic OS tags in DetailFileInformation and Operating Systems section of CVA.
- Released BIOS Configuration Utility as a separate softpaq. Disabled REPSET
functionality in SSM.
- Added support for Windows MultiPoint Server.
-
Added support for debug tracing in admin mode which provides additional
information useful in debugging SoftPaq or CVA problems.
- BIOS config
utility has been separated from SSM and is now a separate executable. -
Monday, January 28, 2013 10:47 AM
Hello,
i can confirm SSM is working well now!
I have only issue.
After the installation of a video-card driver my system is rebooting in the MDT-process, so the MDT-process isn`t finished.
I have used the following SSM-settings:
How can i prevent the system from rebooting after installing some drivers/softpaqs?
Thx
-
Monday, February 18, 2013 10:52 AMI wondering the same thing, Anybody know how? /NOREBOOT?
-
Friday, February 22, 2013 10:42 AM
I use the command
ssm.exe /install /NOREBOOT /force
to prevent a reboot and works perfect.
-
Friday, February 22, 2013 2:27 PMYes that is working correct!
-
Thursday, April 04, 2013 8:03 PM
Hi,
I try to Update the BIOS with SSM.
*I put HP BIOS update in an sub folder
* I build the DB
* I run cmd like SSM.exe /INSTALL /ACCEPT /CSPWD:password /NOREBOOT
But the SSM Administrative Wizard always popup, I cant trigger an silent BIOS update. What do i miss?
/SaiTech
-
Friday, April 05, 2013 12:01 PM
Interesting issue from SaiTech...
waiting for a solution...
.png)
