• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. 88fingerslukee
    3. Posts
    8
    • Profile
    • Following 0
    • Followers 0
    • Topics 11
    • Posts 46
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: Chainloading Failed on EXIT - Hangs on REFIND_EFI

      Okay, so totally weird. It must’ve worked at some point because I had to leave for a while but when I came back it was at the linux prompt. Here’s the lsblk command, sda is the system SSD.

      NAME    MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
      sdb       8:16    0   298.1G  0 disk
      └─sdb1    8:17    0   298.1G 0 part
        sda      8:0   0   238.5G  0 disk
      └─sda4    8:4   0    238G   0 part
      └─sda2    8:2   0   100M  0 part
      └─sda3    8:3   0   128M  0 part
      └─sda1    8:1   0   300M   0 part
      
      

      When I rebooted it went back to the open timeout. So I have no idea what the deal is here.

      posted in FOG Problems
      8
      88fingerslukee
    • RE: Chainloading Failed on EXIT - Hangs on REFIND_EFI

      Sorry, that was without the capture task . Here is what you actually asked for:

      #!ipxe
      set fog-ip 192.168.1.184
      set fog-webroot fog
      set boot-url http://${fog-ip}/${fog-webroot}
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 mac=xx:xx:xx:xx:xx:xx ftp=192.168.1.184 storage=192.168.1.184://files/images/dev/ storageip=192.168.1.184 osid=7 irqpoll hostname=HOST chkdsk=0 img=IMG imgType=n imgPartitionType=all imgid=10 imgFormat= PIGZ_COMP=-6 hostearly=1 pct=5 ignorepg=1 isdebug=yes type=up
      imgfetch init_32.xz
      boot

      posted in FOG Problems
      8
      88fingerslukee
    • RE: Chainloading Failed on EXIT - Hangs on REFIND_EFI

      I get this:

      #!ipxe
      set fog-ip 192.168.1.184
      set fog-webroot fog
      set boot-url http://${fog-ip}/${fog-webroot}
      cpuid --ext 29 && set arch x86_64 || set arch i386
      goto get_console
      :console_set
      colour --rgb 0x00567a 1 ||
      colour --rgb 0x00567a 2 ||
      colour --rgb 0x00567a 4 ||
      cpair --foreground 7 --background 2 2 ||
      goto MENU
      :alt_console
      cpair --background 0 1 ||
      cpair --background 1 2 ||
      goto MENU
      :get_console
      console --picture http://192.168.1.184/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
      :MENU
      menu
      colour --rgb 0x00567a 0 ||
      cpair --foreground 1 1 ||
      cpair --foreground 0 3 ||
      cpair --foreground 4 4 ||
      item --gap Host is registered as PSI1!
      item --gap -- -------------------------------------
      item fog.local Boot from hard disk
      item fog.memtest Run Memtest86+
      item fog.keyreg Update Product Key
      item fog.deployimage Deploy Image
      item fog.multijoin Join Multicast Session
      item fog.quickdel Quick Host Deletion
      item fog.sysinfo Client System Information (Compatibility)
      choose --default fog.local --timeout 5000 target && goto ${target}
      :fog.local
      imgfetch ${boot-url}/service/ipxe/refind.conf
      chain -ar ${boot-url}/service/ipxe/refind.efi || goto MENU
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 loglevel=4
      imgfetch init_32.xz
      boot || goto MENU
      :fog.memtest
      kernel memdisk iso raw
      initrd memtest.bin
      boot || goto MENU
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 loglevel=4
      imgfetch init_32.xz
      boot || goto MENU
      :fog.keyreg
      login
      params
      param mac0 ${net0/mac}
      param arch ${arch}
      param username ${username}
      param password ${password}
      param keyreg 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      :fog.deployimage
      login
      params
      param mac0 ${net0/mac}
      param arch ${arch}
      param username ${username}
      param password ${password}
      param qihost 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      :fog.multijoin
      login
      params
      param mac0 ${net0/mac}
      param arch ${arch}
      param username ${username}
      param password ${password}
      param sessionJoin 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      :fog.quickdel
      login
      params
      param mac0 ${net0/mac}
      param arch ${arch}
      param username ${username}
      param password ${password}
      param delhost 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      :fog.sysinfo
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=sysinfo
      imgfetch init_32.xz
      boot || goto MENU
      :bootme
      chain -ar http://192.168.1.184/fog/service/ipxe/boot.php##params ||
      goto MENU
      autoboot
      
      posted in FOG Problems
      8
      88fingerslukee
    • RE: Chainloading Failed on EXIT - Hangs on REFIND_EFI

      Okay, now it’s getting weird.

      When I create a capture task I get a TFTP Open Timeout error. So it’ll TFTP just fine into the menu without any task enabled but it has an issue with a task? How does that work?

      posted in FOG Problems
      8
      88fingerslukee
    • RE: Chainloading Failed on EXIT - Hangs on REFIND_EFI

      No RAID. There are 2 drives, one SSD with Windows on it, the other as a general storage drive:

      System Drive:
      Drive Controller: Serial ATA 3Gb/s
      Drive Model: CRUCIAL_CT256M225
      Drive Revision: 1819
      Drive Capacity: 244,198 MBytes (256 GB)
      Media Rotation Rate: SSD Drive (Non-rotating)

      Storage Drive:
      Drive Controller: Serial ATA 3Gb/s
      Drive Model: WDC WD3200AAKS-00L9A0
      Drive Revision: 01.03E01
      Drive Capacity: 305,245 MBytes (320 GB)

      posted in FOG Problems
      8
      88fingerslukee
    • Chainloading Failed on EXIT - Hangs on REFIND_EFI
      Server
      • FOG Version: 1.3.0-RC-25
      • OS: CentOS 6.8
      Client
      • Service Version:
      • OS: Windows Server 2012 R2
      • System Manufacturer: Gigabyte Technology Co., Ltd.
      • System Product: GA-78LMT-USB3 6.0
      Description

      This motherboard boots to the menu just fine but gives the Chainloading error when using the EXIT option. When using REFIND_EFI or SANBOOT it hangs with the blinking cursor in the top left corner. The GRUB options don’t work because it’s a Windows EFI installation.

      I have no “Secure Chip” or Secure Boot settings in the BIOS so this is why I’m posting a new thread. It seems my issue might be different than the others.

      I’d love to get this working as I have several of these motherboards in my install base. I’m happy to do some digging, just please let me know what I have to do.
      Here is my boot.php file from (http://x.x.x.x/fog/service/ipxe/boot.php)

      #!ipxe
      set fog-ip x.x.x.x
      set fog-webroot fog
      set boot-url http://${fog-ip}/${fog-webroot}
      cpuid --ext 29 && set arch x86_64 || set arch i386
      goto get_console
      :console_set
      colour --rgb 0x00567a 1 ||
      colour --rgb 0x00567a 2 ||
      colour --rgb 0x00567a 4 ||
      cpair --foreground 7 --background 2 2 ||
      goto MENU
      :alt_console
      cpair --background 0 1 ||
      cpair --background 1 2 ||
      goto MENU
      :get_console
      console --picture http://x.x.x.x/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
      :MENU
      menu
      colour --rgb 0xff0000 0 ||
      cpair --foreground 1 1 ||
      cpair --foreground 0 3 ||
      cpair --foreground 4 4 ||
      item --gap Host is NOT registered!
      item --gap -- -------------------------------------
      item fog.local Boot from hard disk
      item fog.memtest Run Memtest86+
      item fog.reginput Perform Full Host Registration and Inventory
      item fog.reg Quick Registration and Inventory
      item fog.deployimage Deploy Image
      item fog.multijoin Join Multicast Session
      item fog.sysinfo Client System Information (Compatibility)
      choose --default fog.local --timeout 5000 target && goto ${target}
      :fog.local
      sanboot --no-describe --drive 0x80 || goto MENU
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 loglevel=4
      imgfetch init_32.xz
      boot || goto MENU
      :fog.memtest
      kernel memdisk iso raw
      initrd memtest.bin
      boot || goto MENU
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 loglevel=4
      imgfetch init_32.xz
      boot || goto MENU
      :fog.reginput
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=manreg
      imgfetch init_32.xz
      boot || goto MENU
      :fog.reg
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=autoreg
      imgfetch init_32.xz
      boot || goto MENU
      :fog.deployimage
      login
      params
      param mac0 ${net0/mac}
      param arch ${arch}
      param username ${username}
      param password ${password}
      param qihost 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      :fog.multijoin
      login
      params
      param mac0 ${net0/mac}
      param arch ${arch}
      param username ${username}
      param password ${password}
      param sessionJoin 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      :fog.sysinfo
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=x.x.x.x/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=sysinfo
      imgfetch init_32.xz
      boot || goto MENU
      :bootme
      chain -ar http://x.x.x.x/fog/service/ipxe/boot.php##params ||
      goto MENU
      autoboot
      

      thanks
      Lucas

      posted in FOG Problems
      8
      88fingerslukee
    • RE: Fog Installation Error - Cannot restart MySQL

      @Tom-Elliott

      I don’t know how to clarify that. What I know is that the installer fails at trying to restart mysqld. If I edit the mysqld init file adn re-run the installer, the init file is overwritten.

      Nothing else gets installed because of the failure.

      posted in FOG Problems
      8
      88fingerslukee
    • RE: Fog Installation Error - Cannot restart MySQL

      I removed the folder and reran the installer and it still fails. It doesn’t create any files in /var/www/fog or /var/www/html/fog

      How do I change the installer so that it doesn’t overwrite my myslqd init file?

      posted in FOG Problems
      8
      88fingerslukee
    • Fog Installation Error - Cannot restart MySQL
      Server
      • FOG Version: 1.3.0-RC2
      • OS: Centos 6
      Description

      I’m trying to update from RC2 to the latest (RC13 but this happend on RC11 as well).

      The installation fails when trying to restart mysql. The error looks like this:

      * Setting up and starting MySQL...............................Failed!
      

      When I try to manually start mysql after that I get this:

      /etc/init.d/mysqld: line 103: syntax error near unexpected token `fi'
      /etc/init.d/mysqld: line 103: ` fi'
      

      So I go into the mysqld init file and I see the following:

              # If startsos
              if [ "$1" = "sos" ] ; then
              #        MYOPTIONS="$MYOPTIONS --skip-grant-tables --skip-networking"
              fi
      

      When I remove the comment from the MYOPTIONS line, everything starts correctly, but fog is still on RC2.

      Any thoughts?

      posted in FOG Problems
      8
      88fingerslukee
    • RE: Fog Trunk Autologging Out Immediately

      @Tom-Elliott said in Fog Trunk Autologging Out Immediately:

      I did not update the text because I think it’s simpler to enter values in the form of “720 minutes” vs having users run calculations on their own (no offense anybody).

      That said, I was unaware the logout time was being done in seconds and not performing the calculation as it had under the legacy client. (Oversight I suppose, for that i’m sorry).

      This has been patched and pushed though. Thanks for letting us know.

      I agree wholeheartedly and I can confirm that this is now working as it should on the latest 1.3.0-RC2 version.

      thanks!

      posted in FOG Problems
      8
      88fingerslukee
    • RE: Fog Trunk Autologging Out Immediately

      Thanks for your reply. This is the log I was looking for. It appears that the machine is being set to logout after 720 SECONDS, not minutes as the GUI says. So is this a bug or is the GUI wrong?

      ------------------------------------------------------------------------------
      ----------------------------------AutoLogOut----------------------------------
      ------------------------------------------------------------------------------
       7/15/2016 3:20 PM Client-Info Client Version: 0.11.3
       7/15/2016 3:20 PM Client-Info Client OS:      Windows
       7/15/2016 3:20 PM Client-Info Server Version: 8595
       7/15/2016 3:20 PM Middleware::Response Success
       7/15/2016 3:20 PM AutoLogOut Time set to 720 seconds
       7/15/2016 3:20 PM AutoLogOut Inactive for 1 seconds```
      posted in FOG Problems
      8
      88fingerslukee
    • Fog Trunk Autologging Out Immediately

      Hi Everybody,

      Apologies if this has been answered but I have looked everywhere and cannot find where somebody has had this issue. I’m running the latest version of FOG Trunk and 11.3 of the client on my Windows machines. I have Auto Logout selected with a default setting of 720 minutes.

      The issue I face is that the clients are logging out immediately upon going idle. The client log doesn’t show AutoLogout logs at all, so I’m having a difficult time trying to troubleshoot.

      Any help would be greatly appreciated.

      thanks
      88

      posted in FOG Problems
      8
      88fingerslukee
    • RE: Auto Log Out not Logging Out

      Nobody has ever seen this before?

      To add to this, if I set a task, it doesn’t restart the computer.

      The Fog Service is running but the client isn’t responding.

      What’s going on here?

      posted in FOG Problems
      8
      88fingerslukee
    • Auto Log Out not Logging Out

      Hi Everybody,

      The Fog Client is not logging my clients out. They are registered and they can be pinged when I List All Hosts in the Host Management page.

      I have set AutoLogout to on and set it to 720 minutes but nothing is happening.

      fog.log:

      [CODE] 7/17/2014 9:46 AM FOG::HostnameChanger Sleeping for 1 minute.
      7/17/2014 9:47 AM FOG Service Engine Version: 3
      7/17/2014 9:47 AM Starting all sub processes
      7/17/2014 9:48 AM 14 modules loaded
      7/17/2014 9:48 AM * Starting FOG.AutoLogOut
      7/17/2014 9:48 AM * Starting FOG.SnapinClient
      7/17/2014 9:48 AM * Starting FOG.DirCleaner
      7/17/2014 9:48 AM * Starting FOG.DisplayManager
      7/17/2014 9:48 AM * Starting FOG.GreenFog
      7/17/2014 9:48 AM * Starting FOG.GUIWatcher
      7/17/2014 9:48 AM * Starting FOG.HostNameChanger
      7/17/2014 9:48 AM FOG::GUIWatcher Starting GUI Watcher…
      7/17/2014 9:48 AM * Starting FOG.HostRegister
      7/17/2014 9:48 AM FOG::DisplayManager Starting display manager process…
      7/17/2014 9:48 AM FOG::AutoLogOut Starting process…
      7/17/2014 9:48 AM FOG::HostRegister Starting host registration process…
      7/17/2014 9:48 AM FOG::DirCleaner Sleeping for 40 seconds.
      7/17/2014 9:48 AM FOG::HostnameChanger Starting hostname change process…
      7/17/2014 9:48 AM FOG::HostnameChanger Yielding to other subservices for 7 seconds.
      7/17/2014 9:48 AM FOG::ClientUpdater Sleeping for 62 seconds.
      7/17/2014 9:48 AM * Starting FOG.PrinterManager
      7/17/2014 9:48 AM FOG::MODDebug Sleeping for 100 Seconds
      7/17/2014 9:48 AM * Starting FOG.SnapinClient
      7/17/2014 9:48 AM * Starting FOG.TaskReboot
      7/17/2014 9:48 AM FOG::PrinterManager Starting interprocess communication process…
      7/17/2014 9:48 AM * Starting FOG.UserCleanup
      7/17/2014 9:48 AM FOG::PrinterManager interprocess comm startup: OK
      7/17/2014 9:48 AM * Starting FOG.UserTracker
      7/17/2014 9:48 AM FOG::TaskReboot Starting Task Reboot…
      7/17/2014 9:48 AM FOG::UserCleanup Sleeping for 12 seconds.
      7/17/2014 9:48 AM FOG::UserTracker Starting user tracking process…
      7/17/2014 9:48 AM FOG::SnapinClient Starting snapin client process…
      7/17/2014 9:48 AM FOG::UserCleanup Starting user cleanup process…
      7/17/2014 9:48 AM FOG::DirCleaner Starting directory cleaning process…
      7/17/2014 9:48 AM FOG::GreenFog Starting green fog…
      7/17/2014 9:49 AM N/A Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
      7/17/2014 9:49 AM FOG::AutoLogOut Unable to continue, MAC is null!
      7/17/2014 9:49 AM FOG::MODDebug Reading config settings…
      7/17/2014 9:49 AM FOG::MODDebug Reading of config settings passed.
      7/17/2014 9:49 AM FOG::MODDebug Starting Core processing…
      7/17/2014 9:49 AM FOG::MODDebug Operating System ID: 6
      7/17/2014 9:49 AM FOG::MODDebug Operating System Minor: 1
      7/17/2014 9:52 AM FOG::UserTracker Unable to determine MAC address, exiting…
      7/17/2014 9:52 AM FOG::TaskReboot Attempting to connect to fog server…
      7/17/2014 9:52 AM FOG::MODDebug MAC ID 0 80:EE:73:3A:DB:FD
      7/17/2014 9:52 AM FOG::MODDebug MAC POST String: 80:EE:73:3A:DB:FD
      7/17/2014 9:52 AM FOG::MODDebug A user is currently logged in
      7/17/2014 9:52 AM FOG::MODDebug Username: DOMAIN\user
      7/17/2014 9:52 AM FOG::MODDebug Hostname: COMPUTER
      7/17/2014 9:52 AM FOG::MODDebug Attempting to open connect to: http://192.168.1.184/fog/service/debug.php
      7/17/2014 9:52 AM FOG::UserCleanup Module is disabled globally on the FOG Server, exiting.
      7/17/2014 9:52 AM FOG::ClientUpdater Module is active…
      7/17/2014 9:52 AM FOG::DirCleaner Module is active…
      7/17/2014 9:52 AM FOG::DirCleaner Determining which directories should be cleaned…
      7/17/2014 9:52 AM FOG::DirCleaner No directories are configured to be cleaned.
      7/17/2014 9:52 AM FOG::DirCleaner Starting directory cleaning loop…
      7/17/2014 9:52 AM FOG::DirCleaner Module has finished work and will now exit.
      7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : AutoLogOut.dll
      7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
      7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : ClientUpdater.dll
      7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
      7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : DirCleaner.dll
      7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
      7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : DisplayManager.dll
      7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
      7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : GreenFog.dll
      7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
      7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : GUIWatcher.dll
      7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
      7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : HostRegister.dll
      7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
      7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : MODDebug.dll
      7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
      7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : PrinterManager.dll
      7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
      7/17/2014 9:52 AM FOG::GreenFog Module is active…
      7/17/2014 9:52 AM FOG::GreenFog No actions were found.
      7/17/2014 9:52 AM FOG::GreenFog No tasks found after validation!
      7/17/2014 9:52 AM FOG::TaskReboot Module is active…
      7/17/2014 9:52 AM FOG::TaskReboot Attempting to connect to fog server…
      7/17/2014 9:52 AM FOG::HostnameChanger Module is active…
      7/17/2014 9:52 AM FOG::MODDebug Server responded with: Hello FOG Client
      7/17/2014 9:52 AM FOG::MODDebug Module has finished work and will now exit.
      7/17/2014 9:52 AM FOG::TaskReboot No task found for client.
      7/17/2014 9:52 AM FOG::HostnameChanger Hostname is up to date
      7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : SnapinClient.dll
      7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
      7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : TaskReboot.dll
      7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
      7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : UserCleanup.dll
      7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
      7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : UserTracker.dll
      7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
      7/17/2014 9:52 AM FOG::ClientUpdater Checking Status : config.ini
      7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
      7/17/2014 9:52 AM FOG::ClientUpdater Zero byte response returned
      7/17/2014 9:52 AM FOG::ClientUpdater 0 new modules found!
      7/17/2014 9:52 AM FOG::ClientUpdater Client update will be applied during next service startup.
      7/17/2014 9:52 AM FOG::ClientUpdater Client update process complete, exiting…
      [/CODE]

      What am I doing wrong?

      posted in FOG Problems
      8
      88fingerslukee
    • RE: TFTP Open Timeout

      I’ve solved this. I hadn’t configured dhcpd.conf correctly in my pfSense router.

      Apparently, [CODE]option tftp-server-name “ipaddressofserver”;[/CODE] doesn’t do anything, which I find weird. Only the [CODE]next-server[/CODE] seems to work.

      Thanks for your help everybody.

      posted in FOG Problems
      8
      88fingerslukee
    • RE: TFTP Open Timeout

      option 67 was set to undionly.kpxe.

      [CODE] tftp x.x.x.x get undionly.kpxe[/CODE]

      gives me a server error:

      tftpd: read(ack): Connection refused

      selinux is set to permissive and iptables is off. Permissions on /tftpboot are 777.

      posted in FOG Problems
      8
      88fingerslukee
    • TFTP Open Timeout

      Forgive me if this has been answered before but I couldn’t find the solution. I used to have v.32 working just fine.

      I keep getting a TFTP Open Timeout error when a client tries to boot. I can’t get this thing to boot from the server.

      CentOS 6 Server running FOG 1.1.1 (TFTP without DHCP)
      PFsense router with DHCP correctly configured. The clients are given DHCP addresses properly.
      firewall is disabled
      Option 67 is set as /undionly.kpxe.

      Am I doing this right? I can’t tell if TFTP is running because it’s under xinet. That part is new to me.

      posted in FOG Problems
      8
      88fingerslukee
    • RE: Windows 7 image deployment, constant rebooting

      Okay, so I read more and figured out that sysprep does what I need it to do. Questions though:

      1.) What is sysprep actually doing?
      2.) Can I only use it a max of 3 times?

      posted in Windows Problems
      8
      88fingerslukee
    • Windows 7 image deployment, constant rebooting

      Hi everybody,

      so far I think FOG is amazing, but I’m having a bit of trouble deploying an image.

      I’m using FOG to bare-metal backup all of our workstations. They are mostly different hardware so I’m looking for a way to deploy the backed-up image to a new machine if needed (eg. the old hardware dies and cannot be replaced). The problem I’m having is that the image will deploy fine, but the system reboots at the Windows 7 startup screen and I cannot get it to boot.

      Now, I’ve seen this before and I’ve never had a way to get around it. If the drivers configured in the original image don’t jive with the new hardware, I can’t get the system to boot.

      Is there any way of imaging the workstations such that their images can be deployed to any type of hardware? Or am I looking for something that’s impossible?

      thanks for any help.

      posted in Windows Problems
      8
      88fingerslukee
    • RE: [SOLVED] PXE-E51 "No DHCP or DHCP Proxy Offers received"

      Thanks for the info. That’s useful.

      posted in Hardware Compatibility
      8
      88fingerslukee
    • 1
    • 2
    • 3
    • 2 / 3