Topics created by Ravigon

Update!

So I upgraded to Ubuntu 18.04 which did not resolve the issue. I then updated FOG to 1.5.9.71 which must have been release today 🙂 . After completing the FOG update, the services are running and I was able to successfully deploy 2 machines using multicast. I rebooted the server and verified that the services started after a reboot. Thanks for your help and working on this awesome software!

Glad that helped. The beauty of an active forum where ones struggle becomes others solution. Pretty cool.

@ravigon Thank you very much for reporting this. Most definitely this difference is due to Microsoft changing something through a patch made public after our wiki article was initially published. I will get this updated photo into the wiki and again thanks for this! #wiki worthy.

After checking the log I saw that it was still looking at eno1. I found where I missed changing the interface under the default storage node under Storage Management. After changing the Interface setting from eno1 to enp7s0f0 all is good. Hopefully someone else will find this useful.

You can set kernel parameters on a global basis (as you found). You can also set kernel parameters on a per-host basis too (I assume it also applies to FOG groups). So only host will know about shutting down after imaging (or any time bzImage is transferred to the target computer).

BUT I think your quest has merit as a feature request. (in my non-programmer opinion) There should be an option on the setup page for multicast to shutdown after imaging, just like there is for a unicast image. I can see value in having that part of the core function of FOG.

@jgallo Oh I see now. I needed to modify the fog.postinit file to call patch.fullreg. So now the last line in fog.postinit reads
. ${postinitpath}patch.fullreg With that final modification, my custom registration menu now works! Thank you for all the help, this community has been great and I am really liking FOG.

@tom-elliott Great! Thanks, will do.