Looks good, you shouldn't need to worry about the client log files. They are capped at 10MB with a max of 2 files.

@theopenem_admin said in Fresh install and PXE not working:

I'm confused with your proxy settings. In your initial post you say you are using the proxy but your images show that you are not using proxy.

My apologize, I didn't try proxy, only tested PXE with vSphere UEFI boot. And it was working.

@theopenem_admin I was able to get this fixed, I needed to point to each of the different ARCH to their respective bootmgfw.efi once I did this the WIM images worked just as expected ! Thanks for all of the help and assistance !

Alright, thanks. I'll continue as is for now and see if the connections becomes a problem.

@theopenem_admin Gotcha....it has been several months since I did an upload. Thanks.

@theopenem_admin
Very very cool, I did run into an issue though, but it might be an edge case. I'm now getting "Failed" for a last run status on LDAP Sync (bind tests OK). It has ingested the security groups, by name, but membership is at 0 for all of them. It looks like this log message is the relevant exception occurring:

System.Data.Entity.Infrastructure.DbUpdateException: An error occurred while updating the entries. See the inner exception for details. ---> System.Data.Entity.Core.UpdateException: An error occurred while updating the entries. See the inner exception for details. ---> MySql.Data.MySqlClient.MySqlException: Cannot add or update a child row: a foreign key constraint fails ("theopenem"."group_memberships", CONSTRAINT "GROUP_FK" FOREIGN KEY ("group_id") REFERENCES "groups" ("group_id") ON DELETE CASCADE ON UPDATE NO ACTION)

I went through the update sequence as listed in the guide, any chance I dropped a stitch and this one's on me?

Thanks. I'll look into it.

@theopenem_admin Ok, I follow. Every field you include has to be in the query itself. Got it, I know what you mean now. Thanks.

I created a super basic implementation of a self-service portal using the API, it works in a pinch but I wouldn't use it in production without heavy improvement. Mostly just curiosity about what's possible with the API
https://github.com/AidanRB/toem-store

Your issue is the same as this post.
https://forum.theopenem.com/topic/87/deploy-image-error

Your schema isn't missing, it's just invalid. Dell must be doing something different with these new machines causing multiple efi bootloaders to be listed. There is a proposed fix in that thread.

@theopenem_admin OK - it was a Qwertz and Qwerty bug! Thx

switch your pxe bootloader to ipxe

I uninstalled the TOEMS_DHCP_Proxy and reinstalled the CD_ProxyD and then rebooted and it started working.
Thanks

For anyone interested, here is a solution (more accurately a workaround) for using different menus with Proxy DHCP depending on BIOS or EFI boot.

I stumbled on the solution as I was trying to add the command console to ipxe by rebuilding my own. My first build would result in a boot loop where ipxe would ask again for DHCP and load itself back again. ipxe.org has a solution for breaking the infinite loop, and this was the solution to using different menus.

Here's a little help to get started with rebuilding your own ipxe.efi:
Go to https://ipxe.org/download, make sure you have the necessary packages listed (gcc, binutils...), clone the repository git clone https://..., and go in the folder ipxe/src.
WARNING: At first, try to compile it the way it is before making changes, and if you do, don't make too many changes before trying to build it again as your changes will break the build.
Begin by editting the file config/general.h to enable/disable various features. Note that there are commented lines, and they begin with a variety of #define and #undef. Thus, enabling HTTPS means changing the line #undef DOWNLOAD_PROTO_HTTPS to #define DOWNLOAD_PROTO_HTTPS. As such, uncommenting a line may not be enough to enable the feature, same goes for commenting in a line may not be enough to disable the feature.
For BIOS boot, you may want to edit config/console.h. See an example here.
Create a file init.ipxe and add the following content:

#!ipxe dhcp chain proxy/efi64/pxelinux.cfg/default.ipxe

In true TOEM fashion, this should run the proper file which contains the menu for EFI64 boot. You may technically do anything you want here.
Finally, compile the ipxe file with the command make -j4 bin-x86_64-efi/ipxe.efi EMBED=init.ipxe, and this is the resulting file bin-x86_64-efi/ipxe.efi.

