Login
You're viewing the functional.cafe public feed.
  • Nov 13, 2026, 3:33 PM

    @Tom_ofB if it was working it sounds like it is on-prem (kinda hope it is the SE/Subscription Edition, since AFAIK the regular ol' perpetual licensed version didn't get that many updates, even security ones, from 2016 on). If they have Microsoft 365 E3 or E5 (or whatever Microslop calls it today), are in the US or Asia region and had e-mail working properly, it is more than likely it has Exchange Server SE behind the scenes. It saved the company a lot of money in 2 days.
    @chucker

    💬 1🔄 0⭐ 0

Replies

  • Nov 13, 2026, 3:37 PM

    @jt_rebelo @Tom_ofB sure, but “SE” is just Exchange Server 2019 with a different license, with the old license having been killed off.

    💬 1🔄 0⭐ 0
  • Nov 13, 2026, 3:48 PM

    @chucker but with promised "perpetual and ongoing cumulative updates" (I hope).
    Thing is it kept working while the online (cloud) Exchange didn't, we (I, not a tech, but those in IT that I talked with think the same way) just don't know how or for how long SE will keep working (for as long as Microslop can sell Software Assurance, special Enterprise subscription and CAL, maybe?).
    @Tom_ofB

    💬 1🔄 0⭐ 0
  • Nov 13, 2026, 3:50 PM

    @jt_rebelo @Tom_ofB

    > but with promised "perpetual and ongoing cumulative updates" (I hope).

    Sure, but I imagine not major _feature_ updates. In fact, it’s older than I thought; the build is 15.02, and 15.x was originally Exchange Server 2013!

    💬 1🔄 1⭐ 0
  • Nov 13, 2026, 3:50 PM

    @jt_rebelo @Tom_ofB which is relevant to this week’s outage insofar as… are they really on a creaky codebase? Or is Exchange 365 _significantly_ different at this point? Either answer doesn’t seem great.

    💬 1🔄 1⭐ 0
  • 💬 0🔄 0⭐ 0