Posts made by chornbeck

@theopenem_admin Sure, that sounds good. We are in no rush. I did have a similar problem a few years back and a new iPXE build did solve my problem back then. Thank you so much!

@theopenem_admin Sure, I just tried both of those options in the "PXE settings" menu. I got the same result.

Hi there,

We are purchasing some HP ProBook 440 G11 laptops. I'm trying to network boot using iPXE and I'm having trouble. On the laptop, the process stops at "iPXE Initialising devices..." Here's a screenshot:

On the server, when I check the logs viewer in the TFTPD64_gui.exe, I see the following:

Connection received from 10.14.2.19 on port 1897 [31/03 11:37:06.603]
Read request for file <proxy/efi64/pxeboot.0>. Mode octet [31/03 11:37:06.603]
OACK: <tsize=1020416,blksize=1468,> [31/03 11:37:06.604]
Using local port 58007 [31/03 11:37:06.604]
Peer returns ERROR <User aborted the transfer> -> aborting transfer [31/03 11:37:06.604]
Connection received from 10.14.2.19 on port 1898 [31/03 11:37:06.604]
Read request for file <proxy/efi64/pxeboot.0>. Mode octet [31/03 11:37:06.604]
OACK: <blksize=1468,> [31/03 11:37:06.604]
Using local port 58008 [31/03 11:37:06.604]
<proxy\efi64\pxeboot.0>: sent 696 blks, 1020416 bytes in 0 s. 0 blk resent [31/03 11:37:06.747]
Connection received from 10.14.2.19 on port 1899 [31/03 11:37:06.763]
Read request for file <proxy\efi64\autoexec.ipxe>. Mode octet [31/03 11:37:06.763]
File <proxy\efi64\autoexec.ipxe> : error 2 in system call CreateFile The system cannot find the file specified. [31/03 11:37:06.763]

Everything works on all of our other devices. Also, I tried updating the Kernel in the boot menu to the newest version available, "6.13.4x64-updated".

Any ideas on what I can do? Thank you!

@eruthon Me as well, so far so good! I've got two sessions running right now. I haven't tested anything else yet.

@theopenem_admin Thank you!

@theopenem_admin I think we are on to something.

One of our techs started deploying an image. I tried to PXE boot and start a task and it is giving me "Not Authorized" again. It's only happening whenever 1 other task is running.

@theopenem_admin Is it possible that if a task is currently running, starting a new task will not start/queue up in the task list? We're suspecting this might be the case and are going to test it shortly.

Nobody is using the system right now and I've not had any problem getting in.

@theopenem_admin Sure, here's a compilation of the web.config in each folder.

toec-API:

• web.config 4.8
  Toems-API:
• web.config: 4.8
• web.config.mysql: 4.6
• web.config.sqlserver: 4.6
  toems-UI:
• web.config 4.8

Should the web.config.mysql and web.config.sqlserver files be 4.8?

I attempted again using the newly created account that worked before and it gave me "Not authorized" this time. I also regenerated the Imaging token under settings > security.

@theopenem_admin I did not regenerate any tokens. I can try this.

I just ran into the problem again with the admin account.

I tried changing the password for admin, same problem.

I tried one of our techs accounts, no change.

I tried using a newly created account and it worked.

@theopenem_admin I just doublechecked the server and .NET 4.8 is installed. I didn't make any changes to it before or after install theopenem 1.5.0.

@eruthon I personally haven't messed with customizing the boot menu with Theopenem. I did back when we used Clonedeploy. This is on a new server.

@theopenem_admin All of our techs log in with a normal user account that are members of a group that gives them access to only image. Myself, I normally just log in with the admin account. I've had it happen to myself just once, but I've had at least three techs report they've had the problem, to the point where they retry 3-4 times and give up.

@jwasilco I haven't tried setting the IP manually, I'm not sure if that's even possible. We do disable RAID and secure boot to get these to image.

@theopenem_admin I double checked the message from a colleague. It appears it happened after selecting "Start On Demand Task". I'll attached both screenshots. It's happened to him as well as several others and it happened to myself only once using the administrator account.

I also tried changing the PXE bootloader to syslinux and and the problem remained.

Although, I just created a new user for him as an administrator and he said it worked.

@theopenem_admin Sure thing.

Setting webPath to http://10.10.10.39:8888/clientimaging/

System Model: OptiPlex 3000

** Looking For Active Task For cc:96:e5:06:d6:78.8J51GT3.4c4c4544-004a-3510-8031-b8c04f475433 **

{"computerId":"false","task":"ond","taskId":null,"computerName":null}

...... This Computer Was Not Found

** Looking For Model Match Task For OptiPlex 3000 **

{"imageProfileId":null,"imageName":null,"imageProfileName":null}

System Model: OptiPlex 3000

** Looking For Active Task For cc:96:e5:06:d6:78 **

{"computerId":"false","task":"ond","taskId":null,"computerName":null}

...... This Computer Was Not Found

** Looking For Model Match Task For OptiPlex 3000 **

{"imageProfileId":null,"imageName":null,"imageProfileName":null}

This Computer Is Not Registered. No Active Web Tasks Were Found For This Computer. Starting Registration.

** An Error Has Occurred **

...... Not Authorized

Hi there,

I recently updated to 1.5.0 and now I think we are experiencing a bug. We've never had this problem before 1.5.0.

We don't register our devices, we just do unregistered deployments/uploads.

After we network boot using ipxe bootloader, log in and select upload or deploy, we immediately get an error message:

** An Error Has Occurred **

...... Not Authorized

** Rebooting in One Minute **

This seems to happen sporadically.

Is there anything that I can do?

Here is a screenshot of the error:

Thanks!

Thank you so much! I updated this morning and it seems to have solved my problem. I can now PXE boot using iPXE.

@theopenem_admin That sounds good. Thanks! I'll definitely try again when it's updated.

Hi there,

I am trying to get ipxe for EFI64 working on my install. I can use syslinux and grub on some devices, but would like to get ipxe working as well for more hardware support.

I'm having the same issue as this post trying to get ipxe to work:

https://forum.theopenem.com/topic/55/tftp-timeout-during-pxe-boot?_=1654861336035&lang=en-US

I did try installing the old Clonedeploy cdproxy DHCP and disabled the new Toem's proxy DHCP. but, this didn't solve my issue.

One thing I did try was to download the latest ipxe.efi file (1.21.1) from ipxe.org and replaced the existing ipxe.efi files (1.00) in the server. I was able to get ipxe to see my NIC, get an IP and download the pxelinux.0 file repeatedly, but never actually give me the boot menu. So it looks like it's maybe a hardware support issue with the old 1.00 version of ipxe and my newer Dell hardware. That's about the limit of my ability for troubleshooting.

So my thought is would it be possibly considered to update ipxe in Theopenem in the future? Unless I'm going something wrong.

Thanks so much!