Just because I see so many people miss it... WinPE 3.0 - Windows 7 WinPE 4.0 - Windows 8 WinPE 5.0 - Windows 8.1
Use the appropriate drivers for the boot image you are using (x86/x64 respectively). The OS you are deploying has nothing to do with the drivers WinPE uses. Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Tuesday, February 18, 2014 3:50 PM To: [email protected] Subject: RE: [mssms] RE: Instructions for a team member to properly figure out which drivers to add to boot wim when new model comes in So, going back to the original question, the first step should really be to simply boot the system using your current boot image. If it works, job done. You shouldn't add drivers if they are already included in the default driver catalog. If a driver is found to be lacking, then you need to identify if it's a NIC or storage driver by dropping to the command-prompt and running ipconfig and diskpart. From there, download the appropriate driver types for the model from the manufacturers web site, put them on a USB stick, and use drvload to load them one by one until you get an IP (shown by using ipconfig) or the disks show up (as shown in diskpart). Then, add that driver to the applicable boot image. J From: [email protected] [mailto:[email protected]] On Behalf Of Rich Coulter Sent: Tuesday, February 18, 2014 9:45 AM To: [email protected] Subject: RE: [mssms] RE: Instructions for a team member to properly figure out which drivers to add to boot wim when new model comes in Good point. Use HP's Softpaq Download Manager to download the drivers. I would also recommend utilizing the System Software Manager (SSM.EXE) tool. Basically, what this would allow you to do is create a database which references *how* to install the HW-based drivers. So, in stead of going through the hassle of downloading, extracting the softpaqs, then spending heaps amount of time trying to determine how to install them 'silently' or in an 'unattended' fashion - you run SSM.EXE /am_bld_db against a folder structure you create containing all of the Softpaqs (you downloaded using the Softpaq) download manager. Setup two steps in your TS. One to copy the drivers from the server to the client and one to run the SSM.EXE to execute an unattended installation of your drivers. My point with mentioning this is it takes me hours to add new HW support using this method as opposed to months. :) Rich ________________________________ From: [email protected]<mailto:[email protected]> [[email protected]] on behalf of Dzikowski, Michael [[email protected]] Sent: Tuesday, February 18, 2014 9:39 AM To: '[email protected]'; '[email protected]' Subject: RE: [mssms] RE: Instructions for a team member to properly figure out which drivers to add to boot wim when new model comes in 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<http://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]<mailto:[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]> [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Tuesday, February 18, 2014 10:16 AM To: [email protected]<mailto:[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]> [mailto:[email protected]] On Behalf Of Burke, John Sent: Tuesday, February 18, 2014 9:03 AM To: [email protected]<mailto:[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. CONFIDENTIALITY NOTICE: This electronic mail transmission (including any accompanying attachments) is intended solely for its authorized recipient(s), and may contain confidential and/or legally privileged information. If you are not an intended recipient, or responsible for delivering some or all of this transmission to an intended recipient, be aware that any review, copying, printing, distribution, use or disclosure of the contents of this message is strictly prohibited. If you have received this electronic mail message in error, please delete it from your system without copying it, and contact sender immediately by Reply e-mail, or by calling 913-307-2300, so that our address records can be corrected. Although this e-mail and any attachments are believed to be free of any virus or other defect that might negatively affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way in the event that such a virus or defect exists. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
<<inline: image001.jpg>>
<<inline: image002.jpg>>
<<inline: image003.jpg>>
<<inline: image004.jpg>>
