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

    Problem laying image on a virtual machine

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    4
    27
    4.5k
    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.
    • D
      davemccracken @george1421
      last edited by

      @george1421

      Yes, I syspreped before capture.

      I will try the recovery tools. One question which comes to mind though, although since the partition tables are recreated I doubt this is the case, but does that target drive have to have had a working operating system on it prior to the FOG deployment?

      Thank you,
      Dave

      george1421G 1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @davemccracken
        last edited by

        @davemccracken said in Problem laying image on a virtual machine:

        does that target drive have to have had a working operating system on it prior to the FOG deployment?

        No FOG doesn’t care what was there before to deploy it. The point being you can deploy to bare metal or a previous OS, FOG doesn’t care because it destroys the partition table and creates a new one. This error kind of tells me the boot partition is not in a sane state.

        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!

        D 1 Reply Last reply Reply Quote 0
        • D
          davemccracken @george1421
          last edited by

          @george1421 Okay, but the gold image VM boots fine, and so, I am somewhat unsure what would cause a block by block copy of it to have a bad boot partition.

          Interestingly, once I booted from a Win10 ISO file, it then says the registry is missing or has errors. This has me wondering if I should just try to deploy again, as maybe something got lost or corrupted between the image and the target.

          What do you think? Can this be a possibility?

          Dave

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by

            @davemccracken said in Problem laying image on a virtual machine:

            I am somewhat unsure what would cause a block by block copy of it to have a bad boot partition.

            Using image type MPS (Multiple Partitions Single Disk) is not really a block by block copy. Although it is pretty save to properly deploy to another system fine! As you didn’t use the resizable image type (as we see in the picture you posted) partition problems are not very likely. My guess is this has something to do with how you sysprep.

            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

            D 1 Reply Last reply Reply Quote 0
            • D
              davemccracken @Sebastian Roth
              last edited by

              @Sebastian-Roth

              I agree with you that something must be wrong with the image. It has done the same thing on 3 virtual machines so far. I originally had done a multicast for the first 2 and a single machine deploy for the last.

              I am going to go back to the VM with the gold image, and re-sysprep and capture it. Then try the deploy again. Do you have recommended sysprep parameters? I was using /oobe /shutdown

              george1421G 1 Reply Last reply Reply Quote 0
              • george1421G
                george1421 Moderator @davemccracken
                last edited by

                @davemccracken Here is my unattend.xml file and the sysprep command I use: https://forums.fogproject.org/topic/11920/windows-10-1803-sysprep-problem/7

                Make sure you put the unattend.xml file in c:\windows\panther only.

                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!

                D 1 Reply Last reply Reply Quote 0
                • D
                  davemccracken @george1421
                  last edited by

                  @george1421 @Sebastian-Roth @Quazz

                  Thanks George, I tried to use your unattend file, but it kept bluescreening on the host once imaged, so I tried creating a new one today and it worked fine. I probably didn’t change enough things in it, and missed something important, but I got around it now.

                  I greatly appreciate all the help you kind folks have provided. It is very much appreciated. I couldn’t have gotten to this point without it,

                  Dave

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

                  165

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project