Ic. You are going to have many diver issues with clonedeploy. It's too old. You should move to theopenem or use something else.

@theopenem_admin
Apparently I zoned out for that 30 seconds. Found it.

Is there a way to push that policy manually, or force it to run on the test machine that's already finished the original joindomain policy? I've assigned it, but don't see a way to push it to the box and have no idea if/when it'll run.

If it's the only database that's running on there, then it really doesn't matter.

@palehbt Fixed it. Turn off "console Tasks require login" in Admin -> security

@theopenem_admin Yeah i get that, but I found a program, which installs only without specifying any scope in the command. I guess it's a problem of the package maintainer, but it's better to have us as system admins specify, which scope we wish to apply from e.g. a drop-down menu in the winget module.

@theopenem_admin Easy for you to say. I can't take the server off the domain just to install a piece of software.

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

It's actually copying the image to each com server. It's by design and can't be changed. It's done this way so the clients only need to communicate with the com server and nothing else.

I've migrated the installation to an IIS Express and it is working great so far.

@theopenem_admin - Don't chase this further - I believe this is a remnant from my failed attempt at upgrading MariaDB - https://forum.theopenem.com/topic/466/unable-to-to-login-system-invalidcastexception-object-cannot-be-cast-from-dbnull-to-other-types .
Back then I had to downgrade and because of all the database enconding and collation changes I had to manually edit my MariaDB 10.11 backup so I can have it restored under 10.5. I belive this is now causing my database schema, although working to be out of sync with the model/schema in your coude - hense 'The model backing the context has changed since the database was created.'. What I did was go back to a pre-MariaDB upgrade backup, had that restored, it properly updated to 1.5.5. and now I can login fine. Thanks for your help anyway!

@theopenem_admin Im in a university setting on a sub orginzation level.

We have only 100 computers in our ORG, but our AD has over 20,000

@theopenem_admin Ah that is handy info! I might be able to just push a registry fix rather than reimaging the 120 desktops I have than. Your a lifesaver!

Man, these things are awful. That let them get to TheOpenEM fine, and all the way through image selection, and they fail showing no hard drive. The BIOS on these things is so restrictive, I can't put it into Legacy Mode. I tried 5.11.10, 5.6.4 and 4.18.5. I'll come back to it in the morning.

I'll test this quickly
If I can help with testing or translation into French or other things, please do not hesitate to contact me.
thank you

You would just add another script or command module to the policy to delete the folder.

@theopenem_admin So...I'm not sure who to be upset with, myself, or the people who made this image... As it turns out, some genius in the base image UNINSTALLED .NET frameworks...

Thanks for your help, I really appreciate it. After installing .NET Framework 4.8 it installed just fine on Server 2016.

@theopenem_admin Oh, wasn't aware. That would work. Awesome. Thank you for your support. Again an amazing product!

Hmm, I never knew that setup complete would not run with an OEM license. I guess you would just need to change your policies a little to work with your setup.

@theopenem_admin

Okay, I will check these two items out. I appreciate your help with putting me on the correct track, and also for adding this ability last year! Thanks!!

I will keep messing with it, and report what I run into, in case this weird circumstance happens with anyone else. To clarify, this happened after I joined the TOEMS server to another domain and changed it's IP address. So yeah, there's plenty that could go wrong. Hopefully, I'm an edge case.