Using Outlook (2010 & 2013) to connect to Exchange using EWS

First things first.
I know that Outlook on the PC platform uses MAPI to connect to Excahnge while the Mac flavor of Outlook uses EWS, however, i was cycling through some available EX and ExO PowerShell cmdlets and found a parameter for set-casmailbox named EWSAllowOutlook Which
leads me to believe that configuring this setting should allow Outlook to use EWS to connect to Exchange. (This is a separate parameter from EWSAllowMacOutlook).
I tried a manual configuration (entering in the EWS url and setting the correct Outlook Anywhere settings) with no success.
I also tried manual configuration of an outlook.com and activesync account and entering the EWS URL as well with no success.
Has anyone successfully configured Outlook for PC to connect to Exchange using EWS and how did you configure the client?
Thanks

Hi,
Sorry for the late reply.
About the EWSAllowOutlook parameter, I have something to clarify.
This parameter allow or disallow Outlook 2007 to access EWS for the user.
Outlook uses EWS for free/buzy, OOF settings, and calendar sharing.
Outlook connect to Exchange server by using MAPI is a by design behavior.
We cannot change this.
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

Windows XP SP3 and Outlook 2010 can't connect with Exchange 2010 or Exchange 2013

XP+SP3+Outlook 2010 can't connect to Exchange 2010&2013 in the internal network without safe mode.

Hi,
Did you get any error messages?
Do you have Outlook Anywhere and autodiscovery set up properly?
Can you ping the Exchange server?
Please use Test Email AutoConfiguration
to test if the Autodiscover service is configured properly. See:
https://hosting.intermedia.net/support/kb/default.asp?id=2150
We can also use the remote connectivity analyzer to troubleshoot the issue:
https://testconnectivity.microsoft.com/
In addition, turn off your firewall and anti-virus to check the result.
Hope this helps.
Best Regards,
Steve Fan
TechNet Community Support

Unable to connect to Exchange 2013 using Outlook 2010/2013 with latest patch

Dear All,
I'm setting up Exchange 2013 CU2 coexist with Exchange 2010 SP3. Since we are still planning and testing, the internet is still pointing to 2010 for send/receive mails.
The 2013 environment are:-
2 X CAS server with MS NLB configured
2X MBX server with DA
Internal NLB/licent access: excas2013.int.my.domain
External access (current set on 2010 as well): webmail.my.domain
Certificate with valid subject name has been import to 2013 and 2010:
CN: webmail.mydomain
SAN: excas2013.int.my.domain
SAN: excas.int.my.domain (for 2010)
I am able to connect to my Exchange 2010 user thru 2013 CAS server and proxy to exhcnage 2010 by outlook. However, I cannot connect to Exchange 2013 user by outlook. During mail profile create of Exchange 2013 user by autodiscover (pointed to exchange 2013),
the process looks good:-
Establish network connection (checked)
Searching for [email protected] server settings (checked)
Log on to server
The process stop at "Log on to server" and a windows prompt, saying:
The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
Clicked OK, I can see:-
MS Exchange Server:
[email protected]
Mailbox:
=SMPT:[email protected]
WHen I click "Check Name", it said The name cannot be resolved.
I have no idea of what is going on. Just want some help~

