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.
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.
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.
Definitely not want you want to do. You probably just need to create boot files in admin settings->pxe-> global boot menu, also in pxe settings select the correct bootloader and click update, that will copy the correct files to the correct location.
Yes, just copy the images folder from the old to the new, but you will need manually recreate the images in the webui, using the same name.
It doesn't need to say 60, it's just returning your checkin time.
Very strange, I've tested in nearly every browser and I can't replicate this.
It's difficult to say without knowing more about your network. Theopenem can be installed on the same server as DHCP as long as you are not using Theopenem as a DHCP server with the pre-installed Tftpd32, which it sounds like you aren't. As long as your clients can reach the ip of your Theopenem server it should be working.
What browser were you using? Should work fine with just about anything?
Probably isn't anything you can do right now, will need to get some updated kernels and such in the next version. You would probably need to use the WIE in the mean time.
Looks like a bug, I'll need to check out the sql that is generated.
Looks like you are deploying a legacy image to a computer booted to EFI. You need to boot in legacy mode or use an EFI image or create a universal image. You can check out the universal image video.