@theopenem_admin Dell Latitude 53400, 5440, 5540, and Precision 5570. All are the latest Gen. There is definitely something different with these newer ones (I purchased a bunch of laptops and AIOs last year and had no issues with our LIE USBs).

We have not tried WIE yet. I'll have to get that all setup.

@theopenem_admin said in Attempting to enable Proxy DHCP:

your proxy config

See below thanks!

;Config File For Toems Proxy DHCP Server [settings] ; LISTEN-DHCP sets the server to listen for pxe boot dhcp offers and apple netboot dhcp informs on port 67 ; Can be false if Toems Proxy DHCP is installed on the same server as your DHCP Server and option 60 is set to PXEClient on that DHCP Server ; Valid values: true | false listen-dhcp=true ; LISTEN-PROXY sets the server to listen for pxe boot proxy dhcp requests on port 4011 ; Must be true for PXE booting ; Valid values: true | false listen-proxy=true ; INTERFACE sets the nic you want to listen on. ; Any interface can be specified with 0.0.0.0 ; If running on Linux with Mono, you must use 0.0.0.0 ; Valid values: A single IPv4 address | 0.0.0.0 interface=0.0.0.0 ; NEXT-SERVER sets the IPv4 address of the tftp server ; Value is required ; Valid values: A single IPv4 address next-server=192.168.99.251 ; COMSERVER-URL sets the optional url for the com server comserver-url=http://192.168.99.251:8888/ ; CHECK-WEB-RESERVATIONS check the Toems server for static computer boot reservations ; Valid values true | false check-web-reservations=true ; CHECK-TFTP-CLUSTER check the Toems server for tftp cluster groups ; Valid values true | false check-tftp-cluster=false ; TFTP-POLLING-INTERVAL when using clustered tftp server, how often to check to see if they are up ; Valid values number (in seconds) tftp-polling-interval=30 ; ALLOW-ALL-MAC sets the server to respond to all pxe boot or netboot requests or limit to only those set in the allow file ; Valid values true | false allow-all-mac=true ; BIOS-BOOTFILE sets the file that is loaded for legacy bios clients, both x86 and x64 ; Path is relative to your tftp base folder ; If using with Theopenem, it should always be proxy/bios/pxeboot.0 bios-bootfile=proxy/bios/pxeboot.0 ; EFI32-BOOTFILE sets the file that is loaded for efi x86 clients ; Path is relative to your tftp base folder ; If using with Theopenem, it should always be proxy/efi32/pxeboot.0 efi32-bootfile=proxy/efi32/pxeboot.0 ; EFI64-BOOTFILE sets the file that is loaded for efi x64 clients ; Path is relative to your tftp base folder ; If using with Theopenem, it should always be proxy/efi64/pxeboot.0 efi64-bootfile=proxy/efi64/pxeboot.0 ; SERVER-IDENTIFIER-OVERRIDE sets the Server Identifier ; By default this value is set to the inteface value when empty, except in cases where it cannot be, such as an interface set to 0.0.0.0 ; Valid values: A single IPv4 address server-identifier-override=192.168.99.251

@theopenem_admin thanks, that would be amazing. If you need any testing done we're more than happy to do so. Multicast makes our network inf guys happy.

@lwilliamson
No, you're a bit off here... you can basically launch it anywhere you want, you just have to have ADK for creating the WinPE installed on that PC. For me the most optimal is TOMES server itself, because you need to copy the output files into the TOEMS folder in Program Files.
The drivers are only files, that you download from the Lenovo PC's website and that you put inside the Optional folder of the wie_builder.
Your target here is to create a standalone Windows PE, which has the necessary drivers to be able to utilize the devices on client PCs, which drivers are not present in standard WinPE by default.

TL;DR: your guide is here: https://docs.theopenem.com/imaging/build-wie.html

You only want to open the com server, not the ui or application. You can review the security and topology section from the docs.
https://docs.theopenem.com/#security

@theopenem_admin Excellent. Thank you again for your response and assistance!