It also has issues with Bitwarden.
When filling in the password, it leaves the field in plain text.
After that, the javascript that switches the field type between text and password breaks, and it doesn't remove the 8-character limit on the password.

@theopenem_admin - Is there a propery in log4net that is being set for the client IP? If so I could add it into the conversion pattern.

WOL uses other PC's managed by Toems. It looks for a pc on that network, and sends the WOL from that computer. If it can't find one, it uses the WOL relay, but you need to set it up.

There are other threads about the cursor. You need to disable secure boot option when make iso. The WIE is the preferred method. I would switch to that anyway.

@theopenem_admin Thanks. I'll double-check.

@icxnelly Hi guys I just needed to change the boot mode, IDK why I didn't think of that..

THANKS!!!!

@theopenem_admin
Thanks, just found the login tracker policy. We will test this.

Wietse

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.

The problem is still present please help me to resolve it. Thank u

that's good, thought you were using winpe not linux.

@theopenem_admin

Is the com server test where you put in the http://10.129.128.33:8888/Provision/VerifyDb link and it returns "60"? I am getting "60" as the result.

@theopenem_admin That worked. Thank you for your help

It needs to be something mounted on the local computer, so could be local hard drive, smb share, or iscsi, but needs to be mounted. For permissions, you just need to give the network service, modify permissions. You can look at the default location to see how it's permissions are setup.

@theopenem_admin Thought you might find this of interest. There is a tool called PsExec that can remotely call up gui applications via command line. Can be downloaded from https://learn.microsoft.com/en-us/sysinternals/downloads/psexec. Below are some examples:

psexec \\computername -u domain\username -p password -i 1 -d notepad psexec \\computername -u username -p password -i 1 -d C:\Windows\System32\DisplaySwitch.exe 2

Perhaps this can be integrated into TOEMS?

@theopenem_admin Thank you

@surfboy sorry for late reply!

I've had even worse problems lately, so I am doing some troubleshooting; image speeds fall down to 1 GB / min, imaging lasts about 15-20 minutes. I have spare SSD 2.5" drive, SPPC, I've disconnected NVME, put SSD in and put image to that SSD drive - speeds are as expected, around 5.5 GB / min.

In desperation, I've created image with Aomei Backupper, which works through WinPE boot disk, and it works great. Speeds are around 120 MB / s, which was expected from cheap USB3 device, and it took around 5 minutes to finish.

So, linux drivers / support for NVME is the problem here, not network.

@theopenem_admin can something be done about that? WIE is currently not an option, unfortunately.

Thank you!

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

@sesam ....ok - anyway...it suddenly works ;)!

problem solved
thanks