What about using driver CABs or HP SoftPaq (or is it soft pack) to get the drivers for your new hardware?
Sent with Good (www.good.com) -----Original Message----- From: Burke, John [[email protected]<mailto:[email protected]>] Sent: Tuesday, February 18, 2014 09:38 AM Central Standard Time To: [email protected] Subject: [mssms] RE: Instructions for a team member to properly figure out which drivers to add to boot wim when new model comes in yeah i explained that to him, but he seems to get really lost. So basically i was correct in that he needs that hardware id. Then he should look for it in the inf files, If eh goes to the HP sight for example - and downloads the drivers, those hardware id's should be in those inf files correct? ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Tuesday, February 18, 2014 10:16 AM To: [email protected] Subject: [mssms] RE: Instructions for a team member to properly figure out which drivers to add to boot wim when new model comes in The vast majority of your machines are going to come preloaded with an OEM Windows OS that includes all of the drivers. I would typically boot that as soon as I received it, go into Device Manager, and record the Hardware ID for the mass storage controller and NIC at a minimum (usually audio, display and a few other usual suspects as well). Once you have the Hardware ID, you can do a text search of the .inf driver files you already have included and see if it is already included. If you have command prompts support in your boot image (which you should), you can also use the drvload utility (http://technet.microsoft.com/en-us/library/cc766390(v=ws.10).aspx) to test drivers and find the one that works best. Hope that helps! -Phil _________________________________________________________________ Phil Schwan | Technical Architect, Enterprise Windows Services Project Leadership Associates|2000 Town Center, Suite 1900, Southfield, MI 48075 Lync: 312.756.1626 Mobile: 419.262.5133 www.projectleadership.net<http://www.projectleadership.net/> [Description: Description: Description: Arrow email]Lead with Strategy. Leverage Technology. Deliver Results. [linkedin_logo-19x20]<http://www.linkedin.com/in/philschwan>[Twitter-Logo1-20x20]<https://twitter.com/philschwan> [wordpress-logo3] <http://myitforum.com/myitforumwp/author/philschwan> From: [email protected] [mailto:[email protected]] On Behalf Of Burke, John Sent: Tuesday, February 18, 2014 9:03 AM To: [email protected] Subject: [mssms] Instructions for a team member to properly figure out which drivers to add to boot wim when new model comes in it's taking months to get a new model supported and I've been able to help when I have time, but I was hoping there was a sigh that had the step by steps for figuring out exactly which mass storage, and which network drivers to add into the boot wim and sccm catalog of sccm 2007. It would really really help. ________________________________ PRIVILEGED AND CONFIDENTIAL. This email and any files transmitted with it are privileged and confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. If you are not the named addressee you should not disseminate, distribute or copy this e-mail or any of its attachments.
<<inline: image001.jpg>>
<<inline: image002.jpg>>
<<inline: image003.jpg>>
<<inline: image004.jpg>>
