The snapin issue is known about, it’s fixed in RC-9 already.
For now, hosts need images assigned in order to deploy snapins via groups.
And, you can clear host settings via groups already. It’s exactly the same as clearing them on the individual host - but with groups.
@psycholiquid My goal when I wrote that article was just to show people how create DHCP vendor classes and policies using Windows and Linux because at the time of writing there was about zero good documentation anywhere on the Internet for this stuff. The article was more of an educational one giving the tools & knowledge needed to create whatever vendor classes and policies needed.
Ofcourse we can change it to be better, or add notes, or additional sections, or whatever needs done.
Want to point out that 1.3.4 is not released as of yet. Release candidates exist, yes, but not a release deemed worthy of everyone upgrading for - yet.
Can you try undionly.kkpxe instead?
@juice381 said in Making Fog Portable:
I would have no issues switching to one of the os’s you mentioned but I don’t think they have an arm based one developed.
Sure they do.
https://arm.fedoraproject.org/
Of course, I’m still down with developing for Debian, I think Debian is just super-cool. It’s the most “free” of all Linux distributions.
#wiki worthy
@Psycholiquid thank you for the pictures and steps! I will get them included into the wiki when I can. @moderators and @testers if you have wiki access, you can help too!
Just for troubleshooting purposes only, keep the db dump on hand, drop the fog database, re-run the installer and see if it works.
The purpose of this is to isolate if it’s an issue with the imported DB, or with something else.
Here’s how to drop the db:
mysql
drop database fog;
quit
I think you might be out of IP leases… you only have a range of 50 specified…
also, try changing your bootfile to undionly.kkpxe and see what happens. I have some Optiplex 380s at home that boot just fine with undionly.kkpxe (I run a fog server at home and work).
I just setup a VM with Debian 8, going to mess with this today.
@sebastian-roth said in Linux kernel:
Just not sure if it’s worth sending it around the world as I am located in Germany.
His org could just buy you one and have it shipped to you. Of course you are deserving of much more than a crap hardware model, Sebastian. 
Fog can’t help you here, you’re going to have to manually do this.
Best way is to boot both systems with live-boot media, mount both local disks to something like /mnt and then scp the contents of each mounted partition over to the new box.
You’ll have to edit the new box’s /etc/fstab file to mount the partitions as ext4 instead of ext3
No guarantees that will work, but it’ll for sure get the files moved.
As long as whatever partition that has /boot on it is marked as bootable with fdisk then it ought to work.
@Nikolai-Domaev said:
p.s. But you really dont wanna hear where and how this server works. So im not in a mood to bother figuring out to do it.
(In short. Its a vm. On a separate vlan. Oh, no, its not a vlan, its an non existing separate network of an ex-organisation. On a hypervisor with ourdated java interface… Need to install XP to get there -.-).
You should get in the mood soon… that sounds archaic and nobody here can help you with version .32… We will just tell you to update.
FOG support consists of a limited development team, limited moderator team, and limited beta tester team…
I’ve been busy all day at my real job, and I have 13 other unread messages after yours… I simply don’t have time to bother with anything older than 1.2.0 and neither does anyone else that volunteers here.
Keep in mind that the small team that FOG has, helps for free.
It’s literally the equivalent of a mechanic pulling over to help you with your broke down car for absolutely nothing in return.
@juice381 Can you please either git pull or reclone the repo? I’ve done some work on it, it should work for Ubuntu and Debian now.
@fogubuntu said in Ubuntu Image for FOG Clients:
How do I prevent the BIOS boot order from changing after installing Ubuntu?
System boot order is set in firmware on each host. This isn’t something that fog does, it’s something you do.
How should I prepare my source image? Do I need to disable some bootloader option when I Install the OS on my source machine? I would my client machines to boot from the FOG server first before the cloned OS so that I can wipe the drive, re-image etc.
You don’t need to disable anything, don’t need to do anything particularly special to image Ubuntu - the main thing is to not use LVM. fog does not currently support resizable LVM in Linux, but does support resizing basic Ext4 partitions for Linux images. You can use non-resizable LVM images for Linux, but you’ll surely find yourself in a bind soon because of it.
The FOG Client doesn’t accept commands via CLI, it accepts commands from the FOG Server in the form of snapins, printers, reboots, shutdowns, and things that are integrated in the FOG Server. All documentation for the fog client specifically is here: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client and for sending bash scripts and such, search the forums for Snapins, there are probably a thousand threads about it. Plus these may interest you:
https://wiki.fogproject.org/wiki/index.php?title=Snapin_Examples
https://wiki.fogproject.org/wiki/index.php?title=SnapinPacks
This just further shows we need an article on JUST storage nodes… because of things like this.
@george1421 I’d go further by limiting the bind DN account to only the OUs where the fog users and fog groups will be.
@imagingmaster21 If I were you, I would rewrite that configuration to look more like this: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Example_2
Then, for Arch:00007 just play with that filename.
Make sure the path you’re going to exists, and the iso exists exactly as you’re trying to use it in the command. I don’t see anything wrong with the command.
@duanekaeb Inconsistency issues like this are - probably 50% of the time here on the forums - IP conflicts.