I have checked the iis log:-
2013-09-23 06:58:29 10.144.144.71 POST /autodiscover/autodiscover.xml &cafeReqId=99ed5467-a294-481c-95eb-9b21d6530404; 443 mydomain\training101 10.144.85.4 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7106;+Pro) 200 0 0 8018
2013-09-23 06:58:29 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f4652a19-2e8e-4652-a007-0cf0b7fb792e&cafeReqId=f4652a19-2e8e-4652-a007-0cf0b7fb792e; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:29 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=c48cda77-6008-423b-8e8b-d6d40f4d1b39&cafeReqId=c48cda77-6008-423b-8e8b-d6d40f4d1b39; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:29 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=033f1ce4-43ba-49b1-b226-f4cc357e7702&cafeReqId=033f1ce4-43ba-49b1-b226-f4cc357e7702; 443 - 10.144.85.4 MSRPC 401 1 2148074252
15
2013-09-23 06:58:29 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=d2424d25-ca9e-4867-922f-e527b041d9db&cafeReqId=d2424d25-ca9e-4867-922f-e527b041d9db; 443 - 10.144.85.4 MSRPC 401 1 64 0
2013-09-23 06:58:31 10.144.144.73 POST /autodiscover/autodiscover.xml &cafeReqId=ff35f49b-e418-4d55-b66c-dbae509cc12f; 443 - 10.144.92.17 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6662;+Pro) 401 1 2148074254 0
2013-09-23 06:58:31 10.144.144.73 POST /autodiscover/autodiscover.xml &cafeReqId=033f8ed6-d7ce-41b2-8ed2-e275e22e53be; 443 mydomain\tkchung 10.144.92.17 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6662;+Pro) 200 0 64 15
2013-09-23 06:58:37 10.144.144.71 POST /powershell serializationLevel=Full;ExchClientVer=15.0.712.24;clientApplication=ManagementShell;TargetServer=;PSVersion=3.0&sessionID=Version_15.0_(Build_711.24)=rJqNiZqNgbqnsr3Py9GWkYvRlZqc0ZyQkoHOxsvOxsbJzczNgcbQzczQzc/OzN/Ixc/KxczI376y&cafeReqId=5350aa81-6668-489e-b099-3b3647115f10;
80 mydomain\Administrator 10.144.144.71 Microsoft+WinRM+Client 500 0 0 180040
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f961c596-efff-4696-9188-611a0d151601&cafeReqId=f961c596-efff-4696-9188-611a0d151601; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=753d8852-ce19-459c-ac78-849c3e51e0a1&cafeReqId=753d8852-ce19-459c-ac78-849c3e51e0a1; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=c9e86049-c883-4b03-8546-143909361a80&cafeReqId=c9e86049-c883-4b03-8546-143909361a80; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 64 78
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=327ace4c-b2c8-44c1-95ba-7871727f60ef&cafeReqId=327ace4c-b2c8-44c1-95ba-7871727f60ef; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 109
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=a7c8daa9-e458-4f2d-b388-7300e8679dcd&cafeReqId=a7c8daa9-e458-4f2d-b388-7300e8679dcd; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=c40afede-dd8f-4ac7-a3dd-827872bb2e76&cafeReqId=c40afede-dd8f-4ac7-a3dd-827872bb2e76; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=2dc56148-1900-4044-b72a-4b13e5e871f0&cafeReqId=2dc56148-1900-4044-b72a-4b13e5e871f0; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 64 15
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=9475aad3-9537-4dac-86cb-6fdb187fa148&cafeReqId=9475aad3-9537-4dac-86cb-6fdb187fa148; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 31
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=11a54e96-d8d8-4649-8e01-f8138ebf7b8d&cafeReqId=11a54e96-d8d8-4649-8e01-f8138ebf7b8d; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=b1a3e503-1077-4144-84df-fcdb65a7eea4&cafeReqId=b1a3e503-1077-4144-84df-fcdb65a7eea4; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=5b5639ba-4c91-4351-bda6-bcec46d6b218&cafeReqId=5b5639ba-4c91-4351-bda6-bcec46d6b218; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 0 15
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f200806f-3294-4210-8940-e3fee0385ccd&cafeReqId=f200806f-3294-4210-8940-e3fee0385ccd; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 46
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=675d6515-85da-43fa-9cd8-0a18ac06a71f&cafeReqId=675d6515-85da-43fa-9cd8-0a18ac06a71f; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=b97b2c3e-5309-4927-8330-fe0f339b5930&cafeReqId=b97b2c3e-5309-4927-8330-fe0f339b5930; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=504d462a-db21-4e4b-8568-79e4099d78c1&cafeReqId=504d462a-db21-4e4b-8568-79e4099d78c1; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 0 31
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=b4757b1e-8428-454a-91df-ca0a2153144f&cafeReqId=b4757b1e-8428-454a-91df-ca0a2153144f; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 46

Outlook 2010 won't connect to exchange 2010 - logon box appears

Users can't connect to Exchange server from outlook 2010. The domain\user and password boxes keep popping up and will not accept the details. It ends with "the connection to exchange is unavailable. Outlook needs to be online to perform
this action"
I've searched high and low for an answer and none work. Anyone any ideas?
Exchange is behind Threat Management Gateway 2010, with applicable rules setup. Strangeley, Outlook Web Access works fine with no problems what so ever.
Thanks in advance
Andy

