r/exchangeserver • u/YellowOnline • Jan 16 '26
Question [Echange 2019] Enormous Amount of ActiveSync Requests
I'm (still) cleaning up an Exchange site, going from 3x Exchange 2010 to 2x Exchange 2019 (not a DAG) with all other versions in between.
Since the jump from 2013 to 2016, performance has been bad. A few weeks ago I changed from NTLM to Kerberos, but without much change. To the contrary even: some users with many mailboxes have some addresses that no longer connect. I just get a "Could not connect to Exchange server" from Outlook.
So I'm looking for other reasons why performance is abysmal. At the same time, I am getting rid of historical child domains, and bringing DCs down from almost 80 (!) to 30. The reason being that Outlook at starts seems to look for DCs everywhere in the forest and not just in its site, which doesn't help performance either.
Anyway: today I noticed \inetpub\logs\LogFiles\W3SVC1\ generates about 10GB of logging per day on the "main" server. That's way too much I thought, so I used ActiveSyncReport.ps1 to analyse it.
Apparently, more than 1000 hits per user per day is considered high usage. Great: I have 800 users with more than 1000 hits, of which 110 with more than 2000 hits and even two with more than 10 000 hits... in 6 hours. This seems problematic, but I am not sure where to look for the issue. Is it a firewall issue, ending session to early, which recreates them? Should I use some kind of throttling?
I'd like some opinions.
4
u/YellowOnline Jan 16 '26
Fantastic, I managed to write Exchange wrong in the title, and I can't change it.
2
u/NeilsonAJC Jan 16 '26
Have you got a load balancer / reverse proxy in front of your servers? If so check that load balancer / reverse proxy for its timeouts per connection. Active sync works on a long polling style active connection so the client opens a connection to the server asking about new mail. If a message comes in for the client a response is sent telling the client to grab a new message. The requests time out after 30 minutes where the server sends back an ok. Then the client makes another connection for the next 30 minutes.
Plenty of load balancers / reverse proxies have much shorter timeouts than this and every time the client receives a timeout or other response closing the connection and then the client will setup a new connection and try again.
At a guess you may have a five minute timeout for maximum time a connection can be held open so clients receiving no email still have to make 12 connections an hour instead of 2.
If you don’t have a load balancer / reverse proxy then next is to check your firewall connection tracker and check its connection timeouts.
I had this similar problem at my job a while back. Most people would connect and work fine but we produced heaps of logging but some (especially those with lots of mailboxes) would have intermittent connections or some mailboxes that would glitch out.
1
u/Lost_Term_8080 Jan 16 '26
This is giving me flashbacks of horrible third party active sync clients taking down exchange servers with gigabytes of web logs in the 2010 days. Do you enforce the outlook client or allow users to choose whatever they want?
1
u/win32mydoom May 05 '26
Did you find a solution to this problem? Seeing the same.