Kernel-Mode-Driver-Framework
“Context -
SCCM imaging was broken and in need of a fix.”
posted Oct 27, 2014, 3:54 PM
What is this u may ask? Probably something I will never ever have to deal with again however...just in case....its here for reference in the event of.
Here is the story:
User contacts me and says that they are unable to image a T430 using Windows Pro and a new Samsung 840 EVO 500GB SSD. We sweep the logs (smsts / windows / haven't u been reading?). To me this is a disk driver issue. The smsts.log even says it cant find the SSD drive. OK simple enough...locate the driver / add it to the image / and move on. Well it didn't work out that way, as u may have guessed. No matter what drivers we added the drive wouldn't get recognized. We did find out that the Enterprise version would work. So it got me thinking, why one vs. the other. Well the Enterprise version is the most current while the Pro version has not been touched in a while. So that lead me to updating the Pro version with all of the missing updates (updates as in performance / reliability updates). Still no joy....I asked the user to re-image this time and use the 32 bit instead of the 64. Surprisingly it worked. This got the wheels spinning again...why, why, why. Hmm i did notice some errors when adding updates to the 64 bit side of the image. This has got to be update related like I suspected all along.
So I decide to start over again...lets start from the ground up..review logs again...maybe something will jar my memory or give me an angle to pursue....
So I took a look at this screen shot again and it got me thinking about components that have failed and the setupacct.log. So I went to review this log again and decided to look up the error in the box below
Bingo....I got a hit in the form of a MS KB Article - http://support.microsoft.com/kb/2494168
This looked promising....A little more research led me to http://en.community.dell.com/techcenter/b/techcenter/archive/2013/10/07/kernel-mode-driver-framework-1-11-update-what-it-is-and-why-you-need-it
Which led to this - http://www.microsoft.com/en-us/download/details.aspx?id=38423
Which led to getting the issue resolved.
So to recap, this update had to be injected into the image in order for the operating system to be able to even see the SSD driver. Like I said, this is probably only for me but hey maybe someone else can benefit, right?
Go Cowboys!
