[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2006
  • Last Modified:

Exchange 2013 Active Sync - direct push not working for specific user

Hello All and thank you in advance,

I finished migrating a 2007 exchange to 2013.

While they were on coexistence everything was working fine.

As soon as a decommissioned the Exchange 2007 problems can't stop and especially issues with Active Sync.

My latest issue is that direct push is not working for a specific users iPhone ( I have tested the account on my iPhone also with the same results).

From searching on the internet I see that more people are experiencing this issue but haven't found a solution.

I tried to recycle the MSExchangeSyncAppPool and MSExchangeAutodiscoverAppPool on IIS.

 I tried to disable and re enable Active Sync for the specific user but no changes.

Any help would be much appreciate it.

Thank you for your time.
0
jamescarson69
Asked:
jamescarson69
  • 7
  • 4
1 Solution
 
Alan HardistyCo-OwnerCommented:
Please check the inherited permissions as per my article and make sure the permissions are set to be inherited and that the users are not part of any of the groups mentioned in my article:

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2861-Activesync-Working-But-Only-For-Some-Users-On-Exchange-2007-2010.html

Alan
0
 
jamescarson69Author Commented:
Hello Alan,

Thank you for the quick reply.

Unfortunately inheritance is enabled and the user is not a member of any of the groups you have mentioned.

FYI a week ago active sync wasn't working for 2 users, I found the same solution but didn't do it.

I called Microsoft and after hours of troubleshooting the said that this has now been passed to the development team etc.

I resolved the issue by recreating the mailboxes for the users.

But on this specific situation active sync is working it just that I need to manually refresh the phone.

Thank you for your time and help.
0
 
Alan HardistyCo-OwnerCommented:
Sounds like another bit of bad programming with Exchange.  I had similar problems with POP3 on Exchange 2010 when it first came out and it took 5 months for the update to be released that fixed the problem.  They had known about the problem pre-release, but it wasn't a high enough priority for it to be fixed quickly!  I wasn't amused.

Is Exchange updated with the latest Service Pack / Cumulative Update?  Currently SP1 CU4 is the latest.

Alan
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
jamescarson69Author Commented:
Yes unfortunately Exchange 2013 is updated to SP1.

5 months...:S

Well the user is not happy at all so I might have give it a try and recreate the mailbox for him also and see how it will go.
0
 
Alan HardistyCo-OwnerCommented:
Hold on - let me have a quick look for something and I'll post back in a sec.

Alan
0
 
Alan HardistyCo-OwnerCommented:
Okay - please try the following:

If you open up ADSIEDIT.MSC (and very carefully), navigate to the problem user using Default naming Context then under the user, do you see CN=ExchangeActiveSyncDevices?

Delete the CN=ExchangeActiveSyncDevices entry and everything below it and then try setting up ActiveSync again for the user.

Alan

(Be very careful what you are deleting as this is directly modifying Active Directory so any mistakes could be costly).
0
 
jamescarson69Author Commented:
Hello Alan,

Unfortunately that didn't do it either.

However I really appreciate all your help and time.
0
 
Alan HardistyCo-OwnerCommented:
Oh well - looks like the zap and create new account time.

Sorry :(

Nice one MS!!
0
 
jamescarson69Author Commented:
Yeah unfortunately looks like the last solution.

Thank you once again!
0
 
Alan HardistyCo-OwnerCommented:
You're welcome - sorry it isn't a more elegant / pain-free solution.

Alan
0
 
KevinRLiCommented:
Ok this is an article from 1 year ago and I find myself in the same situation. Upgrading from a 2007 Server to an Exchange 2013 Server.  Migrated the 1st set of users and now we're seeing that most of them the Push isn't working. They have to manually refresh their device ( a mix of black berry 10's and Windows 8 phones ) to get new emails. I cannot recreate 50 email accounts to make this work. Any help would be appreciated.
0
 
Alan HardistyCo-OwnerCommented:
@Kevin - you will find that posting your own question and referencing this question will help you to get assistance.

Posting into a closed question will only attract the attention of those experts that were involved in the question and no others (assuming they are still active).  Posting a new question will mean your question is open to assistance from ALL the experts that monitor the particular zones that you specify for the question.

Alan
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

  • 7
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now