locked
Capture Media seems to remove Video Driver RRS feed

  • Question

  • Hello,

    i built a reference machine with Win7 Enterprise and all needed drivers.

    Than i used the Capture Media to build my .wim image of the machine without any problems.

    After distributing this image to another machine i recognized that the video driver

    which i had installed on the reference computer was missing.

    Any ideas for this behaviour ?

    thanks

    Stephan

    Thursday, February 23, 2012 4:26 PM

Answers

  • Couple of things:

    You can probably find drivers within the setup folders.  Look for INFs and if you see that, you have good drivers in the same folder structure of the INF.  I've done alot of HP deployments and have not found too many bad drivers.

    If all your hardware is the same, you can use PersistAllDeviceInstalls tag. http://technet.microsoft.com/en-us/library/ee832798(v=ws.10).aspx


    Jay Parekh | http://www.desktopguy.com

    Project Leadership Associates

    http://www.projectleadership.net

    • Proposed as answer by Sabrina Shen Tuesday, February 28, 2012 7:48 AM
    • Marked as answer by Sabrina Shen Thursday, March 1, 2012 5:17 AM
    Thursday, February 23, 2012 7:29 PM
  • Use the Windows Image Manager (part of WAIK tools) to create the unatttend.xml.  Since you're manually capturing, run sysprep as showen here. http://technet.microsoft.com/en-us/library/dd744512(v=ws.10).aspx#UsingAnswerFilesWithSysprep

    If you use the Build and Capture task to create, apply the file in the Apply Operating System task.


    Jay Parekh | http://www.desktopguy.com

    Project Leadership Associates

    http://www.projectleadership.net

    • Proposed as answer by Sabrina Shen Tuesday, February 28, 2012 7:48 AM
    • Marked as answer by Sabrina Shen Thursday, March 1, 2012 5:17 AM
    Thursday, February 23, 2012 9:23 PM

All replies

  • Any reason why you're not applying the driver package to apply drivers during deployment?  Will save you a lot of trouble and make your imaging process more dynamic.

    Jay Parekh | http://www.desktopguy.com

    Project Leadership Associates

    http://www.projectleadership.net

    Thursday, February 23, 2012 5:32 PM
  • Hi Jay,

    i´m not very experienced with osd.

    I am working with hp hardware and most of the drivers are "bad drivers" ( setup oriented ).

    It´s a pain to figure out the silent install switches for the different drivers.

    So i thought it´s easier to include all drivers in the reference computer.

    I know that the best way is to have a "hardware agnostic" image and

    to aplly the drivers during deployment.But that´s only true for handy drivers !??

    Do you know why the capture media process is removing the driver ?

    regards

    Stephan

    Thursday, February 23, 2012 7:22 PM
  • Couple of things:

    You can probably find drivers within the setup folders.  Look for INFs and if you see that, you have good drivers in the same folder structure of the INF.  I've done alot of HP deployments and have not found too many bad drivers.

    If all your hardware is the same, you can use PersistAllDeviceInstalls tag. http://technet.microsoft.com/en-us/library/ee832798(v=ws.10).aspx


    Jay Parekh | http://www.desktopguy.com

    Project Leadership Associates

    http://www.projectleadership.net

    • Proposed as answer by Sabrina Shen Tuesday, February 28, 2012 7:48 AM
    • Marked as answer by Sabrina Shen Thursday, March 1, 2012 5:17 AM
    Thursday, February 23, 2012 7:29 PM
  • I dont know if I am over stepping the bounds of this forum right now but there is a program called DoubleDriver. Run that on the reference machine to get all the files needed for the drivers you want then import them into SCCM and use a WMI Query in the task sequence to check the model and install those drivers. This allows you to make an OS image using VMWare Workstation, if you have it, or Microsoft Virtual PC that is almost driver free and can be used on ANY model PC as log as you have the drivers for them loaded into SCCM. Make sure that you only get the Non-Microsoft Signed drivers. Here is a screenshot of what I mean:

    Highlighted area is applying the FLAT OS without drivers, the stuff in the Red box is using a query to get drivers for the model you are asking for. In the option tab of your Apply Driver Package is where the query goes. Select Add Condition -> Query WMI and the following Query "select * from win32_computersystem where model like "821%"" - Minus the first and last "". 821% is the model number for the computer I am referencing. Also under the Properties of the Apply Drivers Package check "Do unattended installation......"

    Hope this helps.

    Thursday, February 23, 2012 7:37 PM
  • Good call.  I've used tools as well like Driver Backup http://sourceforge.net/projects/drvback and Driver Magician.

    Jay Parekh | http://www.desktopguy.com

    Project Leadership Associates

    http://www.projectleadership.net

    Thursday, February 23, 2012 7:46 PM
  • Thank´s for the very good hint.The tool "Double Driver" will solve my problems with the "setup based drivers".i am working with a hp 6730b notebook,which needs some system software like "hp quick launch buttons","hp 3d drive guard" .this is a setup and it´s hard for me to figure out the silent method in order to built a package.

    What would you recommend when you are dealing with only three different hardware models?

    For me it seem´s to be easier to build a single image for every model.Could be because i am osd beginner ;-)

    But then i stuck with this "removed video driver" after the capture media process.

    That´s the point to ask Jay ( thanks for your help),how can i use the  PersistAllDeviceInstalls command when i´m using a capture media?

    regards

    Thursday, February 23, 2012 8:57 PM
  • Many thanks for your hints.

    I don´t understand how i can use the PersistAllDeviceInstalls command when i´m using a capture media?

    regards

    Thursday, February 23, 2012 8:58 PM
  • What OS are you trying to Deploy? You may only be using 3 models now but that could expand and you may wish you did a flat OS and then applied drivers after the OS in the task sequence. It allows for setup time to be really minimal when getting new equipment.
    Thursday, February 23, 2012 9:00 PM
  • Use the Windows Image Manager (part of WAIK tools) to create the unatttend.xml.  Since you're manually capturing, run sysprep as showen here. http://technet.microsoft.com/en-us/library/dd744512(v=ws.10).aspx#UsingAnswerFilesWithSysprep

    If you use the Build and Capture task to create, apply the file in the Apply Operating System task.


    Jay Parekh | http://www.desktopguy.com

    Project Leadership Associates

    http://www.projectleadership.net

    • Proposed as answer by Sabrina Shen Tuesday, February 28, 2012 7:48 AM
    • Marked as answer by Sabrina Shen Thursday, March 1, 2012 5:17 AM
    Thursday, February 23, 2012 9:23 PM