Posts made by TylerLoch

We have a new Dell Latitude 7450 (Intel Meteor Lake) that Theopenem's LIE is unable to boot on.
A previous Latitude 7440 (Raptor Lake) booted perfectly fine from the LIE, with Secure Boot disabled.
On the 7450, Grub appears and I can select my boot type, but then am met with a single cursor in the corner of the screen, very similar to how Secure Boot looks with the older shim on new hardware, but Secure Boot is definitely off...
I tried using a newer kernel as provided in this thread, but no luck.

Curiously, other Linux kernels post just fine when injected into Theopenem's boot disk, including the one included in GParted's Live USB, though they panic when trying to figure out the root partition. I haven't fully explored the method Theopenem uses to make a ramdisk yet...

Any insight or suggestions on how to troubleshoot this issue? Kernel arguments to try, grub modifications, etc etc?

Thanks!

@theopenem_admin That works in a pinch! Thank you!
I remember a while back that there was some drama around getting a new version of Grub signed for Secure Boot use. I take it that's not in the cards anytime soon?

I've run into trouble with two device models where Theopenem (and Clonedeploy before) do not show any text when booted to a USB stick for imaging and deployment.

Grub (UEFI) appears, but no Linux kernel output. A single white cursor line is visible in the upper corner.

Strangely enough, the kernel IS booting, and commands can be completed blindly if you're adventurous enough.

Issue seen on an HP Elitebook 1030 G2 (only when Legacy Mode is disabled), and a recent Dell XPS laptop (no workaround found).

Any suggestions on Grub or kernel edits/commands to get basic text appearing?

Thank you!

@theopenem_admin Thank you so much! After the last two days of testing and use, I'm seeing speeds saturating my gigabit connection.
And reliability is now rock-solid. Before, creating images was extremely stressful, as timeouts and errors would happen more often than not, with no obvious notice. I can now create images without worry.

Thanks again!

@theopenem_admin I'm admittedly using older (and slower) host hardware for my VMs. If I were on something more modern, I'm sure i'd be able to max out a gigabit connection.
As it is, w3wp.exe monopolizes only two CPU cores, with about 250mbps of throughput to a 1gbps client. IIS is not my forte, so I haven't been able to figure out if there's any tweaks that can be made to improve throughput.
(Theopenem was installed on a fresh Windows Server 2019 VM)

@theopenem_admin I was able to work around it with an NFS share. Thank you!
Straight SMB connections were definitely less fuss for my use case. Is the SMB Storage feature more for package delivery, or am I missing something?
Seems that all image deploy traffic in Theopenem now goes through IIS, and my server is hit pretty hard with w3wp.exe CPU usage, limiting throughput.

I'm having trouble using remote storage for the creation of images. Is this even possible or supported?

The Com Server settings explicitly spell out "Local Storage Path", but does accept SMB paths.
The Com Server log seems to act as if it is connecting to the share anonymously, rather than with the account and password used in the Storage Location section:

2021-03-03 06:40:00,761 [10] ERROR Toems_Service.FilesystemServices Could not find a part of the path '\\********\******\images\test4'.
2021-03-03 06:40:30,730 [10] ERROR Toems_Service.ClientImagingServices Could Not Create Image Schema
2021-03-03 06:40:30,730 [10] ERROR Toems_Service.ClientImagingServices You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.

Removing this Windows constraint provides another error, indicating that the presumed credentials are not being used:

2021-03-03 06:51:35,256 [8] ERROR Toems_Service.FilesystemServices Could not find a part of the path '\\********\******\images\test5'.
2021-03-03 06:52:09,449 [7] ERROR Toems_Service.ClientImagingServices Could Not Create Image Schema
2021-03-03 06:52:09,449 [7] ERROR Toems_Service.ClientImagingServices Access to the path '\\********\******\images\test5\' is denied.

@ejgagne Thank you for admitting it! That was my exact same problem, and now I'm up and running

Care to elaborate on your dumb error? I'm in the exact same boat, it seems...