+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 28
Windows 7 Thread, Windows 7 sysprep - argh! in Technical; Well thats just great. Spent a week setting up a nice Windows 7 image to dump onto our WDS server ...
  1. #1

    Join Date
    Mar 2007
    Posts
    421
    Thank Post
    14
    Thanked 16 Times in 10 Posts
    Rep Power
    19

    Windows 7 sysprep - argh!

    Well thats just great. Spent a week setting up a nice Windows 7 image to dump onto our WDS server so we can deploy it this summer and as soon as I run sysprep I get the 'a fatal error has occured sysprep cannot continue'

    No my nicely prepared 'donor' pc is useless, cannot login to the domain, cannot logon locally and I'm going to have to start all over.

    Argh!

  2. #2

    Join Date
    Jan 2008
    Location
    South West
    Posts
    1,819
    Thank Post
    217
    Thanked 266 Times in 216 Posts
    Rep Power
    68
    Sorry, I'm no deployment expert but I didn't think you had to sysprep a vista (thus Win7 machine) as the operating system is hardware agnostic? All you have to do is send an image to the wds using winpe.

    I started this last month but got stuck so I'd be interested if you could ouline your process.

  3. #3

    Join Date
    Mar 2007
    Posts
    421
    Thank Post
    14
    Thanked 16 Times in 10 Posts
    Rep Power
    19
    You still have to run the W7 version of sysprep (installed by default) to generalize it before you deploy it

    You're right though - one image is hardware independant, this image was a generic 'classroom' image

  4. #4

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,239
    Thank Post
    882
    Thanked 2,742 Times in 2,316 Posts
    Blog Entries
    11
    Rep Power
    784
    I have found the best way to do a true hardware independent image is to do the template in a virtual machine so no dodgey drivers can stuff it up (intel :angry. You can then just snapshot it before you run sysprep for easy rollback and editing, updating etc later.

    Remember you only get three syspreps with Vista/7 and yes you need to sysprep with generalize ticked to make it hardware non-specific.

  5. Thanks to SYNACK from:

    cookie_monster (16th March 2010)

  6. #5

    Join Date
    Jun 2007
    Posts
    10
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    16
    Actually that is not true... You can sysprep more than 3 times as long as the product is activated when you sysprep.

  7. #6

    Join Date
    Mar 2007
    Posts
    421
    Thank Post
    14
    Thanked 16 Times in 10 Posts
    Rep Power
    19
    I never did get to the bottom of why sysprep failed, but as it scuppered the whole installation it was better to start from scratch anyway. (It was currently activated at time of sysprep)

  8. #7

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,239
    Thank Post
    882
    Thanked 2,742 Times in 2,316 Posts
    Blog Entries
    11
    Rep Power
    784
    Quote Originally Posted by jkuzo View Post
    Actually that is not true... You can sysprep more than 3 times as long as the product is activated when you sysprep.
    Good catch: How Sysprep Works

    I have had issues with it not generalizing properly after the third time in testing though, it started to get stuff wrong like using uniprocessor rather than multiprocessor configuration which was not helpful so I prefer to keep it to a single sysprep if possible and VMs make this easy.

  9. #8
    eddyc's Avatar
    Join Date
    Aug 2008
    Location
    Bristol
    Posts
    438
    Thank Post
    99
    Thanked 47 Times in 43 Posts
    Rep Power
    22
    I had this issue last week - you MUST run sysprep as a domain administrator so that the computer account can be removed from the domain.

    I was gutted last week when this happened to me, three days of tweaking gone...

  10. #9

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,239
    Thank Post
    882
    Thanked 2,742 Times in 2,316 Posts
    Blog Entries
    11
    Rep Power
    784
    @GoldenWonder - Win 7 - sysprep fails - www.windows-noob.com this post might shed some light on its failing.

    I have also had issues with sysprepping a domain joined machine, if you have logged in with any domain accounts at all they need to be completely cleared from the users folder and registry before you sysprep otherwise that user will have profile issues when logging in on an imaged machine.

  11. #10

    Join Date
    Mar 2007
    Posts
    421
    Thank Post
    14
    Thanked 16 Times in 10 Posts
    Rep Power
    19
    I saw a few mentions about the wmp* processes but when I checked they weren't running.

    I was logged in as a domain admin at the time though.

  12. #11
    themightymrp's Avatar
    Join Date
    Dec 2009
    Location
    Leeds, West Yorkshire
    Posts
    1,256
    Thank Post
    218
    Thanked 231 Times in 200 Posts
    Rep Power
    74
    Whenever I've run sysprep, the setup machine has always been activated. After imaging I have had to re-activate every single time, it gives me 3 days to do it. Plus, yes you must be logged in as a Domain Administrator to run the sysprep correctly, unless you are installing software via the special 'Audit mode'.

  13. #12


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,800
    Thank Post
    231
    Thanked 883 Times in 759 Posts
    Rep Power
    300
    my problem is it keeps stripping out intel display drivers randomly (same as vista did) same sysprep file i used previously that diddnt its annoying

  14. #13

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,239
    Thank Post
    882
    Thanked 2,742 Times in 2,316 Posts
    Blog Entries
    11
    Rep Power
    784
    Quote Originally Posted by sted View Post
    my problem is it keeps stripping out intel display drivers randomly (same as vista did) same sysprep file i used previously that diddnt its annoying
    It will do that by default as the intel drivers don't get stored persistently in the driver store so that they survive a sysprep. The easiest way is to integrate them into the driver store of the image after you have captured as is outlined here WDS - Graphic Drivers

    When using MDT it is also trivial to add in all the required drivers to your distribution point which will also solve the issue.

    If all of your systems are hardware identical then you can sysprep without generalizing which will leave the drivers as they are however you loose the ability for an image to be used easily on multiple hardware types.

  15. #14


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,800
    Thank Post
    231
    Thanked 883 Times in 759 Posts
    Rep Power
    300
    Quote Originally Posted by SYNACK View Post
    It will do that by default as the intel drivers don't get stored persistently in the driver store so that they survive a sysprep. The easiest way is to integrate them into the driver store of the image after you have captured as is outlined here WDS - Graphic Drivers

    When using MDT it is also trivial to add in all the required drivers to your distribution point which will also solve the issue.

    If all of your systems are hardware identical then you can sysprep without generalizing which will leave the drivers as they are however you loose the ability for an image to be used easily on multiple hardware types.
    its just annoying that it does it about 50% of the time all or nowt i could cope with (by which i mean if i pull an image in school a it will have intel drivers but same in school b it wont rather than about half the pcs deployed get it)

  16. #15

    Join Date
    Jun 2007
    Posts
    10
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    16
    Quote Originally Posted by sted View Post
    its just annoying that it does it about 50% of the time all or nowt i could cope with (by which i mean if i pull an image in school a it will have intel drivers but same in school b it wont rather than about half the pcs deployed get it)
    Actually there is a line in the unattend file that you need to add to "Persist all device drivers install". This will solve your intel problem. Activation should happen automatically if your using the recommended KMS solution by microsoft and not trying to authenticate all machines with a MAK key.

SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. Windows 7 Sysprep File
    By tbharris09 in forum O/S Deployment
    Replies: 9
    Last Post: 15th March 2010, 09:21 PM
  2. Windows 7 Sysprep and Office 2003
    By mikeglover in forum O/S Deployment
    Replies: 0
    Last Post: 23rd February 2010, 08:33 AM
  3. Windows 7 Sysprep fun
    By Friez in forum Windows 7
    Replies: 11
    Last Post: 23rd November 2009, 08:17 AM
  4. Can I sysprep Windows XP Home?
    By zx2012 in forum O/S Deployment
    Replies: 9
    Last Post: 28th September 2009, 02:19 AM
  5. Replies: 14
    Last Post: 12th September 2007, 10:08 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
  •