I did some digging and it appears bootType is being incorrectly detected as legacy, so the script is formatting the drive as MBR. $env:firmware_type contains the correct value, EFI. I found that the boot type is determined using Confirm-SecureBootUEFI, interpreting a failure to run as legacy boot. This system does not support secure boot, causing Confirm-SecureBootUEFI to crash, although it does use UEFI. Is there a reason Confirm-SecureBootUEFI is used instead of $env:firmware_type for the boot type?

@cracking-skulls I'm having this same issue. Were you able to resolve it?

@theopenem_admin I'm really sorry for mentioning, but I'd really like to find a way to fix this without reinstalling the whole server and clients.
There are no "Active Replications" nor can I found a way to stop the Worker process. I tried to zip all software_uploads on TOEMS local storage, delete the contents of the folder, but it didn't help. The same if I deleted everything in that folder from SMB and local storage.

@notto
Doing further testing JSON error still present on Thinkbook 14s Laptop

Yoga Slim 7 works fine.

How requirement is as below.
We have 10 Agents/IT technician. So each agent should be able to take remote from his system. Is it possible

@amaury In this case, download and test before uploading to the server.

@theopenem_admin when I enable efi on the virtual machine setting in virtual box. I no longer have to ability to f12 into pxe boot. And the vm will not boot. And I also don’t understand because the laptops are dual legacy and uefi. I’ve never had to click enable efi before and it imaged the drives just fine.

@jgitta
J
jgitta
27 Jun 2023, 10:32

@theopenem_admin
Hi, I also have the same problem, I can't log in with the initial user.
Can you help me find the correct password via the web.config file? Thank you

Looks like a bug, I'll need to check out the sql that is generated.

Looks like this is typical for packages that get update frequently like Chrome. I think I'll avoid using Winget for Chrome