bookread.org

Home > Exchange 2010 > Exchange 2010 Activesync Not Working For One User

Exchange 2010 Activesync Not Working For One User

Contents

Well don’t worry, I’ve found out that ADModify.NET is capable of changing this setting on users in bulk. The integrated windows authentication was turned on in EMS not on IIS, but still it appears an IISreset was needed to enable the feature after it was selected. EDIT: Alternatively, if there is some easy way to create a new useraccount/mailbox and copy all of the contents of the old one over, I bet it would work, and that Unfortunately, it does not work correctly. have a peek here

To be continued… Ratish Nair MVP Exchange [email protected] MSExchangeGuru Keywords: Exchange ActiveSync, troubleshooting Exchange ActiveSync, troubleshooting ActiveSync, IIS logs, Exchange 2007, Exchange 2010, ActiveSync not working, Exchange 2010, Http error for But occasionally, things do fail, so knowing what to look at and how to troubleshoot are critical skills. Usually, EAS works perfectly well, so this is not a problem for you. After moving user mailboxes to Exchange 2010, mobile devices could no longer synchronize with a mailbox.

Exchange 2010 Activesync Not Working For One User

Try NOT using this format if it still fails. Check then Allow Inherit Permissions on AD user and computers under system folders 2). You can perform this test using both Autodiscover and using manually configured server settings.

Share this:TwitterFacebookLike this:Like Loading... Any of the other accounts just get "Unable to connect. I am looking forward to your any updates. Activesync Debug Logging Please provide a Corporate E-mail Address.

If the setting is disabled, devices will only connect if they can be automatically provisioned with all of your ActiveSync policy settings. Restart Activesync Service Exchange 2010 I had one user that got a new iPhone yesterday and his phone would "setup" properly, but then nothing would sync. When it was running under 2010, everything worked. How to troubleshoot Exchange ActiveSync connections Staff Writer on October 24, 2014 (1 votes, average: 5.00 out of 5) 2 comments In this mobile-first world, your end users can’t live without

Force the CAS to proxy the connection. Activesync Stopped Working Exchange 2013 phunktional johnkey Says: March 13th, 2014 at 7:29 am Thanks mate! It sends an email into a mail system to an autoresponder address which sends it back. HomeAbout Annoying stuff I figured out (or am trying to) I really hate computers Stay updated via RSS Recent Posts Windows Activation ErrorCodes Locating Orchestrator Runbooks using badcredentials Configuration Manager 1602adventures

Restart Activesync Service Exchange 2010

This issue is easy to fix for a few users (when you know the above that is!), but what if you need to change this setting for several thousands of users? Figure A 3) We implemented a quarantine policy whereby the IT department would have to authorize any and all new devices. Exchange 2010 Activesync Not Working For One User This is done with the following Exchange Management Shell (EMS) command: Get-ActiveSyncVirtualDirectory –Server | Set-ActiveSyncVirtualDirectory –ExternalURL:$Null You can read more about coexistence at Microsoft’s TechNet site. Exchange 2010 Owa Working But Not Activesync And so we implemented a simple BYOD program: The ActiveSync protocol was enabled in our Exchange 2010 system for all users, so that we could skip having to turn it on/off

Right-click MSExchangeSyncAppPool, and then see if it is Started or not If the MSExchangeSyncAppPool is stopped, Exchange ActiveSync will be disabled for that server. navigate here If you’re having difficulty connecting an iPhone to Exchange, or if you find that some ActiveSync policy settings are being ignored, compare your company’s ActiveSync policy settings with the ActiveSync settings Reply Allan Black says December 4, 2015 at 5:22 pm I am 100% sure on the hotfix, as this was put into place today and it allowed me to then select I find it in the IIS-Logs of our Exchange CAS&HUB servers for iPhone, Android, etc. Exchange 2010 Activesync Not Working Iphone

  1. The process works perfectly fine for mailboxes on Exchange 2010, but when using the Microsoft remote connectivity analyzer it fails at "Options" It is worth noting that locally ActiveSync to this
  2. When performing a manual synchronization, I saw this error on the device: Result: ActiveSync registered a problem on the server.
  3. And since you can reach right out and touch your CAS servers, this is probably the first place to start.
  4. msExchOmaAdminWirelessEnable = 4 =  Option 1 and 3 enabled and Option 2 disabled msExchOmaAdminWirelessEnable = 5 = 101 = Option 1 enabled and Option 2,3 disabled msExchOmaAdminWirelessEnable = 7 = 111
  5. What sort of problems?
  6. Ensure that the service account used by the MDM (if any) has the appropriate permissions to the user’s mailbox.
  7. See http://support.microsoft.com/kb/2461792 for more on troubleshooting mobile devices and EAS using logs from the client.
  8. asked 4 years ago viewed 34152 times active 4 months ago Related 1Exchange Server 2003 ActiveSync not working with iPhone0Exchange 2003 ActiveSync problem0Some user accounts cannot use activesync from android/iphone phones
  9. I am looking forward to your any updates.

Exchange ActiveSync was tested successfully. (Edit: Looks like it was successful? Before you allow your users to connect their iPhones to Exchange, take a look at the five most pervasive iPhone and Exchange 2010 connectivity problems and their solutions. Recent CommentsKelly on Exchange 2010: ActiveSync is not working via MobileIronMonthly IT Newsletter – October 2016 - Guy UC World on System Center Data Protection Manager 2016 DeploymentPrabhat Nigam on Public http://bookread.org/exchange-2010/exchange-2010-activesync-not-working-for-some-users.html Find "Microsoft-server-activesync"virtualdirectory 3).Click "Authentication" in the rightpanel. 4).Enable "Basic Authentication" After then, we should restart IIS following the steps below: 1).

Access has been granted. Troubleshooting Activesync Exchange 2010 In these situations, we can either view the technology as the "enemy" and try to figure out how to thwart it, or we can recognize technology as our ally and use There is a lot that can go wrong with an ActiveSync deployment, such as DNS problems, incorrect firewall rules, misconfigured Exchange 2010 SSL certificates, and more.

This setting -- which is disabled by default -- controls which mobile devices are allowed to establish ActiveSync connections with Exchange.

Let's confirm that it is indeed set that way. Keep in mind that ActiveSync *does* work from their phones. Non-provisionable devices The Exchange ActiveSync Mailbox Policy contains a setting called Allow Non Provisionable Devices. Exchange 2010 Activesync Service It's not a pretty solution but it may just do the job if getting company email is more important.

Coexistence challenges The most widely reported issue is an Autodiscover compatibility problem that prevents an iPhone from connecting to Exchange. We canrefer to these articles to recreate this virtual directory: Get-ActiveSyncVirtualDirectory http://technet.microsoft.com/en-us/library/aa996042(v=exchg.80).aspx Remove-ActiveSyncVirtualDirectory http://technet.microsoft.com/en-us/library/aa996916(v=exchg.80).aspx New-ActiveSyncVirtualDirectory http://technet.microsoft.com/en-us/library/aa997160(v=exchg.80).aspx Set-ActiveSyncVirtualDirectory http://technet.microsoft.com/en-us/library/bb123679(v=exchg.80).aspx After recreating virtual directory, we should also restart IIS following the steps below: Scott Mickelson Says: September 17th, 2012 at 8:14 pm I am seeing the following error in the IIS Logs. this contact form Exchange server software Mobility & Wireless Monitoring Office 365 Tools Outlook Addons OWA Addons POP3 Downloaders PST Management Reporting Security & Encryption Services Anti Spam Filtering BlackBerry Hosting Exchange Hosting Hosted

At least in my case, the problem doesn't seem to be related to certificates at all. If this happens, you can probably trace the problem to one of the causes described here. There is a checkbox on the "General" tab of the policy to "Allow non-provisionable devices." (Figure D) Figure D Try turning this option on to troubleshoot.