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

Similar Messages

TLS connection failure with Exchange 2013 (SEC_E_WRONG_PRINCIPAL)

Hi all -
I have Lync 2013 with a single front-end server and am trying to properly integrate with a single Exchange 2013 SP1 server. The Exchange server has certificate signed by GeoTrust, assigned to all roles - IIS, SMTP, POP, IMAP, UM, and UMcallrouter. I'm
seeing the below in my FE logs and am unsure as to why Lync is using the .local address when I have been specifying external FQDNs for the mail server in Lync.
TLS outgoing connection failures.
Over the past 1 minutes, Lync Server has experienced TLS outgoing connection failures 1 time(s). The error code of the last failure is 0x80090322(SEC_E_WRONG_PRINCIPAL) while trying to connect to the server "MAIL.xxxx.local" at address [172.16.3.14:5061],
and the display name in the peer certificate is "Unavailable".
Cause: Most often a problem with the peer certificate or perhaps the host name (DNS) record used to reach the peer server. Target principal name is incorrect means that the peer certificate does not contain the name that the local server used to connect. Certificate
root not trusted error means that the peer certificate was issued by a remote CA that is not trusted by the local machine.
Resolution:
Check that the address and port matches the FQDN used to connect, and that the peer certificate contains this FQDN somewhere in its subject or SAN fields. If the FQDN refers to a DNS load balanced pool then check that all addresses returned by DNS refer to
a server in the same pool. For untrusted root errors, ensure that the remote CA certificate chain is installed locally. If you have already installed the remote CA certificate chain, then try rebooting the local machine.
Any advice/pointers you can give are greatly appreciated.

When integrate Lync and Exchange UM, you need to generate new certificate. The certificate should contain the server’s FQDN.
Lisa Zheng
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."

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.

Search issues with Exchange 2013

The search service no longer works. I have tried with stopping the Exchange Search Service and deleting the folder associated with the databases to no avail.<o:p></o:p>
When I run Get-MailboxDatabaseCopyStatus -Server "NAMEofServer" | Format-Table Name,Status,ContentIndex* -Auto through PS I receive
the below output.<o:p></o:p>
"Database" Mounted Unknown Could not find registry value of Index Status for database {a8281541-35b3-4e9b-b124-4adfa7ebf2d1}.
<o:p></o:p>
I then look to the registry location below to find absolutely nothing in there! No keys, no reference, nothing!<o:p></o:p>
\HLM\Software\Microsoft\ExchangeServer\v15\Search\IndexStatus\<o:p></o:p>
I cannot seem to resolve the search / indexing issues at all. The server is NOT a part of a DAG and issues extend to all 4 databases.<o:p></o:p>
I also am having issues that might be related when trying to move mailboxes to a different databases (same server). "I did try restarting the
replication service"<o:p></o:p>
The RPC call failed with result 'StorageTransientError'<o:p></o:p>
Any help in the right direction would be appreciated. I have had this issues since CU6.<o:p></o:p>
Thank you!<o:p></o:p>

Hi,
Well, we can try to recreate those registry entries.
Since your server is not a member of DAG, then the registry key should be like this:
{79853a57-6c9e-46a2-a5e3-70db036754f1} : 1,1,4294967297,2013-07-16 00:33:17Z,0,
The initial {GUID} is the GUID of the database.
The double numeric values (1,1;) signify the state[s] of the CI
The first number in the series is the Index Status. The second number in the series is the error code.
Index Status:
Unknown = 0
Healthy = 1
Crawling =2
Failed = 3
Seeding = 4
Failed And Suspended = 5
Suspended = 6
Disabled = 7
Auto-Suspended = 8
Healthy And Upgrading = 9
Error Code:
1 Success
2 Internal Error
3 Crawling Database
4 DatabaseOffline
5 MapiNetworkError
6 Catalog Corruption
7 Seeding Catalog
8 Catalog Suspended
9 Catalog Reseed
10 Index Not Enabled
11 Catalog Excluded
12 Activation Preference skipped
13 Lag Copy skipped
14 Recovery Database Skipped
15 Fast Error
16 Service Not Running
17 Index Timestamp too Old
Note: Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number
to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry
Refer from this blog:
http://blogs.technet.com/b/johnbai/archive/2013/07/16/exchange-2013-high-availability-fast-search-and-the-windows-registry.aspx
Please also check if there are any event logs indicated this issue, that will help us to troubleshoot.
Thanks.

