Outlook anywhere not workinhg , exchange 2013

i have exchange 2013 environment everything is working fine except outlook anywhere iam using TMG 2010 for publishing rule (OWA , Active sync and OA ) all are working fine except OA
when i try to configure outlook user his computer not in domain it keep asking for username and password during configuration and after 2 times asking the password it shows the attached screen with no success
can you advice why this happening ?

this happen to all users , no one can use OA but others services like OWA and active sync working fine with all , they all configured in same TMG sever with same listener
get-outlookanywhee | fl output as below
RunspaceId                         : 8153f39f-76d2-4b02-8b4b-fdd8fa9f4977
ServerName                         : severname
SSLOffloading                      : True
ExternalHostname                   : webmail.xxxx.com
InternalHostname                   : webmail.xxxx.com
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://servename.xxxxx.local/W3SVC/1
                                     T/Rpc
Path                               : C:\Program Files\Microsoft\Exchange
                                     Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 847.32)
Server                             : servername
AdminDisplayName                   :
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=P
                                     cols,CN=servername,CN=Servers,CN=Exchan
                                     Administrative Group
                                     (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=xxxxxx
                                     Co,CN=Microsoft Exchange,CN=Services,C
                                     nfiguration,DC=xxxxx,DC=local
Identity                           : servername\Rpc (Default Web Site)
Guid                               : b667bc75-2280-4b1b-99cd-9991b2300f6e
ObjectCategory                     : xxxxxx.local/Configuration/Schema/ms
                                     h-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory,
                                     msExchRpcHttpVirtualDirectory}
WhenChanged                        : 12/18/2014 6:07:17 PM
WhenCreated                        : 11/4/2014 9:07:48 AM
WhenChangedUTC                     : 12/18/2014 2:07:17 PM
WhenCreatedUTC                     : 11/4/2014 5:07:48 AM
OrganizationId                     :
OriginatingServer                  : DC.xxxxx.local
IsValid                            : True
ObjectState                        : Changed
note
my domian xxxxxxx.local and my extrenal url webmail.xxxxxx.com

