Windows 7 with fog- DRIVERS

Discussion in 'General' started by andyroo54, Jan 18, 2012.

  1. andyroo54 Community Manager


    So I've tried searching but can't find much. If someone could point me in the right direction that would be good. Currently we have a win XP sp3 soe that deploys and scans hardware then gets drivers. This was all setup by the person that worked here previously. He has done a very good job with Xp, and we will continue to use that SOE for some time on older hardware. Fog is great for this.

    But I've just started working on a win 7 image. I want to have it cut down as possible, without all the drivers in the image. So I understand that it's possible that during sysprep you can tell the image to search a certain location for drivers, so I would have a file share with the drivers packs on it.

    So this is what I'm hoping to do, I'm building the image up as a VM. I have tried to find some info on it but it is fairly scattered. Most people I talk to use MDT or similar.

    While writing this I've just found a link to this wiki;

    I've read through it and looks like it might solve my problem. But I'd still like to get some thoughts and any suggestions to make the process smooth. I will also post anything up I encounter! If there is a better section for this please move as I'm new and wasn't sure if this was the right section..

    This looks like a good guide too, will have to do some reading!

    Thanks, !!!!
  2. ssx4life Member

    There are several ways around this if you are wanting to add more driver support. But one of the best ways to make your image more compatible with all systems is to have your unttended.xml support as many CPU types as possible.

    The other thing I've done is created a snapin for driverpacks that gets pushed on first reboot using the foservice (you could also script it into your image). Basically you take the driverpacks and make a standalone installer, and then use SFX Maker to encapsulate it and auto run the script in windows)

    Check it here -

  3. andyroo54 Community Manager

    Hi, which part of the componets do you configure to support all CPU types? So you can't make the computer point to a network file share during imaging for drivers?
  4. ssx4life Member

  5. andyroo54 Community Manager

    HI yes I've seen that but he doesn't explain how he does drives, he just installs them in the image. How do all the Fog guys do it?

    Also another stupid question, I've made my unattend XML file, but where do I put it? Do I put it into the C: drive AFTER I've created the VM and running in audit mode??
  6. Ahmed New Member

    i am using windows 7 with multiple hardware support. i run 2 phases, the first phase is the sysprep with audit mode and audit.xml where i point the drivers in the audit.xml. after running sysprep with audit mode, i just generalize the imgae with the unattend.xml and generalize command. i put all the drivers in a folder in the root of driver C: but you can point it to what ever place you want. both the audit.xml and unattend.xml are placed in the c:\windows\system32\syaprep and i advice putting a script to delete the unattend.xml file on first boot.

    the audit.xml file contains only this part
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="auditSystem">
    <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="" xmlns:xsi="">
    <PathAndCredentials wcm:action="add" wcm:keyValue="6873ff00">
    <cpi:eek:fflineImage cpi:source="catalog:windows 7 enterprise.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    the only part that you may want to change is the "C:\drivers" and dont forget the processor architecture. you can put all your drivers there. i usually sort them after model type and hardware type.
  7. andyroo54 Community Manager


    So I'm just trying to understand why you have that seperate "audit.xml" file? I've made my unattend.xml file, and I've got this as part of the unattend:
    Then I choose driver paths,
    Then I set the path and network credentials, but this didn't seem to work.

    Does this have to be seperate in the "audit.xml" file?
  8. Ahmed New Member

    you need definitely to seperate the xml files. it didn't work for me when i chose one xml file. as running the audit mode with unattend.xml will run some of the settings that should be run on the generalize mode and i lost one of the administrator logins " i have 3 logins after the generalize". i dont know why but it worked for me when i separated the files.
  9. andyroo54 Community Manager

    Hi Ahmed,

    Thanks, so you have one unattend.xml, then do you put the audit.xml in the same location as the unattend.xml? and add it to the script? So the audit and unattend files go to the C:\windows \system32\sysprep? Should that be syswow for 64 bit? Ok so you specify that I should have sepeate xml for driver yes?

    So this is currently the components I had set for drivers, in my original unattend.xml.

    Are you saying I should remove them, and create a new file called audit.xml and add the same components as below in the picture, and that should work?

    Attached Files:

  10. Ahmed New Member

    as i said before. i am using 2 xml files "audit.xml and unattend.xml" and both are in "C:\windows \system32\sysprep" and i am using 2 patch files audit.bat where i have this command "C:\Windows\System32\sysprep\sysprep.exe /audit /quit /unattend:C:\Windows\System32\sysprep\audit.xml" after running the audit.bat the sysprep will import all the drivers into the system and then boot windows, at that point it will show you the GUI of sysprep just close it. i run the other phase of sysprep oobe.bat "C:\Windows\System32\sysprep\sysprep.exe /generalize /quit /unattend:C:\Windows\System32\sysprep\unattend.xml"
    and here everything is getting done for deployment. why would you put your drivers into WinPE ??? you should put them into the Audit phase "look at my audit.xml" in the previous post. anyway it depends on your deployment method. this process is working for me and may be there are other ways out there but i couldnt find any better than this. i attached a copy of my audit.xml just try it and see if it works for you. as i said before just change the path to the drivers and the architecture.

    Attached Files:

Share This Page