Outlook 2011 Connection Issue with Proxy Server after 10.8 Upgrade

Hello,
After upgrading my MBA to 10.8, my MS Outlook (Outlook Mac 2011) mail connection does not work for an exchange based mail account where a VPN/proxy server combination is involved. This was not an issue at all under 10.7. What's interesting is that it's not an issue with MS Outlook 2010 on my Parallels VM either under 10.8. There are no internet connectivity issues, I am able to connect to the internet using Safari and other browsers. Any help would be appreciated.
Thanks,
Manish

I was having a similar problem using Outlook 2011 running under Mountain Lion (10.8.2) on an MacBook Pro. When at work, behind our proxy server, I could not get Outlook to connect to a client's public Exchange server, but this worked fine without changing any settings when I was connected to our DMZ network or at home (no proxy server in these cases). My MacBook was configured to use "Auto Proxy Configuration", and Safari worked fine in all three locations (as did Apple mail)
Today, the Microsoft Office auto-updater downloaded an update, and since it was installed, the problem has been fixed and I've been able to connect to our client's external Exchange server event when behind our local proxy server (Outlook now reports that the latest installed update is 14.2.5)
Steve

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.

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

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 2013-SP1/Outlook 2013 connectivity issue.

We couldn't make Outlook 2013 (latest updates) to connect to our Exchange 2013-SP1 through the Internet.
Any PC inside the LAN (on the domain or outside the domain) can connect normally.
Any PC outside the LAN (WAN) cannot connect, it keep showing this error:
"The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
OWA is working fine from the WAN, smartphones (Android & Apple) are also working fine from the WAN.
Port 443 is open on the firewall.
So what we are missing!

Hi,
Firstly, I'd like to say, in Exchange 2013 SP1, Outlook 2013 SP1 clients may use MAPI over HTTP to connect to the server.
Before going further, let's confirm if they use MAPI over HTTP: Get-OrganizationConfig | FL MapiHttpEnabled
If the value of the above property is true, I recommend the following troubleshooting:
1. Check if your Exchange 2013 SP1 server is running on Windows Server 2012 R2.
2. Check MAPI virtual directory settings: get-MapiVirtualDirectory |fl
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Outlook 2013 connectivity issue

Hello!
My Outlook 2013 stopped connecting to my Exchange 2013. After googling for a while I found this article:
http://infused.co.nz/2013/05/13/exchange-2013-outlook-anywhere-rpc-settings/
and checked get-outlookprovider status - it was exactly as in this post:
Name Server CertPrincipalName TTL
EXCH 1
EXPR 1
WEB I don't know whether this is the cause of my issue or not but I'd like to know: if Exchange Server has all required certificates installed why CertPrincipalName is empty in the output above?
Thank you in advance,
Michael

Hi Mavis,
Thank you for the reply!
"How about connect to Exchange server via OWA?" - OWA is working.
"About this confusion, the CertPrincipalName parameter specifies the Secure Sockets Layer (SSL) certificate principal name required for connecting to Exchange from an external location.This parameter is only used for Outlook Anywhere clients." -
as far as I know the only difference between external and internal Outlook connections is that external are SSL-enabled
by default and internal are http-based. All Outlook 2013 connections are Outlook Anywhere connections:
http://technet.microsoft.com/en-us/library/bb123741%28v=exchg.150%29.aspx#outlookanywhere
Outlook Anywhere and Exchange 2013
The Windows RPC over HTTP Proxy component, which Outlook Anywhere clients use to connect, wraps remote procedure calls (RPCs) with an HTTP layer. This allows traffic to traverse network firewalls without requiring RPC ports to be opened. In Exchange 2013,
this feature is enabled by default, because all Outlook connectivity takes place over Outlook Anywhere.
And I can require SSL even for internal Outlook connections any time...may be it is this requirement that makes this parameter (CertPrincipalName) show up...
One more thing that I can't understand: when Outlook starts it tries to connect by using HTTP (and when it succeeds I can confirm this by examining its Connection Status:
When Outlook can't connect the following event is registered:
If Outlook is connecting via HTTP what does this error mean?
Regards,
Michael

