Exchange 2013 - Missing Emails sent internally

Can someone please help me diagnose what has happened with the following problem
User1 sends an email at 23:18 from his works laptop at home which is connecting to exchange using Outlook Anywhere
User1 sends an email to 4 users: "User2, User3, User4, UserEx" - UserEX is an external user.
User3, User4 & UserEX - Received the email
User2 - Did not received the email
User1 - Travels to place of works and logs onto his works PC (not the laptop which is at home)
User1 - Also receives a copy of all messages sent to User2 and notices that he doesn't have a copy of the email he sent to User2 at 23:18.
User1 - Checks his sent items, there is no email there from 23:18
User1 - Confirms that User3, User4 received the email, which they have.
He contacts me (support) asking what is going on. I investigate by looking at his OWA (thinking it could be a syncing issue), the email doesn't show up UNLESS I do an advance search on his OWA Email Box, which tells me there are two emails 1 in his Inbox
and 1 in his drafts. Move away from the advanced search and the email cannot be found.
I complete a Deliver Report for User2 for this missing email; Results below
Submitted
19/01/2015 23:18 EXC01
The message was submitted to exc01.*.
Pending
19/01/2015 23:18 exc01.
Message was received by exc01. from EXC01.
19/01/2015 23:18 exc01.
This message was redirected to another email address.
19/01/2015 23:18 exc01.
The message has been transferred from exc01. to EXC01.
Delivered
19/01/2015 23:18 exc01.
The message was successfully delivered.
Even the Get-MessageTrackingLog tells me the message was sent. Though there was a HAREDIRECTFAIL & AGENTINFO in the processing.
If anyone can help me workout what the heck is happening here, id be very appreciative.
Thanks
Neil

Hi there Amy,
User1 sends about 10-20 emails a day to User2 and they have been fine since and beforehand. Its just this instance.
User1 = Director
User2 = PA
It was an Email not a Meeting Request.
The email in question was being replied to.
To: UserEX
Cc: User2; User3; User4
The Director receives a copy of all emails sent to his PA. In this instance neither one of them received the email. The only people to receive the email was UserEX, User3, User4.
Also the Directors email (User1) wasn't in his sent items on his work PC in the morning. (Remember he sent it from his laptop at home during the late evening the day before).
The trackinglogs & delivery reports, say that the email got delivered to all recipients. Further investigation suggests that this email is there but not visible to them.
Its a strange one I know, but I'm wondering what would cause an email to be there but not invisible?. 