Ok. Done some reading and made some adjustments but still pretty much the same. Microsofts Exchange analyser tool come up with the folowing errors and does indeed pinpoint it down to the autodiscover service. The srv record for the autodiscover
service - should that be on my own internal DNS or on my web host DNS?
The results of the connectivity test are below:
Testing RPC/HTTP connectivity.
The RPC/HTTP test failed.
Test Steps
ExRCA is attempting to test Autodiscover for [email protected].
Testing Autodiscover failed.
Test Steps
Attempting each method of contacting the Autodiscover service.
The Autodiscover service couldn't be contacted successfully by any method.
Test Steps
Attempting to test potential Autodiscover URL https://owa.optima-ws.co.uk/AutoDiscover/AutoDiscover.xml
Testing of this potential Autodiscover URL failed.
Test Steps
Attempting to resolve the host name owa.optima-ws.co.uk in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 78.33.247.168
Testing TCP port 443 on host owa.optima-ws.co.uk to ensure it's listening and open.
The port was opened successfully.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Test Steps
ExRCA is attempting to obtain the SSL certificate from remote server owa.optima-ws.co.uk on port 443.
ExRCA successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=owa.optima-ws.co.uk, OU=Domain Control Validated - GeoTrust(R) SSL Trial, OU=www.geotrust.com/resources/cps, OU=GT52908676, SERIALNUMBER=OyRDVCpo58GRaYQL5CORIFnTYn4Odw9G, Issuer: CN=GeoTrust DV SSL CA, OU=Domain Validated
SSL, O=GeoTrust Inc., C=US.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name owa.optima-ws.co.uk was found in the Certificate Subject Common name.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
ExRCA is attempting to build certificate chains for certificate CN=owa.optima-ws.co.uk, OU=Domain Control Validated - GeoTrust(R) SSL Trial, OU=www.geotrust.com/resources/cps, OU=GT52908676, SERIALNUMBER=OyRDVCpo58GRaYQL5CORIFnTYn4Odw9G.
One or more certificate chains were constructed successfully.
Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate CN=GeoTrust Global CA, O=GeoTrust Inc., C=US.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
ExRCA can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 7/24/2012 7:35:43 PM, NotAfter = 8/25/2012 12:31:49 PM
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details
Accept/Require Client Certificates isn't configured.
Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
Autodiscover settings weren't obtained when the Autodiscover POST request was sent.
Test Steps
ExRCA is attempting to retrieve an XML Autodiscover response from URL https://owa.optima-ws.co.uk/AutoDiscover/AutoDiscover.xml for user [email protected].
ExRCA failed to obtain an Autodiscover XML response.
Additional Details
An HTTP 500 response was returned from Unknown.
Attempting to test potential Autodiscover URL https://autodiscover.owa.optima-ws.co.uk/AutoDiscover/AutoDiscover.xml
Testing of this potential Autodiscover URL failed.
Test Steps
Attempting to resolve the host name autodiscover.owa.optima-ws.co.uk in DNS.
The host name couldn't be resolved.
<label for="testSelectWizard_ctl12_ctl06_ctl00_ctl00_ctl01_ctl00_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Host autodiscover.owa.optima-ws.co.uk couldn't be resolved in DNS InfoDomainNonexistent.
Attempting to contact the Autodiscover service using the HTTP redirect method.
The attempt to contact Autodiscover using the HTTP Redirect method failed.
Test Steps
Attempting to resolve the host name autodiscover.owa.optima-ws.co.uk in DNS.
The host name couldn't be resolved.
<label for="testSelectWizard_ctl12_ctl06_ctl00_ctl00_ctl02_ctl00_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Host autodiscover.owa.optima-ws.co.uk couldn't be resolved in DNS InfoDomainNonexistent.
Attempting to contact the Autodiscover service using the DNS SRV redirect method.
ExRCA failed to contact the Autodiscover service using the DNS SRV redirect method.
Test Steps
Attempting to locate SRV record _autodiscover._tcp.owa.optima-ws.co.uk in DNS.
The Autodiscover SRV record wasn't found in DNS.
<label for="testSelectWizard_ctl12_ctl06_ctl00_ctl00_ctl03_ctl00_tmmArrow">Tell
me more about this issue and how to resolve it</label>

Unrecognized certificate when Outlook 2010 tries to connect to Exchange 2007 on SBS 2008

