Peter van der Woude

Make sure that you completely removed everything from your old environment (mainly in the AD).

Did you check the log files to see why it failed?

You can't remove computers via a query that are manually added. You need to create one query that for example just looks at the installed software.

When you're doubting about something like that, there is only one thing you can do and that's to install one device without installing drivers. After that extract the downloaded drivers locally and manually go by every piece of hardware and try to search for newer drivers and use your extracted drivers as input. After that look at the differences with a device that you deployed.

In ConfigMgr 2012 the SLP is an extra functionality of the MP, so the SMSSLP= is not needed anymore. Also, remove the / before SMSMP. Keep in mind that the auto discover will only work when the site information is written to the AD.

To see what's happening check the adsgdis.log.

Haven't seen this behavior before (as I haven't ever used that combination), but I can imagine that it happens. The settings in the User Experience tab only apply to the deployment of the application itself.

See: http://social.technet.microsoft.com/Forums/en-US/a7a99fd5-163e-404c-9913-b02924e6da9a/what-is-command-line-for-adobe-reader-in-exe?forum=configmanagerapps

You have to separatly push out the CU1 update.

That package is probably your client package (looking at the number). In most cases an update distribution point action will solve this problem.

Weird.. well, maybe the big-brother script does work: http://blogs.technet.com/b/configmgrdogs/archive/2013/05/09/package-amp-application-source-modification-scripts.aspx

Use a select distinct to only get unique resource id's.

It's a custom tool written for ConfigMgr 2007 by somebody from the community. Also, keep in mind that ConfigMgr 2012 also does health checks itself (via a scheduled task). The most efficient, in my opinion, is still a GPO with Jason's script.

If it's only one update you can either add it manually to your update group (and package), or use a custom severity and use that in your ADR query.

Does that mean that you solved it?

You are correct. Use the customization wizard to make the installation the way you want it. ConfigMgr doesn't have any influance on the behavior of the installer itself.

They should get deployable after you downloaded the content.

Not sure what you mean, but the computer needs to be online and you need to be able to connect to it and have enough rights to it.

What about the client.msi.log?

You could retire the application.

Your welcome, sounds like a deal!

Are there any errors above this? Maybe something about disk sizes?

Here is a link for a WinPE 4.0 driver package: http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdDetails/?lang=en&cc=us&sp4ts.oid=5298035&swItem=ob_115707_1 For all the other driver packages, see http://ftp.hp.com/pub/caps-softpaq/cmit/HP_Driverpack_Matrix_x86.html and http://ftp.hp.com/pub/caps-softpaq/cmit/HP_Driverpack_Matrix_x64.html

The location of the variable doesn't matter, as long as it's in front of the Install applications step.

Don't see anything special in this log... "Just" try to relate back to everything you changed the last couple of days.