Link to home
Create AccountLog in
Avatar of cmaohio
cmaohioFlag for United States of America

asked on

Exchange 2003->2010 Upgrade, Activesync Push not working well

Perhaps it's just my perception but I believe Exchange ActiveSync Direct Push isn't working on my server after the upgrade.

I do get e-mails, Sometimes I get them 30-seconds to a minute after they're sent, other times it's 7-9 minutes or I call the server manually. I had this problem before and it was due to the TCP timeout on the firewall so I double-checked the settings for the rules going to the new server and they're set the same as for the 2003 server.

I don't know what else to check in terms of how to make this work. There are no errors on the server that say the client timed out. (Event ID 3033). There are no errors of any kind. Just now sent a test e-mail to myself from another service and it's been 2 minutes and nothing has reached my phone.

I don't believe it has to do with it being a Sunday. I can test this more tomorrow. I'm just really frustrated by this all over again.
ASKER CERTIFIED SOLUTION
Avatar of Alan Hardisty
Alan Hardisty
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
Avatar of cmaohio

ASKER

That article is all for exchange 2003. Is it the same for 2010?
The article is related to Exchange 2003, but Anti-Virus Interference is not biased towards one version of Exchange or another, thus it is totally relevant to your situation.
Avatar of cmaohio

ASKER

Okay, so I made the change. Although the VirusScan key wasn't under there so I had to add that and the entry itself.

I did that on my Mailbox server and restarted the services, on the CAS server (where the client actually connects) the MSExchangeIS key wasn't even under the directory so I didn't so anything.

Interestingly enough, I rebooted my phone and everything was pushing just fine for several hours and then I making dinner this evening and got a notification of a new mail. I looked at it. It was sent at 6:17pm. I received it at 6:53!
Okay -  so it could be that your Anti-Virus software is changing the registry key, or your Anti-Virus software is not configured to Exclude scanning the Exchange structure,

What software have you got installed?
Avatar of cmaohio

ASKER

It is Kaspersky. I haven't looked at it to tell it not to scan. I could probably uninstall it altogether. We don't have anything on both servers but Exchange and our e-mail is scanned once at the firewall level and again at the Spam Firewall level before reaching Exchange.
SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Avatar of cmaohio

ASKER

I'm rebooting the servers after uninstall now. We shall see what happens.

I find it strange that while my phone is set to get mail every 15 minutes regardless if push is working and e-mails are coming in to my phone 30 and 40 minutes after hitting Exchange.
Avatar of cmaohio

ASKER

An initial reboot of the servers after uninstall shows e-mails coming through within a minute of hitting the Exchange server, that is for now. I'll see how it works tomorrow and then let you know.
Sounds promising.  You might want to investigate the Background / ProActive scanning in Kaspersky or advising it not to scan the Exchange Structure as there is something in it that seems to be messing with your server.

Both Proactive / Background scanning registry keys are entered in the location mentioned in my article.

Shout if you need more info on this.

Alan
Avatar of cmaohio

ASKER

Well, checking out Kaspersky, I had the "file servers" version installed on the servers. I should have the Mail Server version. http://support.kasperskyamericas.com/knowledge-base-article/468
Ah!  That might not help : )

So I guess it was scanning the Exchange Structure and causing your headaches.
Avatar of cmaohio

ASKER

I ended up temporarily uninstalling AV on the server and it is continuing to work. We'll be putting an Exchange-specific AV version to help fix it.