+ Post New Thread
Results 1 to 9 of 9
Windows 7 Thread, Sysprep nearly working but drivers going? in Technical; Hi All, I have been struggling for over a week trying to sysprep a windows 7 machine. Where it seemed ...
  1. #1
    reggiep's Avatar
    Join Date
    Apr 2008
    Location
    In the vast area of space and time
    Posts
    1,550
    Thank Post
    518
    Thanked 56 Times in 50 Posts
    Rep Power
    30

    Sysprep nearly working but drivers going?

    Hi All,
    I have been struggling for over a week trying to sysprep a windows 7 machine. Where it seemed so simple on XP it seems a never ending job on 7.
    I thought I had cracked it as I managed to get a sysprep to run and the machine came back on without any errors BUT the graphics driver disappears.
    I had a quick read about PersistAllDevices so added that to my answer file, with true, but I had an error when sysprepping then.
    Can anyone suggest what command would be best when running sysprep so that drivers do not disappear?

    At the moment i currently run...

    Code:
    sysprep.exe /generalize /oobe /shutdown /unattend:c:\windows\system32\sysprep\unattend.xml
    All I want is an image that will go on 70 netbooks that are all identical, can I get rid of the generalize?

    Thanks

  2. #2

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,269
    Thank Post
    884
    Thanked 2,747 Times in 2,321 Posts
    Blog Entries
    11
    Rep Power
    785
    Getting rid of the generalize is not a good idea as then the Windows Update and Machine UIDs remain the same, this does not affect their ability to all co-exist and join AD but will cause issues with WSUS not seeing all the laptops at once and also it shows up as a single computer under KMS so that can mess with your activation count and prevent activations.

    You can reset a small chunk of this by using slmgr -rearm on them afterwards but this only mitigates some of the issues. There may be other issues that I am unaware of but those are the main ones that will bite immediatly.

    Not sure about the command to do it propperly as all of our images now just run off MDT so all drivers needed are injected during the imageing which takes a little longer but negates the need for the non-driver-killing sysprep.

  3. #3
    reggiep's Avatar
    Join Date
    Apr 2008
    Location
    In the vast area of space and time
    Posts
    1,550
    Thank Post
    518
    Thanked 56 Times in 50 Posts
    Rep Power
    30
    Thanks for the help there Synack,
    My problem is that we don't have Server 2008 R2 at the moment so are relying on our FOG server to pump out images to our clients.
    I won't bin /generalize just yet then, I'll keep on looking for ways to keep the drivers.

  4. #4

    Join Date
    Jun 2009
    Location
    Poole
    Posts
    148
    Thank Post
    4
    Thanked 40 Times in 30 Posts
    Rep Power
    21
    According to the 70-680 exam book you need to set the PersistAllDeviceInstalls setting in Microsoft-Windows-PnpSysprep to True in your answer file.

  5. #5

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,269
    Thank Post
    884
    Thanked 2,747 Times in 2,321 Posts
    Blog Entries
    11
    Rep Power
    785
    Quote Originally Posted by reggiep View Post
    I had a quick read about PersistAllDevices so added that to my answer file, with true, but I had an error when sysprepping then.
    What was the error you got?

    Another way to do this would be to add the required drivers to a folder on the c: of the image and add it as a driver search path in your answer file, this should have the same affect as the MDT version that I use allowing you to do a generalize and also not requireing WDS and MDT.
    Add a Device Driver Path to an Answer File

    Ycan use MDT on a non server OS to build a Deployment share, the only thing you loose by not having it on a server is PXE network booting and multicast support. It will still generate ISOs that connect to the network and run the deployment in unicast mode. Probably not what you're after but could be useful for making the base images quickly and easily.

  6. Thanks to SYNACK from:

    reggiep (8th July 2010)

  7. #6

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    16,308
    Thank Post
    901
    Thanked 1,797 Times in 1,548 Posts
    Blog Entries
    12
    Rep Power
    466
    Hi

    I am just wondering what solution worked best for you in the end please?

    Thanks

  8. #7

    Gatt's Avatar
    Join Date
    Jan 2006
    Posts
    6,806
    Thank Post
    880
    Thanked 684 Times in 453 Posts
    Rep Power
    505
    Not sure about the "PersistAllDevices" - though worth setting it if the following doesn't work (I haven't set it and this works for me!)

    Sysprep into Audit Mode with Generalize set
    Then, when it reboots into Audit Mode, Sysprep as the OP is trying

    BTW, I have found that as long as there is a file called unattend.xml in the sysprep folder yiou dont need to specify an unattend file - it automatically detects it and uses it..

  9. #8

    Join Date
    Nov 2008
    Location
    Chelmsford, Essex
    Posts
    144
    Thank Post
    8
    Thanked 21 Times in 14 Posts
    Rep Power
    16
    We use the "PersistAllDevicesInstalls" tag in an XML file. Works wonders when you want a universal curriculum image with multiple drivers from different types and brands of workstation.

    Code:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
        <settings pass="generalize">
            <component name="Microsoft-Windows-PnpSysprep" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
                <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
            </component>
            <component name="Microsoft-Windows-Security-Licensing-SLC" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <SkipRearm>1</SkipRearm>
            </component>
        </settings>
    </unattend>

    To make the process easier, I copy a batch file across to run and that picks up the sysprep.xml I saved from the code above. The "SkipRearm" stops the machine resetting the operating systems and counting down 5 rearms limit rule. Our XML code that's applied to the image itself changes the product code if we need to use MAK instead of KMS.

    Code:
    sysprep /quiet /generalize /oobe /shutdown /unattend:sysprep.xml

    Hope this helps anyone trying to do this in future. This has worked since the early days of deploying Vista.
    Last edited by Tunster; 26th October 2010 at 04:53 PM.

  10. #9


    Join Date
    Feb 2007
    Location
    51.403651, -0.515458
    Posts
    9,607
    Thank Post
    250
    Thanked 2,898 Times in 2,131 Posts
    Rep Power
    828
    Quote Originally Posted by SYNACK View Post
    Another way to do this would be to add the required drivers to a folder on the c: of the image and add it as a driver search path in your answer file, this should have the same affect as the MDT version that I use allowing you to do a generalize and also not requireing WDS and MDT.
    To elaborate on Synack's suggestion a little further, you can find a complete answer file which does this here.



SHARE:
+ Post New Thread

Similar Threads

  1. Sysprep not adding drivers when WDS is used
    By eean in forum Windows Server 2008
    Replies: 2
    Last Post: 26th March 2010, 04:55 AM
  2. Drivers, sysprep and Mini Setup
    By sparkeh in forum O/S Deployment
    Replies: 1
    Last Post: 13th October 2009, 12:44 PM
  3. strange nic lights working/not working
    By browolf in forum Wireless Networks
    Replies: 13
    Last Post: 15th December 2008, 02:50 PM
  4. Sysprep
    By tosca925 in forum Windows
    Replies: 14
    Last Post: 7th April 2006, 02:53 PM
  5. Why isn't sysprep working?
    By Ric_ in forum Windows
    Replies: 10
    Last Post: 16th January 2006, 04:00 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •