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.

If you start the task from the web you should be able to cancel it after is seems frozen to get the log.

Sounds like you are using a mix of the WIE and LIE. You need to use the same one to upload and deploy your image.

It's not the bios. It's when you create the iso in the UI.

It's not related to the drive. You need to build your iso with secure boot support disabled.

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.

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.

It means the client header was missing when trying to authenticate. Is this server public? It could be random port scans or whatever from the outside.

Standard is the most reliable, you just need to select the correct windows partition below when standard is selected.

It would be on the actual image. I think you are talking about in settings.
Images->view->image profiles->deploy options

At a loss here. Everything looks normal, it seems to me that during the upload, the process is stopping during the data transfer. They only thing that comes to mind is firewall.

Are you sure, your logs don't indicate that is happening? Can you post the log from admin settings->logs->com server logs->multicast.log