+ Post New Thread
Page 2 of 2 FirstFirst 12
Results 16 to 21 of 21
Windows 7 Thread, Windows 7 and Imaging in Technical; Originally Posted by dhorowitz Alright, I have found the copy of Sysprep, however after completing the Sysprep (with generalize box ...
  1. #16

    Join Date
    Jan 2010
    Posts
    109
    Thank Post
    2
    Thanked 19 Times in 19 Posts
    Rep Power
    13
    Quote Originally Posted by dhorowitz View Post
    Alright, I have found the copy of Sysprep, however after completing the Sysprep (with generalize box checked) and uploading the image I had created with Ghost, Windows tells me that "Windows could not finish configuring the system. To attempt resume configuration, restart the computer." I restart the computer and I get the same thing. Good thing I took an unprepped image before I created my Sysprepped one. Anyone see this before or can tell me where I can see the logs and possibly look at whats causing this error?
    A Windows 7 or a Windows Server 2008 R2 image deployment process stops when you try to deploy the image on another computer

    I had the same problem with an image that would fail after sysprep and I wasn't including any of the things I'd seen flagged on forums as posssibly causing the issue (certain AV software, network printers etc). I rebuilt it for the umpteenth time and applied the hotfix this time round. Sysprepped and it worked first time.

    Edit: I should say although the KB article mentions deploying to another computer, I had the same issue with the sysprepped image on the reference machine and the hotfix cleared this up.

  2. #17
    themightymrp's Avatar
    Join Date
    Dec 2009
    Location
    Leeds, West Yorkshire
    Posts
    1,257
    Thank Post
    218
    Thanked 231 Times in 200 Posts
    Rep Power
    74
    Yes I know this is quite an old thread but I've just hit this problem.

    I prepared an image (thankfully only to be used on 4 machines) and on reboot got the error mentioned earlier. Tracked it down to the ESET anti-virus and have fixed it by doing the safemode method:

    Code:
    Open command prompt from the error screen with Shift + F10
    
    With Command Prompt open, execute the following
    
     
    bcdedit /set {default} safeboot minimal
    
    Reboot
    
    It WILL fail again!! Now undo what you did above with the following command and reboot:
    
    Bcdedit /deletevalue {default} safeboot
    To prevent it in future image creation (if you use ESET v5) then disable Self-Defense in ESET by entering Advanced Mode, going into Computer -> HIPS, uncheck the "Enable Self-Defense" box, restart the computer, and then do your sysprep.
    Last edited by themightymrp; 14th August 2013 at 03:14 PM. Reason: Modified method

  3. #18
    round2it's Avatar
    Join Date
    May 2009
    Location
    UK
    Posts
    1,036
    Thank Post
    205
    Thanked 156 Times in 113 Posts
    Rep Power
    40
    Don't put av software in your image.

    You could have problems later.

  4. #19

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,265
    Thank Post
    242
    Thanked 1,575 Times in 1,254 Posts
    Rep Power
    341
    These days there's WDS (Windows Deployment Services) or alternatively WinPE booting off a CD, which is compatible with numerous imaging products.

  5. #20
    free780's Avatar
    Join Date
    Sep 2012
    Posts
    1,059
    Thank Post
    45
    Thanked 86 Times in 81 Posts
    Rep Power
    23
    Its probably because you need the c++ runtimes on the image to install the drivers. MDT just makes things easier.

    Dont put an antivirus in the image. Its bound to screw sysprep. Use a virtual for capture. Use a wsus server for updates.
    Last edited by free780; 14th August 2013 at 06:58 PM.

  6. #21
    Ben-BSH's Avatar
    Join Date
    Jun 2009
    Location
    UK
    Posts
    218
    Thank Post
    92
    Thanked 35 Times in 27 Posts
    Rep Power
    22
    I've also had many broken images before i realized putting NOD32 on a master image PC simply means headaches!.

    If you want, Ive got a runonce reg script somewhere, which installs NOD and uses a config file you specify (network reachable - or local) on first boot. - works like a charm, built it when i last had that issue.

SHARE:
+ Post New Thread
Page 2 of 2 FirstFirst 12

Similar Threads

  1. Imaging Windows 7 Machines
    By stevo1565 in forum Windows 7
    Replies: 10
    Last Post: 21st April 2010, 12:29 PM
  2. **Imaging Windows XP/Vista on Intel Mac**
    By Rozzer in forum O/S Deployment
    Replies: 14
    Last Post: 15th February 2010, 11:43 PM
  3. Imaging Windows 7
    By Newton in forum Windows 7
    Replies: 3
    Last Post: 18th November 2009, 10:33 PM
  4. Imaging and Windows VLK
    By rocknrollstar in forum O/S Deployment
    Replies: 39
    Last Post: 22nd July 2009, 06:30 PM
  5. Windows Imaging... has it got a bit confusing?
    By gshaw in forum O/S Deployment
    Replies: 4
    Last Post: 24th March 2009, 09:35 AM

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
  •