• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Windows 7 errors post deployment

Scheduled Pinned Locked Moved Unsolved
Windows Problems
7
15
4.3k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S
    sourcaffeine @Wayne Workman
    last edited by Nov 7, 2016, 3:42 AM

    @Wayne-Workman I described the hardware differences below. The only difference in hardware is hard drive model, and this issue does not seem to occur on any particular brand (three different models).

    Like I said in my previous post, I went ahead and captured an image using FOG on a machine that deployed and installed. I once again disabled the FOG service, and this time the deployment didn’t finish. There was an error that was obscured, with FOG just reporting that there was an error while trying to expand sda2, and that it would reboot in 1 minute.

    W 1 Reply Last reply Nov 7, 2016, 3:54 AM Reply Quote 0
    • W
      Wayne Workman @sourcaffeine
      last edited by Wayne Workman Nov 6, 2016, 10:04 PM Nov 7, 2016, 3:54 AM

      @sourcaffeine Well if these 60 computers are all identical besides the HDD, then taking an image from one that deployed correctly isn’t going to prove or disprove anything, because the original image also deployed correctly on some of these systems.

      For a sanity check, check the free space on the server, look for partitions that have 100% use:
      df -h

      The error you gave in the OP, that’s not the one that is typically given when the FOG Client is causing the issue. The error literally says “could not complete the installation…” The installation of what? My guess? Drivers, maybe some weird attached device like a scanner or printer or flash drive or SD Card, we’ve actually seen times where an SD card that people left in laptops will cause issues for capture/deploy sometimes.

      But, I’m going to guess drivers.

      There’s some simple troubleshooting to figure out what’s going on.

      To test if it’s the FOG Client causing the issue (which I don’t think it is), just delete these 60 hosts from fog, and manually using the boot menu do “Image Deploy” with the correct image. When the computers boot after imaging, the FOG Client will communicate with the server but not get any commands to do anything in this case. If this works fine consistently, then the FOG Client is probably not disabled on your reference image. If this doesn’t make a difference and the systems are still having issues booting after imaging, it’s probably at that point that it’s a driver related issue like @george1421 said, and I’d follow his advice.

      Another very simple thing it could be - mismatched HDD operation modes in the firmware, and mixed operation modes, or the image is BIOS but some of the machines are in UEFI mode in firmware.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
      Daily Clean Installation Results:
      https://fogtesting.fogproject.us/
      FOG Reporting:
      https://fog-external-reporting-results.fogproject.us/

      A 1 Reply Last reply Nov 7, 2016, 4:00 AM Reply Quote 2
      • A
        AngryScientist @Wayne Workman
        last edited by Nov 7, 2016, 4:00 AM

        @Wayne-Workman +1 to the mixed HDD modes. I about tore my hair out one week over some hosts being set to IDE and others AHCI.

        1 Reply Last reply Reply Quote 2
        • W
          Wayne Workman
          last edited by Nov 7, 2016, 4:00 AM

          Also, I was searching on the forums for the error and found this old thread, and it was due to the fog client not being disabled on the image:

          @zpoling said in Windows Fails to Install:

          Specifically on our HP Probook G1 laptops, after deployment I am getting an error on the boot screen that says, “Windows Setup could not configure Windows to run on this computer’s hardware.” The message displays for a only a second, then the machine reboots. I then get the following error, “Windows could not complete the installation. To install Windows on this computer, restart the installation.” This error will stay on screen until I click okay.

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
          Daily Clean Installation Results:
          https://fogtesting.fogproject.us/
          FOG Reporting:
          https://fog-external-reporting-results.fogproject.us/

          1 Reply Last reply Reply Quote 0
          • T
            Tom Elliott @sourcaffeine
            last edited by Nov 7, 2016, 1:04 PM

            @sourcaffeine The message you’re seeing would be coming from Windows, at which point this is not anything FOG is doing.

            You state that you’re using Clonezilla and it works perfectly, except we haven’t got a full testbed.

            If you take the same image from FOG, deploy it, and clone it using clonezilla, then deploy using clonezilla, it should do EXACTLY the same thing.

            Why? Because FOG uses the same tools Clonezilla uses for imaging.

            If this where something FOG was doing, you’d see the exact same problem on all systems in the exact same way.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

            1 Reply Last reply Reply Quote 0
            • G
              george1421 Moderator
              last edited by george1421 Nov 8, 2016, 6:30 AM Nov 7, 2016, 1:30 PM

              Have you taken 2 of these systems (one that imaged and one that has not) and done an actual side be side comparison to ensure the model, included hardware, bios, bios settings are all consistent?

              As I said before I’ve also seen this action with a bad windows driver. When you did the shift-f10 trick and was able to boot into windows, did you review the OOBE logs in either windows\panther or windows\sysprep folders? Those logs should tell you what was going on when the system rebooted.

              One thing that is also not clear, are you using one image for all, or do you have one image per hardware model?

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

              1 Reply Last reply Reply Quote 2
              • S
                sudburr
                last edited by Nov 7, 2016, 3:14 PM

                I have also seen this error caused by the Antivirus in the image. Although it affected all deployments, effectively poisoning the image beyond repair.

                [ Standing in between extinction in the cold and explosive radiating growth ]

                1 Reply Last reply Reply Quote 2
                • S
                  sourcaffeine
                  last edited by Nov 14, 2016, 7:51 PM

                  I was unable to correct this issue with FOG. I verified a number of times that the FOG Client was indeed disabled, even to the point of uninstalling it and going from there. The same issue came up. I attempted to swap hard drives of one that worked, and one that didn’t, same issue.

                  Verified all BIOS settings were the same. Deleted the host from FOG, tried to manually deploy, no luck.

                  I did end up using Clonezilla Server and it deployed without a single issue.

                  1 Reply Last reply Reply Quote 0
                  • C
                    cavalla
                    last edited by Nov 15, 2016, 3:32 PM

                    before imaging (‘syspreping’) look at the line :
                    Remaining windows rearm count : x
                    in the command line console prompt of :
                    slmgr.vbs -dlv
                    perhaps it’s reached 0
                    If so, Look at rearm technic on the net.

                    1 Reply Last reply Reply Quote 1
                    • W
                      Wayne Workman @sourcaffeine
                      last edited by Nov 29, 2016, 3:54 AM

                      @sourcaffeine

                      Moved topic to Windows problems. Please advise if you’ve found a solution to this or are still having the problem.

                      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                      Daily Clean Installation Results:
                      https://fogtesting.fogproject.us/
                      FOG Reporting:
                      https://fog-external-reporting-results.fogproject.us/

                      1 Reply Last reply Reply Quote 0
                      • 1 / 1
                      • First post
                        Last post

                      202

                      Online

                      12.0k

                      Users

                      17.3k

                      Topics

                      155.2k

                      Posts
                      Copyright © 2012-2024 FOG Project