@theopenem_admin Yes, I saved the changes, verified them by setting console as the default selection for boot menu, so it has been loaded. But no setting I've tried can change the keyboard once the login has been shown. I am guessing I will have to recreate the boot files, I think initrd will have to be reconfigured. I have access to linux OS (Rocky Linux 8 and 9) so I think I can do it, but I don't have knowhow - well, time to learn. Can it be done? Can I manually reconfigure it?

@itisljar Hi, I have the same problems. Where you changed those stettings? Bests...

It's only saving a text file. Doesn't matter what's in it. Only two reasons I've ever seen for this are permissions on the image folder and special characters in the name

@grolsch I had to set the TOEC API config file's logging setting to debug from info. Then I got the cause of my issue (Which WAS a time zone problem)

Started to troubleshoot this ongoing issue for me and I found out, that the issue is with not finding BCD file, because the generated file is named BCDx64. After deleting the -x64, the PXE booting started working as expected.

Extra info: I have newest ADK for Win11 and newest WIE Builder 2.0.2 from TOEM website, according to the info from TOEM wiki.

I wonder why it's happening, even when I go according to the guide.

Is your application api url correct in the UI web.config?

You can use the classes since your DHCP server supports it. These are the paths.

proxy/bios/pxeboot.0
proxy/efi32/pxeboot.0
proxy/efi64/pxeboot.0

Leave your Theopenem pxe settings set to proxy.

So it appears I have it working.
I re-generated the key
Restarted the server
went in and retyped the password in LDAP and changed the LDAP Auth Type to Secure.
Updated the changes and clicked Test and it worked.
Not sure why as I did this same thing several times
But it is working.
Sorry to have bothered you

System was in another city. And I didn't have any decent remote shell options available. Remote regedit worked tho

@theopenem_admin Thanks. That has now been changed to match the correct IP and port. I am now seeing error of Could Not Find Any Usable Image Servers.

Thank you admin for the help.. I already find the solution..

I delete the "/Windows/Panther/unattend.xml" then re-upload it again to server.

@itisljar OK, to reply to myself, I've disabled in BIOS every other boot device that pointed to HDD except Windows Boot Loader, and made image with that, and it works.
Will do that as workaround.

@theopenem_admin I've got mine set to 240, but it's logging all of us out after only a couple of minutes. Is this still the same issue?

@wulbs I was having the same problem when I run the toems_dhcp_proxy on the same server, then I run the toems_dhcp_proxy on another computer on the same subnet with the server and it works that way.

If you need to support secure boot, you'll need to use the windows imaging environment. Other than that you need to disable secure boot, image, then reenable.

It's the same for all pxe modes. Won't boot to hd most of the time.

You can do an efi boot with ipxe.

Just to help with this. What happened to me is that I missed the step of setting the organization name. Once set, I could generate the certificates.

Output looks pretty standard. I think I'm gonna use a different machine to make the new image.
https://pastebin.com/scK6pYMk

The permanent deploy feature was removed. I tried to scale back on features that only most people were using. However, the model match feature may work for you if you are using the same image based on models. I mean if a single model always gets the same image, it could work for you.

@theopenem_admin
Wow, thank you so much for following up on this. Public thank you to this team, as you guys do not present that "pulling teeth" feeling that is so frequent elsewhere

I am going to deploy this and see what comes of it - I'll report back.

As an added note, I noticed that in every case of this occurring, I attempt a

net stop toec; net start toec;

and I receive a This service is currently stopping or starting
This very well may be related to an established start/stop connection as well, as if the server "crashes" and attempts to restart, the socket itself may have been hanging it.

Thanks again and I will let you know!