• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Paul Freeman
    3. Posts
    P
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 32
    • Best 1
    • Controversial 0
    • Groups 0

    Posts made by Paul Freeman

    • RE: Trouble with Windows 8.1 image using Host Reg Bypass

      During installation I received the following error.

       Press [Enter] key when database is updated/installed.
      
       * Setting up storage..........................................OK
       * Setting up and starting DHCP Server.........................../lib/common/functions.sh: line 155: 2600:1010:b021:8a9f:e506:70ec:3154:c398: syntax error in expression (error token is ":1010:b021:8a9f:e506:70ec:3154:c398")
       * Setting up and starting TFTP and PXE Servers................OK
      

      I then checked the status and sure enough DHCP had not started.

      eud@FOGVM ~/fogtrunk/bin $ sudo service isc-dhcp-server status
      isc-dhcp-server stop/waiting
      eud@FOGVM ~/fogtrunk/bin $ sudo /etc/init.d/isc-dhcp-server start
      dhcpd self-test failed. Please fix /etc/dhcp/dhcpd.conf.
      The error was: 
      Internet Systems Consortium DHCP Server 4.2.4
      Copyright 2004-2012 Internet Systems Consortium.
      All rights reserved.
      For info, please visit https://www.isc.org/software/dhcp/
      /etc/dhcp/dhcpd.conf line 35: expecting numeric value.
      subnet  netmask 
               ^
      Configuration file errors encountered -- exiting
      eud@FOGVM ~/fogtrunk/bin $ 
      
      posted in FOG Problems
      P
      Paul Freeman
    • RE: Trouble with Windows 8.1 image using Host Reg Bypass

      Looks like i spoke too soon. Immediately after installing trunk everything was working fine. I then shutdown the VM to create a snapshot and rebooted and now the DHCP service will not start (automatically or manually).

      This is what i get when trying to start the service.

      eud@FOGVM ~/Desktop $ sudo /etc/init.d/isc-dhcp-server start
      dhcpd self-test failed. 
      Please fix /etc/dhcp/dhcpd.conf.
      
      The error was: 
      Internet Systems Consortium DHCP Server 4.2.4
      
      Copyright 2004-2012 Internet Systems Consortium. 
      All rights reserved.
       For info, please visit 
      
      https://www.isc.org/software/dhcp/
      
      /etc/dhcp/dhcpd.conf line 0: expecting a parameter or declaration
      # Code
            ^
      /etc/dhcp/dhcpd.conf line 17: no option space named PXE.
      option PXE.mtftp-ip
                 ^
      /etc/dhcp/dhcpd.conf line 18: no option space named PXE.
      option PXE.mtftp-cport
                 ^
      /etc/dhcp/dhcpd.conf line 19: no option space named PXE.
      option PXE.mtftp-sport
                 ^
      /etc/dhcp/dhcpd.conf line 20: no option space named PXE.
      option PXE.mtftp-tmout
                 ^
      /etc/dhcp/dhcpd.conf line 21: no option space named PXE.
      option PXE.mtftp-delay
                 ^
      /etc/dhcp/dhcpd.conf line 40: semicolon expected.
      	max-lease-time
               ^
      /etc/dhcp/dhcpd.conf line 40: expecting a parameter or declaration
      	max-lease-time 43200;
                                   ^
      Configuration file errors encountered -- exiting
      
      
      

      FOG 1.2.0 Base install dhcpd.conf before trunk update

      # DHCP Server Configuration file.
      # see /usr/share/doc/dhcp*/dhcpd.conf.sample
      # This file was created by FOG
      use-host-decl-names on;
      
      ddns-update-style interim;
      ignore client-updates;
      next-server 192.168.0.2;
      
      subnet 192.168.0.0 netmask 255.255.255.0 {
              option subnet-mask              255.255.255.0;
              range dynamic-bootp 192.168.0.10 192.168.0.254;
              default-lease-time 21600;
              max-lease-time 43200;
      #	option domain-name-servers      x.x.x.x;
      #	option routers      x.x.x.x;
              filename "undionly.kpxe";
      
      }
      
      

      FOG 1.2.0 dhcpd.conf AFTER trunk update

      # DHCP Server Configuration file
      #see /usr/share/doc/dhcp*/dhcpd.conf.sample
      # This file was created by FOG
      #Definition of PXE-specific options
      # Code 1: Multicast IP Address of bootfile
      # Code 2: UDP Port that client should monitor for MTFTP Responses
      # Code 3: UDP Port that MTFTP servers are using to listen for MTFTP requests
      # Code 4: Number of seconds a client must listen for activity before trying
      #         to start a new MTFTP transfer
      # Code
          5: Number of seconds a client must listen before trying to restart
      #         a MTFTP transfer
      
      option space PXE;
      option PXE.mtftp-ip code 1 = ip-address;
      option PXE.mtftp-cport code 2 = unsigned integer 16;
      option PXE.mtftp-sport code 3 = unsigned integer 16;
      option PXE.mtftp-tmout code 4 = unsigned integer 8;
      option PXE.mtftp-delay code 5 = unsigned integer 8;
      option arch code 93 = unsigned integer 16; # RFC4578
      
      use-host-decl-names on;
      ddns-update-style interim;
      ignore client-updates;
      next-server 192.168.0.2;
      
      # Specify subnet of ether device you do NOT want service. for systems with
      # two or more ethernet devices.
      # subnet 136.165.0.0 netmask 255.255.0.0 {}
      
      subnet 192.168.0.0 netmask 255.255.255.0 {
      	option subnet-mask 255.255.255.0;
      	range dynamic-bootp 192.168.0.10 192.168.0.254;
      	default-lease-time 21600
      	max-lease-time 43200;
      	#	option domain-name-servers      x.x.x.x;
      	#	option routers      x.x.x.x;
      	filename ;
      
      }
      
      
      posted in FOG Problems
      P
      Paul Freeman
    • RE: Trouble with Windows 8.1 image using Host Reg Bypass

      Ok I now have my test setup on a Virtualbox host with all of the same settings I was using on the physical machine and this time the update to trunk has no problems at all. I am able to PXE boot using my test machine.

      It was not my intention to suggest that I will not be using Trunk or attempting to update to the latest and greatest. During this “test” I realized i could improve my methods a little. In the future I will be sure to report problems with my tests and try to work through them with the experts rather than just starting over off the bat.

      I am going to test the functionality of my original posted question and I will report back.

      posted in FOG Problems
      P
      Paul Freeman
    • RE: Trouble with Windows 8.1 image using Host Reg Bypass

      I am going to take the opportunity to setup the test server on a VM so I can make the rollback process easier. Once i get this setup I will try again and request help.

      My production setup does not utilize the FOG DHCP service and i unfortunately do not have the resources to emulate prod so there wont be an issue related to DHCP on my production machine.

      posted in FOG Problems
      P
      Paul Freeman
    • RE: Trouble with Windows 8.1 image using Host Reg Bypass

      Well unfortunately when I loaded Trunk on my test setup it caused the fog DHCP server to stop functioning. I am going to start over on the test machine.

      posted in FOG Problems
      P
      Paul Freeman
    • RE: Trouble with Windows 8.1 image using Host Reg Bypass

      Thank you for that. I will give this a try on my test setup and report back.

      posted in FOG Problems
      P
      Paul Freeman
    • Trouble with Windows 8.1 image using Host Reg Bypass

      Using Fog 1.2.0 on Linux Mint 17.1 everything has been working perfectly up until this point. I know this isn’t an official feature (even though i would love it to be) but I am running into some trouble using the Host Registration Bypass.

      All of our Windows 7 images with Single disk resizable images it seem to work fine but I am trying to add a Windows 8.1 image that uses a single disk multi partition non resizable image and i get the error “Unable to locate image file for Windows 7/8 (sys.img.000)” I made what seems like the correct changes and tried a few different configurations to the advanced menu but always with the same result. I can pull this image down if i register a host and image normally however. Any help would be appreciated.

      Here is a copy of my advanced PXE menu. The Windows 8 image in question is IMG4 listed below.

      :MENU
      menu
      item --gap Please Select one of the images below
      item fog.local Boot from hard disk
      item img1 <Win7 64 Bit Production 3.2>
      item img2 <Public Health Win7 64 Bit Production 2.8>
      item img3 <Win7 64 Bit Laptop 3.2>
      item img4 <Win8.1 Test>
      item return Return to main menu
      choose --default fog.local target && goto ${target}
      :fog.local
      sanboot --no-describe --drive 0x80 || goto MENU
      :img1
      kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=192.168.0.1 web=${fog-ip}/fog/ consoleblank=0 loglevel=4 type=down img=WIN764PRODV3272715 ftp=${fog-ip} imgType=n osid=5 storage=${fog-ip}:/images capone=1 imgFormat=0
      imgfetch init.xz
      boot || goto MENU
      :img2
      kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=192.168.0.1 web=${fog-ip}/fog/ consoleblank=0 loglevel=4 type=down img=PH64PRODV282415 ftp=${fog-ip} imgType=n osid=5 storage=${fog-ip}:/images capone=1 imgFormat=0
      imgfetch init.xz
      boot || goto MENU
      :img3
      kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=192.168.0.1 web=${fog-ip}/fog/ consoleblank=0 loglevel=4 type=down img=WIN764MAKV3272715 ftp=${fog-ip} imgType=n osid=5 storage=${fog-ip}:/images capone=1 imgFormat=0
      imgfetch init.xz
      boot || goto MENU
      :img4
      kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=192.168.0.1 web=${fog-ip}/fog/ consoleblank=0 loglevel=4 type=down img=81Sysprep ftp=${fog-ip} imgType=n osid=7 storage=${fog-ip}:/images capone=1 imgFormat=2
      imgfetch init.xz
      boot || goto MENU
      :return
      chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} || goto MENU
      autoboot```
      posted in FOG Problems
      P
      Paul Freeman
    • RE: FOG .33b PXE Boot woes

      I had to create the tftp directory in /var/lib. After running the commands and rebooting the client i have the same message on screen. I also tried creating the links to /var/lib/tftpboot since that was an existing directory, though that also had no effect.

      I also just tried with a newer client and receive the same error.

      posted in FOG Problems
      P
      Paul Freeman
    • RE: FOG .33b PXE Boot woes

      Not sure if this will help, but here is a screen shot of what I am getting on the client PC.

      [ATTACH=full]863[/ATTACH]

      [url=“/_imported_xf_attachments/0/863_20140530_143053.jpg?:”]20140530_143053.jpg[/url]

      posted in FOG Problems
      P
      Paul Freeman
    • RE: FOG .33b PXE Boot woes

      Good point. Is there another config file somewhere that deals with the path to the default.ipxe? I assume it just looks for it in the /tftpboot directory but perhaps this isnt the case?

      posted in FOG Problems
      P
      Paul Freeman
    • RE: FOG .33b PXE Boot woes

      Both files are in the /tftpboot folder and are set to 644. Still throwing the same error. I currently have fog as the owner of the /tftpboot directory, should i change this back to root?

      posted in FOG Problems
      P
      Paul Freeman
    • RE: FOG .33b PXE Boot woes

      Yes, I am able to retrieve undionly.kpxe and default.ipxe via TFTP.

      posted in FOG Problems
      P
      Paul Freeman
    • RE: FOG .33b PXE Boot woes

      Changed ownership of /tftpboot to fog user and group and restarted the services and no change.

      posted in FOG Problems
      P
      Paul Freeman
    • RE: FOG .33b PXE Boot woes

      Restarted the service and now it will boot back into iPXE. Now it stops at [I]/default.ipxe… No such file or directory ([url]http://ipxe.org/2d12603b[/url]) [/I]This reads to me like a permissions issue since the file is in the /tftpboot directory.

      posted in FOG Problems
      P
      Paul Freeman
    • RE: FOG .33b PXE Boot woes

      Hello again all.

      I would like to thank you all for your hard work and dedication to the FOG project and all the support you offer everyone and to myself.

      After seeing that .33 was in RC status I decided to wait for the full release. Now I have a fresh install of 1.01 on linux Mint 16 running in production using Cisco router DHCP on 1 NIC.

      I have followed the instructions via the WIKI for using DNSMASQ and after completion I was able to get a PC to start to load into iPXE. It had stopped at trying to load /default.ipxe and I was not sure why, so I rebooted the server and now the machines will no longer boot to iPXE. It now stops again at [I]PXE-E32: TFTP open timeout[/I]. I have verified that both TFTPD-HPA and DNSMASQ services are running.

      I do not understand why it would stop working after a reboot when nothing else has changed.

      posted in FOG Problems
      P
      Paul Freeman
    • RE: FOG .33b PXE Boot woes

      I had rebooted the server machine completely with the same result. Though when i try to restart the tftpd-hpa service it hangs and does not seem to want to start it again. And after a reboot when trying to restart the service the machine hangs at shutdown. Sounds like I may have other issues anyway. Would sorta make sense, i have been all over the place trying to get this thing to work.

      posted in FOG Problems
      P
      Paul Freeman
    • RE: FOG .33b PXE Boot woes

      I was able to download default.ipxe with that command successfully. I am thinking I will start over on my FOG config using what I have learned with this thread and see where that gets me.

      posted in FOG Problems
      P
      Paul Freeman
    • RE: FOG .33b PXE Boot woes

      File exists and FOG has permission to use it. The contents are pointing to the IP of the Server. It was set to Net0 so i changed that to net1 as I am using eth1 for the connections but that had no effect.

      This is what my default.ipxe file looks like.
      [CODE]#!ipxe
      chain http://192.168.1.99/fog/service/ipxe/boot.php?mac=${net1/mac}[/CODE]

      posted in FOG Problems
      P
      Paul Freeman
    • RE: FOG .33b PXE Boot woes

      Awesome! After making the changes the machines are now able to boot to iPXE. HOWEVER, now it is saying it cannot find /default.ipxe. FOG is set as the owner for everything in the /tftpboot folder so i cant imagine its a permissions problem. Perhaps is there another config elsewhere that needs to be changed?

      [ATTACH=full]665[/ATTACH]

      [url=“/_imported_xf_attachments/0/665_IMG_20140414_120339.jpg?:”]IMG_20140414_120339.jpg[/url]

      posted in FOG Problems
      P
      Paul Freeman
    • 1
    • 2
    • 1 / 2