Recently went through this for a Optiplex 9020M (micro) 32bit Windows 7. We had to include the updated Kernel mode Driver framework as the newer drivers required it. We were getting errors about it not being able to continue setting up windows.
Kernel-Mode Driver Framework version 1.11 update for Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 https://support.microsoft.com/en-us/kb/2685811 Between Apply Windows Settings and Setup windows and configuration manager we put a Install Components Offline section to our task sequence. -Make a scratch directory - cmd.exe /c mkdir %OSPART%\Scratch -Install KMDF1.11 - cmd.exe /c X:\windows\system32\dism.exe /ScratchDir:%OSPART%\Scratch /Image:%OSPART%\ /Add-Package /PackagePath:%_SMSTSMDataPath%\Packages\TRN00051\kmdf-1.11-Win-6.1-x86\Windows6.1-KB2685811-x86.cab I am in the stages of moving from SCCM 2007 to 2012R2 and slowly learning all the little niggling issues. (like the above). We are also including the WSUS client hotfix to reduce memory errors (KB3050265) in the same time. Regards Neil Thomson Acting Principal Technical Advisor, Information and Communication Technology, Blue Card Services ICT Service Development Frontline & Digital Services Public Safety Business Agency Phone: (07) 3211 6180 Email: [email protected] [cid:[email protected]] [cid:[email protected]] P Please consider the environment before printing this email. From: [email protected] [mailto:[email protected]] On Behalf Of Paul Cussen Sent: Wednesday, 22 July 2015 12:16 PM To: mssms Subject: Re: [mssms] Issues imaging OptiPlex 3020 - Win7 x64 I had a similar issue with several Dell models where the network wouldn't connect after driver injection. It turned out to be the Dell packaged Intel NIC driver. I simply deleted the NIC drivers from the driver package, imported the Intel packaged NIC driver, and created a step in the TS to auto-apply the Intel NIC driver to the specific models where the issue was seen. I did report the issue to one of the forum moderators at Dell, as well as to a Dell provided technical contact (several weeks ago at this point), but still no word. No matter, what I did is a viable (albeit time consuming to figure out) workaround. On Tue, Jul 21, 2015 at 6:34 PM, Kent, Mark <[email protected]<mailto:[email protected]>> wrote: Is this the Broadcom or Realtek NIC? Mark Kent (MCP) Sr. Desktop Systems Engineer Computing & Technology Services - SUNY Buffalo State From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Murray, Mike Sent: Tuesday, July 21, 2015 1:46 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Issues imaging OptiPlex 3020 - Win7 x64 So I tried using the Driver Grabber, it’s still failing when I image (loses IP connectivity once it restarts). No clue where to go from here. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Chris Carbone Sent: Wednesday, July 15, 2015 3:57 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Issues imaging OptiPlex 3020 - Win7 x64 Yes, import like normal. I only use the driver grabber tool to retrieve what I installed. Driver packages are so much smaller now. ;) From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Wednesday, July 15, 2015 3:45 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Issues imaging OptiPlex 3020 - Win7 x64 Do you just import like you normally would in ConfigMgr or do you use their Driver Inject tool? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Chris Carbone Sent: Wednesday, July 15, 2015 12:31 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Issues imaging OptiPlex 3020 - Win7 x64 There’s another tool where you can automate the drivers importing into SCCM but I have not messed with it. I think with this you can set names and categories. For the categorization you can set this when you manually import the drivers. I do notice that this ConfigMgr injector tool renames the ini files. I think it’s designed to do this for avoiding duplicate ini file names. I just load the OS, drivers, then run the tool, it spits out the drivers, inf, ini files etc into a directory you create. Then just import that into SCCM, done. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Murray, Mike Sent: Wednesday, July 15, 2015 12:01 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Issues imaging OptiPlex 3020 - Win7 x64 I’m tempted to try this utility. It looks like I would have no control of the naming/categorization, though. Is this true? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Chris Carbone Sent: Wednesday, July 15, 2015 9:23 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Issues imaging OptiPlex 3020 - Win7 x64 I also share this frustration. We primarily have Lenovo laptops in our environment. Lenovo finally started coming out with SCCM driver packages. But they include every driver under the sun and completely makes this pointless to bother with. I just load a new computer with base OS, install drivers. Then use the ConfigMgr Driver Injector tool to grab only the drivers needed to import. This tool such a time saver. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Andreas Hammarskjöld Sent: Tuesday, July 14, 2015 3:11 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Issues imaging OptiPlex 3020 - Win7 x64 Now that’s some real frustration built up!!! But I share your pain, like Intel zipping all the drivers up but then having zips in the zip that contains .exe’s to unzip each driver. WTF, so close but so far from target! //A From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Stephen Owen Sent: den 14 juli 2015 22:02 To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Issues imaging OptiPlex 3020 - Win7 x64 That cab includes like fifteen different network drivers, which I think is what's borking the whole thing. I like to image one machine with just a standard windows image, then manually determine which drivers are needed and import them a few at a time. Every manufacturer still releases these monster monolithic cabs with 6,000 drivers in them for every OS configuration ever imagined. So, yeah, I think if you just picked single drivers to import instead of crushing the whole cab into a fine powder and snorting it up, you'd be fine :) On Tue, Jun 30, 2015 at 12:56 PM, Murray, Mike <[email protected]<mailto:[email protected]>> wrote: 3020’s are failing repeatedly when imaging via ConfigMgr 2012 OSD. After the apply drivers step in the TS, it loses network connectivity. No IP address whatsoever. I’m using a recent Windows 7 driver cab from Dell. Anyone else? Best Regards, Mike Murray Desktop Management Coordinator - IT Support Services California State University, Chico 530.898.4357<tel:530.898.4357> [email protected]<mailto:[email protected]> This electronic mail transmission may contain confidential information intended only for the use of the individual(s) identified as addressee(s). If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this electronic mail transmission is strictly prohibited. If you have received this transmission in error, please notify me by telephone immediately. This electronic mail transmission may contain confidential information intended only for the use of the individual(s) identified as addressee(s). If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this electronic mail transmission is strictly prohibited. If you have received this transmission in error, please notify me by telephone immediately. This electronic mail transmission may contain confidential information intended only for the use of the individual(s) identified as addressee(s). If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this electronic mail transmission is strictly prohibited. If you have received this transmission in error, please notify me by telephone immediately. ________________________________ Important Notice for Recipients external to PSBA: This email is to be read subject to the disclaimer below: Unless stated otherwise, this email, including any attachments, is intended for the named recipient(s) only and may contain legally privileged, private and / or confidential information and may be protected by copyright. You may only use the email if you are the person(s) it was intended to be sent to and if you use it in an authorised way. No one is allowed to use, review, alter, transmit, disclose, distribute, print or copy this email without appropriate authority. If this email is received in error, please notify the sender immediately by return email or contact PSBA‘s Service Desk on 07 3211 6111. You must delete this email from your computer system network and destroy any hard copies. Any legal privilege or confidentiality is not waived or extinguished if this email is received in error. Please be aware that the contents of any emails sent to or from PSBA may be periodically monitored and reviewed. PSBA respects your privacy. Our privacy policy can be accessed from our website: http://www.bluecard.qld.gov.au/privacy.html Unless stated otherwise, this email represents only the views of the sender and not the views of PSBA or the Queensland Government. It is the recipient‘s responsibility to ensure that this email does not contain and is not affected by computer viruses. PSBA does not guarantee that the information is free from any virus, nor that the integrity of this email has been maintained i.e. the email has not been intercepted or interfered with during transmission.