Hi all,
I believe this is a security issue rather than a connectivity or configuration problem.
Running Outlook 2010 on Windows 7 trying to connect to Exchange 2007 on SBS 2008, I receive the following error:
"The name of the security certificate is invalid or does not match the name of the site"
When I view the certificate I see that it was issued to "zx-server" by "zx". This is NOT my domain CA nor is it a certificate I recognize. I use a self-issued certificate (i.e. issued by the SBS box). I also receive this certificate error when I browse to
the internal website (companyweb). No other computers on the network are seeing this behaviour.
I have checked the certificate stores in certmgr and I can't find any such certificate or CA. I have also searched the entire hard drive with no luck. I have run Kaspersky AV, Malwarebytes and MS Security Essentials several times but I can't find any malware.
I also recently installed Comodo Firewall (the problem began after this).
I need to find and remove the certificate and prevent it from being presented to me every time I try to connect to the server. All help, advice and suggestions appreciated.
Aide

Hi,
It’s really a common issue.
This issue occurs if the following conditions are true:
You replace the default self-signed Exchange Server 2007 or Exchange Server 2010 certificate with a different certificate.
Note The Setup program in Exchange Server 2007 or in Exchange Server 2010 creates a default self-signed certificate when Exchange Server 2007 or Exchange Server 2010 is installed.
The common name on the replacement certificate does not match the fully qualified domain name (FQDN) of the URL that is stored in the following objects:
o
The Service Connection Point object for the Autodiscover service
o
The
InternalUrl attribute of Exchange 2007 Web Service (EWS)
o
The
InternalUrl attribute of the Offline Address Book Web service
o
The
InternalUrl attribute of the Exchange unified messaging (UM) Web service
By default, the URL that is stored in these objects references the NetBIOS name of the server. For example, a URL that resembles the
following URL is stored:
https://NetBIOS_name.contoso.com/autodiscover/autodiscover.xml
This may differ from the host name that is used in the FQDN of the replacement certificate. For example, the replacement certificate
may have an FQDN that resembles the following FQDN:
mail.contoso.com
This issue causes a name mismatch error to occur. Therefore, you receive the security warning message when you try to connect Outlook
2007 to the mailbox.
For more detailed information about the procedures to fix the issue, please refer to the following KB article:
Title: Security warning when you start Outlook 2007 and then connect to a mailbox
that is hosted on a server that is running Exchange Server 2007 or Exchange Server 2010: "The name of the security certificate is invalid or does not match the name of the site"
URL:
http://support.microsoft.com/kb/940726
Regards,
James
James Xiong
TechNet Community Support

Outlook 2010 Will Not Connect to Exchange 2007 on SBS 2008 Server

Good Morning,
I have a user who cannot connect to the exchange server on SBS 2008 with outlook 2010. When they start outlook, it shows disconnected and will not connect for a minimum of 20 minutes to an hour. Any suggestions on how to fix this would be appreciated.
I have rebuilt their profile, but that does not fix the issue.
Thank you,
Lee F.
Lee Feldman SMB Consultant

Hi,
Thanks for posting in the forum.
Regarding the current issue, since you have recreated the user profile without any issue, I suspect that it’s mainly caused by the network issue. At this time, please first check the TCP/IP
configurations as Larry mentioned. Then, please also refer to the article below for details about how to troubleshoot Outlook connectivity issue.
Troubleshooting Microsoft Exchange: Outlook Connectivity Issues
http://blogs.technet.com/b/mspfe/archive/2011/04/12/troubleshooting_2d00_microsoft_2d00_exchange_2d00_outlook_2d00_connectivity_2d00_issues.aspx
Hope this helps.
Best Regards,
Andy Qi
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Andy Qi
TechNet Community Support

Outlook 2010/2013 not able to connect to Exchange 2013

Hi, I'm the midst of co-exist between Exchange 2010/2013. I have issues where none of internal users that migrated to Exchange 2013 not able to connect via Outlook 2010/2013. OWA is running fine without issue. Using MCA, the issue due to port is blocked
but I have verified that firewall on Exchange 2013 server is turn off all.
    1. Exchange 2010/2013 cert is using public CA cert.
    2. Both outlook anywhere external URL for Exchange2010/2013 is set to outlook.domain.com. internal pointing to server.domain.com. while autodiscover is set to autodiscover.domain.com.
   3. user mailbox in exchange 2010 do not have any issue
while if I try to logon, the error look like below:
Cannot open your default e-mail forlders. You must connect to microsoft exchange with the current profile before you can synchronuze your folder with your outlook data file (.ost).
what else should I check ?
many thanks.

