Outlook 2010 behaves strange with exchange 2013

Hello,
I imported a san certificate with a domain name for local use. This is exchange.xxxx.xx . This is also a A-record pointing to the same ip of the actual server.
The name of the exchange server itself is mail01.xxxx.xx .
My laptop is not a part of the domain. When i want to add my mailbox i use exchange.xxxx.xx for the server. My username can't be resolved. When i use the name of the server mail01.xxxx.xx then it works.
I tested this with outlook 2013 and exchange.xxxx.xx could resolve my mailbox.
So for outlook 2010 i need to use the name of the server where exchange 2013 is installed.
For outlook 2013 i can use the alias exchange.xxxx.xx.
Anyone has any idea ? It's not blocking. We haven't started the migration yet :p

Hi,
Based on my knowledge, in Exchange 2013 environment, the server name option is filled with the new type"mailbox GUID+@+ the domain portion of the user's primary SMTP address" when we configure the Exchange account in Outlook client.
In your case, I recommned you add the following record in the host file of the computer which installs the Outlook 2010: the host name Exchange.domain.com points to your server IP address .
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support
Thx for your feedback. I will check this out.

Similar Messages

  • Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

    Hi all ,
    on my side i would like to clarify few queries.
    Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
    Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
    the autodiscover service to exchange 2013 during coexistence.
    When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
    reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
    Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
    I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
    Internal Outlook Connectivity
    For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
    For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
    Please share me your suggestions and that would help me a lot .
    Regards
    S.Nithyanandham

    Hi Winnie Liang ,
    Thanks a lot for your reply.
    Scenario  1 : for internal outlook connectivity 
    We have below settings for exchange 2010 autodiscover.
    mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
    We are going to have below settings for exchange 2013 autodiscover.
    mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
    During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
    So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
    Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
    servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
    get it updated on user profile.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
    Scenario 2: For exchange services
    mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
    mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
    What about the above services will it get affected during whole exchange 2013 environment failure ?
    Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • Outlook can't connect with Exchange 2013 after migration from Exchange 2007

    <style type="text/css">P { margin-bottom: 0.21cm; }</style>
    Hello,
    recently we've done a Exchange 2007 sp3 to 2013 sp1. Users can conect perfectly with OWA and with his iphone clients.
    But the problem is they can't connect from his Outlook clients (2010, 2013), both internaly and externaly. Always fails with the message: The Connection to Exchange it is not avaliable.... Can't resolve the name of Exchange server.
    To try to resolve it we've done:
    - Check Outlook anywhere configuration en EAC: it is configure with and external url mail.company.com and internal server.domain.local. The security is the default Negociation, but we've tried all.
    - Check the internal dns, there are records for mail.company.com and exchangeserverdomain.local pointing to the exchange local ip. Also there is a public zone company.com with the record mail.caompany.com pointing to the exchange local ip. Also we've made
    records autodiscover.company.com and autodiscover.domain.local pointing to the exchange local ip.
    - In the public dns from our domain there is the record A and MX pointing our public ip. There aren't any record Autodiscover but we think that the manial conection should work.
    Check certificates: we've made a new self-signed certificate including all this internal and external domains and for all services.
    - Check Outlook Anywhere block: we've cheked.
    Currently server state:
    - Old Exchange 07 server can't start, it was in very bad state and we achieved migrate the mailbox to the new server, after that we tried to uninstall, but it crashes with a public folder replication error. We got uninstall all the roles
    unless the mailbox. After a restart it can't start.
    -The new Exchange 2013 looks great, there isn't any trail of the old server, or we haven't seen anything in the EAC or shell.
    I paste below the result of Microsoft Remote conectivity analaizer, with Outlook anywhere test. It is clear that there is a problem with that.
    Sorry because the test is in spanish and I translated it with google, from here I only can access the tool in spanish.
    We continue to try to resolve the problem.
    Thanks to all in advance!
    Testing RPC / HTTP connectivity.
    Error in testing RPC / HTTP.
    additional Details
    Elapsed time: 24295 ms.
    Test steps
    Connectivity Analyzer Microsoft is trying to test Autodiscover for [email protected] .
    Error in automatic detection test .
    additional Details
    Elapsed time: 24294 ms.
    Test steps
    Attempting each method of contacting the Autodiscover service .
    Failed to properly contact the Autodiscover service using all methods.
    additional Details
    Elapsed time: 24294 ms.
    Test steps
    Trying to prove possible Autodiscover URL https://empresa.com/AutoDiscover/AutoDiscover.xml
    Error in testing this potential Autodiscover URL .
    additional Details
    Elapsed time: 1509 ms.
    Test steps
    Attempting to resolve the host name in DNS empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 80.36.252.194
    Elapsed time: 507 ms.
    Testing TCP port 443 on the host to ensure empresa.com listening or is open.
    The port was opened successfully.
    additional Details
    Elapsed time: 464 ms.
    Testing the SSL certificate to make sure it is valid.
    The SSL certificate is not exceeded one or more certificate validation checks .
    additional Details
    Elapsed time: 537 ms.
    Test steps
    Connectivity Analyzer Microsoft is attempting to obtain the SSL certificate from remote server on port 443 empresa.com .
    Connectivity Analyzer Microsoft successfully obtained the remote SSL certificate.
    additional Details
    Remote Certificate Subject : CN = mail.empresa.com , issuer : CN = mail.empresa.com .
    Elapsed time: 454 ms.
    Validating the certificate name .
    The certificate name was validated successfully .
    additional Details
    Hostname empresa.com was found at the entrance of the alternative subject name of the certificate.
    Elapsed time: 1 ms.
    Is validating the trusted certificate .
    Validation Error trusted certificate.
    Test steps
    Connectivity Analyzer Microsoft is trying to build certificate chains for certificate CN = ​​mail.empresa.com .
    Could not build a certificate chain for the certificate.
    Tell me more about this issue and how to resolve
    additional Details
    The certificate chain did not end in a trusted root . Root = CN = mail.empresa.com
    Elapsed time: 31 ms.
    Trying to prove possible Autodiscover URL https://autodiscover.empresa.com/AutoDiscover/AutoDiscover.xml
    Error in testing this potential Autodiscover URL .
    additional Details
    Elapsed time: 21723 ms.
    Test steps
    Attempting to resolve the host name in DNS autodiscover.empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 46.16.56.40
    Elapsed time: 498 ms.
    Testing TCP port 443 on the host to ensure autodiscover.empresa.com listening or is open.
    The specified port is blocked , not listening or does not generate the expected response .
    Tell me more about this issue and how to resolve
    additional Details
    Network Error communicating with the remote host.
    Elapsed time: 21224 ms.
    Attempting to contact the Autodiscover service with the HTTP redirect method .
    Error when trying to contact the Autodiscover HTTP redirect method .
    additional Details
    Elapsed time: 606 ms.
    Test steps
    Attempting to resolve the host name in DNS autodiscover.empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 46.16.56.40
    Elapsed time: 14 ms .
    Testing TCP port 80 on the host to ensure autodiscover.empresa.com listening or is open.
    The port was opened successfully.
    additional Details
    Elapsed time: 202 ms.
    Connectivity Analyzer Microsoft is checking the automatic detection of host empresa.com for an HTTP redirect to the Autodiscover service.
    Connectivity Analyzer Microsoft could not get a HTTP redirect response for Autodiscover .
    additional Details
    Web exception occurred because an HTTP 404 response was received - Unknown NotFound . Headers received: Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27:58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 +
    lenny3 with Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3 HTTP Response Headers : Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27: 58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 + lenny3 with
    Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3
    Elapsed time: 388 ms.
    Attempting to contact the Autodiscover service using the method of DNS SRV redirect server.
    Connectivity Analyzer Microsoft could not contact the Autodiscover service using the DNS SRV redirect method .
    additional Details
    Elapsed time: 186 ms.
    Test steps
    Trying to find the SRV record in DNS _autodiscover._tcp.empresa.com .
    Not the Autodiscover SRV record in DNS found .
    Tell me more about this issue and how to resolve
    additional Details
    Elapsed time: 186 ms.
    Checking for a CNAME record for Autodiscover in DNS for your domain " empresa.com " to Office 365.
    Could not validate the Autodiscover CNAME record in DNS. If your mailbox is not in Office 365 , you can ignore this warning.
    Tell me more about this issue and how to resolve
    additional Details
    No Autodiscover CNAME record for your domain ' empresa.com ' .
    Elapsed time: 268 ms.
    jspt

    Hello,
    We have the Self-signed certificate that comes with Exchange, and we've created a new self-signed including all our domains mail.company.com, domain.local, exchange13.domain.local, autodiscover.company.com, autodiscover.domain.local.
    below I print you the result os the comand Get-ClientAccesServer | fl . Now we've configured a SPC objetct folow the instructions of Wizard
    Exchange Server Deployment from Microsoft. We've executed the commands in our new Exchange 13, but can't did it in the old Exchange:
    $AutodiscoverHostName = "autodiscover.contoso.com"Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 8*") -And ($_.ServerRole -Like "*ClientAccess*")} | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://$AutodiscoverHostName/Autodiscover/Autodiscover.xmlThis is the result of
    RunspaceId                           : 89c86f8e-d156-4480-b31d-59215976879b
    Name                                 : EXCHANGE13
    Fqdn                                 : EXCHANGE13.domain.local
    ClientAccessArray                    :
    OutlookAnywhereEnabled               : True
    AutoDiscoverServiceCN                : EXCHANGE13
    AutoDiscoverServiceClassName         : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri       : https://autodiscover.company.com/Autodiscover/Autodiscover.xml
    AutoDiscoverServiceGuid              : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope                : {Nombre-predeterminado-primer-sitio}
    AlternateServiceAccountConfiguration :
    IsOutOfService                       : False
    WorkloadManagementPolicy             : DefaultWorkloadManagementPolicy_15.0.825.0
    Identity                             : EXCHANGE13
    IsValid                              : True
    ExchangeVersion                      : 0.1 (8.0.535.0)
    DistinguishedName                    : CN=EXCHANGE13,CN=Servers,CN=Exchange Administrative Group
                                           (FYDIBOHF23SPDLT),CN=Administrative
    Groups,CN=First Organization,CN=Microsoft
                                           Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
    Guid                                 : e83055fe-217b-4ed6-9cd0-7711097baf99
    ObjectCategory                       : domain.local/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                          : {top, server, msExchExchangeServer}
    WhenChanged                          : 09/03/2014 12:46:07
    WhenCreated                          : 08/03/2014 19:15:54
    WhenChangedUTC                       : 09/03/2014 11:46:07
    WhenCreatedUTC                       : 08/03/2014 18:15:54
    OrganizationId                       :
    OriginatingServer                    : severdc.domain.local
    ObjectState                          : Unchanged
    I hope this stuff can help you.
    Thanks!!
    jspt

  • Redirect emails in OWA and Outlook 2010 not working in Exchange 2013

    I have an new install of Exchange 2013 with all updates.
    When I setup an inbox rule to redirect messages to another contact it is not working.
    When I used Outlook 2010 and ran the rule manually I received this error:
    "the redirect action is not currently supported with run rules now"
    It seems that I didn't setup up something correctly in Exchange 2013 or a feature is not turned on. Please assist.
    In the EM console when I setup forwarding that is working. Its the inbox rule redirect not working.

    Hi,
    From your description, I recommend you use the following cmdlet to ensure that the DeliverToMailboxAndForward parameter is set to $True.
    Get-Mailbox <identity> | fl DeliverToMailboxandForward
    If this parameter is false, you can use the Set-Mailbox cmdlet to set it and check the result.
    Hope this can be helpful to you.
    Best 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]
    Amy Wang
    TechNet Community Support

  • Outlook save/update error with Exchange 2013 public folder used as Contact Items

    Hello Everybody.
    This problem is driving me crazy.
    In Exchange 2013 i have created a public folder with several subfolders used as Contact Items.
    I've reviewed all settings several times and all is ok.
    Outlook 2010/2013 users several times receive the message:
    "The item cannot be saved to this folder. The folder was deleted or moved, or you do not have permission. Do you want to save a copy of it in the default folder for the item?"
    when try save an existing contact after modification.
    I can assure you that user permissions, server configurations are ok; please, help me.

    Did you make the subfolder the correct type, i.e., a contacts-type folder?
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2010 CAS array with Exchange 2013 Mailbox Servers

    Here is our current scenario,
    Exchange 2007
    2 - Hub Transport Servers
    2 - CAS servers (cluster NLB)
    2 - Mailbox servers (clustered)
    Exchange 2010
    2 - Huib Transport Servers
    3 - CAS servers (array NLB)
    2 - Mailbox servers (1 DAG)
    We have not migrated any users to the Exchange 2010 environment yet. We're thinking that at this point we would rather go from 2007 to 2013. Does the 2013 mailbox server work with a 2010 CAS array?

    Hi,
    As far as I know, CAS array doesn' t exist in Exchange 2013. And OWA and other requests can be proxyed and redirected from Exchange 2013 to Exchange 2010.
    For more information, you can refer to the following article:
    http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
    Thanks,
    Angela Shi
    TechNet Community Support

  • Outlook 2010 gets disconnected with Exchange 2010

    Hi
    We are facing a strange issue that some Outlook users are getting disconnected and it reconnects after 1 or 2 hours or after changing the IP of the system. During the Outlook disconnection period we can't even telnet on port 433 to the CAS BLB name or IP
    (same time we can able to ping CAS name). The security and network team is checking the same, is there any thing to be checked with Exchange servers regarding this issue?
    Thanks in Advance
    LMS

    Also I found a similar article "http://social.technet.microsoft.com/Forums/exchange/en-US/06f4d721-a778-4437-b43a-9ad6ca70344b/outlook-clients-randomly-disconnected-from-cas-array?forum=exchange2010"
    which almost explains the same issue - users are getting disconnected and even unable to telnet teh cluster IP and getting connected after a few minutes.
    So we will go ahead and re configure the NLB. We plan to keep the existing NLB on one server and remove and add second node and do the same for the other. What do you think?
    LMS

  • External emails not received after shutdown of Exchange 2010 in coexistence with Exchange 2013

    I have exchange 2013 and exchange 2010 in coexistence mode. All mailboxes have been moved to Exchange 2013 and firewall/spamfilters already pointed to Exchange 2013 CAS server. I can receive/send from and to external addresses, however when I shutted down
    the Exchange 2010 all incoming external mails were not received. What could be the cause?

    Start by re-checking how the device that takes the traffic from the external MX IP to internal is configured.
    Sniff the traffic to ensure that it is hitting 2013 directly.
    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.

  • Outlook 2013 can't communicate with Exchange 2013

    we're just finishing migration to Exchange 2013 and found some Outlook 2013 clients (migrated from Exchange 2010) can't communicate with Exchange 2013. even if i recreate the Outlook profile.
    what worked is to reinstall Office 2013.  just want to get ideas why a reinstall fixed the problem.
    same outlook proxy is there in the account settings.

    Hi,
    What was the symptom that Outlook couldn't communicate with Exchange 2013? Could you please detail this a bit?
    If the Account Settings are completely same before and after the reinstallation, we can say the cause is not on the Exchange side. While I can't guarantee the root cause based
    on the provided information. A reinstallation fixes the corrupted or missing components/files in Office, but it's hard to say what has been fixed during the reinstallation.
    If you still have some Office 2013 clients that have not been reinstalled, try to run Microsoft Office Configuration Analyzer Tool to quickly identify problematic configurations in Outlook:
    https://www.microsoft.com/en-us/download/details.aspx?id=36852
    Regards,
    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.

  • Can we connect Outlook with Exchange 2013 with the default Self-signed certificate?

    Hi,
    the question is very simple, but after several days searching in this forums and in the web I have not been able to find a definitive answer YES or NOT. I know that Self-signed certificates are not for a production enviroment and only for labs and we must
    purchase a third party certificate or get one from a internal CA.
    Anyone can answer this question with no doubt?
    Thanks in advance!
    jspt

    Hi Abhi,
    I wrote this question because in a recent migration to 2013 from 2007 we've found with this problem: you can view it in the post http://social.technet.microsoft.com/Forums/exchange/en-US/1ddd1e81-1061-4461-95dd-13de653ef8fe/outlook-cant-connect-with-exchange-2013-after-migration-from-exchange-2007?forum=exchangesvrdeploy.
    Also I have installed a new exchange 2013 in a lab enviroment and I also have unabled to connect from a Outlook 2013. The problem is the same Outlook is unable to detect the exchange server. Many people in this forums told me that have to be a certificate
    problem and for that I posted this question. Honestly, I don't know how to do for Outlook can be connect with Exchange 2013. I don't know what I'm doing wrong.
    Anyway thanks for your answer.
    jspt

  • Exchange 2010 coexist with exchange 2013

    Hi All ,
    Planning to have a coexistence scenario in my environment which is mentioned below
    Exchange 2010 - ambiguous url in place - OA enabled 
    For mapi/rpc traffic - mail.domain.in -  exchange 2010
    For https traffic - mail.domain.in - exchange 2010
    mail.domain.in will get resolved in to cas array in exchange 2010 .
    After coexistence On our side we are not going to move the mail.domain.in namespace to exchange 2013 , Instead of that we are going to use a new namespace in exchange 2013 for internal outlook anywhere and it will be outlookmail.domain.in and for the remaining
    exchange 2013 services like pop,imap,owa,active sync url's,external OA will be having mail.domain.in as same as exchange 2010 namespace.
    just consider outlookmail.domain.in is available on the san certificate installed in exchange 2013.
    Note : 
    On my ide I would assume Internal outlook 2010 mapi users will connect directly to exchange 2010 servers on the namespace mail.domain.in
    Likewise i would assume Internal outlook anywhere 2013 users will connect directly to exchange 2013 servers on the namespace outlookmail.domain.in
    Services like pop,imap,owa,active sync ,external OA connections for both exchange 2010 and exchange 2013 from the external world will be routed from firewall to exchange 2013 servers .Then https traffic for exchange 2010 mailbox users will be proxied to 2010
    exchange server via exchange 2013 server.
    question : I would like to know above mentioned scenario is possible or not ?
    On my side I know in my environment i am having ambiguous url's in place and at the same time i don't want the exchange 2010 internal outlook users to connect via exchange 2013 rpc over http even though OA is enabled on exchange 2010.
    So simply i can say i need my internal exchange 2010 mailbox users has to connect via tcp/ip.
    All of you tell me your valuable suggestions.
    Regards
    S.Nithyanandham

    Hi,
    Going Straight to the point... and answering your question...
    The scenario above IS possible For a while... But going ahead in the migration process, You'd face problems once the Exch2013 doesn't know how to handle MAPI connections:
    As per Exchange Team...
    In this scenario where both the MAPI/RPC and HTTP workloads are using the same FQDN you cannot successfully move the FQDN to CAS 2013 without
    breaking your MAPI/RPC client connectivity entirely. I repeat, your MAPI/RPC clients will start failing to connect via MAPI/RPC once
    their DNS cache expires after the shared FQDN is moved to CAS 2013.
    As their recommendation, and I would tell you too by experience, the best option is to really use different internal and external URLs for the clients to connect to.
    change your design to use a specific internal-only FQDN for MAPI/RPC clients. If you are in the middle of a 2010 deployment using an Ambiguous
    URL I recommend you change your ClientAccessArray FQDN to a unique name and update the mailbox database RpcClientAccessServer values
    on all Exchange 2010 mailbox databases accordingly. Fixing this item mid-migration to Exchange 2010 or even in your fully migrated environment will ensure any newly created or manually repaired Outlook profiles are protected, but it will not automatically
    fix existing Outlook clients with the old value in the server field. 
    So the overall for this first point is to enable the OA for all internal users, so as to ease the migration process in the future, even if for the time being its not necessary.
    Also another point you should take into consideration is the version of yours OLK versions, as the minimum supported are as per below:
    Outlook 2007: 12.0.6665.5000 (SP3 + the November 2012 Public Update or any later PU)
    Outlook 2010: 14.0.6126.5000 (SP1 + the November 2012 Public Update or any later PU)
    Outlook 2013: 15.0.4420.1017 (RTM or later)
    I don't know the size of you network, but it might be necessary for you to use an inventory tool in order to identify that.
    As advised, its really worthy to have a look at the following article, thus to clarify your view about this issue.
    Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations
    From <http://blogs.technet.com/b/exchange/archive/2013/07/17/3574451.aspx> 
    Hope it can help you!
    Cheers,
    Think before you ask, give detail as much as possible, then ask and you will get help! Always have in mind, people do not guess! :)

  • Outlook 2013 connection issue with exchange 2013

    my exchange 2013 was upgrade from exchange 2010. after the upgrade (migration), i using outlook 2013 connect to exchange 2013. some very
    weird issues happened.
    when i using auto discovery to create profile and connect to exchange will success. but when i manually create the profilewill failed. the following pic for your reference. (same account, same PC)
    please help, thanks lots!!!!

    This is what changed in Exchange 2013. It uses RPC or HTTPs (Outlook Anywhere) and uses Server GUID to connect...
    "As a result of these architectural changes, there have been some changes to client connectivity. First, RPC is no longer a supported direct access protocol. This means that all Outlook connectivity must take place using RPC over HTTP (also known as
    Outlook Anywhere). At first glance, this may seem like a limitation, but it actually has some added benefits. The most obvious benefit is that there is no need to have the RPC client access service on the Client Access server. This results in the reduction
    of two namespaces that would normally be required for a site-resilient solution. In addition, there is no longer any requirement to provide affinity for the RPC client access service.
    Second, Outlook clients no longer connect to a server FQDN as they have done in all previous versions of Exchange. Outlook uses Autodiscover to create a new connection point comprised of mailbox GUID, @ symbol, and the domain portion of the user’s primary
    SMTP address. This simple change results in a near elimination of the unwelcome message of “Your administrator has made a change to your mailbox. Please restart.” Only Outlook 2007 and higher versions are supported with Exchange 2013."
    From : What's New in Exchange 2013-
    http://technet.microsoft.com/library/jj150540%28EXCHG.150%29.aspx#BKMK_arch
    Blog |
    Get Your Exchange Powershell Tip of the Day from here

  • Outlook 2013 with Exchange 2013 keeps giving read receipts

    Hello experts,
    We have an Exchange 2013 server. All users are joint to the domain, except one user (Windows 8.1) which is in a Workgroup, and using Outlook 2013 with IMAP protocol. 
    This particular user is having a problem. When he send's any email from Outlook and requests a read receipt, after that he keeps getting hundreds of read receipts in his inbox. I have tried disabling (for temporarily) the Windows server 2012 firewall,  but
    still having the same issue. 
    Is this a known bug in Outlook 2013 with Exchange 2013? Any help troubleshooting this?

    Hi,
    According to your description, I understand that IMPA account get hundreds of read receipts while he requests a read receipt.
    If I misunderstand you concern, please do not hesitate to let me know.
    Whether are all account or some special user experience this question? Please do a test in external with IMAP account to double confirm.
    How about the “Request a Delivery Receipt”?
    Also, please run message tracking log to get more details about message mail flow:
    Get-MessageTrackingLog –Server “mailbox server” –Sender “[email protected]” –Recipient “[email protected]” –MessageSubject “Read: message subject” | Select Timestamp, ClientHostname,ServerHostname,Source,EventID,Recipients,RecipientStatus,Sender | ConvertTo-Html > “C:\Test\Test.xml”
    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 2010 install with Exchange 2013 present

    Good day,
    I have an Exchange 2010 SP3 instance, I then added a Exchange 2013 installation, the 2010 Exchange needs to be rebuilt due to space issues on the current host and moving the 2010 Exchange will require too much downtime.
    The issues that I am running into is when installing the new instance of 2010 on the new host with the Exchange 2010 x64 SP1 ISO, I am met with the following error:
    [08/22/2014 07:09:03.0912] [1] 0.  ErrorRecord: The object is read-only because it was created in a version of Exchange later than Exchange 0.20 (15.0.0.0). Current supported version is 0.10 (14.0.100.0).
    [08/22/2014 07:09:03.0912] [1] 0.  ErrorRecord: Microsoft.Exchange.Data.InvalidObjectOperationException: The object is read-only because it was created in a version of Exchange later than Exchange 0.20 (15.0.0.0). Current supported version is 0.10 (14.0.100.0).
    After some reading I understand that Exchange 2010 must include SP3 to co-exist with Exchange 2013, all the roles have installed without any issues except the client access role, I get the above mentioned error, thus I cant upgrade to SP3.
    I came across a solution where the OAB needs to be removed and then re-created, but unfortunately this will cause too much issues as the OAB is always in use.
    So I am stranded where I need 2010 SP3 to install the server, but as far as I know there is no 2010 ISO with SP3 available.
    Any advice would be appreciated.
    Regards,
    Hendrik

    "So I am stranded where I need 2010 SP3 to install the server, but as far as I know there is no 2010 ISO with SP3 available."
    I'm not sure I understand this? If you download Exchange 2010...
    http://www.microsoft.com/en-us/download/details.aspx?id=36768
    That *is* the SP3 version.
    Otherwise, if you install Exchange 2013 (with no other Exchange 2010 servers present), you definitely cannot add 2010 servers after the fact.
    http://forums.petri.com/showthread.php?t=64056
    But if you started with 2010, then add 2013... I think you can add or replace 2010 servers provided they are at SP3.
    What if you had lots of Exchange servers (a hosting company for example) and had to replace a server member of a DAG? Let's assume some mailboxes have been migrated to DAGs on E2K13 and some are still on E2K10.
    Note: within a particular DAG you cannot have differents versions of Exchange but you could have some DAGs with E2K10 and others using E2K13.
    It would seem that you would have to be able to install a new/replacement E2K10 server in this case? You could not replace it with a E2K13 server.
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Exchange 2010 OWA usage in Exchange 2013

    Hi,
    I have Exchange 2010 with Sp3 Currently running in environment, Now we have plan to Migrate it to Exchange 2013.... Total number of mailbox is around 26000.
    Before Migration we want below things to keep in mind...
    1. We want to Use existing exchange 2010 OWA url ( mail.abc.com ), How to accompolish this as it will take couple of months to migrate all mailbox ?
    2. Can i use my Existing Exchange certificate to get the above goal done ?
    3. What will be the steps and pre-requsite to achieve the Goal ?
    An Early reply would be appreciated !! 
    Amit

    Hi Amit 
    First Change SCP of Exchange 2010 CAS VIP to Exchange 2013 CAS VIP.
    Configure external  DNS records accordingly.DNS entries should be pointed to Exchange 2013 CAS from Exchange 2010 CAS.
    Ensure that you are having a seperate name for CAS array from external ews url
    Outlook Anywhere should be enabled and Url should be external URL which points to Exchange 2013.
    Authentication for OUtlook Anywhere should be - NTLM
    for OWA exchange 2010 - FBA and windows 
    Point your new CAS server to the firewall or TMG . Now from exchange 2013 all request will be proxied to 2010 users 
    You cannot use the same certificate . YOu need to add seperate entries as the host name for new servers will vary
    Apply a new certificate with all the required site names included in Exchange 2013 CAS.
    Whats more you can refer my blog as well 
    http://exchangequery.com/2014/05/02/things-to-consider-before-configuring-autodiscover-in-exchange-20102013-coexistence-scenarios/
    Cheers :)
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

Maybe you are looking for