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

    Windows Images - Too large.

    Scheduled Pinned Locked Moved Unsolved
    Windows Problems
    3
    7
    852
    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
      sami.blackkite
      last edited by

      Hey everyone.
      FOG has been great the past couple times I’ve used it and in a current new windows build I’m having a couple issues with cloning and image.

      My windows build is about 80-90GB and I’ve been using FOG’s default settings to clone the image.
      Before, the image would be a 1 to 1 copy, 90gb on my FOG server, however, this time, no matter how many images I take, FOG always picks up the full drive.

      My windows disk is 256GB and my build is 80gb [of used space on the disk]
      I only want to take the size of the Windows image.

      How can I fix this?
      I’ll add some screenshots if required. Thank you.

      Tom ElliottT 1 Reply Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott @sami.blackkite
        last edited by

        @sami-blackkite What are the options you’re using?

        This sounds like you’re using non-resizable as the option, but you really want to use resizable.

        That said, if the drive is bitlocker encrypted then you’re only option is going to be a raw copy.

        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

        S 1 Reply Last reply Reply Quote 0
        • S
          sami.blackkite @Tom Elliott
          last edited by

          @Tom-Elliott
          Hi Tom.
          Thanks for the speedy reply.
          All 3 windows images that I’ve made are set to

          Single Disk - Resizable (1)

          Is that the wrong option?

          Thanks.

          JJ FullmerJ 1 Reply Last reply Reply Quote 0
          • JJ FullmerJ
            JJ Fullmer Testers @sami.blackkite
            last edited by

            @sami-blackkite That’s the right option.
            What version of FOG are you on?

            Have you tried the FogApi powershell module? It's pretty cool IMHO
            https://github.com/darksidemilk/FogApi
            https://fogapi.readthedocs.io/en/latest/
            https://www.powershellgallery.com/packages/FogApi
            https://forums.fogproject.org/topic/12026/powershell-api-module

            S 1 Reply Last reply Reply Quote 0
            • S
              sami.blackkite @JJ Fullmer
              last edited by

              @JJ-Fullmer said in Windows Images - Too large.:

              @sami-blackkite That’s the right option.
              What version of FOG are you on?

              I’m on 1.5.10.5

              It says here that the latest one is 1.5.10 and that I’m not on the latest.

              https://prnt.sc/SNZxKw_L0WVF

              JJ FullmerJ 1 Reply Last reply Reply Quote 0
              • JJ FullmerJ
                JJ Fullmer Testers @sami.blackkite
                last edited by

                @sami-blackkite Looks like you’re on the dev branch, which is good. Updating is always a good first step in troubleshooting stuff like this in case it’s already fixed.
                I’m not seeing anything in the commits (https://github.com/FOGProject/fogproject/commits/dev-branch) that actually looks related since the version you’re on, but sometimes a refresh still helps.

                I took a look at the default settings of a new image and it’s close to what I use, only difference is I set compression to 11.

                Are you familiar with a debug capture/deploy task? If not, simply check the ‘debug task’ checkbox when queuing up the capture task. It allows you to step through the capture process and you can catch any messages that might be telling us why it’s behaving odd. Just use the command fog once it’s booted up and ready to start the image and you’ll hit enter for each step. You can also set it up to watch it and step through over ssh if you want by, before running the fog command, getting the ip address with ifconfig and then setting a password with passwd then you can ssh into the debug session from your workstation with ssh root@ip.add.re.ss then the password you set. The password will only exist for that session on that machine. SSH just makes screenshotting and or copying any error messages to share here a bit easier.

                Have you tried the FogApi powershell module? It's pretty cool IMHO
                https://github.com/darksidemilk/FogApi
                https://fogapi.readthedocs.io/en/latest/
                https://www.powershellgallery.com/packages/FogApi
                https://forums.fogproject.org/topic/12026/powershell-api-module

                S 1 Reply Last reply Reply Quote 0
                • S
                  sami.blackkite @JJ Fullmer
                  last edited by

                  @JJ-Fullmer said in Windows Images - Too large.:

                  @sami-blackkite Looks like you’re on the dev branch, which is good. Updating is always a good first step in troubleshooting stuff like this in case it’s already fixed.
                  I’m not seeing anything in the commits (https://github.com/FOGProject/fogproject/commits/dev-branch) that actually looks related since the version you’re on, but sometimes a refresh still helps.

                  I took a look at the default settings of a new image and it’s close to what I use, only difference is I set compression to 11.

                  Are you familiar with a debug capture/deploy task? If not, simply check the ‘debug task’ checkbox when queuing up the capture task. It allows you to step through the capture process and you can catch any messages that might be telling us why it’s behaving odd. Just use the command fog once it’s booted up and ready to start the image and you’ll hit enter for each step. You can also set it up to watch it and step through over ssh if you want by, before running the fog command, getting the ip address with ifconfig and then setting a password with passwd then you can ssh into the debug session from your workstation with ssh root@ip.add.re.ss then the password you set. The password will only exist for that session on that machine. SSH just makes screenshotting and or copying any error messages to share here a bit easier.


                  Oh thank you so much, JJ.
                  I’ll give those steps a go and report back.

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

                  194

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project