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

problems Loading Windows iso in advanced menu.

Scheduled Pinned Locked Moved Solved
FOG Problems
windows advanced menu linux iso
8
32
16.4k
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.
  • G
    george1421 Moderator @Rayco
    last edited by May 18, 2017, 11:27 AM

    @Rayco This is an interesting puzzle.

    1. The system boots one some and not other systems.
    2. You are using the same WinPE image for all
    3. I assume you’ve confirmed that the iso image on the FOG server is exactly the same as in your windows environment by using md5sum utility in both environments and compared signatures??

    Do you have 2 computers of the same model where 1 works and 1 doesn’t?
    If so have you compared the firmware settings?
    Are these systems all uefi or bios (legacy) format?
    Are the systems with error in one geographic network location?
    Any other times you can think of where we could draw a conclusion?

    On a side note (not related to your problem) you can eliminate the pause at the bottom of the boot (as in your picture) by removing a file from your iso image. If you remove /boot/bootfix.bin the iso image will boot without the pause of “Press any key to boot from CD or DVD…”

    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!

    R 1 Reply Last reply May 18, 2017, 2:25 PM Reply Quote 0
    • R
      Rayco @george1421
      last edited by Rayco May 18, 2017, 8:28 AM May 18, 2017, 2:25 PM

      @george1421 Thanks for your interest.

      We have one WinPE for each Laptop model. In some models work fine, in other not, but in one cd bootable work fine in all.
      Each one has his own WinPE, some models use the same WinPE.
      Yes, they have the same size in bytes.
      When one model work fine, work fine in all of the same model.
      We think the problem is on some hardwares configurations.

      I will test your suggestion of remove bootfix.bin.

      T 1 Reply Last reply May 18, 2017, 2:28 PM Reply Quote 0
      • T
        Tom Elliott @Rayco
        last edited by May 18, 2017, 2:28 PM

        @Rayco If One model is broken, does all of the same model also fail? (Or multiples of the same model more accurately.)

        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

        R 1 Reply Last reply May 18, 2017, 2:31 PM Reply Quote 0
        • R
          Rayco @Tom Elliott
          last edited by Rayco May 18, 2017, 8:31 AM May 18, 2017, 2:31 PM

          @Tom-Elliott

          If one model fail, all of this models fails too. But if burned in to bootable cd, work fine.

          Thank you a lot.

          T Q 2 Replies Last reply May 18, 2017, 2:34 PM Reply Quote 0
          • T
            Tom Elliott @Rayco
            last edited by May 18, 2017, 2:34 PM

            @Rayco I don’t know how you created the menu, but maybe this can help:
            http://ipxe.org/howto/winpe

            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 1
            • Q
              Quazz Moderator @Rayco
              last edited by May 18, 2017, 2:34 PM

              @Rayco Can you share the PXE boot commands you have?

              R 1 Reply Last reply May 18, 2017, 3:08 PM Reply Quote 1
              • R
                Rayco @Quazz
                last edited by May 18, 2017, 3:08 PM

                @Quazz

                 initrd http://${fog-ip}/fog/service/ipxe/iso/asus/TOOL_NB64_W10GPT_V1.3.3.iso
                 chain memdisk iso raw ||
                 goto MENU
                

                This is a config menu.

                @Tom-Elliott
                If some computers work well, I must think that those that do not work is by the configuration of ipxe?

                I will check it, in few hours I answer you.

                G Q 3 Replies Last reply May 18, 2017, 3:11 PM Reply Quote 0
                • G
                  george1421 Moderator @Rayco
                  last edited by May 18, 2017, 3:11 PM

                  @Rayco said in problems Loading Windows iso in advanced menu.:

                  initrd http://${fog-ip}/fog/service/ipxe/iso/asus/TOOL_NB64_W10GPT_V1.3.3.iso

                  Not specifically related to your issue, but I wouldn’t place your files in the FOG package path if you want your files to survive an update. I would recommend you move the iso director to a root level directory on your fog server. i.e. http://${fog-ip}/fog/service/ipxe/iso -> http://${fog-ip}/iso

                  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 0
                  • Q
                    Quazz Moderator @Rayco
                    last edited by May 18, 2017, 3:15 PM

                    @Rayco I would try the wimboot way that’s listed on iPXE website if I were you. I find it this is far more successful to boot WinPE than trying to boot the ISO

                    1 Reply Last reply Reply Quote 0
                    • G
                      george1421 Moderator @Rayco
                      last edited by May 18, 2017, 3:16 PM

                      @Rayco said in problems Loading Windows iso in advanced menu.:

                      TOOL_NB64_W10GPT

                      Just hacking your file name here. So all of these systems you are pxe booting are in uefi mode? If so we have seen some pretty flaky uefi firmware especially on Lenovo systems. I’m not saying this is your issue, just we have seen the issue. It is the handoff between either PXE rom and iPXE or between iPXE and FOS.

                      There is also another way to pxe boot instead of an iso image (I understand that is desirable for portability). In the link I previously posted, there is an second method for pxe booting into WinPE: https://forums.fogproject.org/topic/6284/booting-mdt-2013-litetouch-with-fog/6 I’m not suggesting this will fix your issue, but its something you could try.

                      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!

                      R 1 Reply Last reply May 18, 2017, 3:21 PM Reply Quote 0
                      • R
                        Rayco @george1421
                        last edited by May 18, 2017, 3:21 PM

                        @george1421

                        Thanks you guys, I appreciate your advice, I will change the path of the iso folder, adopt wimboot system, and will check it tonight.

                        THX a lot !!!

                        1 Reply Last reply Reply Quote 0
                        • R
                          Rayco
                          last edited by May 22, 2017, 11:24 AM

                          Hello guys.

                          Finally, with wimboot systems work fine in all computer.

                          This was the code:

                             #!ipxe cpuid --ext 29 && set arch amd64 || set arch x86
                             kernel http://${fog-ip}/iso/asus/133/wimboot
                             initrd http://${fog-ip}/iso/asus/133/BOOT/BCD BCD
                             initrd http://${fog-ip}/iso/asus/133/BOOT/BOOT.SDI boot.sdi
                             initrd -n boot.wim http://${fog-ip}/iso/asus/133/SOURCES/BOOT.WIM boot.wim
                             boot
                          

                          Thank all, a lot.

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

                          156

                          Online

                          12.0k

                          Users

                          17.3k

                          Topics

                          155.2k

                          Posts
                          Copyright © 2012-2024 FOG Project