@sebastian-roth not really, there are a few references to the same problem, and only one person said they were successful by taking the undionly.kpxe file from a debian 10.4 installation.

I will complete this image on a physical machine, it not a big issue. It is just super convenient when working remotely that’s all.

Thanks for taking to time to reply.

Zufar

@sebastian-roth I am having the same issue with ipxe initialialising devices… when booting a generation 1 VM running on Server 2019 HyperV.

generation 2 VM’s pxe boot fine, but we still have computers that have BIOS only, hence the need to build gen 1 VM’s.

I am running the latest dev-branch version: 1.5.9.57, kernel versions 4.19.143

It works fine at another site on Server 2016 Hyper V.

Did you ever figure out a workaround?

Zufar

@Sebastian-Roth the legacy ini file doesn’t contain any credentials. Just what options you want enabling on the client. We only enable the hostname changer.

With the new client, it sounds like if the option is enabled in the gui, it’ll just invoke that on the client?

I have been using the legacy fog client up till now.

On the new client there are is no option to enable sub services for the client i.e hostname changer like the legacy client.

I don’t get these sub options.

Instead I get a settings.json file with limited settings. see below.

{
“HTTPS”: “0”,
“Tray”: “0”,
“Server”: “fogserver”,
“WebRoot”: “/fog”,
“Version”: “0.11.16”,
“Company”: “FOG”,
“RootLog”: “1”
}

I have searched and not found any resources that tell me how I can add the sub services to the .json file! more precisely, what settings are available to add to this file. All I want is to add the hostname changer setting.

Please help!