Restoring image freezing computer



  • Anyone have any issues with specific models of pc’s failing to restore/download a master image because they freeze at certain points during the image process?

    I know my FOG installation is working correctly because I have a HP desktop that I successfully imaged. However, I have a Acer Veriton running 32 bit Windows 7 that fails. It will start the image restore process, but freezes at random intervals or reboots before imaging is complete.



  • Maybe my input might help here because i have had the same issues as some listed here
    This is my process start to finish (Single partition NTFS only, Resizable)

    I install Windows 7 from a CD, when i get to the point where i see the partitions listed i delete all partitions and click next ( At this point you do have a option to create a partition first but i dont because i have had issues before)
    Once windows is installed i make sure all drivers are installed and the machine has ran Windows updates, i then install my software till i feel the machine is ready for Upload

    Now at this point i have my XML file already configured and copied to the Sysprep folder
    So all i do is run the FogPrep
    Run the command prompt with Elevated rights and type in the following command and also assuming you are in the c:/
    cd windows/system32/sysprep/
    sysprep.exe /generalize /oobe /reboot /unattend:%windir%\system32\sysprep\unattend.xml "press enter"
    at this point the sysprep is now running and upon reboot ( at this point you should have set the server to upload this machine) it will connect to the fog server and upload

    If a machine is not sysprep’d correctly it will 90% of the time break before it even started up
    [COLOR=#ff0000]“Whether I run fogprep or sysprep or neither, FOG is breaking my master boot record somewhere along the way. I created a bare bones image from a clean install, uploaded it and tried deploying it and it fails”[/COLOR]
    Now Fogprep and Sysprep is totally different, so make sure when you run the Sysprep you do it with elevated rights ( it does make a difference)

    Hope this helps…


  • Moderator

    When I have tried to do my Windows 7 images, I have been unsuccessful in using the Single-Partition (NTFS Resizable) option. I do a sysprep early on, but mainly for the copyprofile feature. I then complete the setup and finish customizing the computer to the point of installing all our software and updates and updates and more updates to the point I’d be ready to give the computer to the end user, ready for them to log on. This is when I take an image to FOG using the Windows 7, Single Disk Multiple Partition. It works without problem for me.

    I am in a school district with a Volume licensing agreement using a MAK, so there is no need to force every user to go through the 45 minute setup process after sysprep completes.


  • Moderator


  • Moderator

    not sure if you have done this but I would recommend setting your master pc to IDE in the bios storage config -> then installing a fresh windows 7 (basic install let it create the 100mb partition)-> defrag (I use defraggler) then run chkdsk /f and reboot the machine again once this has finished -> then log in and run sysprep (with generalise+OOBE) -> then uploading it. then deploy it to a pc and make sure before your start the deploy that the pc is set to IDE in the bios

    edit: when you create a new image definition on the fog server set to Windows 7 + Single Partition re-sizable



  • Whether I run fogprep or sysprep or neither, FOG is breaking my master boot record somewhere along the way. I created a bare bones image from a clean install, uploaded it and tried deploying it and it fails. The only other thing I can think of is that I’m selecting the wrong choice for my image partition, but I thought I read in these forums that you don’t have to count the 100mb partition from windows when making that choice. So for my image I selected single partition. It resizes the partition correctly according to the output during the upload process. Do I just have a model of Acer that is completely incompatible with FOG? I’ve tried changing SATA emulation from AHCI to IDE and vice versa with the same results.



  • Running fogprep gave me an error about accessing the registry, so I’m not sure if it even ran. I manually deleted the corresponding registry keys.

    What do you mean the master image needs to be a full mini-setup? I’ve built images before without issues. I started this latest master over with a clean install, deleting factory partitions and letting Windows build it’s 100mb partition and using the rest of the hard drive for the OS. I specified single partition NTFS only, resizable as my image type. I created a pre-sysprep image that also fails when I tried deploying that back to a machine to make some changes.

    I’ve never had partition issues like this using Ghost, or Macrium Reflect. Maybe I’m making the wrong selection in FOG somewhere, but I don’t think I’m creating the Windows 7 “master” image incorrectly.

    [quote=“Blackout, post: 675, member: 1”]I personally dont use fogprep on my Windows 7 builds, I’ve never had any problems. Fogprep removes the drive letter assignment <-> UUID registry information. In saying that, some people have had problems with it (on certain hardware sets) and removing the registry information is harmless.

    The master Image needs to be able to complete a full mini setup, otherwise the deployed Image will fail. This is sounding more like your problem.

    I have personally seen this endless reboot loop you are talking about. There is something wrong with your Image. It could be partition related or mostly likely, Microsoft software related (Windows, sysprep auto unattend, Office, Patches, etc).

    Look around the forums for information on partition / MBR related issues.

    You should prove it’s something wrong with the current Image. I would install a fresh copy of Windows onto another computer of the same hardware set, sysprep and upload to a new image. Test if the new master mini setup runs correctly, then deploy the image and test it’s mini setup.

    Sometimes, unless you know what is causing the problem; a full Image recreation is the fastest route. Don’t you love Windows :)[/quote]


  • Developer

    I personally dont use fogprep on my Windows 7 builds, I’ve never had any problems. Fogprep removes the drive letter assignment <-> UUID registry information. In saying that, some people have had problems with it (on certain hardware sets) and removing the registry information is harmless.

    The master Image needs to be able to complete a full mini setup, otherwise the deployed Image will fail. This is sounding more like your problem.

    I have personally seen this endless reboot loop you are talking about. There is something wrong with your Image. It could be partition related or mostly likely, Microsoft software related (Windows, sysprep auto unattend, Office, Patches, etc).

    Look around the forums for information on partition / MBR related issues.

    You should prove it’s something wrong with the current Image. I would install a fresh copy of Windows onto another computer of the same hardware set, sysprep and upload to a new image. Test if the new master mini setup runs correctly, then deploy the image and test it’s mini setup.

    Sometimes, unless you know what is causing the problem; a full Image recreation is the fastest route. Don’t you love Windows :)



  • Ok, I ran sysprep which seemed to run fine. Then I opened web browser, connected to my FOG server and ran the fogprep.exe and it gave an error about accessing the registry. I then uploaded the new image to the server, but my “master” wouldn’t boot back into Windows 7 when it was done. It said Windows couldn’t finish configuring the system, restart to resume configuration. Restarting just put it in a loop of that error, then a reboot, etc.

    [quote=“Blackout, post: 572, member: 1”]You should always run sysprep. This is more than likely your problem.

    The speeds you mentioned are very slow, I can deploy a 60gb image in under 20minutes at around 4.0gb/min.[/quote]


  • Developer

    You should always run sysprep. This is more than likely your problem.

    The speeds you mentioned are very slow, I can deploy a 60gb image in under 20minutes at around 4.0gb/min.



  • Update on the situation…

    Updating the kernel to version 3.1-rc8 Core allowed the deployment of my Windows 7 image to complete.

    Now it’s something else, which is most likely caused by the way I created the image.

    When the pc starts after finishing the deployment, windows starts Startup Repair, where it says it’s attempting to fix disk errors. It takes an hour to finish. I ran chkdsk /f before I uploaded the image, however I did not run sysprep. Also during the deployment I noticed that the data transfer speed steadily declined throughout, almost like it was counting down from 2.2 MiB/min to zero. The graph showing bandwidth also was flat for long periods of time, and then would spike briefly, then repeat. So, from starting the task until I get to login to the pc takes about 4.5 hours. For one pc, on a GB network.

    I’d appreciate any input or ideas to stop windows from running the repair process afterwards and how to speed up the image process.


Log in to reply
 

455
Online

39.4k
Users

11.1k
Topics

105.4k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.