Hello Jon! Thank you for your work on TOEM over the years, it's been a lifesaver. I've deployed it and am still using it at two places, one is a church with around a dozen or two endpoints, and one is a school district with 4000+.
It was a massive upgrade from the old software we were using at the schools, and made centralized deployment of software possible on a scale we couldn't previously accomplish. We are moving some (but not all, at least not currently planned) of our endpoints to Intune; we used to have several thousand more in TOEM. It's been much easier to use, deploy and update software, and get immediate information from TOEM than it is with Intune, and it's also much easier to poke around the backend when things go wrong. I've had a few issues over the years that caused problems, but unlike a proprietary solution, I was able to make changes in the database or files on the server that patched it to work in our environment. Having the source available helped as well, as I could track down exactly where something went wrong.
Integration with cloud services is a bit of a mixed bag. Intune tends to handle almost everything itself, so the only thing TOEM would provide in my mind is immediacy where policies in Intune can take a day or more to apply. Allowing users to sign in with OIDC, though, would be a huge lifesaver; a "sign in with Microsoft" button would look better on audits than LDAP authentication, as it can be secured using Microsoft's 2FA.
Imaging is a big use case for us, and allows us to deploy changes (new OS version, etc) across the district without having to burn hundreds of flash drives every time something needs to change on newly imaged computers.
2.0 would be appreciated, especially with a more user-friendly UX/UI. The current interface, while highly functional, has its rough edges and a bit of a learning curve. If it's written in .NET 10, it would also likely be deployable as a container, which might make maintaining the system easier.
The imaging profiles have actually been helpful; we have some endpoints that need different storage drivers, and detecting the model number lets the right driver set be deployed to them when imaging without having to thumb through a menu and select the right option.
As far as the name goes, we have TOEM baked into our DNS and hostnames for everything, so whether you change the name or not, we'll keep calling it Toem (or, as some of the department types it, OpenM 🙂)