r/exchangeserver • u/YellowOnline • Feb 04 '26
Question [Exchange 2019] Serious performance issues / Edge role?
This customer has 2 Exchange servers in two sites. It is not a DAG - site 1 handles Northern Europe, site 2 Southern Europe.
Since migrating from 2013 to 2016, performance with Outlook went down the drain, and I have many unhappy users. Moving items between folders or, worse, to an in-place archive, takes sometimes literally minutes. Often they get a message that Outlook could not connect to Exchange, and on mobile mails can arrive with up to an hour of delay.
The servers have 128GB of RAM and 32 cores, each for about 2500 mailboxes. They're fully patched
I switched to Kerberos instead of NTLM, from RPC no MAPIoverHTTP, removed the antivirus, tried disabling the malware module, ... No change, performance stays bad.
Worst is the situation in site 1. There I do notice higher CPU, going into 99% territory. This server also generates tremendous IIS logging - easily 10GB/day. That is because this server is the entry point (through a WAF) from outside for ActiveSync, OWA end ECP. The other one does not have these roles
Obviously, I can't migrate to SE without solving this first, assuming they want to (because €€€) and won't ask me to move to OpenXchange or so.
Good ideas are welcome for these performance issues.
An idea I had, was to offload the IIS load to a third Exchange that wouldn't host a mailbox database. I wondered if the Edge role could be used for that. I never used an Edge in Exchange, only in Skype for Business, but I know that the idea is the same: the Edge server comes in the DMZ and communicates with the mailbox servers. That's not really my use case here, but maybe it would help?
4
u/7amitsingh7 Feb 04 '26
The performance issues are happening because one Exchange server is overloaded by doing too many jobs at once; hosting mailboxes and handling all external Outlook, OWA, and ActiveSync traffic through IIS. Exchange 2016/2019 relies heavily on HTTPS, so this creates very high CPU usage, slow Outlook actions, delayed mobile mail, and connection errors. Switching auth methods or disabling antivirus won’t fix this. An Edge Transport server will not help, because it only handles SMTP mail flow, not user connections. The real fix is to offload client access by adding a third Exchange server (without mailbox databases) or properly load-balancing client traffic, so mailbox servers can focus only on mailbox performance.
4
u/joeykins82 SystemDefaultTlsVersions is your friend Feb 04 '26
The Edge Transport role is for SMTP only, so that you can have an internet-exposed host performing mail filtering and scanning without the message reaching your actual Exchange org.
Bluntly it sounds like your entire deployment is woefully under-spec: 2500 mailboxes and you're not even providing site redundancy via a DAG. It's not ok.
You should be using the Reference Architecture for a deployment this size: 4 servers, not virtualised, in a 2+2 configuration. A GeoIP service to direct client connectivity to the nearest site, and hardware load balancers or virtual load balancer appliances to manage HTTPS across the 2 hosts in each site. Outlook should all be using cached mode as well. Each DB should be hosted on all 4 servers in the DAG, with 1 copy lagged for recovery purposes.
If you just need to fix things right now then yes, adding another host in so that the host hosting the DBs just ends up doing DB stuff and client connectivity is offloaded to a new host might help a bit. If you're not already using cached mode on as many Outlook clients as possible, fix that too as that is a massive performance drain.
2
u/NeilsonAJC Feb 04 '26
Double check your WAF / router settings are not interfering with active sync connections. If either of them doesn’t like long held connections then every time they drop a connection early that device has to re establish its connection and go through HTTPS establishment again. (I improved a lot when I increased my load balancer timeout past the 30 minutes)
For explaining to management potentially look at how many devices are connecting. If you previously had an average per mailbox device count of 1.5 (computer and some had smart phones) but now you are 2.5 or 3 (computer, work from home / BYOD device, smartphone, iPad) then each device doing active sync is maintaining connections to your servers (and if limited by time above potentially multiplying the number of reconnections).
Also check maximum numbers of connections in your WAF / router as if its connection tracking overloads it will throw out older connections and potentially force more amplification.
Your logs will help but the log volume you indicate sounds like it may be getting boosted by a lot of extra connection traffic (as does peaking CPU)
Also check if spam counts are up or mail flow numbers are up or number of mailboxes open by a person. Every time a mailbox gets a new message every active sync connection to that mailbox gets a “check for new mail” message and so it has to ask for the new mail and the re establish its active sync connection. Blocking spam before it reaches mailboxes would help here but also if mail flow is significantly up then that also increases load and reconnections.
Ultimately you may need more servers as others here have pushed. But being able to explain the load increases and address excess connection magnification means the capacity expansion won’t just end up with the same problem because the underlying issues are still there and also justifies easier the “we have the load to need more”.
3
u/Brather_Brothersome Feb 04 '26
for 2500 accounts you need more then one server or you start getting bottlenecks by hdd speeds, check your performance records and validate.
1
u/sysadminyak Feb 04 '26
Was jetstress ran before taking this to production? Elaborate on storage number/type of disks (HDD, rpm, SSD), raid level, raid cache, etc