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

Windows not booting after FOG deployment.

Scheduled Pinned Locked Moved
Windows Problems
5
9
1.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.
  • E
    EJoc242
    last edited by May 7, 2018, 3:55 PM

    I have 2 models of computers that will not boot into windows after FOG deployment. One is a laptop, Dell Latitude 6530 and one is a desktop Dell OptiPlex 7010. FOG will run a successful deployment but after the reboot, we get a stop code error when loading into windows on both of these models.

    On restart of windows on both models we get an error saying “Your PC ran into a problem and needs to restart. We’re just collecting some error info and then we will restart for you” the computer just stays in this loop until we have the choice to restore to previous image or resetting PC, ut PC will not allow you to do either. Have tried multiple PC’s of both models. Has anyone else seen anything like this any help would be appreciated.

    1 Reply Last reply Reply Quote 0
    • J
      Joe Schmitt Senior Developer
      last edited by May 7, 2018, 4:04 PM

      @EJoc242 if you aren’t already, I would recommend sysprepping your images before capture. When deploying to vastly different hardware, it may be necessary, as it allows Windows to properly configure itself to your target hardware.

      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.

      1 Reply Last reply Reply Quote 0
      • E
        EJoc242
        last edited by May 7, 2018, 4:05 PM

        We have not been sysprepping. I will give that a shot and let you know how it goes.

        1 Reply Last reply Reply Quote 0
        • E
          EJoc242
          last edited by May 7, 2018, 4:28 PM

          Looking more into it, I found that we aren’t sysprepping since we are making an individual image for each PC model. Would sysprepping still help in that case?

          1 Reply Last reply Reply Quote 0
          • J
            Joe Schmitt Senior Developer
            last edited by Joe Schmitt May 7, 2018, 10:31 AM May 7, 2018, 4:31 PM

            @EJoc242 possibly, it’d be worth trying.

            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.

            1 Reply Last reply Reply Quote 0
            • T
              Taspharel
              last edited by May 9, 2018, 8:56 AM

              It probably goes beyond the scope of support that I can offer on this forum, but yes, you can make images “per device-group” that have specific drivers.

              You could even make a general image without drivers (or with only basic drivers) and inject the drivers according to the device type with post-deployment scripts that are available for FOG.

              If you have specific questions I can try to help … but I’m by no means an expert

              1 Reply Last reply Reply Quote 0
              • I
                imagingmaster21
                last edited by May 22, 2018, 4:08 PM

                @EJoc242
                Connect one of those computers at a time to FOG server and run a TCP dump. Once you know the vendor id try modifying that in your DHCP settings.

                1 Reply Last reply Reply Quote 0
                • Q
                  Quazz Moderator
                  last edited by May 23, 2018, 3:14 PM

                  What stop code is it?

                  If it is 7B then the cause is most likely the storage drivers. (eg imaged as RAID, BIOS settings at new PC set to AHCI)

                  1 Reply Last reply Reply Quote 0
                  • E
                    EJoc242
                    last edited by May 23, 2018, 4:59 PM

                    The stop code error I got was “Critical Process Died”, Tried sysprepping, with and without an answer file and neither of those options have worked. I have verified in the bios that storage drivers are the same on all of these models. Sorry for the delay in responses I only get a couple of hours a week dedicated to this project.

                    So far our other 3 models, Dell OptiPlex 9020, 7040, and our Dell Lattitude 5580 have not had any issues. It is just when we get to these older models that we have problems.

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

                    156

                    Online

                    12.0k

                    Users

                    17.3k

                    Topics

                    155.2k

                    Posts
                    Copyright © 2012-2024 FOG Project