@phil_guy did you configure ISC-DHCP yourself? I’m assuming so the way you use the term.
Just because DHCP is running and handing out IPs, that doesn’t mean it’s configured correctly for fog. Please post the configuration file: /etc/dhcp/dhcpd.conf
Also, try to restart the tftp-hpa service.
Reading through this thread, I’d say we need a champion to help the FOG Project with the money and process. Here is where any for-profit company reading this should consider helping with two things.
Personally, I think it should be Microsoft who helps. If FOG is unable to easily deploy Windows 11 due to secureboot related difficulties, School Districts will have further reason to just buy Chromebooks instead of Windows PCs.
Cross linking similar threads:
https://forums.fogproject.org/topic/7855/sql-error-when-upgrading-database-schema
https://forums.fogproject.org/topic/7873/sql-error-after-updating-to-trunk-at-login
https://forums.fogproject.org/topic/7862/nfs-mount-fails-network-unreachable/16
@fry_p said in Windows 11/Future for Us:
Just out of curiosity, how much would it cost to have Microsoft to sign the certs?
Microsoft should consider doing this for FOG as a donation.
It’s got a special section just for iPXE.
If your submission contains iPXE functionality, then additional security steps are required. Previously, Microsoft has completed an in depth security review of 2Pint’s iPXE branch. In order for new submissions with iPXE to be signed, they must complete the following steps:
Pull and merge from 2Pint's commit: http://git.ipxe.org/ipxe.git/commitdiff/7428ab7
Get a security review from a verified vendor. Refer vendor to the iPXE Security Assurance Review blog post. Emphasis of the review should be on:
NFS functionality being removed
Wireless functionality being removed
Non-UEFI loaders are not included
Ensuring all known reported security problems are fixed (identified in the iPXE Security Assurance Review blog post).
Share the specific commits that are made to the project, allowing Microsoft to ensure the expected changes are made.
2 answers in under 2 minutes, from a moderator and a senior developer - for free. Can Microsoft do that? Nope. Takes them 2 days to respond to a paid support email.
Is it possible to use fog with an existing pxe server ?
Depends on the setup, but generally Yes. The only thing that would prevent you is not being able or not knowing how to chain-load to other things. There is no one way to do it, and some things are harder than others to chain-load.
What would be the configuration in my PXE server (default file in pxelinux.cfg directory)
Normally when people have a pre-existing something that uses network booting and they want to add fog, we recommend setting up FOG as the next-server and setting one of the boot files used with FOG as DHCP option 067 (either in windows server or isc-dhcp). After this is in place, you can create menu items on the fog boot menu that will chain to other items on your network. For instance you can chain to DBAN or a Windows PE environment to install Win7, or a live Linux, or Symantec Ghost. And now thanks to @Tom-Elliott, you can now edit and create tasks via a plugin system in the FOG web interface. Meaning if you have a system setup to image via symantec - You’d create a task in FOG to tell that client to basically chain to your ghost server. I’m almost positive this can be done, although I haven’t done it myself… FOG has eliminated my need for symantec ghost completely.
Where are located client boot images ?
If you mean FOG’s boot files, they are in /tftpboot after you install FOG. If you mean the actual images that you upload from hosts to the fog server, generally, they are located in /images
i saw that it could be better to use ipxe, it’s not possible to use pxelinux.0
You might not need to use pxelinux.0 initially because of chain-loading abilities.
Does fog support that my server is in 3 differents networks ? and what is the way to make it works like that ?
You would configure the FOG Server’s single NIC as a trunk port, and then configure the port on the switch it connects to as a trunk port with all three vlan networks assigned to that port. Then create three virtual NICS on the fog server that connect through the physical NIC on the server. Assign each virtual NIC to a network… OR if you are lucky enough to have three physical NICs on the fog server, you could simply connect each one to a port on a switch assigned to the correct vlan. You would then configure your isc-dchp to operate properly on each network, handing out the correct 066 and 067 options. L3 routing takes care of the rest.
There is a thread somewhere here in the forums about this exact thing but… I apologize, our new forum’s search feature isn’t all that great… I’ve instead found examples from external sites for you to learn from. Feel free to do additional research though (and I would encourage additional research).
http://www.microhowto.info/howto/configure_an_ethernet_interface_as_a_vlan_trunk.html
http://www.microhowto.info/howto/configure_an_ethernet_interface_as_a_vlan_trunk_on_debian.html
http://www.microhowto.info/howto/configure_an_ethernet_interface_as_a_vlan_trunk_on_redhat.html
I can help with more exact configuration - but I need you to first choose a path and attempt the configuration yourself. If you have problems, come back and let us know. We’re here to help. Also, if you are successful, please come back and share how you did it. This is one way you can give back to the community - by leaving behind instructions on how you did it for others to read and use.
Also, for this endeavor, I’d really urge you to use FOG Trunk. Many of the FOG features I mentioned are only available in the Trunk version. Here is a link on that, and no it requires no prior fog installation to be used: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
@george1421 dnsmasq with UEFI in ProxyDHCP mode now aparently works. I’m on the dnsmasq mailing list and have been keeping an eye on that topic.
https://forums.fogproject.org/topic/7424/dnsmasq-to-support-proxydhcp-for-uefi
@brakcounty Pretty sure it’s not required.
There’s a wiki article that walks you through migration:
https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG
@gwhitfield said in FOG service on 0.10.6 not restarting after reboot:
demon ninja gremlins
We are certified demon ninja gremlin dispatchers.
Pinging our partitioning hot shots @Tom-Elliott @Sebastian-Roth @george1421
Also, what’s the output of: fdisk -l /images/UPSpvc/d1.mbr ?
And the output of this: cat /images/UPSpvc/d1.fixed_size_partitions
@JJ-Fullmer Yup. I copied the wrong number lol.
Maybe checkmark boxes in the image definition to tell the inits to move the start sectors? Could be I guess 5 checkboxes, for 5 partitions. Some may have more partitions than that but I think 5 would cover most.
Well, to join a domain automatically - you need the fog client installed.
To manage host names - you need the fog client installed.
To do a full host registration, you just pick that from the boot menu, tell it you want to join the domain, give the correct name, and so on.
Quick register assigns the MAC address as the computer name - any that show up like that were quick registered.
What version of FOG are you using? What version of the fog client?
What I don’t understand is why people are using Ubuntu 12.
Windows 7 will setup a GPT partition layout and install that way if the system it’s installing on is operating in UEFI mode (I think).
@mabarton said in Chainloading failure: Toshiba Tecra C40-C UEFI & Samsung SSD MZNLF128HCHP-000:
@Tom-Elliott
It doesn’t
Then make it.
mkdir /home/fog
chown fog:fog /home/fog