@_Eugene_0 As of now, that is the case, yes. We hear the need for a
"better hybrid management solution" but as things stand now, your
options are either to run management tools only via PowerShell or run
Exchange Server on-premises to have access to EAC and manage that way.
Seeing that Exchange 2016...
2 comments... 1. 2,000 is a pretty low limit for a large company that
does things like BPO outsourcing. Sending a few thousand emails to an
individual external recipient in a day from one mailbox is fairly
commonplace. Let alone to greater than 2,000 different recipients. I
hardly think this qualifi...
It's fine and acceptable "giving precedence" to EXO and convince people
moving forward to cloud, by the way in my opinion, some "basic" features
as DKIM and DMARC should be integrated asap also in onprem solution.
After all, Exchange SE is "included in the price" and doesn't come free
of charge
@RuffDay currently the cmdlet only shows historically out-of-date
builds, not current builds. We updated the FAQ above to communicate
that. @Victor Onofrei agreed on documentation, we'll get on it.
We're in the same boat as @Jpanski. Running Exchange 2016 on Server 2016
in a hybrid environment and holding off setting up a new server and
updating everything as we were hoping to just get rid of it entirely.
We've almost migrated everything to Exchange Online and really don't
want to have to crea...
Latest Comments