Thanks. 1.5.7 is behind schedule it's shaping up to be much larger than anticipated and facing some challenges. It's probably still a couple months away. Mainly just going through the forum and implementing suggestions.

You can run the following sql query to reset the toemsadmin user password back to the original value of toemsadmin

UPDATE `theopenem`.`toems_users` SET `toems_user_pwd`='ynR74SyWh73NxqzWQNpwsWzHJPOdmWJd1BgxuOxVd+4=', `toems_user_salt`='8Q+LD8za/YzoK7OuAlU8orXTpeu/YpCyNl0yNxEKinQzzfwjI4njKt4FANt74ZxR2D2G7N1QxsNpreLNfd3Dpg==' WHERE  `toems_user_id`=1;

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

I haven't been able to see the issue. Is the new version not working on the older machines either?

That is not the intended result. It should order them based off the group endpoint priority. If you select a computer and view the effective policy, it should list the policies in the order they will run. Changing the priority should change the order they appear in the effective policy. Is that happening?

Thanks, I was trying to replicate this and was unable to, I'll update to latest security updates and try again.

Looks like the tftp server is empty for some reason. I'll double check some things

Here is the latest version, i see you are using the proxy.
http://files.theopenem.com/ipxe.efi

Place it in
Program Files\tftpboot\static\ipxe\proxy\ipxe_efi_64

Then in admin settings->pxe /boot menu ->pxe settings, change your ipxe 64 bootloader to something other than ipxe_efi, save it, and then change it back to allow the new file to copy to the correct folder.

Sorry my dev vm died and I lost a lot of my build scripts. Getting everything setup again, hopefully in the next day or 2.

I could try building the latest version of iPXE but it may take a few days

can you try using the ipxe snp only or snp file

It means you have a duplicate computer name or install ID, or that computer needed to re-provision for some reason. Just apply that reset request and if it goes away you are good, if it then knocks off a different computer then those 2 computers are somehow duplicated.

There is a new 6.13.4x64-updated kernel available, can you give it a try?