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

Super newbie guide for creating image to w10?

Scheduled Pinned Locked Moved
Windows Problems
3
29
4.2k
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.
  • M
    motto @george1421
    last edited by motto Dec 21, 2017, 2:01 AM Dec 21, 2017, 7:11 AM

    @george1421 Hello George, here are my 2 photos.

    The problem is still the same, so im 100% sure that im doing something bad or there is something bad with my config.

    I boot using legacy bios, so I assume that it will be more “easy” to solve than in UEFI mode.

    FIrst, I boot the ipxe and choose my menu entry for w10
    Config:
    initrd nfs://${fog-ip}:/images/os/mswindows/10Pro/WinPE_amd6411.iso
    chain memdisk iso raw
    boot || goto MENU

    Then, it downloads the iso (I added two 1 at the and of the name for testing)
    w10dl

    After it download, it boots with this message (with your iso and mine)
    failing

    If I dont pressed anything or a key, it just boots from the local hard drive, so its like its not doing anything.

    Thanks!

    edit: I updated the menu , and now the error is different!

    new menu parameters:
    initrd /images/os/mswindows/10Pro/WinPE_amd6411.iso
    chain memdisk iso raw
    boot || goto MENU

    Error:
    newerror

    G 1 Reply Last reply Dec 21, 2017, 10:45 AM Reply Quote 0
    • S
      Sebastian Roth Moderator
      last edited by Sebastian Roth Dec 21, 2017, 3:05 AM Dec 21, 2017, 9:04 AM

      @motto Pictures tell more than a thousand words. The MEMDISK error bootstrap too large to load` to me sounds like that machine doesn’t have enough RAM to load that ISO…

      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

      M 1 Reply Last reply Dec 21, 2017, 10:31 AM Reply Quote 0
      • M
        motto @Sebastian Roth
        last edited by Dec 21, 2017, 10:31 AM

        @sebastian-roth Hello! I tried with 2 laptops, one with 8gb, so it cant be the problem :S

        1 Reply Last reply Reply Quote 0
        • G
          george1421 Moderator @motto
          last edited by george1421 Dec 21, 2017, 4:47 AM Dec 21, 2017, 10:45 AM

          @motto said in Super newbie guide for creating image to w10?:

          If I dont pressed anything or a key, it just boots from the local hard drive, so its like its not doing anything.

          This is normal. There is a file you need to remove from the iso image to skip this “feature”. If you were to burn that iso image to a cd or usb flash disk it would do the same thing. There is a file in the root of the iso image, <something>.bin (as said from an early morning memory). If you remove that from the iso image booting will not stop, it will boot straight to winpe.

          edit: I updated the menu , and now the error is different!

          Um, Unedit the menu. What you had was working correctly.

          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!

          M 1 Reply Last reply Dec 21, 2017, 10:52 AM Reply Quote 0
          • M
            motto @george1421
            last edited by Dec 21, 2017, 10:52 AM

            @george1421 maybe that was the problem, I will try it right now 🙂 and with the first menu, wich is the one it is supossed to be.

            G 1 Reply Last reply Dec 21, 2017, 11:04 AM Reply Quote 0
            • G
              george1421 Moderator @motto
              last edited by george1421 Dec 21, 2017, 5:05 AM Dec 21, 2017, 11:04 AM

              @motto I don’t intend to confuse you, but I just remembered I had/have a second way to boot this winpe image that may support uefi booting too. I know it works for bios mode. https://forums.fogproject.org/topic/6284/booting-mdt-2013-litetouch-with-fog/6

              I know this talks about lite touch, but mdt lite touch also uses winpe. I may have to alter the files loaded for winpe10. Please understand I’m still trying to find th ideal way to show people how to do advanced things with fog. I don’t load win10 via dvd any more since I use MDT for reference image deployment, so I haven’t had a “need” to perfect the tutorial.

              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!

              M 1 Reply Last reply Dec 21, 2017, 11:07 AM Reply Quote 0
              • M
                motto @george1421
                last edited by Dec 21, 2017, 11:07 AM

                @george1421 Sure, no problem

                My only goal here is to get to the w10 installation load, just that, because my linux installation is working and loading.

                I will try the MDT 🙂

                G 1 Reply Last reply Dec 21, 2017, 12:27 PM Reply Quote 0
                • G
                  george1421 Moderator @motto
                  last edited by Dec 21, 2017, 12:27 PM

                  @motto Lets backup and start over.

                  Please reset every thing so that we can get you to the message “Press any key to boot from CD or DVD…”

                  1. At this message press any key on the keyboard before it boot the local hard drive. This should launch the winpe image you created.
                  2. At the end of the booting process it should drop you to a cmd prompt.
                  3. Manually map to your win10 network share
                  4. Run the setup.exe program.
                  5. The Win10 installer should launch
                  6. Abort the install.

                  If you get to step 6, then we can work on fine tuning the steps. We will know all of the parts work, we just need to improve the flow.

                  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!

                  M 1 Reply Last reply Dec 21, 2017, 12:55 PM Reply Quote 0
                  • M
                    motto @george1421
                    last edited by Dec 21, 2017, 12:55 PM

                    @george1421 Stuck at 1º step at the moment…

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

                    234

                    Online

                    12.0k

                    Users

                    17.3k

                    Topics

                    155.2k

                    Posts
                    Copyright © 2012-2024 FOG Project