Attention, Internet Explorer User Announcement: Jive has discontinued support for Internet Explorer 7 and below. In order to provide the best platform for continued innovation, Jive no longer supports Internet Explorer 7.
I have narrowed it down to there being some issue in the HP SoftPaq Download Manager. HP SoftPaq Download Manager / I did: Build Driver Pack tab / Show Latest. HP SoftPaq Download Manager Release Notes. Client Management Solutions - HP SoftPaq Download Manager (SDM). Downloaded softpaq can be shown in build driver pack mode.
Jive will not function with this version of Internet Explorer. Please consider upgrading to a more recent version of Internet Explorer, or trying another browser such as Firefox, Safari, or Google Chrome. (Please remember to honor your company's IT policies before installing new software!) • • • •.
Hey guys, So I'm new to SCCM and I feel like I'm missing something. We have 4 kinds of laptops here: HP Elitebook 840 G1, G2, G3, G4.
At first, I went to to download the driver packs, extract them and manually inject them into packages in SCCM. I faced so many errors and issues that I posted about it a while back and got two recommendations which followed: • Use this which works 80%.
I mean, it's okay and all but it has it's issues. • Use HP's own to import drivers which almost never works.
My issue with the Automating tool is that it's not precise. There are drivers for Windows 10 1709 and for 1703, and according to HP they are different, but the tool has trouble providing information on which download is which. It's an awesome tool, and works very well, but I don't feel like it is ideal for me. HP's tool is worst. I barely understand what is the purpose of it, even afte reading their documentation a few times.
It errors out a lot, isn't as custom as I want it to be and it downloads duplicate drivers all the time and I don't know if that's okay. Clearly, I have a lot to learn. Any help sorting out drivers would be great, some tips, tricks and stuff I may not know.
Thanks:) • • • • •. Hey, we only use HP laptops here and I support the models you specify. If this is not how you do it, you should start. This works 100% of the time, provided that the drivers are correct.
I use this myself and have had zero issues since implementing it. • Download driver packs from here:. Yeah, they're big but storage is mostly cheap nowadays and you will save time. If there is no driver pack for your model and OS I would recommend you to download HP Softpaq Download Manager and build the driver pack for the target model. Also note that the driver packs will most likely not contain updated drivers for all the vulnerabilities discovered this year, you need to double check this.
When you download the driver pack, there is a text file listing all the drivers it contains along with driver versions. • Skip creating 'driver packages' and create regular packages (without a program).
• Configure your TS to use dism.exe to inject the drivers while in WinPE, right after your 'Apply Operating System' step. Use a run command line step: DISM.exe /Image:%OSDTargetSystemDrive% /Add-Driver /Driver. /Recurse /logpath:%_SMSTSLogPath% dism.log (point this step to the regular driver package you created in step 2). Add 2 and 50 as success codes on the Options tab for each driver step. • Drivers required for boot images will still need to be imported in the 'old' way, you cannot use these regular packages for that. I use a WMI query: SELECT * FROM Win32_ComputerSystem WHERE Model = 'HP EliteBook 840 G1' There is also something called 'dynamic driver management' which you might want to look up but maybe that's a bit overkill for you now since you're new to the product. I've used this myself but for other reasons it's not really practical for us to use it and I've reverted back to WMI queries.
I also forgot that you need to set some custom return codes as 'success codes' on each driver step. You need to add 2 and 50, otherwise the driver step will fail.
• • • • • • •. When using dism.exe to apply the drivers, you will very likely not get a return code 0 back since there will be drivers in the driver pack that are not applicable to the exact specification of your laptop models and therefore the driver injection will fail for just that/those drivers. Spot checking a few of our recent OS deployments, I only see a return code of 2 and not 50, but I know there was some reason why 50 was added also.