Yes, then in admin settings -> imaging client, enable upload / deploy direct to smb

That won't work. The second video of the getting started series talks about how to install the client.

https://www.youtube.com/user/coverthisone/videos

What version of Windows did you install Theopenem on?

A few options:

Rebuild the image - Make sure you delete the program files\toec folder if it exists, otherwise install Toec, then run the --prepareImage, leaving Toec installed on the image.

Keep existing image - Delete program files\toec before installing again.

Keep existing image - Install Toec, then run --prepareImage and restart service

The installation id is the only thing that matters. If 2 pc's have the same id, it's going to show the behavior you are describing. Are you certain that it's not already on the image? It's nearly impossible for 2 machines to have the same installation id. Here is the code for how it is generated.

UpdateDbSetting(Guid.NewGuid().ToString(), "installation_id");

It is basically randomly creating a guid upon installation. The guid is not based on anything on the computer such as hardware or sids.

I'm also not sure whats going on with your script. Is that how you are installing on the client or what you are trying to do to fix it?

Understood. It was done this way because I didn't want a scroll bar on the main nav menu. So if the main nav menu can't fit on your screen then it switches to mobile.

The security bug has been fixed and now Microsoft is signing the shim loader again. I'm waiting for the newest shim version of 15.5 to be released before I try to get it signed. I'm hoping to have this done as soon as possible but it's a pain.

c:\program files\toec\toec.exe

It's fine to put it on the image but you must prepare it for image, or like you said the installation id will be the same on each machine.

From the docs:

Toec.exe --prepareImage

If you want to install Toec before capturing an image of the computer. You must run this prior to the last shutdown of the computer. Failure to run this will cause each client's installation id to be the same, preventing Toec from working properly.

You should be able to run that command on the machines that have already imaged in order to fix them also.

Your approach is correct. Only open up port 8888 to allow the endpoints to communicate, keeping the ui and api locked down to just the internal network.

This was a bug and is fixed in the latest download.

https://github.com/theopenem/wie_builder/releases/download/v2.0.0/wie_builder.zip

I've released kernel 5.14.12, although I doubt it will make a difference. You can download it from admin-settings-> kernels. Remember to recreate your pxe files or usb with the new kernel.

I'm running it without any issues.

Secure boot is currently not supported with the Linux imaging environment and PXE. You can use the Windows imaging environment with PXE and secure boot, or the Linux environment with USB for secure boot.

Did you fill in the organization name?

What OS are you installing on and is it 64 bit?

Are you installing on a clean OS or does it have mysql or mariadb already installed on it?

sc config delete Remotely_Service

The only thing that is checked is the the remotely service. When you remove remotely is the service being uninstalled?

If your front end is using https://doamin.com, then your upload url should start the same, not using the ip address.