Hello @george1421!

absolutely amazing. I just found a tutorial that shows you how to do that on the FOG website. It’s a shame that the google TOP site when you search the keywords “how to install fog server” doesn’t include this information. I’ve tried to install FOG on several other distros as well, all with the same sort of issues. I can be confident in assuming that switch to the dev-branch would rectify all issues with the distros i’ve tried before. Thank you so much for your assistance!

@sebastian-roth This actually worked. Thank you so much!

@tbasura First let me say I know nothing about how acronis works. But for PXE booting there are two methods.

Update dhcp options 66 with the fog server’s ip address. Update dhcp option 67 with ipxe.efi for uefi or undionly.kpxe for bios based computers.

Configure a proxy dhcp server. The proxy dhcp server will send out pxe boot information that will override option 1’s settings.

If you install acronis on a server some place and its taken over pxe boot control that is probably your problem. On the box where the acronis server is installed… Check to see if there are any acronis services running, like netboot, or pxe booting service. It might be wise to just stop all acronis services on that test server.

@george1421 Does seem to be a problem with this computer on a second look. This computer is a HP 290 G3, it’s now showing “EFI stub: loaded initrd from command line option” upon deploying the image.

I’ve managed to image another computer of the same model and it worked fine, I’ve also managed to image an older machine and that worked fine.

@arunpalepu said in DHCP Configuration & BIOS configuration for Client workstation:

Can you send me the Edgemax12 router configuration setup for options 66 & 67.

Doing a search on the web I get the impression the Edge Router OS is using DNSmasq as DHCP server. Find some information on how to adjust it’s configuration via command line: https://community.ui.com/questions/Autoinstall-setup-to-support-many-EdgeSwitches/ce17c5da-7540-4e1f-b931-f7381d1d2b99#answer/7df2555d-ecd7-4105-8f1a-b3780a0ff88e

For accessing the router via CLI see manual page 93ff (page nr 89 in the PDF).

Though I think it would be way easier to setup DNSmasq as a so called DHCP proxy on your FOG server: https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_with_dnsmasq

@george1421 said in rEFInd - themes:

Also something to try is because the error references “themes\theme.conf” we might want to use the dos path separator instead of the unix one. \ vs / in the --name key value.

I did this as the first project, this is much mor work than i thought… it has to be made by hand, no search and replace…
But there is some success:

imgfetch <somename> <uri> **<somename>**

this second somename made a change and I even saw for a second the backgroundimage before it fell back to textmode! So the syntax and the path works ina way
but this fallback to textmode led only to another problem:
“Icons directory doesn’t exist; setting back textonly =TRUE”

Also in your imgfetch, I don’t see you actually sending “themes\theme.conf” to iPXE. Maybe that is why its throwing the error. Again I’m doing a lot of educated guessing here because I’ve never needed this method. So its going to be some trial and error here.

it is there 🙂 in the first row - and after adding the second “somename” on the end it works…

@thomgee Can you change the configuration file to look for the icons and images in the same path where the refind.efi and refind.conf? I really don’t know how the directory structure works within this ipxe vhd . The concerns is that its a simple directory structure where sub dirs are not supported.

Maybe I don’t need this in the moment, as it is reading the themes/theme.conf and the huge amount of files.
the Icon-dir is my problem, as refind needs is obviously somehow.
I guess it needs the default icon-folder refind ships - but I feel horrified to fetch every single file…

@george1421 The ASUS was set to uefi mode and the Levovo was set to legacy. I updated the firmware on the Lenovo and changed it from legacy to uefi and now i’m presented with the eEFIND about page.

The change worked great, Thank you!!!

iPXE itself is pretty powerful when it comes to menus and booting options, obviously your results may vary from distro to distro or application to application etc. etc.

This example is using the Advanced menu, with subcategories etc.
I haven’t had much need for this in a while due to my work changing the way the boot system here works breaking things out of my control, but this is a post from a few years back that should still work but you would need you to look up specific settings per distro based on what you are trying to do.

https://forums.fogproject.org/topic/7329/sub-menu-within-fog-advanced-menu

This guy has some impressive examples: https://gist.github.com/robinsmidsrod/2234639

Additional information DHCP Options:
https://gist.github.com/robinsmidsrod/4008017

Example for Sysrescue:
https://gist.github.com/robinsmidsrod/1c7bbd4a058f0e6892df

Results may vary. ¯\_(ツ)_/¯

Just for reference as the link did not get pasted…
https://forums.fogproject.org/topic/14621/ldap-with-access-control-default-role-assignment-at-first-login

Thanks again, George! This is the 2nd time that you have helped me!

@sebastian-roth I successfully built image from the type of computer that don’t work on image deployment. It seems to me that there must be some kind of hardware config that prevents the image deployment to expand the disk properly

@george1421 said in Certificate of Data Destruction:

e also trivial: https://www.geeksforgeeks.org/php-send-atta

Thank you so much . Makes perfect sense. Let me try that way .

@sebastian-roth I updated and it’s working now. Thank you so much!

@gregors said in FOGclient Response Failed to decrypt data on server:

The IP or the host name was not changed from the initial OS installation.

Thanks for the info. No idea what would cause the new generated cert to not match the key.

@mahammad-rafi What version of the FOS Linux kernel is installed? It sounds like bzImage is not running completely.

@mcana66 Well I want to thank you again BrakCountry. Although the solution you posed did not work, you got me delving into the scripts to figure this out on my own. Took a while but here is what I did to fix my issue of the reboot loop in the FOG menu.

First I started playing with chain boot and replaced the initial chain statement with the one below:

chain https://(Fog-IP)/fog/service/ipxe/refind.efi

This booted directly into refind.efi and booted the first hdd. So I got the thought of how many items can you chain boot?

I kicked off a job to image my target and added that chain statement to the bottom of default.ipxe because hey why not. lol. After FOG completed imaging the target, the machine performed a normal reboot and booted to boot.php##params however and I am only guessing, there were no jobs present in FOG so when the menu appeared, “Boot from HDD” was the default selection and then chain booted to the refind.efi which booted the os on the HDD.

Again thank you to all who tried to offer help or advice!!