Andrioid 4.4.4 Galaxy S5 and Exchange 2010 / Active Directory issue

I have posted this here because I don't see a category for Exchange 2010 which is what we currently use and I am not sure where else to post it. Please redirect if needed.  Thanks in advance.
I am an IT Tech and I am trying to connect my phone to my email using the standard email application on the phone, with no success. 
I was convinced for a long while that it was my phone. 
I tried everything I could with the phone and restricting background data and everything but nothing worked. 
I type in the credentials and it accepts them and shows me the mailbox but then it never loads the mail and folders. 
I must have gone through this process 100 times and occasionally I get a message saying the certificate is incorrect do I want to accept it anyway. 
I view the certificate and it is for another domain.  When that doesn’t happen I just get pushed from checking the server setting and then it moves right to the settings of the mailbox. 
However I don’t get the warning like I did when I created a new mailbox and AD account.
Create new exchange mailbox/ AD account – This worked, but ultimately I want my current user name and mailbox to work. 
I don’t want to move to a new one if I don’t have to – I created a new mailbox which intern created an AD account. 
After this was done I attempted to sync this account with the phone. 
It worked first time without a problem.  After the phone checked the server settings it gave me the warning that I was going to have to let the server control the device like it always does. 
It also made me accept the System Administrator settings. 
I sent a test email to and from it with no problem.
There are other people on our server with Galaxy S5’s and other Android based devices and I have added mail to their devices just like I would my device and they have no problems at all. 
I have matched up the mailbox settings and AD settings and everything is the same for the most part. 
It is bound to be a little different because I am an IT Tech so obviously I have more than the others, but I don’t feel like additional security should not allow me to add to my mailbox to my device 
Other things I tried through the process, with no success, in no particular order are:
Tried connecting my account from different devices
Disconnected and recreated mailbox
Deleted and recreated AD account
There is one thing I noticed in the security tab of the AD account, other people using our mail system and Android based devices have something called
Data Sync.  That is some sort of contact in AD
I guess.  I cannot find any information about it and when I add it to my security tab, it will not stay. 
After I close AD and check back 15 minutes late it is gone. 
I am trying to describe this the best possible way.  Has anyone experienced similar issue? 
If there is any further information needed feel free to ask. 

Then I would firstly suggest visiting the Remote Connectivity Analyzer Website to check common availability to your mailbox. Just run through the test.
I ran this test as suggested two different ways.  With my user name and password and then a second time with the mail server.  Both times in failed all tests with the exception of the following three:
Attempting to resolve the host name in DNS.
Testing the TCP port 443 on host to ensure it's listening and open.
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server on port 443.
All three of these passed.  I am not sure what most of this means, but we have people in the company a variety of different devices that connect with no problem.  For this reason I believe this problem is localized to my AD account or my mailbox,
I have matched up settings with people that I know have the same device and use it on a daily basis with no problem and can not find anything different.