Similar Messages

  • Exchange 2013 autodiscover finds external & internal SSL certificate causing autodiscover to fail

    <p>Hi:</p><p>I'm currently working on a windows 2012 server, with exchange 2013, lets say our internal domain is "cars.com" and ALSO the case for&nbsp;our external domain. We have purchased an SSL wildcard positive certificate
    *.cars.com so that we could configure Outlook Anywhere, we have created the needed DNS records at godaddy and our internal server, OWA, ECP it all works if you go to&nbsp; <a href="https://bird.cars.com/owa">https://bird.cars.com/owa</a>
    because we have a DNS record for bird in godaddy and out local server, so all of that is working like a pro ! here comes the tricky part, our website is registered in godaddy but hosted by someone else a company called poetic systems; when we test the connection
    with the remote connectivity analyzer website we get a very peculiar error that says SSL certificate not valid, now it provides the name of the certificate it found and is not ours, we found that the hosting company is listening in port 443, therefore, it
    is pulling their self signed certificate also, does anyone have a fix for this, I have done this same setup before for other companies and this is the first time a situation like this happens. I REALLY NEED HELP !!!!!</p>

    Hi,
    According to your description, there is a certificate error when you test Outlook Anywhere connection by ExRCA.
    If I misunderstand your meaning, please feel free to let me know.
    And to understand more about the issue, I’d like to confirm the following information:
    What’s detail error page?
    Check the Outlook Anywhere configuration: get-outlookanywhere |fl
    Check the certificate : get-exchangecertificate |fl
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange 2013 (lab): emails stuck in OWA Drafts

    Hello I have setup for testing purposes an Exchange 2013 CU5 on a 2012R2 which is also DC and DNS.Network wise I have two virtual interfaces one for the internal network (10.10.10.x/24) and another one linked to the Ethernet physical interface of my computer
    which gets its properties from DHCP (usually my gateway router).
    Everything seem to work normally but when I try to send emails to the outside world I only get a copy of it inside the Drafts folder. :-)
    I thoroughly checked the DNS service (inside the Exchange too), A, PTR records and SOA, I tested the DNS server and nslookuped some internet addresses all resolving fine.The DNS service registers both interfaces DNS servers (the internal one which
    is the DC and the external one which comes through DHCP).
    Through Test-ServiceHealth in Exchange Management Shell I checked all required services are up and running.
    With Setspn -L hostname  I verified all required services are registered correctly on my server.
    I also checked Event Viewer and besides some performance counters errors about exchange nothing else in there too.
    I haven't registered an MX record because I don't need to receive mail just to send in that  early stage.Am I right in that?
    Any ideas are welcome and thanks in advance.

    When you see this piling up in drafts, it is not even making it to transport. 
    OWA sends mail via drafts folder.  So can you please restart the "Microsoft Exchange Mailbox Transport Submission"  service and see what happens.
    This is also a very bizarre setup.  DCs do not normally have multiple interfaces, and while Exchange is supported on a DC (apart from DAG) its still not recommended.  
    You probably want to simplify this as you troubleshoot - can  you remove the internal interface from the test box, and clean up DNS and host files etc.
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Sending email using Exchange 2013 defined email addresses not the account email address.

    Currently we are using exchange 2013. Let's say a user has a mailbox account defined that has a default email reply address of [email protected] Now I define additional email address for the same account. When the user tries to send an email he can only send from
    the default email address. Is it possible to send from a defined email anndress and not the default account email address?
    Best Regards
    Best Regards

    Not natively with Exchange.
    You will need 3rd party software if you want to have only one mailbox and the ability to send as any of the proxy addresses associated with it
    Example:
    http://www.ivasoft.biz/choosefrom2007.shtml
    Not sure if Exchange 2013 is supported with it yet
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Mail for Exchange and missing emails

    Hi,
    We have a problem with out Mail for Exchange mobile synhronization. All the mails are received in Outlook (Exchange Server) but in MfE some emails are missing. The missing emails are randomly selected inside or outside organization emails. Let's say few emails per day are totally missing inf MfE. What could be the problem? We have e72 mobiles, our Exchange server is 2007 and we are using Forefront 2010 to ISA connection.

    Go to your outlook web access website and click on the lock and then view certificate. The details and then you can save it in DER format to your desktop.
    Then go to this site:
    http://www.redelijkheid.com/symcaimport/ and insert through the browse button and then copy the link to your phone.
    Then you should be able to download it
    You can also go to your IIS default site on the exchange server and directory security and export your certificate under edit certificate.
    I have tried everything now. I can download my certificate and the valicert from GoDaddy, but the Nokia phone is still saying "do you trust this certificate" every time the phone syncs.
    Our firm have taken the E-phones away now and went over to windows mobile and all of them worked within 10 minutes without any errors.
    The funny thing is that when you try to call nokia, they wont help you with Mail for Exchange, and it is there program
    I know my GoDaddy certificate works on windows mobile phones, so It must be something with Mail for Exchange.
    Every guy I talked to about symbian phones have told me they always gives problems with SSL. I am a bit **bleep**, but can conclude that Nokia is for the private consumer.
    Best Regards
    Morten @ Denmark
    Message Edited by asp3200 on 02-May-2008 08:37 AM

  • How to disable Exchange 2013 Outlook Anywhere for internal Outlook client

    Hello;
    By default, Exchange 2013's Outlook Anywhere is enable for all user mailbox, if I disable the Outlook Anywhere per user mailbox, the user will not able to connect his Outlook client to Exchange 2013.  What is the best method to disable the Outlook anywhere
    on mailbox but let the Outlook 2013 still able access to Exchg server.
    The initial idea is to prevent user from access to company Exchange server from ANYWHERE, we just want to open the Outlook Anywhere for the authorized user only.  Looks like Microsoft did not think about the security.
    thanks!

    Hello;
    By default, Exchange 2013's Outlook Anywhere is enable for all user mailbox, if I disable the Outlook Anywhere per user mailbox, the user will not able to connect his Outlook client to Exchange 2013.  What is the best method to disable the Outlook anywhere
    on mailbox but let the Outlook 2013 still able access to Exchg server.
    The initial idea is to prevent user from access to company Exchange server from ANYWHERE, we just want to open the Outlook Anywhere for the authorized user only.  Looks like Microsoft did not think about the security.
    thanks!
    I don't understand your request. If you disabled Outlook Anywhere, Outlook will only be able to connect via IMAP or POP3.
    If you want to disable this ability and allow some then perhaps use cas-mailbox to disable in bulk and then enable only those allowed:
    http://technet.microsoft.com/en-us/library/bb125264(v=exchg.150).aspx
    The MAPIBlockOutlookRpcHttp parameter enables or disables access to the mailbox by using Outlook Anywhere (RPC over HTTP) in Microsoft Outlook.
    Valid values for this parameter are:
    $true   Only Outlook clients that aren't configured to use Outlook Anywhere (RPC over HTTP) are allowed to access the mailbox. By default, Outlook 2013 is configured to use Outlook Anywhere.
    $false   Outlook clients that are configured to use Outlook Anywhere (RPC over HTTP) are allowed to access the mailbox.
    The default value is $false.
    Twitter!:
    Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2013 incoming emails being delayed

    grey mail can do this, as can grey listing. - on your spam filter are they delivered on time but slow at the exchange side or are they delayed by your filter before being delivered?

    http://blogs.technet.com/b/messagedelaysinexchange2013/archive/2014/08/26/message-delays-out-the-box-in-2013.aspx
    http://community.spiceworks.com/topic/444283-exchange-2013-400-4-4-7-message-delayed-gmail

  • EXCHANGE 2013 - ECP AND OWA INTERNAL ERROR 500 - NEW INSTALL

    Really hoping someone can help me here.
    I first installed 2012 OS and 2013 exchange and users were getting 'Unable to open your default folder' when trying to open outlook. After much googling and nothing working I decided to put 2008 R2 on the server with 2013 Exchange. Now i am running into massive
    issues. 
    Firstly i get Internal Errror 500 after putting in credentials for ECP and OWA. I did notice that it is also defaulting straight to this URL after entering password https://localhost/owa/auth.owa
    I check the management shell and that connects without any issues. I also logged on to a computer to see what it did. After autodiscover it is not able to log onto server and then it looks like it is look for the old server information from previous server.
    Any help would be appreciated. Can i do another reinstall of OS and how am i meant to remove the previous data that it seems the server has found?

    Hi,
    According to your description, I understand that cannot login internal ECP\OWA with error 500, also autodiscover failed.
    If I misunderstand your concern, please do not hesitate to let me know.
    I notice that autodiscover “looks like it is look for the old server information from previous server”, have you installed multiple version Exchange in your environment?
    Please run below command to double check the virtual directory configuration:
    Get-OutlookAnywhere | FL Identity,*Host*,*Auth*
    Get-OwaVirtualDirectory | FL Identity,*url*,*auth*
    Get-EcpVirtualDirectory | FL Identity,*url*,*auth*
    Get-WebServicesVirtualDirectory | FL Identity,*url*,*auth*
    Get-ClientAccessServer | FL Identity,*URI*,*auth*
    Then, open IIS and check on the Application Pools to view whether MSExchangeOWAAppPool and MSExchangeECPAppPool is running on .NET Framework v4.0, and recycle virtual directory for test.
    Additional, here’s a thread about “Removing Old Exchange and installing a new one”, for your reference:
    https://social.technet.microsoft.com/forums/exchange/en-US/46ca107c-7ece-4da7-8aea-46b705793f37/removing-old-exchange-and-installing-a-new-one
    Thanks
    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]
    Allen Wang
    TechNet Community Support

  • Exchange 2013 allowing emails from spoofed domains

    We upgraded from Exchange 2010 to 2013 about 6 months ago and are very disappointed. We were running Forefront protection for Exchange on the 2010 server, and had little to no spam every. Now with 2013 we are getting a ridiculous amount of spam, including
    clearly spoofed phishing emails. The most recent are from
    '[email protected]' with an attached zip. We get about 4-5 of those a day, and since we do use salesforce, I can't just block the address/domain.
    I have followed the TechNet guide, and enabled all of the antispam features with the Exchange management shell. I have enabled the senderIDConfig, and have it set to delete spoofed domains. The reverse dns check is working, as it shows the
    status on the messages that are sent to quarantine. We also have the content filter enabled, and every day I have to go through the spam and add keywords it actually blocks something.
    So how is it that spoofed messages are still making it through? I have checked salesforce and they have their SPF records setup, so it should not be hard for Exchange to see the mail did not originate from any of the IPs in the list. We are seriously considering
    moving back to our exchange 2010 server....

    Here are the headers of the email, which show its not coming from an IP listed in the SPF record for that domain...
    Received: from ExchServer.domain.local (EXCH_IP) by ExchServer.domain.local
     (EXCH_IP) with Microsoft SMTP Server (TLS) id 15.0.775.38 via Mailbox
     Transport; Fri, 21 Feb 2014 06:51:55 -0800
    Received: from ExchServer.domain.local (EXCH_IP) by ExchServer.domain.local
     (EXCH_IP) with Microsoft SMTP Server (TLS) id 15.0.775.38; Fri, 21 Feb
     2014 06:51:55 -0800
    Received: from nacha.org (176.103.168.1) by ExchServer.domain.local (EXCH_IP)
     with Microsoft SMTP Server id 15.0.775.38 via Frontend Transport; Fri, 21 Feb
     2014 06:51:42 -0800
    Received: from  176.103.168.1 (account [email protected] HELO
     hlijear.cieewgas.org) by  (CommuniGate Pro SMTP 5.2.3) with ESMTPA id
     993713337 for [email protected]; Fri, 21 Feb 2014 15:51:39 +0100
    Received: from smtp01-was.mta.salesforce.com ([96.43.148.64]) by
     m1pismtp01-011.prod.mesa1.secureserver.net with ESMTP; Fri, 21 Feb 2014
     15:51:39 +0100
    Return-Path: <[email protected]>
    Received: from [10.236.73.76] ([10.236.73.76:58434]
     helo=na10-app2-11-was.ops.sfdc.net) by mx2-was.mta.salesforce.com
     (envelope-from <[email protected]>) (ecelerity 2.2.2.45 r()) with ESMTP
     id 64/F1-22599-B8956259; Fri, 21 Feb 2014 15:51:39 +0100
    Date: Fri, 21 Feb 2014 15:51:39 +0100
    From: "[email protected]" <[email protected]>
    To: <[email protected]>, <[email protected]>,
     <[email protected]>
    Message-ID: <[email protected]>
    Subject: Check you payment data!
    MIME-Version: 1.0
    Content-Type: multipart/mixed; boundary="----------CE9B863200324FC"
    X-Priority: 2
    X-SFDC-LK: S82SNJ6CSHXLTTR
    X-SFDC-User: KNAXCL1Y1DWN5IT
    X-Sender: [email protected]
    X-mail_abuse_inquiries: http://www.salesforce.com/company/abuse.jsp
    X-SFDC-TLS-NoRelay: 1
    X-SFDC-Binding: System
    X-Nonspam: Whitelist
    X-MS-Exchange-Organization-PRD: salesforce.com
    X-MS-Exchange-Organization-SenderIdResult: SoftFail
    Received-SPF: SoftFail (ExchServer.domain.local: domain of transitioning
     [email protected] discourages use of 176.103.168.1 as permitted sender)
    X-MS-Exchange-Organization-Network-Message-Id: 321bc164-8c39-43ea-f8af-08d0fd2b98f4
    X-MS-Exchange-Organization-SCL: 1
    X-MS-Exchange-Organization-PCL: 2
    X-MS-Exchange-Organization-Antispam-Report: DV:3.3.5705.600;SID:SenderIDStatus SoftFail;OrigIP:176.103.168.1
    X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
    X-MS-Exchange-Organization-AuthSource: ExchServer.domain.local
    X-MS-Exchange-Organization-AuthAs: Anonymous

  • Exchange 2010 inbound email (external/internal) randomly stuck in delivery queue

    Dear all,
    We got a problem email is not deliver to mailbox normal.
    For example. I send a email to recipient A,B and C in same internal email.
    The result is A can receive email normally, but B and C email is stuck in delivery queue.
    We need to re-start the CAS transport service to release the email from delivery queue.
    Any idea for this kind of email deliver issue?
    Exchange server environment:
    1. Two CAS/HT server in NLB mode (Exchange std. ver.)
    2 Two Mailbox server in DAG mode (Exchange Ent. ver.)
    We got this issue around 12 months on production migrate from 2000 to 2007 to 2010.
    Felix.

    hi,
    What's the last error in the queue viewer? Do you have some error code?
    You can use message tracking log to find more information about your issue.
    If you create 3 new users and send a test mail to they, can they always receive the mail. May be your user account have some problem.
    we need more information about your issue. Always is the stationary users or it is randomly?,The frequency of occurrence and so on.
    hope can help you
    thanks,
    CastinLu
    TechNet Community Support

  • Exchange 2013 not receiving internal and external emails ..

    I have a coexistence of exchange 2007 and exchange 2013 ..2013 mailboxes where able to receive and send mails (internal and external) but suddenly the mail flow has stopped. 
    Mail flow status
    2013 to 2007 = OK
    2013 to internet = OK
    2013 to 2013 = OK
    2007 to 2013 = FAIL
    Internet to 2013 = FAIL 
    incoming internet mails return the NDR below
    Diagnostic information for administrators:
    Generating server: mydomain.com
    [email protected]
    Remote Server returned '< #4.4.7 smtp;400 4.4.7 Message delayed>'
    What could be a possible reason for this? 
    Cheers guys ..
    ..forever is just a minute away*

    Hi Richard,
    Thank you for your question.
    When there is a coexistence of Exchange 2007 and Exchange 2013, external email will be sent and received by Exchange 2013.
    4.4.7 means message expired, message wait time in queue exceeds limit, potentially due to remote server(your Exchange server ) being unavailable.
    If your organization has correct MX record in ISP. We could refer to the following link to check if MX record is correct:
    http://technet.microsoft.com/en-us/library/aa998082(v=exchg.65).aspx
    If we could telnet Exchange server by the following command: telnet mail.domain.com 25
    If there is a receive connector on Exchange 2013 to receive Internet emails, we could create a receive connector to receive message from the Internet by the following link:
    http://technet.microsoft.com/en-us/library/jj657447(v=exchg.150).aspx
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim

  • Establish mail flow from Exchange 2007 to Exchange 2013

    I am currently using Exchange 2007 into three sites in three cities and two of the sites are connected to Internet sending and receiving emails via Edge transport servers.
    Now I am planning to upgrade to exchange 2013 CU1. I don't find any documentation on how to establish mail flow between Exchange 2007 and Exchange 2013. Will it be automatic or do i need to create specific connectors between them?

    Was this question answered.  We're in the same situation now as we're upgrading to Exchange 2013 from 2007. The latest CU certainly helped.   Initially the test mailboxes on Exchange 2013 couldn't email each other - This was resolved with CU7 and
    using "Custom Settings" - manually entered IPs for DNS in the Exchange  Admin Center "DNS Lookups".
    Issue at the moment Test mailboxes on Exchange 2013 cannot email mailboxes on 2007 or visa-versa and mail from external sources queues on the 2007 box.  
    Any assistance will be greatly appreciated.  

  • Exchange 2013 Domain Prep Fails: Setup /prepareschema, setup /PrepareAD, Setup /PrepareDomain

    Whenever I try to prep for a 2013 exchange install I always get:
    "earlier versions of the server roles that are installed were detected"
    whenever I try to run Setup /prepareschema OR setup /PrepareAD OR Setup /PrepareDomain
    I am working on a Server 2012 standard machine with Exchange 2010 currently installed. This server is a DC (bad I know), DNS, DHCP.
    I am trying to prep the domain so that I can install Exchange 2013 on a VM and eventually remove Exchange 2010 from the organization altogether.
    There are no other domain controlelrs in the domain. The domain started life as a SBS 2003 machine which was demoted and removed once the server 2012 box was up with exchange 2010 running.
    Any help would be greatly appreciated.
    Here is some info that may help:
    1. PrePare Schema
    Navigated an elevated command prompt to the folder with Exchange 2013 CU3.
    Ran setup /PrepareSchema
    This command should perform the following tasks:
    A: Connects to the schema master and imports LDAP Data Interchange Format (LDIF) files to update the schema with 
    Exchange 2013 specific attributes. The LDIF files are copied to the Temp directory and then deleted after they are imported 
    into the schema.
    B: Sets the schema version (ms-Exch-Schema-Verision-Pt) to a Exchange 2013 value.
    This command fails with: Earlier versions of server roles that were installed were detected.
    First I confirmed that administrator account for domain is a member of schema admins and enterprise admins.
    Next I ran asdiedit.
    I navigated to: "CN=ms-Exch-Schema-Version-Pt,CN=Schema,CN=Configuration,DC=BDA,DC=LAN"
    and reviewed the current "rangeUpper" attribute.
    The ms-Exch-Schema-Verision-Pt is not updated to CU3 range Upper setting.
    The current range upper 14734 which means its still at Exchange 2010 SP3 settings. 
    In short, updaing the schema fails.
    2. Prepare Active Directory
    Navigated an elevated command prompt to the folder with Exchange 2013 CU3.
    setup /PrepareAD [/OrganizationName:<organization name>]
    This command fails with: Earlier versions of server roles that were installed were detected.
    schema update version 56
    I began reviewing the long, long list of the following containers and objects under
     CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
    which are required for Exchange 2013:
    missing cn=Auth Configuration
    missing CN=ExchangeAssistance
    missing CN=Monitoring Settings
    missing CN=Monitoring Settings
    missing CN=Monitoring Settings
    missing CN=Workload Management Settings
    Checked Management role groups within the Microsoft Exchange Security Groups OU
    missing Compliance Management group  --- Manually created this entry
    Step 3 Prepare Domain:
    Navigated an elevated command prompt to the folder with Exchange 2013 CU3.
    Ran setup /PrepareDomain
    This command fails with: Earlier versions of server roles that were installed were detected.
    confirmed the following:
    ObjectVersion property fails as it is still set to Echange 2010 sp3 -  13040
    You have a new global group in the Microsoft Exchange System Objects container called Exchange Install Domain Servers-DONE
    The Exchange Install Domain Servers group is a member of the Exchange Servers USG in the root domain.-DONE
    On each domain controller in a domain in which you will install Exchange 2013, the Exchange Servers USG has permissions 
    on the Domain Controller Security Policy\Local Policies\User Rights Assignment\Manage Auditing and Security Log policy.-DONE
    Thanks.

    Whenever I try to prep for a 2013 exchange install I always get:
    "earlier versions of the server roles that are installed were detected"
    Hi,
    That tells us that you are trying to run the prep on your combined DC and Exchange 2010 Server - That will not work. Run it on the Server where you plan to install Exchange 2013.
    It is not mandatory to run this before the actuall Exchange install - It will run automatically for you, if it hasn't been done already and if you are logged on with an account with the proper permissions.
    Martina Miskovic

  • Exchange 2013 user cann't access exchange 2013 public folder

    Hi, during the coexistence exchange 2007 and exchange 2013, outlook is unable to access public folder of exchange 2007 from exchange 2013, I've install CU2 for exchange 2013 and also set authentication to Ntlm, but also failed. please help to look into this
    problem, thanks.
    belows are information about outlook anywhere in our exchange.
    exchange 2007:(primary site)shmail04,shmail05,shmail06; (DR site)drpmail05,drpmail06
    exchange 2013:(primary site)shcas01,shcas02; (DR site)wxcas01
    Identity                           : SHCAS01\Rpc (Default Web Site)
    InternalHostname                   : infor.tdw.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : True
    ExternalHostname                   : infor.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHCAS02\Rpc (Default Web Site)
    InternalHostname                   : infor.tdw.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : True
    ExternalHostname                   : infor.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : WXCAS01\Rpc (Default Web Site)
    InternalHostname                   : infor.tdw.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : True
    ExternalHostname                   : infor.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHMAIL04\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHMAIL05\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : SHMAIL06\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : DRPMAIL05\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}
    Identity                           : DRPMAIL06\Rpc (Default Web Site)
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    ExternalHostname                   : legacy.tdw.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    IISAuthenticationMethods           : {Ntlm}

    Hi,
    I have found an article said that we need to set the external host name the same. See more details in the following link:
    http://blogs.technet.com/b/mspfe/archive/2013/10/21/upgrading-to-on-premises-exchange-server-2013.aspx
    To allow your Exchange 2013 Client Access server to redirect connections to your Exchange 2007 servers, you must enable and configure
    Outlook Anywhere on all of the Exchange 2007 servers in your organization. If some Exchange 2007 servers in your organization are already configured to use Outlook Anywhere, their configuration must also be updated to support Exchange 2013.
    The following configuration is set on each Exchange 2007 server:
    The Outlook Anywhere external URL is set to the external hostname of the Exchange 2013 server.
    Sent By
    Silver

  • MS Exchange 2010 Sp3 Ent Migration to Exchange 2013

    Hello,
    We currently have 2 Exchange 2010 SP3 servers in 1 DAG. Both servers host CAS, Mailbox and Hub Role.
    I want to introduce a 3<sup>rd</sup> Exchange 2013 Server and slowly move users onto a new DAG I build in Exchange 2013.
    Can I create a 3<sup>rd</sup> Exchange 2013 Server with CAS and Mailbox Server Role and make the 3<sup>rd</sup> Exchange server (2013) a member of the existing (2010) CAS array then slowly perform local move requests for users mailboxes
    from my Exchange 2010 DAG to the Exchange 2013 DAG without any disruption to my outlook, OWA and AS clients?
    Exchange 2010 (Windows 2008 R2)
    Exchange 2013 (Windows 2012 R2 DataCenter)

    Hi,
    In Exchange 2013, all Outlook connectivity (Internal and External) takes place over Outlook Anywhere(RPC/HTTP). Thus, CAS array which is used internal for RPC/TCP protocol (MAPI) no longer exists in Exchange 2013.
    For your coexistence environment and the plan to migrate all mailboxes to Exchange 2013 in the future,
     we need to set all virtual directories for CAS 2013 and enable Outlook Anywhere for Exchange 2010. If the mailbox is moved to Exchange 2013, the Outlook client would connect to the server which is set in Outlook Anywhere External host name
    and Internal host name instead of CAS array. If all configurations are proper, CAS 2013 would also proxy the service requests for Exchange 2010 users.
    Here are some reference about Client Connectivity in an Exchange 2013 Coexistence Environment:
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Exchange 2013 Client Access Server Role
    http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
    Exchange Server 2013 Client Access Server High Availability
    http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
    Exchange 2010/2007 to 2013 Migration and Co-existence Guide
    http://msexchangeguru.com/2013/05/10/exchange2013-migration/
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please
    make sure that you completely understand the risk before retrieving any suggestions from the above link.
    Regards,
    Winnie Liang
    TechNet Community Support