Hello,
What server does “outlook.domain.com” and “autodiscover.domain.com” point to, Exchange 2013 FE or 2010 CAS?
You can also do a Outlook Test Email AutoConfiguration by the following steps:
a. While Outlook is running, click the CTRL key and then right-click the Outlook icon in the system tray and then select “Test Email Autoconfiguration”.
b. Confirm that your email address is in the address field, uncheck “Use Guessmart” and “secure Guessmart authentication” boxes. Then click the “Test” button.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Outlook 2010/2013 clients, outside of our main office, can't connect to our Exchange 2010 server

Hi,
Our remote users had been connecting to our Exchange server at our office since the Exchange server was installed in 2011.
Starting last Wednesday, Outlook 2010/2013 clients, outside of our main office, can't connect to our Exchange 2010 server. Outlook kept asking for a username and a password. At the same time, entries of Event 4625 were generated on the Event
log on out Exchange server.
Events 4625 has the following properties, "Logon Type: 3", "Failure Reason: An Error occured during Logon.", "Status: 0xc000006d", "Logon Process: NtLmSsp", and "Authentication Package: NTLM".
By the way, I had used a laptop to test this problem. Its Outlook work fine ion the main office, but it won't work outside of our office.
Does anyone have any idea?
Thanks.
Johnnie :(
Johnnie

http://blogs.technet.com/b/rmilne/archive/2015/03/17/update-015_2d00_027-revised-_2800_3002657_2900_.aspx
For additional people reading this thread, please update to v2 of that update.
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.

Connection Office365 Exchange - Outlook 2010/2013 (Desktop)

I have an Office365 account with Exchange function, connected with my personal domain. This works perfect for almost a year now, but since a few days, Outlook (desktop) can't connect to my ExchangeMail/Office365 anymore. Some details:
I can reach my mail via the Web App
My iPhone receives my email; no problems here
The password has not been changed
I've tried to connect with Outlook2010 on Windows7 and with Outlook2013 on Windows8; both can't connect
Profile removed and re-added: no result
As during creating/editing the profile in the ConfigurationScreen/Email, as in Outlook (2010 & 2013) itself, the login window pops up and can't connect (and because of that, Outlook automatically close).
In short: what is the problem here and -more important- how can I fix this?
Many Thanks,
Ewoud
PS: Apologies if this question has been asked in the wrong forum.

Hi,
Please check the problematic users' Outlook settings by the following steps:
1. Click File > Account Settings > Account Settings > Change > More settings.
2. In Security tab, make sure "Encrypt data between Microsoft Outlook and Microsoft Exchange" option is checked, "Always prompt for logon credentials" is unchecked.
3. Change the logon network security to Negotiate Authentication, and Apply > OK to set it.
Restart Outlook to have a try. If the issue persists, please
re-create Outlook profile to check whether the issue persists.
Regards,
Winnie Liang
TechNet Community Support
Thank you for the response.
I did as you suggested and the problem persists

Using Outlook Web App Web Parts in Exchange Server 2013 - OWA ? Possible?

Using Outlook Web App Web Parts in Exchange Server 2013 - OWA ? Possible?
We recently upgraded from Exchange 2010 to Exchange 2013.
The links that used OWA Web parts have completely stopped working and generate the " :( something went wrong contact your help desk" screen for domain Authenticated users other than myself. The links accessed content of a Shared Account of which
I am an owner and can set the necessary permissions using the Outlook 2013 client.
Using the example from the link provided below we were able to provide calendar access to all authenticated users in our area. The link for calendar still works for me but for noone else. Additionally, all navigation menus are missing when I use this link.
<server>/owa/<SMTP address>/?cmd=contents&module=calendar&view=weekly name
Another crafted link provided web access to our group's task list. This has completely stopped working for anyone including myself. However, when I use "open another mailbox" I am able to navigate to the needed pages.
<server name>/owa/<SMTP address>/?cmd=contents&module=tasks
These links were crafted using advice provided from this provided link.
technet.microsoft.com/en-us/library/bb232199(v=exchg.141).aspx
Is it still possible to use Outlook Web App Web Parts in Exchange Server 2013 - OWA?
Or
Is this a misconfiguration of some sort?
My IT support has given up and closed out the ticket stating that maybe Microsoft will fix this someday...

Hello,
At present, there is no official article to verify whether we can use Outlook Web App Web Parts in Exchange Server 2013. In exchange online, the Outlook Web App Parts is supported.
Cara Chen
TechNet Community Support
Hi, you said this feature is supported in Exchange Online (I understand you're referring to Office 365). Can you please point me to some documentation as I was trying to use it with my E3 account and it doesn't seem to work?
What I'm trying to acomplish is something similar to our old URL (Exchange 2010) in Office 365:
https://ourserver.mydomain.com/owa/[email protected]/?cmd=contents&module=calendar&view=monthly
The best I can do in Office 365 is this:
https://outlook.com/owa/mydomain.com/[email protected]/#path=/calendar
But it's clearly not the same and Office 365 ignores all the information I add to the URL. I would greatly appreciate something in the line of the document referred by 'MarquetteENG' (technet.microsoft.com/en-us/library/bb232199(v=exchg.141).aspx)
Thanks.
Paulo.
Paulo Dias - IT Pro Evangelist

Currently using Outlook 2010. It started acting up today. If I purchase 2013, will it solve my problem, or could the problem be coming from a corrupt PST file?

I use outlook 2010. It has been working perfectly. Today I got an error message that I never "caught" quickly enough. Something about a fax ad on not working properly and I should contact the ad on people. Ever since then, my outlook is not working
properly. When I create an e-mail a box appears, similar to a text box but with nothing inside. I cant type in the box, and can therefore not send out e-mails. Will buying 2013 outlook solve my issue?

Hi there
I’m sorry to hear that you have been unable to access your voicemail!
It seems like due to the SIM switch, the voicemail service has temporarily been put into an inactive state. When swapping between devices, this will occur and requires re-setting up the voicemail service. Your unheard and saved messages would not be affected. Are you currently still in the Hong Kong area?
Thanks,
Charise

Unbale to install November update on Outlook 2007 SP3 for connecting to Exchange 2013

Hi
I was trying to upgrade my outlook 2007 clients for connecting to Exchange 2013 environment. First I have installed Office SP3 (kb2526086). Outlook version after that is 12.0.6607.1000. Later I tried to install nNovember 2012 update which is a
prerequisite for connecting to Exchange 2013 clients (support.microsoft.com/kb/2687404/en-us) but it shows me a message "Expected version of the product was not found on the system". No idea how to proceed now, expecting help.

I recommend that you post this in the Outlook Forum: http://social.technet.microsoft.com/Forums/en-US/outlook/threads
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Delayed received emails Using Outlook 2010 and Exchange Server 2010 SP3

Hi,
Some of our users are encountering delayed emails. When our clients sent email to us, some of our clients received this an hour late, sometimes they will received this the next day.
Our users uses Outlook 2010 and our Exchange Server is 2010. We have already patch this to SP3 as it says that the delayed emails was already fixed in this SP3 but we still encounter the delayed emails.
Thanks.
Collins.

Hi Collins,
In order to narrow down this issue, please use OWA to send and receive a test email, see whether the delay will still happen or not.
From your description, the issue happens when certain users receive emails from internal. I recommend you use message tracking log to determine which step delays.
Here is an article for your reference.
Configure Message Tracking
http://technet.microsoft.com/en-us/library/aa997984(v=exchg.141).aspx
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Microsoft Outlook 2010 & 2013 cannot set automatic reply settings

Hello,
We cannot seem to set automatic reply's within outlook 2010 & 2013. We have an exchange server 2010. We
can setup automatic reply through OWA absolutely fine. The error that we receive is 'Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later.
However we can setup out of office on any other office version below 2010 fine. We have run through
a number of tests and have come to the conclusion that the auto discover service is not configured correctly. I have been told to run through the following
"We need to make sure the IIS service is assigned to the certificate which includes mail.mydomainname.co.uk
name:
Enable-ExchangeCertificate -Thumbprint 62C247B3BD081D0A8B074D4A928A76E6DA3BABBA -Services
POP,IMAP,SMTP,IIS
Then restart IIS service
to apply the changes.
If the user is connect
to mailbox from external environment as your test results, it is recommended to add the autodiscover.mydomain.co.uk name in your certificate with IIS service. If so, the autodiscover
service can be accessed successfully in your posted second steps(https:/autodiscover.mydomain.co.uk/autodiscover/autodiscover.xml). Alternatively, if you don’t want to change your certificate configuration, we need to create a new SRV record for mail.mydomainname.co.uk
to make your autodiscover succeed in last steps of Srv Record lookup method".
So I followed this and opened Exchange Managemnet Shell and ran the following.....
'Enable-ExchangeCertificate -Thumbprint 62C247B3BD081D0A8B074D4A928A76E6DA3BABBA -Services POP,IMAP,SMTP,IIS'
The following output was displayed:
"VERBOSE: Connecting to SERVER2011.EXCHANGE.local
VERBOSE: Connected to SERVER2011.EXCHANGE.local.
[PS] C:\Windows\system32>Enable-ExchangeCertificate -Thumbprint 62C247B3BD081D0A8B074D4A928A76E6DA3BABBA -Services POP,I
MAP,SMTP,IIS
WARNING: This certificate will not be used for external TLS connections with an FQDN of 'SERVER2011.EXCHANGE.local'
because the CA-signed certificate with thumbprint '71ADF367E190E269C1036BBF4A09C55E62536791' takes precedence. The
following receive/send connectors match that FQDN: Default SERVER2011.
WARNING: This certificate will not be used for external TLS connections with an FQDN of
'mail.companyname.co.uk' because the CA-signed certificate with thumbprint
'67ECB1A383CBD05424C58F6A5E753C9377F49D3D' takes precedence. The following receive/send connectors match that FQDN:
Windows SBS Internet Receive SERVER2011, Fax/Printer.
Confirm
Overwrite the existing default SMTP certificate?
Current certificate: '67ECB1A383CBD05424C58F6A5E753C9377F49D3D' (expires 09/08/2015 09:06:17)
Replace it with certificate: '62C247B3BD081D0A8B074D4A928A76E6DA3BABBA' (expires 06/08/2015 17:05:22)
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"):"
I opened up 'Internet Information
Services (IIS) Manager to find 2 Server Certificates issues to 'mail.companyname'
with the certificate hash' 62C247B3BD081D0A8B074D4A928A76E6DA3BABBA' and '71ADF367E190E269C1036BBF4A09C55E62536791'.
I opened up the Exchange Management
Console to confirm that the IMAP, POP, IIS, and SMTP services are bound to both of the certificates for 'mail.companyname'.co.uk
I need to know if it is okay to proceed in replacing the certificate and running this
command.
Thank you

Hi,
We have this problem with some of our users, in that they get the server unavailable error when trying to activate the out of office.
In our case this is because the Proxy is blocking the connection from the PC to the Exchange, so we just go to Internet Options - Connections - LAN Settings - Advanced (under proxy server) then just add *.domain.com into the Exceptions box at the bottom.
This seems to resolve the issue and allow them to set their out of office. The only reason this reoccurs for these users is because their roaming profile for some reason won't save the proxy settings, which is a different issue.
Hope this helps.

Outlook clients unable to connect to Exchange / Windows user profile

Exchange 2010
Outlook 2010/2013
I've seen a dozen or so computers in the last few weeks with this problem. The user suddenly cannot connect to the Exchange server in Outlook. (Sorry, I don't have specific error messages for this part.)
If I try a repair on the Email account or try to create a new Mail profile, I get this error:
"The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
I have verified all Exchange and mail security settings. Outlook configuration is not the problem.
I tried deleting %appdata%\microsoft\outlook and %localappdata%\microsoft\outlook.
I tried a repair on Microsoft Office.
I tried creating a new Mail profile for a different email account.
The only thing that has fixed this problem is a completely new Windows user profile, which tells me there is something else broken in the user profile. Does anyone have any idea what it might be?
Blog /
Twitter

Hi,
Please try to access Exchange via OWA.
This issue may occur when the HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders registry key does not contain all of the required data. Specifically, these problems occur if the AppData string value is missing from this
registry key.
To resolve this issue, import the User Shell Folders registry key from a working Windows User Profile.
Steps to perform on a working computer
Start Registry Editor. Click Start , type regedit in the Search programs and files box, and then press Enter.
Locate and then select the following registry subkey: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
On the File menu, click Export.
Specify the name of the .reg file and then click Save.
Copy the .reg file to the computer exibiting this problem.
Close Registry Editor.
Steps to perform on the computer displaying the above error(s)
Start Registry Editor.
On the File menu click Import.
Locate and select the .reg file exported from the working computer.
Click Open.
Close Registry Editor.
Best Regards.

Using Outlook (2010 & 2013) to connect to Exchange using EWS

Similar Messages

Maybe you are looking for