Similar Messages

  • Exchange 2003 and Exchange 2010 Coexistence Activesync Issue

    Hello,
    I am currently on the progress of migrating mails from Exchange 2003 SP2 to Exchange 2010 SP3. Before I can do actual migration, I need to make sure that OWA and Activesync works when Exchange 2010 becomes Internet facing.
    Right now Exchange 2003 is Internet facing while Exchange 2010 is internal LAN only. OWA login from Exchange 2010 to a mailbox in Exchange 2003 works fine. However, trying to open a mailbox in Exchange 2003 from Exchange 2010 Activesync fails.
    Activesync login from Exchange 2010 to a mailbox in Exchange 2010 works fine, as well as logging in from Exchange 2003 to mailbox in Exchange 2003.
    Tests using AccessMyLAN ActiveSync Tester using Exchange 2010 as entry point are inconclusive. The test shows the app successfully contacting ActiveSync version 6.5 which is Exchange 2003, but results in "Activesync detected, but not correctly configured."
    Tests using Test-ActiveSyncConnectivity from Exchange 2010 reveals Error HTTP 400 when contacting Exchange 2003. The cmdlet also shows it successfully contacting Activesync version 6.5 (Exchange 2003).
    I have searched around, installed hotfix KB937031, enabled Integrated Windows Authentication on Exchange 2003 Microsoft-Server-Activesync, disabled Require SSL for Microsoft-Server-Activesync and exchange-oma, yet I still can't connect to a mailbox inside
    Exchange 2003 through ActiveSync 2010. Website Multiple Identities for port 80 has been set correctly. Exchange 2003 has Forms-Based Authentication Enabled and is the one thing we haven't tried disabling yet.
    We want to make sure everything works first, then make Exchange 2010 Internet facing, and finally do the mail migration. We do not want to migrate everyone in a single sitting. Please if anyone have ideas any help is welcomed!

    Exchange 2010 will proxy ActiveSync for Exchange 2003.  For OWA, it will redirect, so you need a legacy redirect URL.  You can test all of this internally without changing your Internet connection.  For ActiveSync you can use a WiFi connection.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2010 Active Sync issues

    I know I've posted a lot lately, but the issues keep rolling in with this upgrade.   Since upgrading to Exchange 2010, I have 2 users ( that have come forward thus far) saying they are unable to add exchange mail back onto their phones. 
    When I go into EMC to look at it and right-click on the uses it shows the option to manage mobile device.  Usually when there is no device paired, that option doesnt come up.  When I go into manage mobile device, it shows that there is no device
    listed.  If I run Get-ActiveSyncDeviceStatistics -Mailbox:"alias" I get the same result.  It shows no device.  I think this is locking the user out somehow from being able to add exchange back onto their mobile device.  
    I have also tried removing their email box from the server, then re-attaching it.  I get the same results each time.  They can add exchange to their phones, but when it tries to download mail it gets "Cannot get mail.  Connection to the
    server failed."  Even after they were able to add their account into their phone.

    Since you had ActiveSync devices on these accounts on the old system, the tools know those devices existed.  However, you can't manage them until you connect through the new system.  Is your Exchange 2010 system the one that handles the inbound
    ActiveSync connections?  Downlevel systems can't support any
    mailbox connections to newer systems.

  • Problems with a shared calendar using Outlook 2007 and Exchange 2010

    Hello all,
    We are having a problem with sharing a calendar using Outlook 2007 and Exchange 2010.
    I will start with some background. I have just started my position with this company. I have been working with networks for awhile at the small business level. I have not had much production experience with exchange. There is only myself and my supervisor
    who has inherited a midsized network which was built by five previous techs that are no longer with the company. Of course, the previous techs did not leave much documentation, so the original hows and whys for our system setup has been lost.
    One of the managers has a calendar she shares with some of our users. I believe this calendar has been in use since sometime in 2006. A mailbox was created to hold this calendar to keep it separate from the managers calendar. I am not sure what version
    of exchange they were using at that time, but I assume there was one or two migrations of it getting to its current state on our exchange 2010 server. At some point it was observed that the other workers she was sharing with were not able to access it correctly.
    I am not fully sure what the original problem was (possibly some people not being able to see or connect to the calendar), but it was decided to give everyone who needed access to this calendar full access permissions through exchange. Correct me if I
    am wrong, but I believe that gave everyone connected the ability to do anything with the calendar. Of course the manager was not happy about that. This is where I started working on the problem.
    I removed everyone, except the manager who wants to control the calendar, from having "Full Access Permissions". This did have the effect of making some people just able to see the calendar and not make changes. Though there were others that were
    able to connect to the calendar who I thought would not be able to. The manager that originally created the calendar did try to manage access to it through the Outlook interface, though it currently does not seem to be fully in effect.
    So, to get to the point of what we are trying to do, is there a way to get the original manager back into control of the calendar though Outlook? It would be preferred to be able to keep the history of what they tracked of this calendar, so starting a new
    one would be something we would rather avoid. After that, getting all of the users that need to connect to the calendar reconnected with the correct access permissions and making sure they are all synchronized.
    I realize this is a big mess, and your help would be greatly appreciated.

    Hi Nigel,
    How is the impact, just one user or all users, Outlook or OWA?
    If just one user, it seems like an issue on the Outlook Client side.
    Please trying to re-create new profile to fresh the caches.
    Please runing Outlook under safe mode to avoid some AVs, add-ins and firewall.
    Found a similar thread for your reference:
    Calendar Sharing not available error message
    http://social.technet.microsoft.com/Forums/exchange/en-US/d9b33281-d7bb-4608-8025-16fb26643d0d/calendar-sharing-not-available-error-message?forum=exchangesvrclientslegacy
    Hope it is helpful
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 and Exchange 2010 coexistense

    We have a and exchange 2010 organization with SP3 on most servers except for one 2010 CAS server that still requires SP1 for the purpose of legacy application compatibility. Can we introduce exchange 2013 in the org or will the setup detect
    that there is an exchange 2010 server still with SP1 and fails to continue?

    Hi,
    For Exchange 2013 coexistence with Exchange 2010, the mininum version of Exchange server is Exchange 2010 SP3 on all Exchange 2010 servers in the organization. For more information about it, please refer to the Coexistence of Exchange 2013 and earlier versions
    of Exchange server part in the article below:
    http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
    Personal suggestion, please upgrade your legacy application to the latest version which is supported with Exchange 2010 SP3 or higher Exchange version.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Outlook 2010 and Exchange 2010 SP3

    Hello,
    we are planning to upgrade from Exchange 2010 sp1 to SP3, most of client PCs has Windows XP sp3 and Oultook 2010 with VSTO addins working with mapi properties.
    I need to know if there are any known issues between this client environment and Exchange 2010 SP3 ??
    thanks a lot,
    Mauricio.
    Mauricio

    Windows XP is not supported in any scenario, so yes, I'd call that a known issue.
    Mike Crowley | MVP
    My Blog --
    Planet Technologies

  • CallManager 7.01 and Exchange 2010 UM

    We want to integrate CallManager 7.01 and Exchange 2010 UM.  The plan is to build two Exchange 2010 UM servers.  Who would be resonsible for load balancing (messanging) between the two Exchange 2010 UM servers?  CallManager or Exchange?  Does anyone know if there is any documentation on this?

    I would guess you just make a SIP trunk to both UM servers.  From here you can make a circular Route Group which would load balance the calls accross the UM's..
    So I guess the answer is call manager!
    HTH,
    Chad

  • Exchange 2010 Virtual Directory Authentication Settings

    Is it normal for authentication settings to be different in IIS Manager and Exchange 2010 Management Console? OWA and ECP are set to forms based in EMC, but IIS shows OWA and ECP as basic = enabled and everything else = disabled. IIS shows
    OAB as windows = enabled and everything else = disabled.

    Hi,
    Here is a reference about the default IIS authentication settings and default
    Secure Sockets Layer (SSL) settings for the Client Access and Mailbox server roles:
    http://technet.microsoft.com/en-us/library/gg247612(v=exchg.141).aspx
    It is recommended to manage your Exchange virtual directories authentication settings in Exchange Management Console or Exchange Management Shell instead of IIS manager. Some authentication changes in IIS require an IIS reset. If you are using Exchange management
    tools, you will see a warning that would tell you to reset IIS if needed.
    Thanks,
    Winnie Liang
    TechNet Community Support

  • Could we have same name's for User and Groups in Active directory

    When iam trying to create a user name " Logistics " under a OU, I am getting a error
    "The pre-windows 2000 logon name you have chosen is already in use in this domain. Choose  aother pre-windows logon name, and then try again"
    We already have a group by the name " Logistics "
    Could we have same name's for User and Groups in Active directory?
    Thanks in Advance

    sAMaccountName attribute is unique. So, the short answer is you cannot.
    This posting is provided AS IS with no warranties or guarantees , and confers no rights.
    Ahmed MALEK
    My Website Link
    My Linkedin Profile
    My MVP Profile

  • Windows 8.1 Mail app and Exchange 2010 EAS partnership - "Make Windows user account an Administrator" to meet security requirements?

    As the title says,  I have a new Windows 8.1 based device which I'm trying to connect to my Exchange 2010 box (SP3 Update Rollup 2).  I currently have my iphone set up as an EAS client with no problems.  I have an EAS policy on my mailbox
    with the following settings surrounding passwords :
    Require Password, Require Encryption, Allow Simple Password, Time without user input - 10 minutes.  Allow non-provisional devices is also checked.
    The Windows 8.1 device has Bitlocker enabled, which meets the encryption requirement - I know this because the 1st time I tried this it moaned about Bitlocker needing to be enabled to meet requirements, though at that time the local user account on the Windows
    8.1 device was an admin level account so it never mentioned this issue, it worked normally.
    Now, while using a std user account on the Windows 8.1 device and trying to connect up via EAS, it complains that my local windows user account must be an ADMIN level account to meet the security requirements...?
    Anyone encountered this?

    Did anyone solve this problem? I'm also struggling with this issue.
    this is still a problem. I'm just hitting it now and it's not doing much for management's love of Microsoft devices.
    Evidently, it has to be an admin to set the policies on the device to match the policies on the EAS. And once set, a user can be changed back.
    But this is seriously not cool. Don't the "app" folks and the enterprise folks talk to each other?

  • Legacy integration between Exchange 2003 and Exchange 2010

    Dear Team,
    we are using Microsoft Exchange 2003 & 2010 Server for Emails, now we have both servers are connected, we want to raise new Single incident request for doing this activity, we want disconnect 2003 server from 2010 server so accordingly need support,
    we are ready to pay for this incident, 
    pls do the needful,
    Thanks & regards
    Anteshwar Bhosale

    Hi Anteshwar,
    If you want to remove Exchange 2003 from your coexistence environment, please perform the following procedure:
    1. Move all mailboxes to an Exchange 2010 server in the organization.
    2. Move all content from the public folder database on the legacy Exchange 2003 server to a public folder database on an Exchange 2010 server in the organization.
    3. On Exchange 2003 servers, for each offline address book (OAB), move the generation process to an Exchange 2010 server.
    4. Verify that Internet mail flow is configured to route through your Exchange 2010 transport servers.
    5. Verify that all inbound protocol services (Microsoft Exchange ActiveSync, Microsoft Office Outlook Web App, Outlook Anywhere, POP3, IMAP4, Autodiscover service, and any other Exchange Web service) are configured for Exchange 2010.
    If all above steps have been prepared, we can remove the last Exchange 2003 server from the Exchange 2010 organization from ADSIEdit. For detailed steps about this, please refer to:
    https://technet.microsoft.com/en-us/library/gg576862(v=exchg.141).aspx
    Regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Winnie Liang
    TechNet Community Support

  • ICal, Macbook Air, and Exchange 2010

    I have a user whos iCal is not syncing with Exchange 2010. When creating a new event, it gives the message "iCal can't save the event "xxxx" to the Exchange server. The account "xxxx" currently can't be modified. To discard your changes and continue using the version of your calendars that's on the server, click Revert to Server. To save your changes on your computer until the problem is resolved, click Go Offline."
    The user is on a 2011 13" Macbook Air, 1.86 GHz Core 2 Duo. Snow Leopard 10.6.7, iCal 4.0.4. Mail and Address Book sync fine. The calendar works fine from the users iPhone, Outlook Web Access, and Outlook 2011 on the computer.
    I have tried deleting the account, deleting all caches, and recreating it, but it still doesn't work. I created the account on my Macbook and it works fine, no problems syncing over wired or wireless connections. Macbook is also on 10.6.7, iCal 4.0.4. So I was thinking it was an account issue. I created a new account on the Macbook Air, set up the exchange account in iCal, and I get the same problem as on the original account, no syncing.. I have everything set up exactly the same as on my Macbook, but the Macbook Air refuses to sync. This error only appears when an event created on the Macbook Air is in the calendar. It pulls events from the server fine, but once an event is created it refuses to cooperate.
    Do Macbook Airs just not play nice with Exchange?

    This is not an issue with the Macbook Air.  I have had this same problem since upgrading to Lion.  One solution suggested (from MacRumors.com forum reply)  was to
    1) Open iCal and go into the iCal Menu/Preferences. Go to Advanced tab and enable Time Zone Support. Close iCal
    2) Open System Preferences and click on Date & Time. Click on Time Zone tab and enable the checkbox for auto detect time zone.
    I did this several times without success before I finally got rid of the errors.  I have been error free for 3 weeks, but today the error is back (with no apparent changes made by me).  I'm still struggling to get rid of it now.

  • Mail 4.4 and Exchange 2010: not staying connected

    I am using Mail 4.4 connected to an Exchange 2010 account, and with an SMTP server instead of the actual Exchange connection to send outgoing mail due to the "no from: field" issue.
    I have noticed that Mail is not staying connected to the server. IIRC, Exchange is intended to be a live connection, and messages that arrived quite some time ago are nowhere to be seen until I click "Get Mail." Up to now, I've relied on IMAP with IDLE for mail, as I'd rather receive everything in real time instead of relying on a scheduled polling interval.
    Why is this? Is it just an issue of being Exchange 2010 instead of Exchange 2007, or is there something I can do to fix it?
    My iPhone running iOS 4.2 works perfectly with the same Exchange account.

    IMAP with IDLE for mail, as I'd rather receive everything in real time
    Certainly in the current version of Mail, you'll get more of a push effect if you use IMAP IDLE instead of EWS for communication with an Exchange server. Exchange Web Services feel less responsive.
    The Get Mail routine is much quicker with IMAP IDLE than with EWS. With EWS: the more mailboxes you have, the longer it takes.
    However: if you use IMAP instead of EWS, some features of Exchange will appear less graceful. Noticeable with e.g. messages relating to calendaring.
    (Note to self: I should review this after our organisation has completed its transition from Exchange Server 2003 to Exchange Server 2010.)
    messages that arrived quite some time ago are nowhere to be seen until I click "Get Mail."
    Using EWS: in the absence of a real-time/push effect, three approaches come to mind:
    a) pull manually (click Get Mail)
    b) prefer a schedule
    c) simply move or delete any message to trigger an update of that mailbox.
    For my Inbox, I prefer (c). An update of the Inbox alone is much faster than the (Get Mail) update of all mailboxes.
    Eventually, I guess that Apple will improve Mail to make it respond immediately to changes on the EWS side.
    Then, I'll go back to using e.g. GrowlMail to weed most messages immediately, as each one appears (much more pleasing than ploughing through a massive Inbox).

  • Problem with Assigning Policy button in Outlook 2010 and Exchange 2010

    First of all, I'm posting here because I'm not sure how to post in the previous version of Exchange forums.
    Secondly, I'm re-posting this from the Outlook forums as I'm not getting any responses there despite of views.
    Hi,
    I'm having an issue in Outlook 2010 where I can't assign personal policies to folders. I have setup personal tags and added the mailbox to the right policy. I have also ran Start-MangedFolderAssistant in Exchange 2010 Shell against the mailboxes.
    When I go into OWA, everything shows up perfectly, I can right-click and assign policies at will, but when I open Outlook 2010 then the Assign Policy button never appears. I force added it to the ribbon and I can see from there that the button stays grayed
    out irregardless of where I click in the folder structure. I have even assigned the mailbox user Owner rights to all the folders to see if it will  make a difference.
    If anyone can help me solve this problem I will very grateful, I'm pulling my hair out here and I'm certain I could just be missing something very obvious somewhere,
    It might be worth mentioning that the company has been using .prf files to configure Outlook thus far, I'm
    looking to eliminate that. I'm not sure if that will have any effect on my current problem.
    Thanks for your time.
    Nico

    Thanks for the reply Max, that's a pretty good link.
    Like is I said though, I have the policies all set up in the Exchange configuration side of things, when I use OWA all the options for applying tags appear. It's just in Outlook 2010 Standard that the Assign Policy button stays grayed out.
    Thanks.
    EDIT:
    This has been solved, looks like version problem with Outlook.
    http://office.microsoft.com/en-us/outlook-help/license-requirements-for-personal-archive-and-retention-policies-HA102576659.aspx

  • Exchange online and Exchange 2010 on-premise calendar availability

    I am running a hybrid exchange 2010 on-premise and online exchange environment.  The online exchange users cannot see calendar availability of anybody on premise.  The on-premise users can see the online exchange availability.  I can see the
    calendar if the calendar is shared, but trying to setup a meeting or calendar appointment still shows the unavailable through all days.
    All of the users are using office 365 for outlook on premise and exchange online.  If it is only working one way, could it be an autodiscover issue where it is not configured correctly on our on-premise exchange 2010 or online exchange?  Which
    side would be causing the issue?

    I have done a little more research and ran the following in powershell:
    [PS] C:\Windows\system32>Get-FederationInformation -domainname weiman.com
    RunspaceId            : f4af09c7-134a-4fe7-95c0-acd120c63949
    TargetApplicationUri  : outlook.com
    DomainNames           : {Weiman.onmicrosoft.com, weiman.com, Weiman.mail.onmicrosoft.com}
    TargetAutodiscoverEpr : https://autodiscover-s.outlook.com/autodiscover/autodiscover.svc/WSSecurity
    TokenIssuerUris       : {urn:federation:MicrosoftOnline}
    IsValid               : True
    [PS] C:\Windows\system32>Get-OrganizationRelationship | FL
    RunspaceId            : f4af09c7-134a-4fe7-95c0-acd120c63949
    DomainNames           : {herbertstanley.com, weiman.com, Weiman.mail.onmicrosoft.com}
    FreeBusyAccessEnabled : True
    FreeBusyAccessLevel   : LimitedDetails
    FreeBusyAccessScope   :
    MailboxMoveEnabled    : True
    DeliveryReportEnabled : True
    MailTipsAccessEnabled : True
    MailTipsAccessLevel   : All
    MailTipsAccessScope   :
    TargetApplicationUri  : outlook.com
    TargetSharingEpr      :
    TargetOwaURL          : http://outlook.com/owa/herbertstanley.com
    TargetAutodiscoverEpr : https://pod51043.outlook.com/autodiscover/autodiscover.svc/WSSecurity
    OrganizationContact   :
    Enabled               : True
    ArchiveAccessEnabled  : True
    AdminDisplayName      :
    ExchangeVersion       : 0.10 (14.0.100.0)
    Name                  : On Premises to Exchange Online Organization Relationship
    DistinguishedName     : CN=On Premises to Exchange Online Organization Relationship,CN=Federation,CN=WEIMAN,CN=Microsof
                            t Exchange,CN=Services,CN=Configuration,DC=herbertstanley,DC=com
    Identity              : On Premises to Exchange Online Organization Relationship
    Guid                  : 26b4ec5d-fe93-473e-b451-1f9aa2e94ebb
    ObjectCategory        : herbertstanley.com/Configuration/Schema/ms-Exch-Fed-Sharing-Relationship
    ObjectClass           : {top, msExchFedSharingRelationship}
    WhenChanged           : 1/13/2014 1:25:54 PM
    WhenCreated           : 12/17/2013 1:04:32 PM
    WhenChangedUTC        : 1/13/2014 7:25:54 PM
    WhenCreatedUTC        : 12/17/2013 7:04:32 PM
    OrganizationId        :
    OriginatingServer     : gemini.herbertstanley.com
    IsValid               : True
    I am not sure why we have that value for the OriginatingServer.  That server is a backup domain controller, not the server that houses the on-premise exchange.
    I then ran the set-OrganizationRelationship and get the below error.
    [PS] C:\Windows\system32>Set-OrganizationRelationship -Identity weiman.mail.onmicrosoft.com -targetapplicationUri outloo
    k.com -TargetAutodiscoverEpr https://pod51043.outlook.com/autodiscover/autodiscover.svc/WSSecurity
    The operation couldn't be performed because object 'weiman.mail.onmicrosoft.com' couldn't be found on 'gemini.herbertst
    anley.com'.
        + CategoryInfo          : NotSpecified: (0:Int32) [Set-OrganizationRelationship], ManagementObjectNotFoundExceptio
       n
        + FullyQualifiedErrorId : F2215CB2,Microsoft.Exchange.Management.SystemConfigurationTasks.SetOrganizationRelations
       hip
    How do I change the originating server to be my exchange server?

Maybe you are looking for