I have encountered 3 HP applications that will not install during OSD, but I can deploy them as a mandatory advertisement afterwards just fine- the same exact packages.THey are the Soundmax audio, 3D drive guard and synaptics touchpad software. How can I make these install as part of the OSD?Thanks

I have an NC6400 that requires the following packages because they can't be imported:DPS (has to be installed in XP mode)Fingerprint ScannerQuick Launch ButtonsStorage Controller (for media card reader)Synaptics TouchpadMy audio files imported just fine.I saved all the downloadable .exe files to an easy to navigate folder structure on the network. Then I ran the executable (there are some .exe files that require extracting from command line with a switch) by double-clicking, then changing the location to which they were extracted. Then imported everything SCCM could, and made typical software install packages for the rest (listed above). Then I just called the 'setup.exe /S /v/qn' in the commandfor the package. The quick launch buttons have a "known compatibility issue" dialogue box that comes up at first logonand the DPS has to be installed in XP mode (had to do some batch file and registry trickery for this one to work). But they all install fine as part of my OSD task sequence (the DPS errors out, so I install it last, but when the OS comes up everything works - haven't had a chance to delve into that one yet). HTH.At the end of my task sequence I added the steps under General>>Install Software and pointed to the package. It's a good idea to test these on a live OS and debug before adding these to an OSD.

Which application did you need the setup.exe /s /v /qn for? Does anyone have a website\blog\etc where people can post models, all of the drivers and list how to make each application\driver work properly with configmgr?? I still do not get how some of these can run just fine as a mandatory advertisement after the TS, but cannot run during it properly. It does not make sense to me. Thanks

Alternatively you can run them after the TS has finished, but still as a part of the deployment process. (guide Here ) Michael Petersen http://kongkuba1.spaces.live.com

What Mike has suggested is not a bad idea.When you are testing the HP driverapps out you can runmost of themfrom a command promptusing 'setup.exe/?' and that will show you what the available switches are for that exe. Also, appdeploy.com has some good info that you should also check out and may serve you well in the future.As far as the reasons why they aren't running properly in the deployment task sequence, well, you'll have to look atthe smsts.log file and run it down. The right-click tools for sccm open up some web reporting functionality that can help you find out where in the TS it failed as well as what program was running at the time. HTH.

It ended up just being the quicklaunch software for win 7 that fails if run during a TS. The others were not running because I had them in the same group as the quicklaunch so after the quicklaunch failed it was skipping the rest of the group in the TS. Also the soundmax works if you do "run command line" and type in setup.exe /s, but fails if you run the program as part of the software package. I ended up just making a collection based on model number, and adding the HP software as a mandatory advertisement to that collection. Definitely not ideal, but it does solve the problem. I am not comfortable with scripting enough to use the provided .vbs script, so this is a reasonable solution for my environment. -does anyone have a website where people can post what manufacturer\models they have, and list how to make every necessary driver\piece of software work automatically? Some things like realtek and ati software can take a few tries to make work, as some work from the .inf files, some require the installer be run, some the installer doesn't work silently, etc.

For HP Drivers look inside *.cva files [Silent Install] section.

hi i want to capture win 7 i made build and capture task sequence and disable build part. is this possible to boot client with pxe and then capture or i should adverties TS to client when they are runing full os not boot with pxe

It ended up just being the quicklaunch software for win 7 that fails if run during a TS. I got around this by using a batch file and a registry file to set it to run the .exe in XP mode. Had to copy off the package content, merge the registry entry to set the file attributes to XP mode, and then call the .exe and it ran fine. It took several tries to get it correct, but it was working. HTH.

HP Quicklaunch Buttons: Create a software-package (the files can be found in C:\swsetup) and use the following command in the installation-program: "setup.exe -s /f2c:\setup.log" More information can be found here: http://scug.be/blogs/sccm/archive/2010/01/28/sccm-osd-hp-quicklaunch-application-installation-integrated-in-a-task-sequence.aspx If you only want to install the drivers for the Quicklaunch Buttons without using the application, you can find them in "C:\Program Files\Hewlett-Packard\HP Quick Launch Buttons" on a system where the software is installed. Synaptics Touchpad-Tool: I found someone who said that you just have to add the whole directory (including the .exe-files) that you find unter C:\swsetup as drivers to SCCM. Drivers AND tool should get automatically installed using the .inf-file included in that directory. But that does not work. Anyone got an idea, how I can install the synaptics-tool using an OSD-tasksequence?

Did you figure our the synaptics issue?

First import the synaptics drivers in the OSD Drivers store and assign them to your TS (you might want to extract the exe before you can import it) This is to install the DRIVER for the pointing device. Afterwards, create a package with following program in it : Setup.exe -s /f2c:\windows\synaptics.log and assign the program to your TS This is to install the APPLICATION for the pointing device.

Hello Jeroenda, Thank you, that did the trick!!!

The command "Setup.exe -s /f2c:\windows\synaptics.log" works when used in a script (and the script is called in the TS). When I put it into a software package, the installation fails - but after a reboot the software is installed. Seems a little like SCCM gets no return code on success.