Hello and Welcome to the Blog of Kevin Fason! This is my Day to Day Technical Journal. Currently I am the End User Computing Architect for a large Engineering firm in Denver. Had various roles over the years from Communications (PBX & Voicemail) , Administration, even IT Global Manager. Deployment is a big part of my mindset (OSD, MDT, going back to dd) so I have come across lots of scenarios and issues working for a firm that's on all the continents and zillions of countries.

Saturday, April 25, 2015

Driver is not applicable to any supported platform

"The selected driver is not applicable to any supported platforms."

Wait, what? We are on SCCM 2012 R2 CU3 (CU4 any day!) so we should not get something like this. Did I somehow get some secret Windows 10 drivers somehow? Lots of mis-written INF files? This is strange.

In my last post I was talking about one time driver injection. We've moved past that as we liked the Toshiba device and decided to buy a large number of them so they need to be setup in SCCM. Initially, a Toshiba INF driver was mis-written to state it supported 64-Bit when the DLL it called for were 32-Bit only. BSOD's all around. After fixing that I still had to address this supported platform problem. While trying to import drivers we would get this error about several of them, mostly NIC drivers not being imported due to being unsupported . In the case of the Toshiba, the physical NIC did not import, however the WiFi driver imported, so after sysprep the Toshiba started imaging over the wireless interface. That was fun, I don't recommend that.

Looking at the INFs they were written in normal Intel fashion and even making some modifications to strip down to Windows 8.1 did nothing. Digging through the SCCM logs was not a ton of help either. AdminUI.Log, DriverCatalog.Log, SMSAdmin.Log, Setupapi.app.log, you name it. All just said the same thing, driver not applicable. Those actually gave an error code of 0x80070661.

Turns out the issue is due to our Site Server being on 2008 R2. Specifically with the OS. The signing in these drivers is using a newer method thats not native in 2008 R2. Microsoft released KB3025419 which states to install KB2837108 and KB2921916 to update the OS to support the newer signing method in ConfigMgr. Coincidentally both this KB and the Toshiba device came out at the same time. After applying the hotfix and restarting (not required but the KB states to do anyway) we are now able to import these newer signed drivers and image the Toshibas up successfully and quickly.

2 comments:

Kevin, this is a very timely post as we just ran into this issue at my organization as well. We want to apply the hotfixes to correct the issue, but we're wary of doing so because of this line in the KB article:

"After you install hotfix 2837108 or hotfix 2921916 and then restart the server, any affected driver that's already in the System Center Configuration Manager console will have to be removed and then reimported."

Did this affect many of your previously imported drivers causing you to have to re-import them? We don't want to "break" anything that's currently in use. Perhaps it just means that the drivers would need to be re-imported to get them to show up as "signed" but they would still work if left in place? Anyway, just curious about your experience. Thanks!

We have had this patch in play for 2 1/2 weeks and image globally about 50 systems daily and have had zero reports of issues from techs regarding drivers. I concur that it applies to unsigned drivers needing to be redone so they are signed. This issue is the first we had of any problem with a driver not able to be imported so I don't believe we have any drivers unsigned that should be signed.

Additionally we are about 14-30 days behind Dell when they release a new cab so it should resolve itself within several months if we had any.