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.

post the entire deploy log

It tries all of them.

In the toec api web.config change the log level from INFO to DEBUG

It's not required, just an easy way to run some extra commands after the computer boots the first time. It wouldn't change your issue since you aren't getting that far.

I haven't been able to replicate this. Using Win11 22H2, boot to audit mode, install toec, run image prep, leave all default options, select setupcomplete file and sysprep file, finish image prep, capture image, then deploy. All works as expected. Let me know if you find the issue.

Could be a driver issue, I would try adding that specific nic driver to your winpe image.

Toec can't change name, only changed with sysprep, or if you name the computer during imaging it will auto change the name.

Thanks for your research. I had planned on updating mysql.data to the 8.x version in the last release, but was having problems with it and scrapped it. I'll try and work through the problems and get it into the next release.

Script module runs as the system account, there wouldn't be a %username% variable because no user is logged in.

Yes, you can delete them, there are many reasons a computer may be archived, it's kept around for historical purposes.