George,

Thanks for the ideas. I am going to try to build my own customized LIVECD version and see if I can get it to run. Will report back (will most likely take me a while!).

Thanks for the insight.

Colin

@x23piracy If you want to deal with the logistical elements of doing such a thing, I can’t really stop you. I think most would worry, however, that the money they send to a third party never making it to who they intended to receive it.

@FrancoDin said in Getting inventory from all PC.:

Ok, I was thinking maybe some thing about the dchp, when the PC are on. I guess there is no way.

What exactly do you mean by that?

If you can grab all the MAC addresses from your DHCP server then you could compile a list of hosts to import to your FOG server or just run a wake on lan utility to wake those PCs for you. You still need to do the modifications @Taspharel suggested to have the clients go straight into quick register. After that you could do another round for hardware inventory…

So I guess it is possible but needs some work to be done by you. We don’t have a ready set solution for you I am afraid.

@AndrewG78 while it is true that you can incorporate our product with yours, the only request (and I believe it is covered in the GPL as well) is that you credit our software and links to our software as being included.

This way people know for things related to FOG directly know to come to us for support needs.

@robertkwild To clarify, I’m not sure if that’s what’s causing it, just an idea to try out.

You can do a clean shutdown with shutdown -s -t 0

@WalterT said in Quick register of Host removes Graphic driver:

after installing a correct graphic driver, this problem is gone. Seems to be an issue of the Intel NUC mini PCs which use a graphic driver that is not contained in windows 10 basic installation.

I have seen this many times.

For FOG you can look into driver injection method or include the drivers as part of your golden/reference image.

@WalterT
ok
now i have TWO hosts and also two physical maschines, one captured the image from and one deployed on it.

Hosstname on both machines different to the database. How to change? Client Service not installed.

@Sebastian-Roth I would think if one only wanted the system to shutdown after a full registration you could update the iPXE FOG Menu item for full registration and add in shutdown=1 to the Boot Options field.

I have not personally tried doing that, so its only an educated guess.

Yes you should rerun the installer. The update database gets the system ready for the second phase of the update done back in the linux console. If you stopped the installer waiting for the database update and then happened to hit ctrl-c and exited the installer your system will only be half way setup. There is quite a bit of actions happening after the database is configured.

It will be better if you provide further info.
While you are trying to figure it out, I’ll be busy setting up a wireless dog fence in the backyard.

@nguyenhaongnam You are right, so far FOG does not impose password complexity rules. Probably something we can add. But I am wondering what exactly your project is about? I am asking because there is no access control build into FOG either. One of our active users created a plugin (see here) but it’s not used widely and I am not sure about it’s current state.

lovely stuff, job done -

kernel http://fog/listing/centos7_1804/images/pxeboot/vmlinuz ks=http://fog/listing/centos7_1804/ks.cfg
initrd http://fog/listing/centos7_1804/images/pxeboot/initrd.img
boot || goto MENU

How do I setup my fog server so that it deploys the kickstart file to a host via PXEboot

@Daan To use FOG within a proxmox OpenVZ container you need to make sure NFS is loaded an enabled on the host system first:

# lsmod | grep nfsd nfsd 312315 14 # grep nfsd /proc/filesystems nodev nfsd

Now enable NFS for the container as well ($CONTAINER_ID is just a variable, put in the real ID of your container):

# vzctl stop $CONTAINER_ID # vzctl set $CONTAINER_ID --feature nfsd:on --save # vzctl start $CONTAINER_ID

As well make sure to set the network up as bridge (veth instead of venet) so wake on lan and multicast will work properly.

@george1421 said in Bulk editing hosts:

If you are going to mass update the database like this, stop apache and php-fpm first, then run your update, and finally restart php-fpm and then apache. Both php-fpm and apache cache database values for faster access. You are changing the underlying database but its not seen in the UI because of the cache.

#wiki worthy.

@Aaron-McLaughlin said in Backing up images:

I tried to do this, but the restored image comes up with a 0 kb size and is unable to be used.

You see the 0 kb size because when re-creating the image definition in the FOG webUI we simply don’t know the size as it is only being recorded when capturing the image.

You are saying the the image cannot be used after copying it back. This can be for various reasons.

File access rights (chmod -R 777 /images/imagename) Path name (Linux is case sensitive, so ImageName is not equal to imagename) Image definition (make sure the new definition does match the old one - resizable/non-resizable, compression method

In some cases the error on screen can shed a light on what is wrong with the image. So please take a picture of the error and post here.

Next time: Don’t touch the image definition in the web UI. Just move images to an external disk to get some space and let the definition alone. After moving it back you don’t have issues with the image definition.

Seems legit. May have to try that out.

@EAHarvey FOG supports basically all iPXE can support and then some in terms of UEFI. Do note that this does not mean all hardware will function as expected, since a lot of manufacturers decide to ignore the spec and do their own thing or some devices are so new the iPXE drivers aren’t updated for them yet.

Still, in most cases, it will work wonderfully.