• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. kinger37
    3. Posts
    K
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 20
    • Best 2
    • Controversial 0
    • Groups 0

    Posts made by kinger37

    • RE: Booting MDT 2013 LiteTouch with FOG

      @george1421 Thank you for this tutorial - it worked great but I did discover that these steps are not compatible if booting into FOG using UEFI, it only works if using Legacy. When I tried at first using UEFI, it would load to the boot menu and once I picked my WinPE entry iPXE would fail with this error “Could not boot: Exec format error (http://ipxe.org/2e008081)”. Then i tried using Legacy mode to boot into Fog and launched my iso and it worked like a charm. I know this is not a fog issue but iPXE but figured I would post this in case someone else come across this issue.

      @Wayne-Workman I think this would be a good note to add when these steps are added to wiki.

      posted in Tutorials
      K
      kinger37
    • RE: What exactly is: Host EFI Exit Type?

      @george1421 Thank you George - that does clarify and answer my question. Appreciate the help as always.

      posted in General
      K
      kinger37
    • RE: What exactly is: Host EFI Exit Type?

      @Wayne-Workman Right after I posted this - I was wondering if it had something to do with our machines having an Admin Password set for the BIOS Setup, in your case are you using a password to edit the boot sequence? Also the machines I have seen this on are Dell’s as well.

      posted in General
      K
      kinger37
    • What exactly is: Host EFI Exit Type?

      Hi,

      The version I am currently running: Running Version 1.3.0-RC-8; SVN Revision: 5948 on Ubuntu Server 14.04. All my computers are UEFI but when an image is deployed the boot order is wrong. I am wondering if this field is what I am looking for but looking for some clarification. Will this field update my UEFI boot order? If I want to boot to hard drive by default - should i select GRUB_First_HDD?

      Any help would greatly appreciated. Also I checked Wiki and couldnt find any reference but if I missed it I would love to know where to look.

      posted in General
      K
      kinger37
    • RE: Quick or Full Host Registration fails - screen goes black

      @Tom-Elliott Sorry for the delay - I am on an isolated network for my FOG Server - so right now only 3 machines in the FOG environment.

      posted in FOG Problems
      K
      kinger37
    • RE: Quick or Full Host Registration fails - screen goes black

      @kinger37 Deployment was successful - I think I have it working now - thank you for everyones help.

      @TOM ELLIOTT On my first time booting into FOG PXE menu I receive the chainloading error, but after rebooting and going back in - it doesnt show up again.

      posted in FOG Problems
      K
      kinger37
    • RE: Quick or Full Host Registration fails - screen goes black

      @george1421 @Wayne-Workman I have just updated to the latest SVN 5858 and updated the firmware of the 7040 to 1.4.4 - wasnt getting a plain black screen anymore but kept failing on registration “An Error has been detected” “Cannot find disk on system”

      Solution to that issue was in my BIOS\UEFI settings - under Device Config-Sata Operation: Raid On was enable and I had to change it to AHCI.

      Testing deploying a image right now.

      posted in FOG Problems
      K
      kinger37
    • RE: Quick or Full Host Registration fails - screen goes black

      @george1421 Hi George - I just had it work - without doing an updates - not sure what changed. The only that i did try was doing the Legacy boot after scheduling a task to capture the image. I am going to try a straight from the factory 7040 and see what happens.

      If it fails again though I will update firmware and FOG trunk.

      Thanks again for all your help!

      posted in FOG Problems
      K
      kinger37
    • RE: Quick or Full Host Registration fails - screen goes black

      @george1421 Hi George, I just finished testing that and you are correct - it registers correctly, however when i check inventory of that machine - no hard drive installed 😞

      posted in FOG Problems
      K
      kinger37
    • RE: Quick or Full Host Registration fails - screen goes black

      I also want to add something i just noticed - I have to use UEFI or my hard drive (M.2 256GB PCIe SSD Samsung PM951 NVMe Drive) isnt detected under Legacy boot. @george1421 Do you have the same hard drive as I do?

      posted in FOG Problems
      K
      kinger37
    • RE: Quick or Full Host Registration fails - screen goes black

      @Tom-Elliott Hi Tom i just confirmed that all my UEFI boot options are using ipxe.efi.

      posted in FOG Problems
      K
      kinger37
    • RE: Quick or Full Host Registration fails - screen goes black

      @george1421 I currently have it set to UEFI and Secure Boot off. I tested it again today and now receiving this error after the FOG PXE menu sits for a couple seconds “Chainloading failed, hit ‘s’ for the iPXE shell: reboot in 10 seconds”. I will start sifting through the forums to see if I can find anything on that error.

      posted in FOG Problems
      K
      kinger37
    • Quick or Full Host Registration fails - screen goes black

      Any ideas on this one:

      This issue is affecting me with both Fog 1.2.0 and now Trunk, running Ubuntu 14.04 Server. The host machine I am trying to register is a Dell Optiplex 7040M. I am using iPXE and everything works right up until I select either Full Host Registration and Inventory or Quick Host Registration and Inventory. Once I select either one of these the screen goes black - same thing happened on FOG stable and FOG Trunk (just updated it today using SVN).

      Any help would be greatly appreciated.

      posted in FOG Problems
      K
      kinger37
    • RE: PXE-E53: No Boot File Received

      @Sebastian-Roth @george1421 After setting up a fresh install of Ubuntu 14.04 Server and FOG Server 1.2.0 I have finally got it working on a isolated network - only thing now is that the switch I want to use has to have STP disabled (waiting to get a console cable). Thank you all for your help.

      posted in FOG Problems
      K
      kinger37
    • RE: PXE-E53: No Boot File Received

      @Sebastian-Roth @george1421 Thank you both for all your responses, I am going to change our setup and use a isolated network for FOG and cloning computers. I will update everyone once I have set it up and tested.

      posted in FOG Problems
      K
      kinger37
    • RE: PXE-E53: No Boot File Received

      @george1421 Here is two new pcap files - one on a machine that will not work and one from the VM that is working. The system I am trying to boot is an Dell Optiplex 7040M - where I have tried both BIOS and UEFI - would prefer to use UEFI. We have juniper EX3300 switches which I believe are providing DHCP services - but 100% percent sure.

      1_1467047901006_output-error.pcap
      0_1467047901006_output.pcap

      posted in FOG Problems
      K
      kinger37
    • RE: PXE-E53: No Boot File Received

      @Sebastian-Roth I have attempted this with a couple different Machines, same thing happens. I do have a symlink that points undionly.0 to undionly.kpxe. Here is my LTSP.conf file:

      # Don't function as a DNS server:
      port=0
      
      # Log lots of extra information about DHCP transactions.
      log-dhcp
      
      # Dnsmasq can also function as a TFTP server. You may uninstall
      # tftpd-hpa if you like, and uncomment the next line:
      # enable-tftp
      
      # Set the root directory for files available via FTP.
      tftp-root=/tftpboot
      
      # The boot filename, Server name, Server Ip Address
      dhcp-boot=undionly.kpxe,128.119.61.43,128.119.61.43
      
      # rootpath option, for NFS
      #dhcp-option=17,/images
      
      # kill multicast
      #dhcp-option=vendor:PXEClient,6,2b
      
      # Disable re-use of the DHCP servername and filename fields as extra
      # option space. That's to avoid confusing some old or broken DHCP clients.
      dhcp-no-override
      
      # PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
      pxe-prompt="Press F8 for boot menu", 3
      
      # The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
      # Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
      # This option is first and will be the default if there is no input from the user.
      pxe-service=X86PC, "Boot from network", undionly, 128.119.61.43
      
      # A boot service type of 0 is special, and will abort the
      # net boot procedure and continue booting from local media.
      #pxe-service=X86PC, "Boot from local hard disk", 0
      
      # If an integer boot service type, rather than a basename is given, then the
      # PXE client will search for a suitable boot service for that type on the
      # network. This search may be done by multicast or broadcast, or direct to a
      # server if its IP address is provided.
      # pxe-service=x86PC, "Install windows from RIS server", 1
      
      # This range(s) is for the public interface, where dnsmasq functions
      # as a proxy DHCP server providing boot information but no IP leases.
      # Any ip in the subnet will do, so you may just put your server NIC ip here.
      # Since dnsmasq is not providing true DHCP services, you do not want it
      # handing out IP addresses.  Just put your servers IP address for the interface
      # that is connected to the network on which the FOG clients exist.
      # If this setting is incorrect, the dnsmasq may not start, rendering
      # your proxyDHCP ineffective.
      dhcp-range=128.119.61.43,proxy
      
      # This range(s) is for the private network on 2-NIC servers,
      # where dnsmasq functions as a normal DHCP server, providing IP leases.
      # dhcp-range=192.168.0.20,192.168.0.250,8h
      
      # For static client IPs, and only for the private subnets,
      # you may put entries like this:
      # dhcp-host=00:20:e0:3b:13:af,10.160.31.111,client111,infinite
      

      Mod edited to use code box.

      posted in FOG Problems
      K
      kinger37
    • RE: PXE-E53: No Boot File Received

      Hi - our DHCP server is a Juniper Switch. The PC (I have tried different PC’s as well) are all on the subnet as the FOG Server. Yes, the VM that PXE booted is on the same VMHost. I have the network adapters bridged on both VM and FOG Server and are on the same subnet.
      I dont have rights to modify our DHCP server.
      I have attached the two network captures, issues.pcap is the PC that wont PXE boot and the works.pcap is the VM that worked.

      0_1466883705633_IMG_1005.JPG

      1_1466882742690_works.pcap
      0_1466882742689_issue.pcap

      posted in FOG Problems
      K
      kinger37
    • PXE-E53: No Boot File Received

      I have just installed Fog 1.2.0 on Ubuntu 14.04 (VM on VirtualBox). I am not using DHCP or DNS on FOG and have installed DNSMASQ - which the status says its working. Also I have confirmed that I am able to access undionly.kpxe from my Windows PC using TFTP. I did two tests - where I boot a PC into PXE and I get this error: PXE-E53: No Boot File Received. I then create a new Windows VM in VirtualBox and boot into PXE where is loads into FOG no issues. Any ideas on what could be the issue?

      posted in FOG Problems
      K
      kinger37
    • 1 / 1