locked
Importing Win 7 Drivers - .inf files RRS feed

  • Question

  • Is anyone having any problems importing Windows 7 drivers into ConfigMgr Sp2?  I have download a number of  Windows 7 drivers from Dell and Lenovo and SCCM SP2 (RC) reports that the driver does not contain any supported platforms.  Checking the .inf files shows that the Windows version is specified as NTx86.6.1.1.  Other Win 7 drivers that are importing OK specify version NTx86.6.1.

    I am not running SP2 RTM just yet so I am not sure if this is a ConfigMgr SP2 RC issue or whether incorrect version information has been put into the INF files.  Most of the incorrect ones seem to be Intel drivers.

    Is anyone else having similar problems?

    Thanks.

    Tuesday, November 3, 2009 9:26 AM

Answers

  • 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
    Thursday, January 14, 2010 8:11 AM

All replies

  • i think everyone has upgraded to the Final release of SP2 and unless someone on Connect is reporting this problem, you should do the same

    cheers
    niall
    my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
    • Marked as answer by Yog Li Wednesday, November 11, 2009 9:11 AM
    • Unmarked as answer by Mark_Thomas Wednesday, November 11, 2009 9:25 AM
    Tuesday, November 3, 2009 10:04 AM
  • We have now upgraded to the RTM release of Sp2 and still have the same issue.  Initially we upgraded from RC to RTM and then when the issue still occurred we did a complete reinstall with the RTM version (SP1 RTM + R2 + SP2 RTM).  Since discovering the issue we have upgraded another SCCM test lab to SP2 RTM and it is working fine.  The same driver that fails to import in the first lab imports successfully in the second.  The only difference between the two environments is that the one that is failing is running Windows Server 2008 x64 with remote SQL 2008 (x64).  The working site is running Windows Server 2003 x86 with remote SQL 2005 (x86).

    Thanks,

    Mark.

    Wednesday, November 11, 2009 9:33 AM
  • most likely an SQL server issue then, is it sql server 2008 sp1 ?
    my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
    Wednesday, November 11, 2009 10:01 AM
  • Hi Niall,

    It is SQL 2008 SP1.  Not sure about post SP1 updates, will check.

    Mark.
    Wednesday, November 11, 2009 11:13 AM
  • We have exactly the same problem in our POC environment, any suggestions for how to solve this issue?

    SCCM R2 SP2 upgraded from RC, Database2008 sp1,
    Only the drivers with NTX86.6.1.1 inf files has this problem
    It is possible to change the inf file manually and import the dirvers, but than the driver is useless in SCCM, it becomes Un-Singned because of the modification made to the INF file.
    The version of the OSDCORE.dll files in all catalouges on the SCCM server is 4.0.6487.2000
    Here is the log from the SCCM server:

    <![LOG[Initializing driver digest from '\\sccmserver01\e$\SCCMDriverSource\nic\intel\10.0.6.0\w7_32\E1Y6232.inf']LOG]!><time="11:30:27.811+-60" date="11-19-2009" component="DriverCatalog" context="" type="1" thread="2084" file="osddriverdigest.cpp:2607">

    <![LOG[\\sccmserver01\e$\SCCMDriverSource\nic\intel\10.0.6.0\w7_32\E1Y6232.inf is not applicable to any supported platforms.]LOG]!><time="11:30:28.150+-60" date="11-19-2009" component="DriverCatalog" context="" type="3" thread="2084" file="osddriverdigest.cpp:2811">

    <![LOG[Driver is not applicable to any supported platforms. Code 0x80070661]LOG]!><time="11:30:28.152+-60" date="11-19-2009" component="DriverCatalog" context="" type="3" thread="2084" file="osddrivercatalog.cpp:838">

     


     

     

    • Edited by Haruna Thursday, November 19, 2009 3:42 PM
    Thursday, November 19, 2009 2:09 PM
  • i tested this by importing the dell e6400 NIC driver for windows 7 X86, it failed like yours for the first attempt

    i then edited a filed called E1Y6232.inf and found the lines

    change

    [Manufacturer]
    %Intel%     = Intel, NTx86.6.0, NTx86.6.1.1


    to

    [Manufacturer]
    %Intel%     = Intel, NTx86.6.1.1


    savev the file and it imports just fine into SCCM

    can you try this please ?


    my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
    Thursday, November 19, 2009 2:47 PM
  • Thx Niall
    but as I mentioned in my previos reply It is possible to modify the inf file and import it in to SCCM, but the driver becomes useless during the installations since it becomes an Un-Signed driver because of the modification that we do to the INF file.
    Any other ideas?
    I think the difference between the RC version and the RTM regarding driver imports is osddriverdigest.cpp , in RC it seems to check 3 digits of the OS version number but in the RTM it checks for the first 2 digits and ingnores the other digits in the INF file.
    What can we do to replace
    osddriverdigest.cpp with the RTM version? the SP2 RTM installation does not seem to change all the RC binaries.
    Thursday, November 19, 2009 4:04 PM
  • i don't think this is windows 7 specific or even os specific, look at this old Vista/XP thread referencing practically the same issue

    my suggestion would be to download the Intel version of this driver from intels website and see can you import it, please let us know the results of that... or wait until Dell releases edited INF files or use your own INFs


    my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
    Thursday, November 19, 2009 5:34 PM
  • I'm not sure that the drivers are at fault... as I said in one of my earlier posts we have another SCCM lab where the same driver is importing fine.  This lab has never been deployed using RC code.  It started out as RTM, then SP1 RTM, then R2 RTM and now SP2 RTM.  What is weird is that we have reinstalled SCCM in the lab which is failing to import the driver using only RTM code and it still fails...  We did not re-install the site server OS, just a complete uninstall of SCCM RC and then reinstall using the RTM code.  Perhaps there was some RC code left somewhere, not sure.

    Niall - has the environment where you replicated the issue been upgraded from SP2 RC to RTM also?

    Mark.
    Thursday, November 19, 2009 6:35 PM
  • yup it has, and of course that is not a supported scenario. but i dont think that is where the issue lies... have you verifed how your other server is setup ?
    my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
    Thursday, November 19, 2009 8:04 PM
  • Ok, but does anyone have any suggestions for how to solve this driver import issue? on the systems that are upgraded from RC to RTM?
    Reinstalling all the servers and SCCM R2 with SP2 from scratch again would be too expensive for the project, any ideas?
    Friday, November 20, 2009 1:21 PM
  • There is another thread on this topic here:

    http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/553320f0-781c-46cb-8a48-3030298018f3

    As I post this there is no answer there either
    Thursday, November 26, 2009 2:08 AM
  • FYI, i downloaded the intel drivers today for the same error today and receive this error still....
    Tuesday, December 8, 2009 4:15 AM
  • 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
    Thursday, January 14, 2010 8:11 AM
  • You can fix it by either upgrading to windows server 2008 R2, or call microsoft support for hotfix KB 978754.
    ... or just download it from http://support.microsoft.com/kb/978754/en-us, because it was just released ;-)
    Wednesday, February 10, 2010 12:58 PM