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.

Yes, I've run 1000 clients with 16Gb of RAM without issue. Your non server os will basically stop responding and act like it's frozen by an artificial limit imposed by Windows, completely unrelated to Toems.

You should be able to manage a least 1000 with 32Gb of RAM. Processor doesn't really matter that much and a nice storage array if you are imaging.

A non server OS will only allow around 10 connections regardless of your specs. Have you read the getting started docs?

That's your problem.

Are you using a server OS?

This is unlikely to work. Ldap was really only added to support active directory. Wasn't even aware Google had LDAP.

thanks for the update, I'll add it to the bug list.

Not sure what you are asking. You can stop the tftp service and the world wide web service if you want

No fix has been released yet.

You need to create a user group, from there you can assign the computers.