"The selected driver is not applicable to any supported platforms" issue still occur on SCCM SP2+R2 for Win7 Drivers
- Hi there,
when I try to import some Win7 Drivers into SCCM SP2+R2, I still get the following error message:
"The selected driver is not applicable to any supported platforms"
I heard it was fixed in SP2? any idea?
problematic Driver example: Dell NIC driver for Intel 825xx 10.0.6.0 - R235484
Все ответы
- I just downloaded the driver(s) and was able to import them:
"CreateFromINF("\\myserver\myshare\INTEL_825XX-GIGABIT-PLATFORM_A01_R235484\win7-32", "E1Y6232.inf")
Client SSL is disabled. Setting state to 0x0.
Initializing driver digest from '\\myserver\myshare\INTEL_825XX-GIGABIT-PLATFORM_A01_R235484\win7-32\E1Y6232.inf'
Successfully initialized driver digest.
Returning 1 driver definition.
CreateFromINF("\\myserver\myshare\INTEL_825XX-GIGABIT-PLATFORM_A01_R235484\win7-64", "E1Y62x64.inf")
Initializing driver digest from '\\myserver\myshare\INTEL_825XX-GIGABIT-PLATFORM_A01_R235484\win7-64\E1Y62x64.inf'
Successfully initialized driver digest.
Returning 1 driver definition. " - Torsten, thanks for your quick reply!
I will reboot the site server this weekend and then try it again. I will let you know the result.
btw, I got the error message from the SCCM console, so can you please share some log files for drivers importing to troubleshoot it? - I've taken the lines I posted from DriverCatalog.log: http://technet.microsoft.com/en-us/library/bb932135.aspx
- Thanks! that's what I got from that log file - another driver R240912 with the same error:
CreateFromINF("\\sccmserver\sccm$\Source\Drivers\Video\x86\R240912\payload\Graphics", "kit19047.inf") DriverCatalog 11/16/2009 3:48:10 AM 6156 (0x180C) Initializing driver digest from '\\sccmserver\sccm$\Source\Drivers\Video\x86\R240912\payload\Graphics\kit19047.inf' DriverCatalog 11/16/2009 3:48:22 AM 6156 (0x180C) \\sccmserver\sccm$\Source\Drivers\Video\x86\R240912\payload\Graphics\kit19047.inf is not applicable to any supported platforms. DriverCatalog 11/16/2009 3:48:23 AM 6156 (0x180C) Driver is not applicable to any supported platforms. Code 0x80070661 DriverCatalog 11/16/2009 3:48:23 AM 6156 (0x180C) CreateFromINF("\\sccmserver\sccm$\Source\Drivers\Video\x86\R240912\payload\HDMI", "IntcHdmi.inf") DriverCatalog 11/16/2009 3:48:23 AM 6156 (0x180C) Initializing driver digest from '\\sccmserver\sccm$\Source\Drivers\Video\x86\R240912\payload\HDMI\IntcHdmi.inf' DriverCatalog 11/16/2009 3:48:24 AM 6156 (0x180C) \\sccmserver\sccm$\Source\Drivers\Video\x86\R240912\payload\HDMI\IntcHdmi.inf is not applicable to any supported platforms. DriverCatalog 11/16/2009 3:48:24 AM 6156 (0x180C) Driver is not applicable to any supported platforms. Code 0x80070661 DriverCatalog 11/16/2009 3:48:24 AM 6156 (0x180C)
Also, I found the same error report for a HP driver on SCCM SP2:
http://h30434.www3.hp.com/psg/board/message?board.id=OS&thread.id=23811 Hi Torsten,
I rebooted the site server but the same error is still there.
1. I downloaded the driver from here: ftp://ftp.dell.com/network/INTEL_825XX-GIGABIT-PLATFORM_A01_R235484.exe, is the same source as the one in your test?
2. I listed all osdcore.dll (as per KB961105) files in my site server as below, are they same as the files on your site server? the version of 3 files on my site server is all 4.0.6487.2000
Directory of D:\PROGRAM FILES\bin\i386
09/18/2009 03:00 AM 574,816 osdcore.dllDirectory of D:\PROGRAM FILES\OSD\bin\i386
09/18/2009 03:00 AM 574,816 osdcore.dllDirectory of D:\PROGRAM FILES\OSD\bin\x64
09/18/2009 03:00 AM 961,904 osdcore.dll
any other ideas on how to fix this issue?- I hit this issue a few weeks ago... see my other thread:
http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/ba2edc3f-61a3-4e1a-ad34-48af2a43f4ae
It seems as though it may be related to SP2 RC to SP2 RTM upgrades. I have two sites, one has never had any RC code installed and is working fine. The other was upgraded from SP2 RC to RTM and does not work (with the same driver).
What we have found is that modifying the version info in the .inf file works around it, although it's obviously not a good idea. So far we have not found a way of fixing the issue on the site that has been upgraded from RC.
Has your site been upgraded from SP2 RC to RTM?
Mark. - Hi Mark,
No, we didn't upgrade to SP2 RC. We installed directly SP2 RTM on SP1+R2 RTM without any errors during upgrade.
Modifying the INF will break the certificate Hi All.
I have this issue with a number of drivers. My SCCM site is a nice clean fresh install of SCCM 2007 + SP1 (i.e. combined), R2 installed, then upgraded to SP2. I have the problem in both my lab and in production. The site server in both environments is on a Windows 2008 x64 machine and the database is on a remote SQL 2008 machine (though in the lab the SQL 2008 machine is on the site server). I'm doing the imports from either an Windows 7 x64 machine or at the console of the servers. I haven't tried to do an import of a driver to the catalogue from an x32 machine.
Here are some of the drivers I have issues with if someone wanted to try them out:Broadcom Wireless LAN Driver for Microsoft Windows 7 (5.30.21.0)
Source: HP Website (EliteBook 6930p)Mobile Intel(R) 965 Express Chipset Family (8.15.10.1912)
Source: Windows Update CatalogSoundMAX Integrated Digital HD Audio (6.10.1.5240)
Source: Windows Update CatalogSome other threads suggest editing inf files. I definitely do not want to do this, that is a hack and could introduce new problems, and I don't think it’s the driver .inf file at fault, these drivers work if manually installed so PnP can read the .inf files. They can also be imported into the MDT driver catalogue, so the MDT scripts have no problem consuming the .inf files.
Some other threads suggest downloading the drivers from the component manufacturers instead of the laptop/desktop vendor. I've tried this and those drivers (Intel in my case) also fail to import.
Any thoughts at this stage would be great.
James.- I think we have all agreed that modifying the INF's is not a viable option... we have just been testing it in order to further understand the issue and try and work out why it is failing.
It's interesting to know the problem is not limited to RC to RTM upgrades. As I said in the other thread the difference between our two labs (one works, one doesn't) apart from RC to RTM upgrades is Server 2008 x64 with remote SQL 2008 x64. The one that fails is running 2008, the one that is working is running Server 2003 with SQL 2005. Perhaps it's to do with x64 or SQL 2008?
Initially we had the provider on the SQL 2008 server but have also tested it with the provider on the site server and still get the same issue...
Mark. - All
I've opened a case with Microsoft. They have given me a simple work-around that involves a very simple addition to the .inf files and the workaround appears to work from my quick testing so far. The hack doesn't change any of the lines in the .inf file, it just adds an extra line to one common section. I've asked them some follow-up questions:
- what the impact is on the driver file signatures in hacking at the .inf files (i.e. will this cause me other issues)
- do they intend to release a hotfix so I don't have to use the workaround?
- does my organisation's support agreement allow me to share the workaround here?
I'll update when I know more. Since this is a know issue, I imagine there will be no charge for the call, so suggest you open a case with Microsoft if you need to get the answer before I have posted back here.
James. We are also having this issue. I am working with the Lenovo T61 at the moment and so far the video, sound, and biometric drivers have all failed with this error. We upgraded to SP2 from an existing SP1 R2 environment.
- editing the inf has not been a problem to me, but I think we should wait and see what the official workaround is going to be, hopefully we'll see that soon
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - Can only hope its soon,a client has just upgraded to SP2 and is in the process of Procuring about 8000Clients for this, across 12countries.... not exactly going to edit 4 models of H/W per country to facilitate this..... i hopeIf the drivers in the System prior to the Upgrade they still work, however new drivers wont :S
- I've got contact from MS in regards to this... let you know :-)
Hi All
I can't give you much of an update because Microsoft has asked me not to make some of the knowledge they have shared with me public at this stage. I can say that my open case with them is progressing well they have reproduced the issue and believe they have identified the root cause and are now working with the product teams to identify a workable solution. If you have this issue, my advice is to open a case with Microsoft. You may get offered advice to hack at the .inf files, reject that advice and ask for a solution to the root cause of the problem. There are also two other workarounds that I've been offered but they have other consequences that I don't want to deal with, but could be perfectly OK for your environments (these are the details I've been asked not to share at the moment, that's why I suggest you open a case with MS).
BTW - the .inf file hack they may give you seems to works, but I just believe it creates work that we don't need, and may create other problems down the road because it breaks the driver signatures, so I'm pressing for a 'better' solution.
I do have an ulterior motive in encouraging folks to open a case with Microsoft. The more evidence they can gather from customers about the problem and the impact it is having, the more likely that a solution will be delivered for all of us.
James.- Yup i agree, i've been given that option and rejected it.... working through both the connect options and also corporate contract support :-)heres hoping :-)
- so any idea of a real solution from Microsoft and a timeframe for us ?
my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064 - No, I haven't been able to tie them down on a timeframe yet. The answer I've been given by the support folks is they are working with the product teams and they will not know until the product folks can come up with some options. I haven't pushed hard on this as I have a lot of other development work to do around our Windows 7 SOE so can work around this for now.
- I just now ran into this issue "The selected driver is not applicable to any supported platforms" on SCCM SP2+R2 when adding W7 drivers. Has any one had any success or resolution from Microsoft?
- I am also seeing this issue. So far I haven't been able to import any Win 7 drivers.
- This issue is specific to running SCCM 2007 SP2 on windows server 2008 (you won't have it on windows server 2008 R2).
And for drivers that apply exclusively to windows 7.
You can fix it by either upgrading to windows server 2008 R2, or call microsoft support for hotfix KB 978754.
"Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm- Предложено в качестве ответаjsc.19 15 февраля 2010 г. 23:06
- Kim, I can't find anything from MS Website about KB 978754. I heard from my MS account manager that they are working on a hotfix for this, is hotfix 978754 that? have been released finally?
- It isn't public yet, but if you contact microsoft support they should be able to send it to you.
"Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm - Microsoft sent me a hotfix for this issue. You will need to ask them for it as it is still in testing.
It seems to have resolved the issue for me. It is KB306392 which obviously isn't up yet. Hmmmm.... Microsoft says there is no hotfix available on that KB number. It had been archived/yanked!
Was it KB306392 you requested?When I logged the call I mentioned KB978754 as per advice from others. However KB306392 was what was shown as "installing" when I installed the hotfix.
As I said the fix is still in testing but they seemed to have no issue giving it to me.
I have a 2008 SP2 server. Apparently the issue doesn't exist on 08 R2.- Any update? R2 isn't an option.
I've just come back from a month's break over Christmas (summer holidays here in Australia). While I was away Microsoft has provided a private hotfix for this problem and my initial testing is totally positive. As I mentioned above, Microsoft asked me not to share some of the initial workarounds they gave me. Since Kim has posted some details above, I can say that one of the offered work-arounds was to upgrade to Windows 2008 R2 or downgrade to Windows 2003. Nether of these were possible for me, but I'm sure that would work for some of you, but the hotfix seems a good solution.
The KB numbers I have are below. These are not public as far as I know so you will need to call Microsoft. As far as I know, there is no charge if you request assistance from Microsoft and a bug is the root cause of your problem. I certainly don't expect to be charged for my open case. My case does remain open, but only so I get notified when the public fix comes out so I can upgrade my SCCM infrastructure. I'll post here if/when I hear anything.
KB 979492 is the number in my email correspondence with MS
KB 306392 is the number in the name of the private patch I have been givenAny update? R2 isn't an option.
Contact PSS to get hotfix KB978754. It is now a "public" release internally and not published on the MS website yet. They gave me the fix and it has worked in my lab and did not require a restart. (I cannot install it in production until our next scheduled server maintenance date).
Nick Moseley - SCCM Admin http://t3chn1ck.wordpress.com- I had the same issues, contacted MSFT for KB978754 and attempted to install it. In both my Test and Prod enviornments the MSI did not install correctly, it simply would hang on the progress bar. Looking at the msi log it was as it attempted to stop WMI on the server. Out of dumb luck I happened to kill one of the msiexec threads and it magically made the "do you want to create a package/program window".
Looking at the msi it appears to only update osdcore.dll (i386 and x64). The driver import worked after the install. However I can't find any documentation on the client side patch that this creates "sccm2007ac-sp2-kb978754-x86.msp". Does anyone have any idea what this is for? I'm waiting for a response from MSFT. - The hotfix is now available: http://support.microsoft.com/kb/978754/en-us
- Предложено в качестве ответаnickmo 10 февраля 2010 г. 14:49
- I've removed the testing version of this and installed the final. It prompts to create a package for a client update.
Why is there a need to update the scmm client? What has changed here? - I was able to successfully import the drivers listed above (82567LM) using the ftp link from dell. I would submit to you that an update or hotfix is needed to correct your issue. HTH.
- All, a quick update.
Microsoft has now closed my case on this issue and have posted the following KB article and hotfix. This is a different approach than what is discussed by others above. I have been using a private version of this fix for a month or so and it solved the issue for me. I don't know the reason for the two approaches. I do know when I asked MS about the hotfix mentioned above that they said I should focus on KB979492 and not use KB978754. I don't know the reason (I didn't think to ask when talking the the tech at MS).
http://support.microsoft.com/kb/979492
FYI- Предложено в качестве ответаjsc.19 15 февраля 2010 г. 23:05
- Hi!
I also had this issue and installed the hotfix. Like the others here I am wondering what the sccm2007ac-sp2-kb978754-x86.msp (and the corresponding sw-package the patch creates in SCCM) is for. Do I deploy this to all clients? Do I just ignore it?
Please advice.
/TrondWH
