none
SCCM 2012 SP1 drivers are not installed

    Frage

  • Hi

    I've the problem that drivers are not installed by PXE staging. I'm 100% sure I've the correct drivers. I've installed them over a pendrive without any problem but, SCCM doesn't install any driver, also I receive no error message. I see that the drivers are downloaded during the staging process but after the driver installation step nothing is installed. I have this problem on all hardware types and devices. It's ever the same. The task sequenze is also correct. We checked that again and again.

    First I loaded the whole driver package (including all drivers for this hardware tag) => dosen't work.
    Have deleted all drivers and assigend just the exact network driver to the categorie ==> dosen't work.

    Had also an SCCM specialist in the house which analyzed this issue but, he also cannot explain what could be the reason. He has never seen such a problem and he has installed a lot of SCCM2012 environments.

    Has anyone an idea or maybe similar problems?

    Thank you!
    Sacha

    Mittwoch, 30. Januar 2013 09:11

Alle Antworten

  • How are the drivers installes? Apply Driver Package (plus WMI conditions)? Auto Apply Drivers? What about the status messages for the deployment? What about smsts.log and the Windows Setup logs? Which OS is going to be installed? You have to provide as much details as possible.

    Torsten Meringer | http://www.mssccmfaq.de

    Mittwoch, 30. Januar 2013 09:26
  • Hi,

    I have the same problem. SP1 seems to have some bugs with the driver installation. Task Sequences that worked before the update fail with SP1.At found  workaround in the forum by using an unattend file (http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/d62fde47-27da-4ce9-8c0a-8560d7625ccc) but this is not the final solution.With this unattend file drivers are injected but there are other problems.

    You have to use two section for drive C: and D: in the unattend file if you have a BDE drive otherwise it will not work.

    Sometimes the windows setup fails because the setup was not able to parse some inf files but after I removed this drivers and this error is solved the installation stops with the funny error 0x80004005.

    At the moment I stopped all my projects and I think I have to open a call at Microsoft. I think they have only tested this part with virtual machines or Windows 8. Virtual machines without the need of installing drivers are working. Just if I need to inject drivers the installation will fail.

    I apply the drivers with WMI query and only use driver packages.

    regards

    Christoph

    Freitag, 1. Februar 2013 07:42
  • I think this might be the same issue as what i am experiencing, i have also tried recreating the task sequence without much luck. As SP1 has the boot image for Windows 8 (MARMITE), it could be the case that we require a windows 8 compatible driver. This is my next course to try.

    I have my smsts-time-date.log if you feel it would be of any use.


    Regards James Loker-Steele http://www.lokersteele.co.uk/

    Freitag, 1. Februar 2013 12:10
  • Hi,

    I have had the same issue when updating from SP0 to SP1.

    There were two things which i had to consider.

    1. Installation with Operating System Image (THICK Image)

    I used a THICK Image to deploy Windows 7 with all the business applikations.

    With the Image createt from SCCM 2012 SP0 the Task Sequence run the apply Image action and the apply driver action. After this the install prozess gave up and did not report any error.

    1. Solution

    I had to recreate the THICK Image. The new created Image did the job correctly.

    2. Installation with Operating System Installers (setup.exe)

    When using the classic unattended setup you can not use it with SCCM 2012 SP1 anymore.

    Configmgr SP1 : Windows 7 deployment is not supported anymore from the setup.exe

    http://scug.be/sccm/2013/01/13/configmgr-sp1-windows-7-deployment-is-not-supprted-anymore-from-the-setup-exe/

    2. Solution

    You now have to use the original install.wim with the Operating System Image Method.

    There must be a Task Sequence Variable set before the "Apply Operating System" to force the installation to be done to the C drive.

    OSDPreserveDriveLetter=False

    I hope this can help you to solve your issue.

    Regards

    Thomas

    Montag, 4. Februar 2013 11:39

  • 2. Installation with Operating System Installers (setup.exe)

    When using the classic unattended setup you can not use it with SCCM 2012 SP1 anymore.

    Configmgr SP1 : Windows 7 deployment is not supported anymore from the setup.exe



    I don't know if it's no longer supported, but it can still be done though. You cannot select an "OS installer" when using the wizard to create a new task sequence, but you can chance it later on. See http://technet.microsoft.com/en-us/library/jj591552.aspx#BKMK_WhatsNewSP1_Software: "The build and capture task sequence was updated to apply an operating system image instead of running Setup.exe for installation. You can still run Setup.exe for Windows 8 deployments by editing the task sequence in the task sequence editor. The build and capture task sequence was updated to apply an operating system image instead of running Setup.exe for installation. You can still run Setup.exe for Windows 8 deployments by editing the task sequence in the task sequence editor."

    Torsten Meringer | http://www.mssccmfaq.de

    Montag, 4. Februar 2013 11:55

  • I don't know if it's no longer supported, but it can still be done though. You cannot select an "OS installer" when using the wizard to create a new task sequence, but you can chance it later on. See http://technet.microsoft.com/en-us/library/jj591552.aspx#BKMK_WhatsNewSP1_Software: "The build and capture task sequence was updated to apply an operating system image instead of running Setup.exe for installation. You can still run Setup.exe for Windows 8 deployments by editing the task sequence in the task sequence editor.

    Torsten Meringer | http://www.mssccmfaq.de

    Hello Torsten,

    for Windows 7 i can tell that the setup.exe installer is not supported.

    I have tried to install Windows 7 x64 with setup.exe and a driver package and you always get ERROR 31 (boot critical driver could not be installed) inside the windows install log setupact.log.

    At the end i had nearly no driver inside the driver package and there was no boot critical driver inside.

    Same driver package with the Operating System Image Method did work as expected.

    I think it has something todo with WinPE4 and the new ADK, but i have no proof of that for now.

    Regards

    Thomas

    Montag, 4. Februar 2013 12:50
  • Hello Thomas,

    If you try to install Windows 7 x64 from setup media and only use a minimal set of drivers you will see that it work.

    I was able to install the system without an error if I only use the network driver. If I take the driver package that works woth SCCM 2012 RTM the installation will fail with ERROR 31. I have opened a call at Microsoft for this problem. I had the same problem also with THICK images.

    There seems to be an error in the driver injection process of SCCM.

    regards

    Christoph

    Montag, 4. Februar 2013 16:43
  • Hello Christoph,

    What did Microsoft say, can you post the ticket nummer and pm it.


    Andre van den Berg

    Mittwoch, 13. Februar 2013 12:39
  • Hello Andre,

    I got now an answer from Microsoft. It really seems like the setup installation is no longer supported for Windows 7 like Thomas said.

    The better formulation in the WhatsNew in SP1 (http://technet.microsoft.com/en-us/library/jj591552.aspx#BKMK_WhatsNewSP1_Software) would be:

    The build and capture task sequence was updated to apply an operating system image instead of running Setup.exe for installation. You can only still run Setup.exe for Windows 8 deployments by editing the task sequence in the task sequence editor.

    First I thought this would be a joke but seems so. I was able to very that it will work if you use an image. With the image all drivers were installed and the task sequence ended without any error.

    I loaded the install.wim from the original CD as image install and used the OSDPreserveDriveLetter setting like Thomas said.

    I asked Microsoft for an official statement if this install type would be supported by Microsoft or what the recommended way is to create the golden image by using SCCM. At the moment I’m waiting for the final answer. I don’t want to use unsupported installation methods for my customers.

    I will post the answer from Microsoft after I got it.

    We all could be happy that we now have Windows 8 and all Company want to install Windows 8 at all systems otherwise we have to wait until we get a supported way. ;.)

     

    regards

     

    Christoph

    Freitag, 15. Februar 2013 18:02
  • Christoph,

    Any response on this one?  I was wondering if you determined the best methodology:

    -Edit the unattend file

    -Use the install.wim

    -some other workaround

    Thanks!

    Donnerstag, 28. August 2014 18:55
  • What issue are you talking about exactly? What's (not) happening? Please add some details. Thanks

    Torsten Meringer | http://www.mssccmfaq.de

    Donnerstag, 28. August 2014 19:11
  • When creating a "build and capture" image - you get an error 31 because no network driver was applied (the apply drivers task is not being recognized by the setup.exe process during the operating system installers).

    It appears from this thread people have come up with various workarounds - but no formal response was made for Windows 7.  I ran into the same error, and worked around it by adding c:\_smstasksequence\drivers to the unattend.xml for now.

    Thanks!

    Donnerstag, 28. August 2014 19:39
  • When creating a "build and capture" image - you get an error 31 because no network driver was applied (the apply drivers task is not being recognized by the setup.exe process during the operating system installers).


    Why don't you use the .wim instead of setup.exe?

    Torsten Meringer | http://www.mssccmfaq.de

    Donnerstag, 28. August 2014 19:52
  • My Thoughts on it:

    1.  Because I have built images with ConfigMgr for 7 years across several versions and service packs and have ALWAYS been able to use the Build & Capture a reference operating system image.  Seemed a bit silly that Microsoft would suddenly drop support of using that feature (and leave it in the console).

    2.  Because using the install.wim felt a bit "non-supported" - and with no formal documentaiton on that methodology on technet or on microsoft sites - it did not feel like the correct methodology.

    If the community has moved to just selecting the install.wim from the source media as the permanent solution for windows 7 - we'll just do that during our next "build and capture" task for windows 7.  Just didn't want to start moving in a path that was undocumented and possibly unsupported.


    • Bearbeitet Beamer25 Freitag, 29. August 2014 13:36 reword
    Donnerstag, 28. August 2014 20:01
  • Figured i should put up a final response to my question since I've figured out several good methodologies for this now:

    1.  Using Windows Setup Method:  so if you want to use Windows setup (like I had been so eager to use) - you simply have to add an unattend.xml file with the drivers path being c:\_SMSTaskSequence\Drivers in the OfflineServicing phase.  Then of course import the Unattend.xml as a package and add it to the OS task in the task sequence.

    2.  Use the Install.wim (as stated above).  This is highlighted in a brief statement in the SP1 upgrade documentation: 

    In this case, while it is not documented well in the technet documentation, you simply find the install.wim under the ..\sources folder.  Just remember the OSDPreserveDriveLetter=False, and/or partition steps for making windows end up on c:.

    I'm guessing the inclusion of the note on What's new in SP1 makes this method the new approved method for Configmgr to deploy Windows 7 - so I feel confortable using method 2.  Option 1 does work fine as well, since the issue is really just about drivers being located during the mini-setup steps.

    Thanks!

    • Als Antwort vorgeschlagen Beamer25 Mittwoch, 1. Oktober 2014 20:38
    Mittwoch, 24. September 2014 18:30