k- doing that now. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Tuomo Leppänen Sent: Tuesday, September 16, 2014 10:26 AM To: mssms@lists.myitforum.com Subject: Re: [mssms]Kernel Mode Driver Framework
Just try the method I described earlier: %windir%\system32\dism.exe /Image:%OSDisk% /ScratchDir:%OSDisk%\Windows\Temp /Add-Package /Package/PackagePath:%CD% On 16.9.2014 20:15, Taxter, Latisha wrote: Here are the logs from a few minutes ago.. I will go peruse them myself to see if they point me to what the issue is. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Jeff Poling Sent: Tuesday, September 16, 2014 7:11 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms]Kernel Mode Driver Framework I looked a little deeper at what I did - it works successfully. I have the steps to inject the KMDF directly after the Apply Operating System Step and prior to installation of any other driver packages. It's working successfully at the one client where I implemented it. As others have said, it's likely easiest to use DISM to update your WIM; however, I was not in a position to do that at the time I implemented this. So, try moving your KMDF steps to just after the OS gets applied and see if that helps. Thanks, Jeff ________________________________ From: dratl...@humana.com<mailto:dratl...@humana.com> To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms]Kernel Mode Driver Framework Date: Tue, 16 Sep 2014 13:48:30 +0000 I tried Dustin’s method as well, because of new models that needed the KMDF and we were not ready to rebuild our base image. We could never get it to work, when the machine would run through windows setup the update would install and then windows setup would bomb because this update was needed. If I rebooted the machine and looked at the image from WinPE, DISM showed the update as ‘Install Pending’. We ended up rebuilding our image. Daniel Ratliff From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Jeff Poling Sent: Tuesday, September 16, 2014 9:24 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms]Kernel Mode Driver Framework Try checking the box for "Package" and select the package that contains the KMDF install. Jeff ________________________________ From: ltax...@kh.org<mailto:ltax...@kh.org> To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms]Kernel Mode Driver Framework Date: Tue, 16 Sep 2014 00:06:17 +0000 Thanks. This is what I have.. tried it both with command line and package.. I am assuming I don’t have something set correctly. [cid:image001.png@01CFD199.04E67F90] From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Jeff Poling Sent: Monday, September 15, 2014 5:03 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms]Kernel Mode Driver Framework I've done it successfully at a client. I will get exactly what I did and send it to you tomorrow, unless someone else responds sooner. Jeff Sent from my Windows Phone ________________________________ From: Taxter, Latisha<mailto:ltax...@kh.org> Sent: 9/15/2014 6:07 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms]Kernel Mode Driver Framework Has anyone been able to inject this using command line? Following this article :- http://deploymentramblings.wordpress.com/2013/10/24/osd-injecting-the-windows-7-kernel-mode-driver-framework-kmdf/ It fails after creating the scratch directory and I can’t find anything is smsts.log that helps. Any other ways of doing this other than updating the image directly? Thanks. Latisha Taxter Server Administrator III Kootenai Health 2003 Kootenai Health Way Coeur D’Alene, Idaho 83814 • 208-625-4192 ltax...@kh.org<mailto:ltax...@kh.org> http://www.kh.org [cid:image001.jpg@01CEFC06.C6A6DA30] 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.
