Navigation

    • Register
    • Login
    • Search
    • Recent
    • Popular

    windows pe boot

    Support
    3
    8
    1004
    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
      simonjwhitlock last edited by

      f3cb3bac-de11-40a5-9be2-40fbe8ec54fe-image.png

      hi me again

      so interesting new problem... i suspect ive missed something really dumb and silly.
      i am going to be using this for base installs so am setting up to use the wpe system. i downloaded wip bits and followed the istructions but i now get this.

      when i go to http://192.168.35.9/clientimaging/test i get "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."
      but going to http://192.168.35.9:8888/clientimaging/test i get "true"

      thanks for any help.
      Simon

      1 Reply Last reply Reply Quote 0
      • T
        theopenem_admin last edited by

        Your com server url should have the 8888 in it. You should update the com server url in the Toems-UI if it does not. Then you will need to update the wie build, com server url and build it again.

        S 1 Reply Last reply Reply Quote 0
        • S
          simonjwhitlock @theopenem_admin last edited by

          @theopenem_admin cool thanks - thats the silly bit i missed out.

          1 Reply Last reply Reply Quote 0
          • G
            godfather last edited by

            Hello,

            i have the same issue but my settings were ok...
            Here this error message:

            Could Not Contact Theopenem Server. Possible Reasons:
            The ClientImaging Web Service Is Not Functioning.
            Try Entering http://192.168.17.17:8888/clientimaging/Test In A Web Browser.
            A Driver Could Not Be Found For This NIC.
            The Computer Did Not Receive An Ip Address.

            http://192.168.17.17:8888/clientimaging/Test
            Result is also "true"

            Secure Boot is disabled.

            Computer: Dell Latitude 5430, Windows 11 22H2, UEFI

            C:\Program Files\Theopenem\tftpboot\pxelinux.cfg\default.ipxe:

            #!ipxe
            chain 01-${net0/mac:hexhyp}.ipxe || chain 01-${net1/mac:hexhyp}.ipxe || goto Menu

            :Menu
            menu Boot Menu
            item bootLocal Boot To Local Machine
            item theopenem Theopenem
            item console Client Console
            choose --default bootLocal --timeout 5000 target && goto ${target}

            :bootLocal
            exit 1

            :theopenem
            kernel http://192.168.17.17:8888/clientimaging/IpxeBoot?filename=5.6.4x64&type=kernel initrd=initrd.xz root=/dev/ram0 rw ramdisk_size=156000 web="http://192.168.17.17:8888/clientimaging/" USER_TOKEN= consoleblank=0
            imgfetch --name initrd.xz http://192.168.17.17:8888/clientimaging/IpxeBoot?filename=initrd.xz&type=bootimage
            boot

            :console
            kernel http://192.168.17.17:8888/clientimaging/IpxeBoot?filename=5.6.4x64&type=kernel initrd=initrd.xz root=/dev/ram0 rw ramdisk_size=156000 web="http://192.168.17.17:8888/clientimaging/" USER_TOKEN= task=debug consoleblank=0
            imgfetch --name initrd.xz http://192.168.17.17:8888/clientimaging/IpxeBoot?filename=initrd.xz&type=bootimage
            boot

            Do you have any idea, why this error message occur?
            A Test-Windows 10 Image (VM in HyperV) i can safe upload... but not this Notebook.

            1 Reply Last reply Reply Quote 0
            • T
              theopenem_admin last edited by

              Sounds like winpe doesn't have a driver for that machine. It has a lot of built in drivers, but not all of them. You'll need to add them to the winpe drivers folder before you build it.

              1 Reply Last reply Reply Quote 0
              • G
                godfather last edited by

                Thank you very much for this fast answer. Could you tell me please, where can i found this folder? Tank you!

                1 Reply Last reply Reply Quote 0
                • G
                  godfather last edited by

                  5.6.4 Kernel was this problem... with 5.17 it works!

                  Thank you!

                  1 Reply Last reply Reply Quote 0
                  • T
                    theopenem_admin last edited by

                    that's good, thought you were using winpe not linux.

                    1 Reply Last reply Reply Quote 0