Maybe you are looking for

  • How to Connect to TCP Server in AIR?

    I have a TCP server that apparently is working and is listening for incoming connections: package     import flash.display.Sprite;     import flash.events.EventDispatcher;     import flash.events.Event;     import flash.events.*;     import flash.eve

  • IPhoto app and library install - which first???

    I had to replace my MacBook. I just picked up a MacBook Air. I was able to install the iPhoto app from the app store. I have not yet run iPhoto. I am in the process of restoring my iPhoto library from CrashPlan (I know - should have a local back up -

  • File to R3: Unable to test mapping

    Hi, I am working on File to R/3 scenario. I plan to use File adapter and IDoc adapter. And I did my message mapping from file fields to "Cremas..01". To my knowledge, I mapped all the required fields. But when I test my mapping by entering the input

  • IPad doesn't sync all photos + earlier iPhoto versions work with iPad

    1. I have my iPad set to sync with iPhoto, but the iPad doesn't have all of the photos that are in iPhoto. I get a message that it can't sync IMG_0026.JPG so I wonder if when that photo is reached the sync just stops. Could this be the reason? 2. Als

  • T530 Replacing DVD with HDD drive

    Hello, Lenovo community! I decided to upgrade my new T530 with SSD OCZ Vertex4 drive. Put it instead of preinstalled 1TB WD hdd drive. Remove DVD and put 1TB WD via ESPADA SS12: http://www.nix.ru/autocatalog/notebook_accessory/Espada_SS12_SATA_HDD_SA