Outlook Anywhere settings in a Exchange 2013 coexistence scenario with Exchange 2007

I have exchange 2013 and 2007 set up in a coexist environment. At the moment, the few mailboxes I am testing on Exchange 2013 are getting multiple pop ups in outlook and cannot connect to items like Public Folders on 2007. I found an article
that told me to change the authentication method from Negotiate to NTLM and that broke some of my Lync 2013 compatibility issues on users on exchange 2007 (ie conversation history and they got outlook integration errors.) I would like someone to confirm
if the change I am about to make from doing research will help me in my situation.
Current Setup:
Exchange 2007 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: NTLM
IISAuthenticationMethods : {Basic, Ntlm}
Exchange 2013 OA CAS Settings
ExternalClientAuthenticationMethod : Negotiate
InternalClientAuthenticationMethod: Negotiate
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
New Settings I am considering based on research:
Exchange 2007 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: Basic
IISAuthenticationMethods : {NTLM}
Exchange 2013 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: Basic
IISAuthenticationMethods : {Basic}
Will this work and eliminate my popups?

Hi,
The following TechNet article indicates that:
“In order to support access for Outlook Anywhere clients whose mailboxes are on legacy versions of Exchange, you will need to make some changes to your environment which are documented in the steps within the
Exchange Deployment Assistant. Specifically,
you will need to enable Outlook Anywhere on your legacy Client Access servers and enable NTLM in addition to basic authentication for the IIS Authentication Method.”
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
As for the Autodiscover service, please make sure the Autodiscover.domain.com is pointed to your Exchange 2013 in Internal and External DNS. For more detailed information about Exchange 2013 coexistence with Exchange 2007, please refer to:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
Regards,
Winnie Liang
TechNet Community Support

Exchange 2010 ambiguous URL'S issue while coexist with exchange 2013

Hi ,
Please correct me if i am wrong and also all of you tell me your valuable suggestions.
Like as said in the below article we are having an exchange 2010 ambiguous url's in place.
Referred
article :
http://blogs.technet.com/b/exchange/archive/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations.aspx
As said in this article, if we have exchange 2010 ambiguous url's in place we will face issues during exchange 2013 coexistence.I agree with that point .
Question : On such case why don't we use a separate namespace for internal and external outlook anywhere settings in exchange 2013 which is different from cas array name and also there is no need to disturb the existing exchange 2010
environment by changing the rpc client access attribute in exchange 2010 databases or by forcing the exchange 2010 internal outlook clients to connect via OA. Please clarify my doubt and say whether the mentioned scenario is possible or not ?
Note : Same time please consider the new namespace which is going to be utilized on exchange 2013 outlook anywhere settings is available on SAN certificate.
Regards
S.Nithyanandham

Hi ,
Please someone shed light on this case.
Regards
S.Nithyanandham
Thanks & Regards S.Nithyanandham

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

How do i connect manually to Exchange 2013 from Outlook 2007/2010 in another forest?

Hello All,
I have a source organization: Windows 2003 domain + Exchange 2010 SP3 + smtp domain acme.com
Target organization: Winows 2012 R2 domain + Exchange 2013 CU3 + smtp domain acme.com
We are migrating to target organization.
I want to connect Outlook 2007/2010 to their target mailbox (Exchange 2013) from a machine which is joined to Source DOmain.
I couldn't use autodiscover, because as the machine is joined to source domain, autodiscover it's mapping to Exchange 2010.
It only works when I machine is joined to target domain.
Any idea how to connect manually to eXCHANGE 2013 mailbox from a machine which is joined to source domain?
Regards
José Osorio

Hi,
Firstly, I’d like to explain, Autodiscover service can be used cross forest:
1. the two forests must be trusted.
2. configure a mail contact in the original forest.
For more information, please refer to the partition named how to configure the Autodiscover service for cross-forest moves in the following article:
http://technet.microsoft.com/en-us/library/jj591328(v=exchg.141).aspx#BKMK_ConfigureForCrossForestMoves
Thanks,
Angela Shi
TechNet Community Support

Outlook 2013 connection issue with exchange 2013

Similar Messages

Maybe you are looking for