@theopenem_admin ok, found the client installators in SMB storage. Copied it from there manually to com server. Should work, I hope. But if you have time, please, check my issue with the replication. And also you can delete this thread.
@theopenem_admin ok, found the problem - it comes down to the problems with SMB share not being synced due to Robosharp... I synced it manually and the command looks good
It shouldn't be touching the 2nd drive, but clearly is. It's most likely a bug with multiple drives. I'll need to look into it. Looks like you are using the LIE? Have you tried it with the WIE?
Following my suspicion of IIS, I logged in as the (Built-in) Administrator and used Server Manager to remove IIS and its dependencies completely, and then ran the installer again and now it works. Looking at the Server 2019 image I have (installed via WDS), it has IIS enabled by default, so IIS was corrupted from the start.
I am now able to log into the web ui without issue.
Thanks for your help diagnosing this, if someone finds this in the future, I hope it helps!
@theopenem_admin I have a Windows 11 Education VM. I installed Toec and issued Toec.exe --prepareImage command in powershell. Placed unattend.xml sysprep file in C:\Windows\System32\Sysprep. I left it in audit mode. I know, it's sloppy, but I was just testing.
I'm not sure exactly what you mean. Client / server communication is already encrypted with the certs built in to Theopenem. If you want to use additional certs on top of that, you just need to install the certs on your server and assign them to your front end and com server in your IIS bindings. Finally, change your com server url to use https and port 4444
@brywhi Nevermind... this is fixed. Bad DB config on our part that eventually led to the DB being too slow. Fixed now. Not a TOEM bug at all, definitely an error on my side