Similar Messages

  • Outlook clients cannot connect Exchange 2013 cutover from 2010

    Hello,
    My company has been running an Exchange 2013/2010 coexistence. Currently, Exch 2013 (2mbx and 1 CAS) utilizes "mail2.domain.com" for the name space. Exch 2010 (1MBX 1 CAS) uses "mail.domain.com"
    We recently attempted to cutover external and internal DNS to point "mail.domain.com" and "autodiscover.domain.com" to the Exch 2013 server. 
    We changed all virtual directories on 2013 to use "https://mail.domain.com/owa" (ECP, EWS, etc. were changed too) for the internal and external URL. The Exch 2010 virtual directories internal URL are set to "https://internalFQDN.domain.com/owa"
    the external URLs are $null
    Both CAS servers were setup to use Outlook Anywhere since this is how 2013 proxies to 2010. The internal URLs for both were set to "mail.domain.com" IIS authentication Methods (Basic, NTLM). ClientAuthenicsationMethod: NTLM.
    For both servers the autodiscoverserviceinternaluri was set to: https://autodiscover.domain.com/autodiscover/autodiscover.xml
    The 2013 server has two SSL certificates installed. One is a wildcard cert for "*.domain.com" and the other includes our SANs (mail.domain.com, mail2.domain.com, webmail.domain.com, autodiscover.domain.com) it also includes the FQDN for the 2010
    and 2013 CAS servers.
    I'm speaking in the past tense because we had to roll back. The problem was no Outlook user could connect. This goes for mailboxes hosted on the Exchange 2013 and 2010 servers. The error was: "Cannot
    open your default e-mail folder" to "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete".
    Everything else worked fine during the cutover. OWA 2013 login page proxied 2010 logins properly, Outlook 2011 could connect with EWS fine, Active-Sync worked without issues too.
    It was only the Outlook 2010 and 2013 clients that could not connect.
    We rolled back and everything is working as it was before with the separate namespace. That leads me to think it's something with Outlook Anywhere (RPC/HTTPS)
    but the settings seem correct unless I'm missing something. Any help is appreciated.
    Thanks!

    Hard to say. I've had to change the router to point to the old server as mail wasnt getting in. But OWA did seem ok, although I couldn't send messages... I could only see the inbox and contacts etc.

  • Outlook Cannot Logon Error - Exchange 2013

    Hi all,
    I simply cannot create an Outlook (2007 or 2010) account to connect to my new installation of Exchange 2013 in Windows Server Essentials environment:
    1) Using autodiscover:
    I get green ticks for "Establishing network connection and "Search for [email protected] server
    settings". At "Log on to Server" I get the error message "The action cannot be completed.  The connection to
    Microsoft Exchange
    is unavailable.  Outlook must be online or connected to complete this action"
    2) Using manual configuration:
    Outlook Anywhere (RPC over HTTP) Exchange Proxy settings configured using the internal FQDN for the Exchange
    server and negotiate for authentication.  Clicking "check name" button to resolve servername (internal FQDN) and
    username (user email address) gives error, "Outlook cannot logon.  Verify you are connected to the network and are
    using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable.  Outlook must be
    online or available to complete this action.
    3) I can ping Exchange server using hostname and FQDN
    4) PC is member of the domain
    4) I have verified Exchange certiicate is installed on the client PC (although in the "Other People" certificates folder. Makes no difference when moved to the Trusted Root Certification Authority folder.
    5) I can successfully connect to the user mailboxes via OWA
    I've been working to resolve this issue for several days now and am at a complete loss as to what to do next to get this up and running.
    Any assistance will be greatly appreciated.
    RS
    RS

    Hi RS,
    Did you try to run Office Configuration Analyzer Tool (OffCAT) only for Outlook and check the results? If not, proceed and run the Tool and post the results.
    Additional info how to run the tool and check the results, you can find here: http://blogs.technet.com/b/catastrophic_failure_joannav/archive/2013/10/30/how-to-view-offcat-report-that-was-created-on-another-computer.aspx
    If no 
    Regards, Catastrophic Failure "JV"

  • First timeout, push retry and then succesfull connect?! Starting Outlook 2010 connect to Exchange 2013

    Hi!
    Some info:
    2x AD/DC Windows 2003 Native.
    Previous Exchange 2003 installed, but now cleanly as it gets uninstalled.
    Exchange 2013CU2v2 Aka Version 15.0 (Build 712.24)
    Office 2010 with Outlook 2010 (Latest SP, and WU)
    Outlook-prf configured for Outlook Anywhere. (i've also tried to configure manually, no difference)
    Exchange: SAN Cert. GUI requested from ECP. This one covers all possible host names the server can use. autodiscover, owa, mail, "netbios"-name. Self issued from the internal CA. CA distributed to clients with GPO. I get NO certificate warnings
    surfing to OWA, ECP.
    Exchange: ECP/Server/Outlook Anywhere; Auth set to NTLM (not Negotiate)
    Ping inside host names resolves to the Exchange server.
    Starting Outlook.exe with /rpcdiag show two connections for a while. One of the type catalog and one of the type redirect.
    Problem:
    When starting Outlook you see "Loading profile" for about 30-40 seconds. /rpcdiag show two connections CID "9","11"; SERVERNAME "---","[GUID]@thedomain", AUTH and ENCRYPT is empty.
    The the a dialog comes up that says that the server isn't available?!
    Clicking "Retry" makes Outlook connect as it should. Everything from there works like a charm! /rpcdiag windows show that it has connection as it should.
    Tried to click "Reconnect" in /rpcdiag. It also takes about 30 sec before it regains the conneciton. The part hanging there is the Type: Redirect.
    So, does anyone have a clue for why it doesn't work and then does?
    Can it be something wrong with the autodiscover?

    Hello,
    Do you mean the issue occurs when you select manually configure outlook exchange account or automatically configure outlook exchange account? If so, please make sure whether all users have the issue.
    I recommend you check if there exists redirection on your rpc virtual directory.
    I recommend you use "test e-mail autoconfiguration" tool to check if your autodiscover is correct.
    Besides, I recommend you to enable global and advanced logging for outlook to check RPC trace events.
    How to enable global and advanced logging for Outlook 2010 and Outlook 2013
    http://support.microsoft.com/kb/2260527
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

  • Outlook 2010 connecting to Exchange 2013 and 2007 ... delivery fails

    Hello,
    we are having a problem with a few Outlook 2010 Clients that have two Exchange accounts setup in one profile. One account is connecting to the company's Exchange 2013 Server, the second account is connecting to an external provider's Exchange 2007 infrastructure
    using Outlook Anywhere.
    The companies Exchange 2013 was recently migrated from Exchange 2010 and this is the point where the problem started.
    Some users are no longer able to send using the external Exchange 2007 account. When they try they are receiving an NDR with the following error message:
    #554 5.6.0 STOREDRV.Deliver; Corrupt message content##  from the external provider's servers.
    When I setup a profile containing only the external provider's mailbox everything works fine until I am adding the company's Exchange 2013 back in at which point the same error appears.
    We have no problems using the company's Exchange 2013 servers.
    Does anyone have an idea what causes this and how to resolve it? The external provider is uncooperative in troubleshooting so we are left with the problem.
    Thank you
    Sascha

    Hi,
    The problem should be related to the External Exchange 2007.
    Please refer to this kb below:
    http://support.microsoft.com/kb/2203381/en-us
    This problem occurs when the email message is a multipart/mixed MIME message which contains a text/plain body and an application/applefile body.  If the corresponding body is not a real application/applefile body, the Exchange Server 2007 server considers
    that the email message is invalid. Therefore, it generates the NDR. However, Exchange Server 2010 can deliver this kind of email message successfully.
    To resolve this problem, you should let the External Provider install the following update rollup:
    2279665 Description of Update Rollup 1 for Exchange Server 2007 Service Pack 3
    Hope this helps.
    Thanks,
    Melon Chen
    Forum Support
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please click
    here

  • Outlook 2010 connected to Exchange 2013 prior to coexistence

    I installed Exchange 2013 into the environment (Exchange 2010 SP3) and left it at that (ie no additional config).  I noticed Outlook 2010 client connected to Exchange 2013 somehow (it got a cert warning).  Why would Outlook connect to the new
    Exchange 2013 server like that?  Although I enabled Outlook Anywhere, it is not trying RPC/HTTP first, but rather RPC/TCP.

    Hi,
    By design, if the user mailbox located in Exchange 2010 server, the Outlook client will connect to Exchange 2010 server automatically.
    According to your description, I found that we have nothing additional configuration on Exchange 2013. So, only server name and internal services' URLs are configured automatically during the Exchange 2013 server installation.
    If it has no mailbox located in Exchange 2013, it is odd that Outlook client connect Exchange 2013 first.
    I suggest running "Test E-mail AutoConfiguration" in Outlook to verify which Exchange server the Outlook connected.
    Thanks
    Mavis 
    Mavis Huang
    TechNet Community Support

  • 530 5.7.1 Client was not authenticated - Exchange 2013 to external domains

    Hi all,
    I have an Exchange server 2013 on windows 2012 R2 and do all the configuration for sending and receiving the mail according to the document provided by Microsoft.
    But whenever I am trying to send mails from external domains to my exchange server domain I got the following error:
    530 5.7.1 Client was not authenticated
    Same thing I am getting If I am sending mail through outlook from my Exchange domains to external domain.
    But if I am selecting the
    <label for="ResultPanePlaceHolder_ReceiveConnector_Security_contentContainer_chkPermissionGroupAnonymousUsers" id="ResultPanePlaceHolder_ReceiveConnector_Security_contentContainer_chkPermissionGroupAnonymousUsers_label">Anonymous
    users in the security option of Default Frontend XXXX, I am able to send the mails through outlook.</label>
    <label for="ResultPanePlaceHolder_ReceiveConnector_Security_contentContainer_chkPermissionGroupAnonymousUsers" id="ResultPanePlaceHolder_ReceiveConnector_Security_contentContainer_chkPermissionGroupAnonymousUsers_label">But I don't
    want to use this option as it will enable to send the mails without validating the Exchange server user name and password.</label>
    SO can anyone please suggest some solutions to resolve this as using Anonymous users fro sending and receiving mails is not secure.
    Regards
    Pankaj Raman.
    <label for="ResultPanePlaceHolder_ReceiveConnector_Security_contentContainer_chkPermissionGroupAnonymousUsers" id="ResultPanePlaceHolder_ReceiveConnector_Security_contentContainer_chkPermissionGroupAnonymousUsers_label">
    </label>

    I have a java code for sending mails using the SMTP address of the servers. For sending a mail it required a valid user name and password. For all other SMTP servers if I have used invalid user name and password then I am getting the  530
    5.7.1 Client was not authenticated error, but
    if I am using my SMTP address and invalid user name and password then also I am able to send the mails.
    So I just want to know what I have to configure in the exchange 2013 server so that it will validate the user name and password.
    Regards
    Pankaj Raman.
    Hi Pankaj,
    Thank you for your question.
    Was invalid user name and password included in Java code?
    Did outlook send emails?
    If this issue happen on Java code instead of outlook?
    In fact, Exchange server didn’t validate user account and password, user account and password will be validated on domain controller,
    I suggest we create a new dedicated receive connector and enable “anonymous” permission for java code
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    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]
    Jim Xu
    TechNet Community Support

  • Users cannot access calenders from outlook after migration to exchange 2013

    I have a strange situation after upgrading to exchange 2013 some users are reporting that they cannot open or create calender appointments for calenders they used to be able to manage. we currently are using outlook 2010. also when the users access the calenders
    with the webmail they are reporting that they can access the calenders and are able to do all the things they need to do.
    i have tried reinstalling office and adding their exchange accounts but this does not help.
    another stange thing is that to be sure i had setup the correct access policy i have reset all the security entries on all the calendars with the help of powershell. this seemed to have helped but after a couple of hours some users started reporting that they
    could not access calendar items again!

    Hi,
    Is there any error description when the problematic users cannot open or create calendar items? Since the issue only happens to some users instead of all users and all calendars can work well in OWA, I think the calendar in the mailbox
    should be configured properly.
    Please configure the problematic user’s Outlook account in a clean computer with new installed Outlook to check whether the issue persists.
    Thanks,
    Winnie Liang
    TechNet Community Support

  • Outlook 2010 disconnects from Exchange 2013

    One of the users running Outlook 2010  (14.0.7108.5000) randomly gets disconnected from her mailbox on Exchange 2013. The disconnect lasts about 5 min and then connection reestablishes. While outlook gets disconnected, computer does not have any problems
    accessing any other network resources. Event 25 gets logged on the client when outlook disconnects and states the following. "Network problems are preventing connection to Microsoft Exchange."
    Other users in the same mailbox database don't experience or notice the same issue. 
    The error message states that the mailbox database is offline, but it's probably  misleading as the database remains online and mounted while the disconnect happens. The problems seems to follow the user no matter what mailbox database she is in.
    The following information gets logged in exchange RCP Client Access log Listed in chronological order.
    RopHandler: OpenFolder: [StoragePermanentException] There was an error parsing the entry ID. -> [MapiExceptionInvalidParameter] Unable to obtain the FID and MID from the entry id. (hr=0x80070057, ec=0) 
    ClientRPCCount=42;AvgClientLatency=00:00:00.0022142;ServerRPCCount=8;AvgCasRPCProcessingTime=00:00:00.0057500;AvgMbxProcessingTime=00:00:00;MaxCasRPCProcessingTime=00:00:00.0460000;20%ClientPercentile=10;40%ClientPercentile=10;60%ClientPercentile=10;80%ClientPercentile=10;90%ClientPercentile=10;95%ClientPercentile=20;99%ClientPercentile=20;100%ClientPercentile=50;20%CasPercentile=10;40%CasPercentile=10;60%CasPercentile=10;80%CasPercentile=10;90%CasPercentile=10;95%CasPercentile=10;99%CasPercentile=10;100%CasPercentile=50;20%MbxPercentile=10;40%MbxPercentile=10;60%MbxPercentile=10;80%MbxPercentile=10;90%MbxPercentile=10;95%MbxPercentile=10;99%MbxPercentile=10;100%MbxPercentile=10;ClientRpcFailureData:
    RpcEndPoint: [ServerUnavailableException] Connection must be re-established -> [SessionDeadException] Connection is severed (ConnectionFailedTransientException). Client needs to reconnect. -> [ConnectionFailedTransientException] Cannot get row count.
    -> [MapiExceptionNetworkError] Unable to get table row count. (hr=0x80040115, ec=0) 
    RopHandler: Logon: [RopExecutionException] Mailbox is temporarily unavailable. Error code = MdbOffline (0x00000476) -> [MailboxOfflineException] Cannot open mailbox /o=CORP/ou=Office/cn=Recipients/cn=Banger. -> [MapiExceptionMdbOffline] Unable to make
    connection to the server. (hr=0x80004005, ec=1142) 
    RpcEndPoint: [ServerUnavailableException] Connection must be re-established -> [SessionDeadException] The primary owner logon has failed. Dropping a connection. -> [RopExecutionException] Mailbox is temporarily unavailable. Error code = MdbOffline
    (0x00000476) -> [MailboxOfflineException] Cannot open mailbox /o=CORP/ou=Office/cn=Recipients/cn=Banger. -> [MapiExceptionMdbOffline] Unable to make connection to the server. (hr=0x80004005, ec=1142) 
    Any help would be greatly appreciated

    After reviewing the entire RCP Client log on the server, I am ruling out the client PC at this moment.
    The disconnect seems to be getting triggered by a Healthmailbox  check that starts right before users gets disconnected.
    Here is a similar problem with exchange 2010 with no answer.
    http://serverfault.com/questions/474123/one-email-user-keeps-disconnecting-from-our-exchange-server
    Healthmailbox associated with user's mailbox database  preforms the following operations at 19:00:05.899Z
    Connect
    OwnerLogon
    OwnerLogoff
    Disconnect
    a minute later, at 19:01:43.526Z Healthmailbox associated with  initial mailbox database  preforms the following operations
    Connect
    ArchiveLogon
    ArchiveLogoff
    Disconnect
    and then at 19:01:46.479Z server logs RopHandler: OpenFolder: [StoragePermanentException] There was an error parsing the entry ID. -> [MapiExceptionInvalidParameter] Unable to obtain the FID and MID from the entry id. (hr=0x80070057, ec=0) for the
    client connection and client notices the disconnect.

  • Outlook Anywhere not working for some users

    Hi All,
    I am having a strange issue today with a customer -
    Outlook Anywhere has been enabled on their Exchange 2010 environment, but it doesn't work for some users.
    Using the ExRCA I have been able to identify the following error on the users who are unable to connect:
    "Testing the MAPI Mail Store endpoint on the Exchange server."
    "Attempting to log on to the mailbox"
    Mailbox logon returned ecLoginPerm 1010. You don't have the correct permissions to log in to the mailbox.
    EMSMDB Status: ecLoginPerm 1010
    Elapsed Time: 225 ms.
    On users that are able to connect it goes through the ExRCA without any issues.
    Any help would be much appreciated.
    Cheers,
    Jack
    Testing the MAPI Mail Store endpoint on the Exchange server.
    An error occurred while testing the Mail Store.
    Additional Details
    Elapsed Time: 333 ms.
    Test Steps
    Attempting to ping the MAPI Mail Store endpoint with identity: outlook.mg.com:6001.
    The endpoint was pinged successfully.
    Additional Details
    Attempting to log on to the Mailbox.
    An error occurred while logging on to the Mailbox.
    Additional Details
    Mailbox logon returned ecLoginPerm 1010. You don't have the correct permissions to log in to the mailbox.
    EMSMDB Status: ecLoginPerm 1010
    Elapsed Time: 225 ms.

    Hi,
    I notice that this issue only impact "some users".
    I suggest double confirm whether the Outlook Anywhere configuration set correctly on Outlook client. Pic as blow:
    Thanks
    Mavis Huang
    TechNet Community Support

  • Active Sync not Working - Exchange 2013 with Exchange 2007

    Hi
    Recently we introduced Exchange 2013 servers to our existing Exchange 2007 organization. The servers are just configured with default self-signed certificate and URLs are pointing to server FQDNs.
    Everything is at default as far as configuration is concerned in Exchange 2013.
    After just introducing the Exchange 2013 CAS servers was checking the ActiveSync functionality using a new mailbox created on Exchange 2013. We have not yet published our Exchange 2013 servers to
    Internet (before even doing that, want to ensure ActiveSync is working). We're connecting using our Private network and trying to make a connection to CAS FQDN. Checked a iOS7 (iPad) and a Windows Phone device, both of them configure successfully (with the
    certificate warning, which is obvious) but when it comes to synchronizing the contents they fail saying "Cannot Get Mail. Connection to Server Failed"
    Checked the IIS Logs on CAS server and found that the device makes a successful connection - as is indicated by successful configuration but thereafter nothing happnes on the device and no error
    logged in Event Viewer as well. Could it be that the mailbox server is denying the connection....how to check. How to go ahead with the troubleshooting.
    Everything else expect ActiveSync is working perfectly. Tries accessing the ActiveSync VD using the link
    HTTPS://Server_FQDN/Microsoft-Server-ActiveSync, this pops-up a window asking for credentials – which is normal behavior indicating ActiveSync virtual directory is good.
    Thanks
    Taranjeet Singh
    zamn

    Hey Guys
    Just to update here my initial testing revieled that if I run Test-ActiveSyncConnectivity by not specifying the -URL parameter like this:
    Test-ActiveSyncConnectivity -MailboxCredential (get-credential User1) |FL
     the command fails for an obvious reason as shown in the result. The command is getting the mailbox server name in the ActiveSync URL returned automatically:
    ClientAccessServer         
    : SITE-MBX-02.ABC.COM
    Scenario                   
    : Options
    ScenarioDescription        
    : Issue an HTTP OPTIONS command to retrieve the Exchange ActiveSync protocol version.
    PerformanceCounterName     
    : DirectPush Latency
    Result                     
    : Failure
    Error                      
    : The OPTIONS command returned HTTP 200, but the Exchange ActiveSync header
                               (MS-Server-ActiveSync) wasn't returned. The request likely did not reach a
    Client Access
    server, either because
    - A proxy server intervened (check the headers below for any that may have been
    returned by a proxy)
    -The virtual directory could not be reached:
    https://SITE-MBX-02.ABC.COM/Microsoft-Server-ActiveSync
                         - The virtual directory does not point to a Client Access server:
    https://SITE-MBX-02.ABC.COM/Microsoft-Server-ActiveSync
    If however, I manually provide the -URL parameter value with FQDN of CAS server:
    Test-ActiveSyncConnectivity -URL
    https://SITE-CAS-02.ABC.COM/Microsoft-Server-ActiveSync
    -MailboxCredential (get-credential User1) |FL
    it succeeds.
    We have our CAS and Mailbox servers installed on separate systems - no colocation.
    This is strange and makes me curious to find out, where does the command without -URL parameter is getting the ActiveSync URL that has mailbox server in it. I checked that the new Exchange 2013 CAS servers have InternalURL parameteres populated with their
    own FQDNs and the ExternalURL is empty for now.
    Need help in drilling down this further.
    Thanks
    Taranjeet Singh 
    zamn

  • Outlook anywhere issue for exchange 2010 users

    Hi Guys really hoping some one can help me out here.
    I have just introduced 2 new exchange 2013 servers into our existing exchange 2010 environment. 1 CAS server and 1 mailbox server.
    The issue i'm having is that any users that are on exchange 2010 mailbox servers can't connect to their profiles in outlook via the exchange 2013 cas box. OWA works fine and users that are on exchange 2013 mailboxes also work fine.
    Authentication is set to on exchange 2013 and 2010 cas boxes to
    Exchange 2013 cas
    ExternalClientAuthenticationMethod : Ntlm
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm}
    Exchange 2010 cas
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm}
    I was also wondering should I have a reg key on my exchange cas box of HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy\validports_autoconfigure_exchange  ???

    Thanks for the reply i have changed it to the following
    Exchange 2013 cas
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm}
    Exchange 2010 cas
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm}
    and reset iis but still no luck authenticating with outlook on existing profiles or a new profile.

  • Can not install exchange 2013

    Hai
    I try to install exchange 2013 but there is a problem showed at below:
    This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Please install the software from http://go.microsoft.com/fwlink/?LinkId=260990.
    Finally I follow it to install the Microsoft Unified Communications Managed API 4.0, but i got error like this:
    Microsoft Unified Communications Managed API 4.0, Runtime cannot be installed side by side with the following components. Installation cannot continue.
    Microsoft Server Speech Platform Runtime (x64)
    I already uninstall the Microsoft server speech, but i still got the same error. 
    How can I solve this problem, installing MUCM API 4.0 without error?
    Thank you

    Duplicated. Will help you move to
    http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploy/thread/5a2061ec-ac34-4369-81c2-069c85f2e5df
    Fiona Liao
    TechNet Community Support

  • Mac outlook 2011 users with Exchange 2013 cu5

    Hi all, I had a strange issue that came up after I reconfigured our receive connector in exch2013.
       I have Exch2013 with Cu5 and a 2010 sp3. In order to fight spam I needed to reconfigure a new connector that's a bit locked down compared to the default frontend that's open to all remote networks, so in the new connector under
    the scope settings I put our internal network ip and disabled the default frontend connector that was created during install. Since our exch2010 box is the main server that sends in and out, and has better antispam features, this is where all emails went
    through and got routed to the 2013 box.
      After restarting services, all was working including iphones and androids, except for Macs with outlook 2011, they were suddenly not able to connect to the exch2013 box after the changes. I looked at the transport logs but I couldn't see
    anything showing why these users were not connecting, event viewer as well. It did block a lot of spam from getting through, but I had to revert back to the default front end connector just to get the Mac outlook users working again, has anyone seen
    this before, or any other settings I might have missed. If anyone can get me some ideas or pointers, I'd greatly appreciate.
    Thanks in advanced.
    Carlo

    Hi,
    I suggest try to re-create MAC 2011 user profile for testing.
    Find a related KB for Exchange Online (even if it isn't for Exchange on-premises, please try it.) for your reference:
    http://support.microsoft.com/kb/2847916/en-us
    Thanks
    Mavis
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Mavis Huang
    TechNet Community Support

  • Outlook 2010 not showing Exchange 2010 archives, OWA does.

    We have activated Exchange 2010 archives for all users but most of them are not showing up in their Outlook, but everyone can see them in OWA.
    Office 2010 Standard - MAK licenses, 2 distinct keys
    Majority of systems are Windows XP, some Vista and 7.
    Through testing it seems to be a system problem. Using 3 test accounts I log onto various systems, some freshly reimaged, some pre-existing. The test account profiles were new to each system. Sometimes the archive folder would appear, sometimes it wouldn't,
    but it was consistent per computer. Meaning that if the folder didn't appear for 1 person, it didn't show up for anyone on that specific computer.
    Anybody know how to fix this? Am I missing a setting or registry key somewhere?
    Thank you for any help,
    Greg

    Ok, just spent some time looking into this more, if you google "office 2010 suite and version comparison guide pdf" and locate the .pdf file and open it, on page 17 under
    Managed E-Mail Folders & Retention Policy:
    "Provide a secondary location for users to store their e-mail messages and
    manage their mailbox quota with new online managed folders. Unlike localOutlook Data Files (PSTs), this information can be backed
    up and managed by Exchange Server."  - is an Office Professional Plus feature only.
    So, it would appear that we now not only have to purchase an enterprise CAL for Exchange, but Office Professional Plus as well so we can, I suspect, use the
    one extra useful feature that most sys admins wanted Exchange 2010 SP1 for in the first place, which is so centrally manage e-mails and e-mail archives.  Whilst this may not be a big deal for larger companies, educational institutes
    etc, as the sys admin for a small private business with 70 users, this extra cost hurts.  As for the lack of clarity - if you want to tie up Office versions with Exchange functionality, how about standardizing naming conventions - call the Exchange
    CALs "standard" and "professional" to match the required Office clients, or rename Office Professional to Office Enterprise - either way, match up the client apps and CALs to make it clearer.

Maybe you are looking for