The boss is giving us till the end of next week before pulling our SCCM project! Hope not as we've spent months getting it this far but he's not happy with all the problems with it.
Today we took delivery of yet another model of laptop from HP. This one is an HP4530s. We have the previous HP4520s working great through SCCM (well, not great obviously but it's good enough for us). I have downloaded all the drivers from the HPs site but when I try to import them SCCM tells me they are already in the database. Fair enough, the specs must be the same as the previous model so one less thing for me to worry about. Oh hang a sec, no they are not the same. I know the NIC in the 4530 is slightly different than the 4520 as I had to inject yet another NIC driver into the boot wim for PXE. Mmmmmmm, so if the NICs are different, perhaps other hardware in the laptop are different. How can I tell SCCM just to add all the drivers I tell it to, wether they are already in the database or not? Why can't I just create a new folder called HP 4520s and put all the drivers in there and then another folder called 4530 and put all the drivers in that one.
so then....if the drivers are already in the database how come NONE of the drivers are working through the OSD task? The 4530 is using the same task sequence as the 4520 where we have set 'Auto Apply Drivers' and selected use drivers from any category.
I thought perhaps creating a driver package and using that would help....nope, can't even do that. When I create a new driver package it's all great until I start adding drivers to it lol The error comes up 'some packages cannot be updated, please check the logs'. Would be nice to have a link to which log I should be looking at. I'd really rather not use a driver package, much happier using the auto apply driver task and let it do a pnp scan and pick what it needs. Last time I made a driver package for an HP laptop I got an out of memory error. Seems the driver package was too big for the registry limit or something. Not surprising with 300mb bluetooth drivers!!!! go figure.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Argh!
The boss is giving us till the end of next week before pulling our SCCM project! Hope not as we've spent months getting it this far but he's not happy with all the problems with it.
Today we took delivery of yet another model of laptop from HP. This one is an HP4530s. We have the previous HP4520s working great through SCCM (well, not great obviously but it's good enough for us). I have downloaded all the drivers from the HPs site but when I try to import them SCCM tells me they are already in the database. Fair enough, the specs must be the same as the previous model so one less thing for me to worry about. Oh hang a sec, no they are not the same. I know the NIC in the 4530 is slightly different than the 4520 as I had to inject yet another NIC driver into the boot wim for PXE. Mmmmmmm, so if the NICs are different, perhaps other hardware in the laptop are different. How can I tell SCCM just to add all the drivers I tell it to, wether they are already in the database or not? Why can't I just create a new folder called HP 4520s and put all the drivers in there and then another folder called 4530 and put all the drivers in that one.
so then....if the drivers are already in the database how come NONE of the drivers are working through the OSD task? The 4530 is using the same task sequence as the 4520 where we have set 'Auto Apply Drivers' and selected use drivers from any category.
I thought perhaps creating a driver package and using that would help....nope, can't even do that. When I create a new driver package it's all great until I start adding drivers to it lol The error comes up 'some packages cannot be updated, please check the logs'. Would be nice to have a link to which log I should be looking at. I'd really rather not use a driver package, much happier using the auto apply driver task and let it do a pnp scan and pick what it needs. Last time I made a driver package for an HP laptop I got an out of memory error. Seems the driver package was too big for the registry limit or something. Not surprising with 300mb bluetooth drivers!!!! go figure.
/rant
Grrr!!!
Share this post
Link to post
Share on other sites