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.

I'm working on getting the ad group criteria added, and hoping to release in a few weeks. Would that alone solve your issue?

The profiles are only stored in the database. They would always be there unless they were deleted or you setup a new database.

No, that shouldn't effect them. What do you mean you don't seem them? Is it a blank page?

Are you just testing this installation, or have you pushed it out to your computers. If you are just testing so far. I would regenerate your toems ca and and intermediate. Install the new certs on your server, regenerate Toec. Install Toec on a new machine. To rule all of those things out.

In your toec-api web.config file towards the bottom, find the line that says

<root>
     <level value="INFO" />
     <appender-ref ref="ClientApiLog" />
   </root>

change it to:

<root>
      <level value="DEBUG" />
      <appender-ref ref="ClientApiLog" />
    </root>

Additional log info can be found at https://docs.theopenem.com/tutorials/logs/

Yea just put them in the drivers folder before you build, in inf format

you need to include the dell raid drivers, or switch to ahci in bios. I personally gathered all of the dell raid drivers and put them into the wie. I think it was only 4 driver sets to go all the way back to 2009

I've seen this happen when the computer takes too long to get an ip. If you exit to shell and do the following:
type powershell press enter
then type wie and press tab
then press enter

see if it works, if so, the ip is taking too long

That is the toec client. I need the com server log.

Can you create a feature request post so I remember. That's generally all I look at when releasing new versions, the support topics are too many to go through.