Bolton09
asked on
No Email on iOS Devices after Email Migration to Exchange 2013
Hi,
We currently have 3 Exchange 2007 servers and 1 Exchange 2010 acting as a link between us and Office 365.
The Exchange 2007 and Exchange 2010 servers are both on-premise.
We've now installed an Exchange 2013 server on-premise and we've migrated a few test mailboxes over to it.
Outlook and the Outlook Web App work OK, however any iOS device we setup the accounts on do not.
The accounts add on the devices OK and autodiscover works OK. However when we go into the account in the in-build mail app on the devices it shows no mail at all. We are unable to send from them either. The email just sit in the Outbox.
In the past it just worked without additional setup on the Exchange servers, are we missing something?
Thanks
We currently have 3 Exchange 2007 servers and 1 Exchange 2010 acting as a link between us and Office 365.
The Exchange 2007 and Exchange 2010 servers are both on-premise.
We've now installed an Exchange 2013 server on-premise and we've migrated a few test mailboxes over to it.
Outlook and the Outlook Web App work OK, however any iOS device we setup the accounts on do not.
The accounts add on the devices OK and autodiscover works OK. However when we go into the account in the in-build mail app on the devices it shows no mail at all. We are unable to send from them either. The email just sit in the Outbox.
In the past it just worked without additional setup on the Exchange servers, are we missing something?
Thanks
Did you totaly delete the exchange account from the phone and recreate it or are you piggy backing off the old one? When i went 03 to 10 i had to delete and recreate as there were some encryption differences with 2010.
Does it work internally? or does it not work internally and externally? To which version or Exchange server the Public IP for Activesync is NATed to?
After installing Exchange 2013 server on the domain the Public IP should be NATed to it. This is because Exchange 2007 and 2010 are not aware of Exchange 2013 servers but Exchange 2013 would proxy connection to mailboxes in Exchange 2007 and 2010.
After installing Exchange 2013 server on the domain the Public IP should be NATed to it. This is because Exchange 2007 and 2010 are not aware of Exchange 2013 servers but Exchange 2013 would proxy connection to mailboxes in Exchange 2007 and 2010.
ASKER
I've completed deleted the accounts off my iOS devices and re-added and it didn't work.
The Exchange 2013 had its own public name and IP which is NATed through to the internal on our firewall and is completely separate to the Exchange 2007 and 2010 servers.
OutlookAnywhere internally and externally are configured for the internal and external names.
The problem occurs but internally and externally.
OWA works internally and externally.
The Exchange 2013 had its own public name and IP which is NATed through to the internal on our firewall and is completely separate to the Exchange 2007 and 2010 servers.
OutlookAnywhere internally and externally are configured for the internal and external names.
The problem occurs but internally and externally.
OWA works internally and externally.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Is the ActiveSyncVirtualDirectory 's externalUrl and InternalUrl configured?
Use below cmdlet:
Get-ActiveSyncVirtualDirec tory -Identity "<servername>\Microsoft-Ac tiveSync (Default Web Site)" | fl
Check ExternalURL and InternalURL in the output of the command. Ensure they both are correct. If not, use Set-ActiveSyncVirtualDirec tory to set them up correctly.
Use below cmdlet:
Get-ActiveSyncVirtualDirec
Check ExternalURL and InternalURL in the output of the command. Ensure they both are correct. If not, use Set-ActiveSyncVirtualDirec
Agree with Andy on the security permissions.
Also, test one of the problem users with the ActiveSync test @ www.exrca.com and post the results here.
Also, test one of the problem users with the ActiveSync test @ www.exrca.com and post the results here.
ASKER
It was to do with the Security Permissions, thanks.
Needed the "Include inheritable permissions from object's parent" box ticked on the Security tab of the user object.
Needed the "Include inheritable permissions from object's parent" box ticked on the Security tab of the user object.