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 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?

These are the 3 intel rst drivers that most people need for dell drive detection in RAID.

https://www.intel.com/content/www/us/en/download/720755/intel-rapid-storage-technology-driver-installation-software-with-intel-optane-memory-11th-up-to-13th-gen-platforms.html

https://www.intel.com/content/www/us/en/download/19512/intel-rapid-storage-technology-driver-installation-software-with-intel-optane-memory-10th-and-11th-gen-platforms.html

https://www.intel.com/content/www/us/en/download/19755/intel-rapid-storage-technology-driver-installation-software-with-intel-optane-memory-8th-and-9th-gen-platforms.html

There is also one newer one 20.1 I think, it's hard to track down.

Yes, it does the whole dism thing. The driver need to be in inf format, that's how winpe works, you can't just drop an exe into winpe, the drivers need to be extracted. For them to show up in the winpe builder page, you need to add them as a file copy module with the is driver option checked. I typically just add all of my drivers to a single zipped upload, but you can add multiple files to the module if you want.

I'm not sure I'm following you. This already exists, When you build WinPE you just need to select which drivers you want to add to it. I have all the RVST drivers packaged together and I just check the box when I want to embed it into the WinPE, no problems with drives being detected.

It is technically possible to send WinPE over http but the problem is that it breaks secure boot, so I have not included it. If you haven't already seen this page, it goes over the pros and cons of each imaging environment.

https://docs.theopenem.com/imaging/imaging-environments.html

Yea, Microsoft is making things difficult. The nature of the program which allows remote commands to execute causes the false positive. I've submitted a request to get it allowed, but I highly doubt they will approve it.

Impersonation only works when running as a service, won't work at login since it runs under that users context.