Outlook 2013 with Exchange 2010

we upgraded from Outlook 2010 to 2013 x64it and the exchange server is the same 2010
when trying to cleanup public folders the Clean Up tool is grayed our and it says "outlook 2013 this feature is not available because you are running in online mode and connected to microsoft exchange server 2007 or earlier" none of this is true.
It works fine when you are in your own inbox, only grays out in Public folders, this worked fine with Outlook 2010
David

Hi David,
Sorry for the late reply.
Since Outlook 2010 works well, just Outlook 2013 has this issue, I still believe this issue related to the Outlook 2013 Client side.
I suggest also create a thread on Outlook Forum so that we can get more professional suggestions.
For your convenience:
https://social.technet.microsoft.com/Forums/office/en-US/home?forum=outlook
If this issue really related to the Exchange 2010 server side, I suggest re-setting the default public folder database for testing.
Please make a back up for the current setting in case of some crash. If it doesn't work, please back to the current setting.
Then please follow following article to change the default public folder database:
Change the Default Public Folder Database for a Mailbox Database
http://technet.microsoft.com/en-us/library/bb629522.aspx
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

Fully automated Outlook 2013 with Exchange 2010 client setup

Hi,
I'm trying to create a situation where a user fires up Outlook 2013 for the first time and the Exchange account is configured for them without any intervention whatsoever.
I currently have it that when a user opens Outlook, they see the "Welcome to Outlook 2013" screen and they click next. They are asked if the want to setup Outlook to connect to an email account and click Next. On the next screen, there
primary SMTP address is automatically filled out, and then autodiscover takes over and configures the rest for them.
I have configured AutoDiscover correctly (including SCP), and configured a GPO with "Automatically configure profile based on Active Directory Primary SMTP address".
However, I still get that "Welcome to Outlook 2013" screen.
How do I get rid of that to make the whole process fully automated?
Many thanks,
-Mark

Hi Mark,
I have this issue before.
When we first add our accout to Outlook, we should better create a new profile manually.
I suggest removing our accout from Outlook via "Mail" and re-creating new profile.
Operation details as below:
1. Start-->Control Panel-->Mail-->E-mail Accounts...-->select your account and Remove it-->Close
2. Show Profiles...-->Add-->then configure your account again.
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Outlook 2013 with Exchange 2007 - out of office problem

We are using outlook 2013 with Exchange 2007. When users select their out of office it will work fine for the first day, however there after the Out of Office replies stop working. Out of Office is set correctly within Outlook, but what we have found
is that if the user opens Outlook the Out of Office starts to work again. Also when the user opens Outlook it takes around two minutes before it registers that Out of Office is on.
Any Ideas?

Hi,
How do you configure your OOF? From standard OOF wizard or define an automatic reply template from Rule wizard?
If you are using a template, Outlook must be running for the Rules Wizard to automatically reply. Please refer to the Note in the following KB:
http://support.microsoft.com/kb/311107
If it is configured by using standard Out of Office assistance in File > Automatic Replies, please remove OOF settings in Outlook and set it from OWA 2007, then check whether the issue can be reproduced.
Regards,
Winnie Liang
TechNet Community Support

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

Help needed with buggy Outlook 2013 and Exchange 2010 trashing profiles

Hi All,
I have a customer who has eschewed MOLP and buys all their Office OEM from Dell. So as a result they are starting to have more and more office 2013 be deployed. They have a SBS 2011 server with Exchange 2010 and it is patched to the latest
rollups and service packs. (SP3, RU2) Their Outlook 2010 and earlier clients are just peachy on this. But the Outlook 2013 clients are having problems.
What is going on is that periodically I'll get a complaint from a user that their Outlook 2013 is randomly crashing. In all cases the fix is going into the Outlook Profiles, creating a new profile, then setting the new profile as the default
and going back into Outlook 2013 and letting it rebuild the cached data on the PC. This seems to happen a few times a month with random users on the network.
I told the customer it was probably people not logging out of Outlook 2013 at night and their machines being power spiked but I think that's highly unlikely since it doesen't happen to the Outlook 2010 clients.
I don't know if any Microsoft developers read this but if you do, please take it back to your bug database. Any other suggestions would be appreciated (other than scotch Outlook 2013 - while I'd appreciate that, my customer wouldn't)

In all cases the fix is going into the Outlook Profiles, creating a new profile, then setting the new profile as the default and going back into Outlook 2013 and letting it rebuild the cached data on the PC.
The Outlook 2013 crash problem would be fix after you re-create a new profile and re-sync the data from Exchange, right?
When we meet the same problem in next time, I suggest we run the Outlook Product Stability Diagnostic tool to isolate known causes of crashes in Outlook. The Outlook Product Stability Diagnostic also creates a diagnostic report outlining the data it collected
and recommendations on possible steps you can take to reduce or eliminate Outlook stability issues.
Please click the following link to run the Outlook Product Stability Diagnostic tool in the Microsoft Fix it Center Pro portal:
Outlook Product Stability Diagnostic:
https://wc.ficp.support.microsoft.com/SelfHelp?knowledgebaseArticleFilter=2764035
Other troubleshoot steps for Outlook 2013, please refer to the link below.
Let me know the result.
http://support.microsoft.com/kb/2632425/en-us
Tony Chen
TechNet Community Support

Problem appearing olders emails outlook 2013 with Exchange 2007 SP2

hi everyone,
recently i have problem with user mailbox OST more than 20 Gb (configured with outlook 2013 and exchange 2007 SP2 ) and if i scroll down in the olders mails in the Inbox Folder it's stoped in 2011 but i have more than this year ! i tried to add regedit keys
such as Maxlargesize... and no changes and tried also with exporting this ost to PST File (i proceed with computer 32 bits ....) and always stop in 2011
Please if you have ideas to resolve this
best regards
vote if you think useful

Hi,
OST file is a local copy of your email messages, calendar, and other items that are on the Exchange server, it is always synchronized with the items on the server. So, the first thing we need to check is to login to OWA and check if you can see older
emails from there.
If you can't see the old email from OWA, it means the emails are removed from the server. In this case, you'll need to contact your Exchange admin to see if your old emails are archived. We can also check if you have enabled AutoArchive feature in your Outlook,
which may move your emails from your OST file to a local PST file. See:
https://support.microsoft.com/kb/830119?wa=wsignin1.0
If you can see the old emails from OWA, your OST file may be corrupt. We can exit Outlook, find the .OST file and rename it to .old, and then restart Outlook to let it sync a new one. By default, the OST file are save in:
drive:\Users\%username%\AppData\Local\Microsoft\Outlook
Please let me know the result.
Regards,
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
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]

Outlook 2013 with Exchange Server - Changed custom form for contacts is not shown

Hello,
Our infrastructure:
Exchange Server 2010
Outlook 2010
Outlook 2013
Windows 7 Pro, Windows 8 Pro and Windows 8.1 Pro
The situation:
We've used an old custom form for contacts, worked perfectly fine
I've updated the form (adding some new custom fields and checkboxes) using Outlook 2013 and publishing the form (with a new name) to the Exchange folder
I've set the form as default form in our contacts folder
I've used this Script to set the new form for the existing contacts and the name of the new form is saved correctly
BUT if I open a contact in our Exchange contacts folder, Outlook 2013 (Outlook 2010) still shows the old form
Steps I've taken so far:
Cleared Outlook forms cache
Repeated the above steps 1-4 in Outlook 2010
Switched Cached Exchange Mode off and back on
Allowed Scripts in Trust Center Settings
Used a new clean Windows installation with a new Outlook 2013 installation
Used different Exchange users on different systems, but some behavior when opening contacts
I'm out of options I can think of, so maybe somebody else has some new view on this problem.
Thank you very much in advance!
Greetings,
Karl

Hi,
Is the Exchange folder in which the custom form is published available to all users?
From the description, the script used to work for the old custom form, correct? Which version of Outlook did you use with the old custom contact form? Outlook 2010/Outlook 2013 or an earlier version? If you used the script with an earlier version of Outlook,
we can't make sure it will still work with Outlook 2010/Outlook 2013.
In addition we may also try creating a new contact form and test the steps to see if it will work.
Please let me know the result.
Regards,
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
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]

Outlook 2013 with Exchange 2013: Mails stuck in Outbox

Hi everybody,
I am using Outlook 2013 connecting an Exchange 2013 server. After sending a mail, all outgoing mails remain in the outbox. After removing the cache files it works for a while until the problem occurs for the next time (approx. once every two days).
I already re-installed Windows 8 to test it on a completely clean environment...OWA works fine, the problem only exists with Outlook.
Additional note: It might be interesting that after sending a mail, the "Send/Receive progress" window states "sending [email protected] - complete" but the Mail is still in the outbox and was not delivered to the recipient. Safe mode doesn't work
for me. Other users connecting with Outlook 2010 don't have a problem with this exchange server.
Do you have any ideas? If I can provide you with further information, please let me know.
Greets,
Basti

Thanks for your answer. Here are the requested information:
>What addins are you using?
No 3rd party addins, at the moment "Microsoft Exchange Add-In", "Microsoft VBA for Outlook Addin",
"OneNote Notes about Outlook Items" and "Outlook Social Connector 2013" are activated. But the problem also occurs if no addin is active (or even in Safemode).
>Antivirus
scanners can prevent Outlook from moving messages to the sent folder.
I will try to deactivate the virus scanner the next time. (Avira is used)
>Can
any address trigger this behavior or does it happen with certain addresses?
No, it does happen with any address by random. Once the problem occurs, I can try to send as much mails as I want to
any address - nothing leaves the outlook client.
>Is
this your mailbox or a shared/secondary mailbox?
It is a user's mailbox, nothing shared.

Outlook 2013 with exchange online account disconnected, tryin to connect for hours or indefinitely

I posted this in another forum (office 365) and was told to copy it here as it wasn't an office 365 issue so here is what I posted there:
===================================
Let me see if I can clarify better. This issue has been ongoing as long as I have worked for this client (I started in January but have been told the issue has been going on since before November of last year). The client has multiple construction sites
and its headquarters. There is a remote desktop server setup with a public IP address for the users "in the field" for accessing network resources at headquarters. At major construction sites (currently 3) they have high speed internet service installed
since the projects typically are 1+ years to complete. So at current times we have the following:
Main office:
Remote Desktop Server with logins for all employees
Main 2012R2 server
50MB/s internet connection via CenturyLink ISP
Site 1:
3 main users of computers. 1 constant user, 2 minimal use users. All 3 have experience the issue 3+ times a week
Comcast 50MB/S ISP
Site 2:
3 Main users of computers. 1 constant, 2 medium use users. All 3 experience the issue 3+ times a week
Comcast 50MB/s ISP
Site 3:
4+ computer users. 1 constant, 2 medium use users and the rest check email couple times a day. They also experience the disconnect issue 3+ times a week
15 MB/S DSL from CenturyLink ISP
There have been instances where (as examples) user 1a called me to tell me it was happening. Users 1b and 1c were not experiencing the issue. I was able to use a remote tool called Teamviewer to connect to her computer. Once connected I tried to open OWA
but it would not connect. I tried to ping the site and could not get a response. To verify I remoted into user 1b computer and his outlook was still connected and pinged fine. Both users being at the same site are on the same network. Had user 1a remote desktop
into the RDserver at the main office. Remoted into the server at the office her outlook on that machine connected no issues (in my mind rules out account issue?).
I don't believe it is network related due to the other computers working fine and being able to connect to her computer indicated to me that her NIC was fine. I don't think it was her account because it worked fine from the RD Server plus email service to
iPads/iPhones continue to work without issue. Once the computer is rebooted everything works fine for a while (could be hours, could be days).
Now to answer the questions for you:
1. it happens to all computers not at the main office but happens at random times to them. It also does not affect every computer at a remote location. It could be 1 or it could be multiple computers at the same time.
2. Affected users iPhones, iPads and outlook 2013 pro session on the RD Server at the main office continue to work no issues.
3. They cannot get to OWA on their machines when in that state, however can log into OWA on another machine plus the answer to #2 above.
4. It is all users at those locations, however I have experienced it myself at my house 1 time since January (I have a different exchange online plan/company than the one I am discussing in this post). The issue is random and it is uncertain if it will correct
itself if left sitting long enough (longest time it has been left is about 20 minutes or so) however even 20 minutes is a long time to wait for the service to return so users just reboot.
Please let me know If you have any solutions/ideas.
Thanks,
Brandon Smith
Cadence Communications
====================================
Hi Branon,
Thanks for your detailed information.
After going your post carefully, I am impressed by your strong technical skills. Regarding “I don't believe it is network related due to the other computers working fine and being able to connect to her computer indicated to me that her NIC was
fine. I don't think it was her account because it worked fine from the RD Server plus email service to iPads/iPhones continue to work without issue. Once the computer is rebooted everything works fine for a while (could be hours, could be days)” ,
I go along with you. Since the affected account could connect to other clients without issue , it indicates Office 365 account is no problem. And other computer were working fine and can connect to her computer, it shows the network environment does not cause
the issue. In this situation, the issue should relate to the specific Outlook Client. However this forum mainly focuses on Office 365 online services, to get more accurate responses, it’s suggested that you raise the problem in the Outlook forum. If they got
any result and you need further assistance from Office 365 side, please feel free to let us know.
In addition, about “I have had the users try to use OWA when it gets disconnected but they cannot get to that URL either. IE comes up with page not found”, I’d like to collect some information:
1. Does the issue only happen to IE? Have you tried logging in other browsers using the OWA address (like Chrome or Firefox)? Does it work?
2. Does only this user have the issue? Does it happen to other users?
3. Which version of Internet Explorer browser does the user use?
4. Could you provide us with the whole screenshot of the error message? You can post screenshots in our forum by clicking Use rich formatting and selecting the Insert Image icon.
Also, please try the following steps for troubleshooting:
a. Clear the IE caches and cookies when you log into Office 365 again.
b. Use the InPrivate Browsing of Internet Explorer to login.
c. Reset Internet Explorer’s settings, and try again.
d. Try to login in another network environment.
If there is any update, please let us know. I ’ll keep on monitoring this thread.
Best regards,
Jamie
===============================
As of today we still randomly experience this disconnect issue. Just today I had my test user call me to say she was disconnected. She is in location 2 where I have a test laptop also setup with her logged in. When she called I had her check the test laptop
and the outlook profile on that machine (same network) was still connected while her computer was not connected. I had her run the online analyzer tool on her machine (the one that would not connect) which ran for almost 2 hours. The tool finished right at
the same time that her outlook finally connected back to the server.
If anyone has any ideas/solutions please let me know.
Thanks in advance,
Brandon Smith
Cadence Communications Inc.

Oddly enough my computer is right at this moment in this same disconnected state. Outlook shows an exclamation point in a yellow triangle. Its state is disconnected. If I go to portal.office.com I get to the login page but get page can't be displayed after
entering my credentials. I tried using google and found this for login
https://outlook.office365.com/owa/ it too times out and can't be displayed.
if I try and ping these sites I get:
====================================================================
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\brandon.CAD1>ping portal.office.com
Pinging us.portal.office.akadns.net [2a01:111:f100:4001::4625:61ea] with 32 byte
s of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 2a01:111:f100:4001::4625:61ea:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\brandon.CAD1>ping login.microsoftonline.com
Pinging aadg.windows.net.nsatc.net [168.62.24.150] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 168.62.24.150:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
===============================================================================
If I remote into another machine at a client site I can log into portal.office.com using my email account.
I ran the outlook connectivity analyzer tool and got this if it helps:
===============================================================
Testing Outlook connectivity.
The Outlook connectivity test completed successfully.
Additional Details
Elapsed Time: 41017 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for
[email protected].
Autodiscover was tested successfully.
Additional Details
Elapsed Time: 12161 ms.
Test Steps
Attempting each method of contacting the Autodiscover service.
The Autodiscover service was tested successfully.
Additional Details
Elapsed Time: 12161 ms.
Test Steps
Attempting to test potential Autodiscover URL
https://cadcom.us:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 475 ms.
Test Steps
Attempting to resolve the host name cadcom.us in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 184.168.55.1
Elapsed Time: 173 ms.
Testing TCP port 443 on host cadcom.us to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 149 ms.
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Elapsed Time: 152 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server cadcom.us on port 443.
The Microsoft Connectivity Analyzer wasn't able to obtain the remote SSL certificate.
Additional Details
The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.
Elapsed Time: 91 ms.
Attempting to test potential Autodiscover URL
https://autodiscover.cadcom.us:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 9000 ms.
Test Steps
Attempting to resolve the host name autodiscover.cadcom.us in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 132.245.92.232, 132.245.58.104, 132.245.3.136, 132.245.64.248, 132.245.82.56, 132.245.88.200, 132.245.81.200, 132.245.81.136, 2a01:111:f400:2c84::8, 2a01:111:f400:1014::8, 2a01:111:f400:2c61::8, 2a01:111:f400:2c5d::8, 2a01:111:f400:142a::8,
2a01:111:f400:5242::8, 2a01:111:f400:2414::8, 2a01:111:f400:4c0b::8
Elapsed Time: 304 ms.
Testing TCP port 443 on host autodiscover.cadcom.us to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
Tell me more about this issue and how to resolve it
Additional Details
A network error occurred while communicating with the remote host.
Elapsed Time: 8696 ms.
Attempting to contact the Autodiscover service using the HTTP redirect method.
The Autodiscover service was successfully contacted using the HTTP redirect method.
Additional Details
Elapsed Time: 2684 ms.
Test Steps
Attempting to resolve the host name autodiscover.cadcom.us in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 132.245.92.232, 132.245.58.104, 132.245.3.136, 132.245.64.248, 132.245.82.56, 132.245.88.200, 132.245.81.200, 132.245.81.136, 2a01:111:f400:2c84::8, 2a01:111:f400:1014::8, 2a01:111:f400:2c61::8, 2a01:111:f400:2c5d::8, 2a01:111:f400:142a::8,
2a01:111:f400:5242::8, 2a01:111:f400:2414::8, 2a01:111:f400:4c0b::8
Elapsed Time: 39 ms.
Testing TCP port 80 on host autodiscover.cadcom.us to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 57 ms.
The Microsoft Connectivity Analyzer is checking the host autodiscover.cadcom.us for an HTTP redirect to the Autodiscover service.
The redirect (HTTP 301/302) response was received successfully.
Additional Details
Redirect URL:
https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml
HTTP Response Headers:
Pragma: no-cache
X-FEServer: BY2PR07CA071
Connection: close
Content-Length: 0
Cache-Control: no-cache
Date: Tue, 21 Apr 2015 04:40:05 GMT
Location:
https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml
Server: Microsoft-IIS/8.0
X-Powered-By: ASP.NET
Elapsed Time: 47 ms.
Attempting to test potential Autodiscover URL
https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml
Testing of the Autodiscover URL was successful.
Additional Details
Elapsed Time: 2540 ms.
Test Steps
Attempting to resolve the host name autodiscover-s.outlook.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 132.245.24.82, 132.245.92.34, 132.245.92.194, 132.245.80.146, 157.56.239.194, 132.245.64.146, 2a01:111:f400:1414::2, 2a01:111:f400:2c2c::2, 2a01:111:f400:1428::2, 2a01:111:f400:4c32::2, 2a01:111:f400:2c40::2, 2a01:111:f400:5000::2
Elapsed Time: 345 ms.
Testing TCP port 443 on host autodiscover-s.outlook.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 44 ms.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Additional Details
Elapsed Time: 177 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover-s.outlook.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US, Issuer: CN=Microsoft IT SSL SHA1, OU=Microsoft IT, O=Microsoft Corporation, L=Redmond, S=Washington, C=US.
Elapsed Time: 119 ms.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name autodiscover-s.outlook.com was found in the Certificate Subject Alternative Name entry.
Elapsed Time: 0 ms.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US.
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=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE.
Elapsed Time: 18 ms.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer 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.
Elapsed Time: 3 ms.
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 = 2/13/2015 12:38:15 AM, NotAfter = 2/13/2016 12:38:15 AM
Elapsed Time: 0 ms.
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details
Accept/Require Client Certificates isn't configured.
Elapsed Time: 146 ms.
Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
The Microsoft Connectivity Analyzer successfully retrieved Autodiscover settings by sending an Autodiscover POST.
Additional Details
Elapsed Time: 1827 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL
https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml for user
[email protected].
The Autodiscover XML response was successfully retrieved.
Additional Details
Autodiscover Account Settings
XML response:
<?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>Brandon Smith</DisplayName>
<LegacyDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon</LegacyDN>
<DeploymentId>5135be05-06e4-4e3b-9cbd-f39b6108647f</DeploymentId>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol Type="mapiHttp">
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<MailStore>
<ExternalUrl>https://outlook.office365.com/mapi/emsmdb/[email protected]</ExternalUrl>
</MailStore>
<AddressBook>
<ExternalUrl>https://outlook.office365.com/mapi/nspi/[email protected]</ExternalUrl>
</AddressBook>
</Protocol>
<Protocol>
<Type>WEB</Type>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<Internal>
<OWAUrl AuthenticationMethod="LiveIdFba, OAuth">https://outlook.office365.com/owa/</OWAUrl>
<Protocol>
<Type>EXCH</Type>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
</Protocol>
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba">https://outlook.office365.com/owa/cadcom.us/</OWAUrl>
<Protocol>
<Type>EXPR</Type>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
</Protocol>
</External>
</Protocol>
<Protocol>
<Type>EXHTTP</Type>
<Server>outlook.office365.com</Server>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
<OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>
<OABUrl>https://outlook.office365.com/OAB/fb606d0b-79d8-4255-9c7b-552a0fccb72f/</OABUrl>
<UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>On</SSL>
<AuthPackage>Basic</AuthPackage>
<EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>
<EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>
<SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>
<EcpUrl>https://outlook.office365.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=cadcom.us</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=cadcom.us</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=cadcom.us</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=cadcom.us</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=cadcom.us</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=cadcom.us</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=cadcom.us</EcpUrl-photo>
<EcpUrl-connect>Connect/Main.aspx?rfr=olk&exsvurl=1&Provider=<Provider>&Action=<Action>&realm=cadcom.us</EcpUrl-connect>
<EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=cadcom.us</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=cadcom.us</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=cadcom.us</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=cadcom.us</EcpUrl-extinstall>
<ServerExclusiveConnect>On</ServerExclusiveConnect>
</Protocol>
</Account>
</Response>
</Autodiscover>
HTTP Response Headers:
request-id: 443c7500-1216-4307-b195-8d742873d0f0
X-CalculatedBETarget: co1pr04mb474.namprd04.prod.outlook.com
X-DiagInfo: CO1PR04MB474
X-BEServer: CO1PR04MB474
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Set-Cookie: ClientId=JYEVNJSG0UERWBME1PF2A; expires=Wed, 20-Apr-2016 04:40:07 GMT; path=/; secure; HttpOnly,EXOBasicAuth=compactTicket=&key=brandon%40cadcom.us+microsoft.exchange.autodiscover+157.56.138.143+&signature=QJdNVZ9GjQrYkxZg4iXgN8XbU7ZlhTifQyXVjqCwqbBgJL14yiG8oVRxKprB6LXqEBx90YDherBvRURQmGweF+XHW5Eg4gKIhRhSgy6XhMdQslO+PSV1TuZJIHB0g8KcM1MDr4LEuS19bT1HFPpLEUf7A+tmrfTQyy6l21zaUohb/Z0XZUn1o/pkbIcBBSb+tOVAemIsTyHN/p0VbbkA2AeMdVVJIz1wHLW7s9o7fCtJ7cM33Wzz9M6g5k/bNv/NAe9a2nbCZjpyqdmDkKrdmalekhBVkusIskPX5p8aVU8CuiTRtyIcRq8IWxvDhwyH3RiFnyVd5ytNy42M0r7+gQ==&puid=100300008CF2A4C2&expireTime=635651446880000000&membername=brandon%40cadcom.us&flags=False&userType=ManagedBusiness;
expires=Mon, 20-Apr-2015 16:38:08 GMT; path=/Autodiscover; secure; HttpOnly,[email protected]=u56Lnp2ejJqBzc6Znc7OmcjSnpnJzdLLx8qa0sfOyM/Sms7OyMzLyJmbms/HgZyem5yQktGKjIHNz87K0s/K0s3Oq8/LxcvPxc/HgZGeko+Nm8/L0Y+NkJvRkIqLk5CQlNGckJI=;
expires=Thu, 21-May-2015 04:40:08 GMT; path=/Autodiscover; secure; HttpOnly,[email protected]=u56Lnp2ejJqBzc6Znc7OmcjSnpnJzdLLx8qa0sfOyM/Sms7OyMzLyJmbms/HgZyem5yQktGKjIHNz87K0s/K0s3Oq8/LxcvPxc/H; expires=Thu, 21-May-2015 04:40:08 GMT; path=/Autodiscover;
secure; HttpOnly
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
X-FEServer: BY1PR10CA0031
Date: Tue, 21 Apr 2015 04:40:08 GMT
Content-Length: 4345
Elapsed Time: 1525 ms.
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL
https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml for user
[email protected].
The Autodiscover XML response was successfully retrieved.
Additional Details
Autodiscover Account Settings
XML response:
<?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>Brandon Smith</DisplayName>
<LegacyDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon</LegacyDN>
<DeploymentId>5135be05-06e4-4e3b-9cbd-f39b6108647f</DeploymentId>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol>
<Type>EXCH</Type>
<Server>[email protected]</Server>
<ServerDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]</ServerDN>
<ServerVersion>73C18088</ServerVersion>
<MdbDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]/cn=Microsoft Private MDB</MdbDN>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
<OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>
<OABUrl>https://outlook.office365.com/OAB/fb606d0b-79d8-4255-9c7b-552a0fccb72f/</OABUrl>
<UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<AuthPackage>Anonymous</AuthPackage>
<PublicFolderServer>outlook.office365.com</PublicFolderServer>
<EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>
<EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>
<SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>
<EcpUrl>https://outlook.office365.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=cadcom.us</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=cadcom.us</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=cadcom.us</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=cadcom.us</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=cadcom.us</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=cadcom.us</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=cadcom.us</EcpUrl-photo>
<EcpUrl-connect>Connect/Main.aspx?rfr=olk&exsvurl=1&Provider=<Provider>&Action=<Action>&realm=cadcom.us</EcpUrl-connect>
<EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=cadcom.us</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=cadcom.us</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=cadcom.us</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=cadcom.us</EcpUrl-extinstall>
<ServerExclusiveConnect>off</ServerExclusiveConnect>
</Protocol>
<Protocol>
<Type>EXPR</Type>
<Server>outlook.office365.com</Server>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
<OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>
<OABUrl>https://outlook.office365.com/OAB/fb606d0b-79d8-4255-9c7b-552a0fccb72f/</OABUrl>
<UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>On</SSL>
<AuthPackage>Basic</AuthPackage>
<CertPrincipalName>msstd:outlook.com</CertPrincipalName>
<EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>
<EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>
<SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>
<EcpUrl>https://outlook.office365.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=cadcom.us</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=cadcom.us</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=cadcom.us</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=cadcom.us</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=cadcom.us</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=cadcom.us</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=cadcom.us</EcpUrl-photo>
<EcpUrl-connect>Connect/Main.aspx?rfr=olk&exsvurl=1&Provider=<Provider>&Action=<Action>&realm=cadcom.us</EcpUrl-connect>
<EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=cadcom.us</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=cadcom.us</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=cadcom.us</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=cadcom.us</EcpUrl-extinstall>
<ServerExclusiveConnect>on</ServerExclusiveConnect>
<EwsPartnerUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsPartnerUrl>
<GroupingInformation>CO1PR04</GroupingInformation>
</Protocol>
<Protocol>
<Type>WEB</Type>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<Internal>
<OWAUrl AuthenticationMethod="LiveIdFba, OAuth">https://outlook.office365.com/owa/</OWAUrl>
<Protocol>
<Type>EXCH</Type>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
</Protocol>
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba">https://outlook.office365.com/owa/cadcom.us/</OWAUrl>
<Protocol>
<Type>EXPR</Type>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
</Protocol>
</External>
</Protocol>
<Protocol>
<Type>EXHTTP</Type>
<Server>outlook.office365.com</Server>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
<OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>
<OABUrl>https://outlook.office365.com/OAB/fb606d0b-79d8-4255-9c7b-552a0fccb72f/</OABUrl>
<UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>On</SSL>
<AuthPackage>Basic</AuthPackage>
<CertPrincipalName>msstd:outlook.com</CertPrincipalName>
<EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>
<EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>
<SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>
<EcpUrl>https://outlook.office365.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=cadcom.us</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=cadcom.us</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=cadcom.us</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=cadcom.us</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=cadcom.us</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=cadcom.us</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=cadcom.us</EcpUrl-photo>
<EcpUrl-connect>Connect/Main.aspx?rfr=olk&exsvurl=1&Provider=<Provider>&Action=<Action>&realm=cadcom.us</EcpUrl-connect>
<EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=cadcom.us</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=cadcom.us</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=cadcom.us</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=cadcom.us</EcpUrl-extinstall>
<ServerExclusiveConnect>On</ServerExclusiveConnect>
</Protocol>
</Account>
</Response>
</Autodiscover>
HTTP Response Headers:
request-id: 4412d758-013f-4700-bde1-06dc5e66bf6d
X-CalculatedBETarget: co1pr04mb474.namprd04.prod.outlook.com
X-DiagInfo: CO1PR04MB474
X-BEServer: CO1PR04MB474
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Set-Cookie: ClientId=YVWYC2UW3EAOSJXJYJDCDW; expires=Wed, 20-Apr-2016 04:40:08 GMT; path=/; secure; HttpOnly,[email protected]=u56Lnp2ejJqBzc6Znc7OmcjSnpnJzdLLx8qa0sfOyM/Sms7OyMzLyJmbms/HgZyem5yQktGKjIHNz87K0s/K0s3Oq8/LxcvPxc/HgZGeko+Nm8/L0Y+NkJvRkIqLk5CQlNGckJI=;
expires=Thu, 21-May-2015 04:40:08 GMT; path=/Autodiscover; secure; HttpOnly,[email protected]=u56Lnp2ejJqBzc6Znc7OmcjSnpnJzdLLx8qa0sfOyM/Sms7OyMzLyJmbms/HgZyem5yQktGKjIHNz87K0s/K0s3Oq8/LxcvPxc/H; expires=Thu, 21-May-2015 04:40:08 GMT; path=/Autodiscover;
secure; HttpOnly
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
X-FEServer: BY1PR10CA0031
Date: Tue, 21 Apr 2015 04:40:08 GMT
Content-Length: 9631
Elapsed Time: 301 ms.
Autodiscover settings for Outlook connectivity are being validated.
The Microsoft Connectivity Analyzer validated the Outlook Autodiscover settings.
Additional Details
Elapsed Time: 0 ms.
Testing MAPI over HTTP connectivity to server outlook.office365.com
MAPI over HTTP connectivity was verified successfully.
Additional Details
HTTP Response Headers:
request-id: 2931fc03-73eb-4bb0-8ffc-34b9445369ed
X-FEServer: BY2PR09CA0048
Content-Length: 0
Date: Tue, 21 Apr 2015 04:40:08 GMT
Set-Cookie: ClientId=ZZCG7DWJLKIDNUIKMHP0Q; expires=Wed, 20-Apr-2016 04:40:09 GMT; path=/; secure; HttpOnly
Server: Microsoft-IIS/8.0
WWW-Authenticate: Basic Realm=""
X-Powered-By: ASP.NET
Elapsed Time: 3246 ms.
Test Steps
Attempting to resolve the host name outlook.office365.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 132.245.24.82, 132.245.92.34, 132.245.92.194, 132.245.80.146, 157.56.239.194, 132.245.64.146, 2a01:111:f400:2c40::2, 2a01:111:f400:5000::2, 2a01:111:f400:1414::2, 2a01:111:f400:2c2c::2, 2a01:111:f400:1428::2, 2a01:111:f400:4c32::2
Elapsed Time: 152 ms.
Testing TCP port 443 on host outlook.office365.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 70 ms.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Additional Details
Elapsed Time: 251 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server outlook.office365.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US, Issuer: CN=Microsoft IT SSL SHA1, OU=Microsoft IT, O=Microsoft Corporation, L=Redmond, S=Washington, C=US.
Elapsed Time: 141 ms.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name outlook.office365.com was found in the Certificate Subject Alternative Name entry.
Elapsed Time: 3 ms.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US.
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=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE.
Elapsed Time: 34 ms.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer 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.
Elapsed Time: 6 ms.
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 = 2/13/2015 12:38:15 AM, NotAfter = 2/13/2016 12:38:15 AM
Elapsed Time: 0 ms.
Testing HTTP Authentication Methods for URL
https://outlook.office365.com/mapi/emsmdb/[email protected].
The HTTP authentication methods are correct.
Additional Details
The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Basic
HTTP Response Headers:
request-id: 2931fc03-73eb-4bb0-8ffc-34b9445369ed
X-FEServer: BY2PR09CA0048
Content-Length: 0
Date: Tue, 21 Apr 2015 04:40:08 GMT
Set-Cookie: ClientId=ZZCG7DWJLKIDNUIKMHP0Q; expires=Wed, 20-Apr-2016 04:40:09 GMT; path=/; secure; HttpOnly
Server: Microsoft-IIS/8.0
WWW-Authenticate: Basic Realm=""
X-Powered-By: ASP.NET
Elapsed Time: 190 ms.
Testing the MAPI Address Book endpoint on the Exchange server.
The address book endpoint was tested successfully.
Additional Details
Elapsed Time: 1987 ms.
Test Steps
Testing the address book "Check Name" operation for user
[email protected] against server outlook.office365.com.
Check Name succeeded.
Additional Details
DisplayName: Brandon Smith, LegDN: /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon
Elapsed Time: 1987 ms.
Testing the MAPI Mail Store endpoint on the Exchange server.
We successfully tested the Mail Store endpoint.
Additional Details
Elapsed Time: 594 ms.
Test Steps
Attempting to log on to the Mailbox.
We were able to log on to the Mailbox.
Additional Details
Elapsed Time: 594 ms.
Testing RPC over HTTP connectivity to server outlook.office365.com
RPC over HTTP connectivity was verified successfully.
Additional Details
HTTP Response Headers:
request-id: 64e2bf62-0b20-4e36-912d-005c7a017fb4
X-DiagInfo: BY2PR09CA0048
X-FEServer: BY2PR09CA0048
Content-Length: 0
Date: Tue, 21 Apr 2015 04:40:11 GMT
Set-Cookie: ClientId=SKGVNJCDX0OA7M7QPJFWLA; expires=Wed, 20-Apr-2016 04:40:12 GMT; path=/; secure; HttpOnly
Server: Microsoft-IIS/8.0
WWW-Authenticate: Basic Realm=""
X-Powered-By: ASP.NET
Elapsed Time: 25606 ms.
Test Steps
Attempting to resolve the host name outlook.office365.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 132.245.24.82, 132.245.92.34, 132.245.92.194, 132.245.80.146, 157.56.239.194, 132.245.64.146, 2a01:111:f400:2c40::2, 2a01:111:f400:5000::2, 2a01:111:f400:1414::2, 2a01:111:f400:2c2c::2, 2a01:111:f400:1428::2, 2a01:111:f400:4c32::2
Elapsed Time: 42 ms.
Testing TCP port 443 on host outlook.office365.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 61 ms.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Additional Details
Elapsed Time: 223 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server outlook.office365.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US, Issuer: CN=Microsoft IT SSL SHA1, OU=Microsoft IT, O=Microsoft Corporation, L=Redmond, S=Washington, C=US.
Elapsed Time: 121 ms.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name outlook.office365.com was found in the Certificate Subject Alternative Name entry.
Elapsed Time: 1 ms.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US.
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=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE.
Elapsed Time: 36 ms.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer 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.
Elapsed Time: 5 ms.
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 = 2/13/2015 12:38:15 AM, NotAfter = 2/13/2016 12:38:15 AM
Elapsed Time: 0 ms.
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details
Accept/Require Client Certificates isn't configured.
Elapsed Time: 173 ms.
Testing HTTP Authentication Methods for URL
https://outlook.office365.com/rpc/[email protected]:6002.
The HTTP authentication methods are correct.
Additional Details
The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Basic
HTTP Response Headers:
request-id: 64e2bf62-0b20-4e36-912d-005c7a017fb4
X-DiagInfo: BY2PR09CA0048
X-FEServer: BY2PR09CA0048
Content-Length: 0
Date: Tue, 21 Apr 2015 04:40:11 GMT
Set-Cookie: ClientId=SKGVNJCDX0OA7M7QPJFWLA; expires=Wed, 20-Apr-2016 04:40:12 GMT; path=/; secure; HttpOnly
Server: Microsoft-IIS/8.0
WWW-Authenticate: Basic Realm=""
X-Powered-By: ASP.NET
Elapsed Time: 27 ms.
Attempting to ping RPC proxy outlook.office365.com.
RPC Proxy was pinged successfully.
Additional Details
Elapsed Time: 2099 ms.
Attempting to ping the MAPI Mail Store endpoint with identity:
[email protected]:6001.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 47 ms.
Elapsed Time: 5049 ms.
Testing the MAPI Address Book endpoint on the Exchange server.
The address book endpoint was tested successfully.
Additional Details
Elapsed Time: 6447 ms.
Test Steps
Attempting to ping the MAPI Address Book endpoint with identity:
[email protected]:6004.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 218 ms.
Elapsed Time: 4230 ms.
Testing the address book "Check Name" operation for user
[email protected] against server
[email protected].
Check Name succeeded.
Additional Details
DisplayName: Brandon Smith, LegDN: /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon
Elapsed Time: 2216 ms.
Testing the MAPI Referral service on the Exchange Server.
The Referral service was tested successfully.
Additional Details
Elapsed Time: 6271 ms.
Test Steps
Attempting to ping the MAPI Referral Service endpoint with identity:
[email protected]:6002.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 640 ms.
Elapsed Time: 4630 ms.
Attempting to perform referral for user /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon on server
[email protected].
We got the address book server successfully.
Additional Details
The server returned by the Referral service:
[email protected]
Elapsed Time: 1640 ms.
Testing the MAPI Address Book endpoint on the Exchange server.
The address book endpoint was tested successfully.
Additional Details
Elapsed Time: 923 ms.
Test Steps
Attempting to ping the MAPI Address Book endpoint with identity:
[email protected]:6004.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 62 ms.
Elapsed Time: 72 ms.
Testing the address book "Check Name" operation for user
[email protected] against server
[email protected].
Check Name succeeded.
Additional Details
DisplayName: Brandon Smith, LegDN: /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon
Elapsed Time: 851 ms.
Testing the MAPI Mail Store endpoint on the Exchange server.
We successfully tested the Mail Store endpoint.
Additional Details
Elapsed Time: 4286 ms.
Test Steps
Attempting to ping the MAPI Mail Store endpoint with identity:
[email protected]:6001.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 656 ms.
Elapsed Time: 3656 ms.
Attempting to log on to the Mailbox.
We were able to log on to the Mailbox.
Additional Details
Elapsed Time: 628 ms.
=============================================================================

Problems using Outlook 2013 with Exchange Server Small Business Server 2003

Hello,
We have just upgraded our Office suite from Office 2007 Pro to Office 2013 Pro. When I try to configure Outlook 2013 to connect to Exchange Server 6.5 (SMS 2003) I get an error "Outlook 2013 being blocked by current version of Exchange Server".
Outlook 2013 at present is not communicating with Exchange server 6.5
Are there any fixes I have to install on our SMS 2003 server to allow Outlook 2013 to work with SMS 2003 Exchange Server?
Any configuration changes I need to make? Any help is appreciated.
Thx
John G.
John Grace

Hi
Outlook 2013 is not supported with exchange 2003:
http://technet.microsoft.com/en-us/library/ee624351.aspx#section10
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Public Folders no longer visible in Outlook 2007 with Exchange 2010

Hi all,
This is a perplexing problem because I though I had done everything right
About 1 year ago, I migrated my Exch2007 to Exch2010. The 2007 hardware was showing signs of quitting but it hung in there long enough to complete the migration.
All the user mailboxes, OWA, all other functions moved to the new server.
We use legacy Pub Folders and I manually created a Pub folder database and set up all the Pub folders to replicate from 2007 to the 2010. Once replication has taken place, I removed the 2007 replication partner on all the Pub and System folders in
prep for removing the 2007. But then I got busy and never finished removal.
Flash forward to a few weeks ago and the Exch 2007 box goes down hard, RAID containers gone, totally lost. I did not immediately worry since all was still fine with Outlook and Pub Folder Access.
I got around to cleaning things up and after verifying that there was nothing pointing to the old server including the OAB and any PF, I used ADSIedit to remove the reference to the old server in the Exchange Organization. Since then, although I still
see the PF object in the Mgmt Tool, Outlook does not see their existence. OWA cannot see them either.
I have read that GAL problems can cause this so I have recreated this object to see if will help.
Has anyone else faced this situation? I really need to get PF access back...

Here is an update:
When attempting to "Update" the Default Offline Address List, I get the following error:
Microsoft Exchange Error
Action 'Update' could not be performed on object 'Default Offline Address List'.
Default Offline Address List
Failed
Error:
Couldn't find database "Acteon.local/Configuration/Deleted Objects/Public Folder Database
DEL:9f2e6205-6d06-4cc8-91be-423df4248a4c". Make sure you have typed it correctly.
OK

Limitations of SharePoint 2013 integration with Exchange 2010?

Customer using SharePoint 2013 and looking at whether its possible to integrate this with Exchange 2010 and which features would be available / limitations. Looking for a matrix similar to those found in the Good, Better, Best documents available for previous
versions. Nothing available on Recently Published content for SharePoint 2013 yet http://technet.microsoft.com/en-us/library/cc262043.aspx

I haven't seen a specific list, but the three features I've run into that only work with Exchange 2013 are eDiscovery in Exchange, Automatic Task Synchronization with Outlook and the Site Mailbox feature. There is a Legacy Task Synchronization mode
available that will work with Exchange 2010 if you turn off the Farm level feature controlling Exchange 2013 task synchronization. It lets users manually sync specific task lists with Outlook. But there is no task aggregation. I found this
whitepaper helpful for exploring the new features and how to turn them off when using Exchange 2010.
http://www.microsoft.com/en-us/download/details.aspx?id=38799
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Exchange 2013 CAS functionality in coexistence with Exchange 2010 CAS

Hi,
I am planning to migrate Exchange 2010 to Exchange 2013 for 15000 users. We have a pool of 6 CAS 2010 servers added in a single CAS array. So my question is if we introduce a new CAS 2013 server in same site then will it affect CAS traffic anyway ? If we
point our HLB to all CAS servers including CAS 2010 and CAS 2013 so will the CAS 2010 servers wil take traffic or is it only CAS 2013 servers who will take traffic. We will be putting same URLs in CAS 2013 same as CAS 2010. I have read lot of MS articles and
all say that CAS 2013 should be enabled for CAS traffic and it will proxy request to CAS 2010. But I am not sure if we will face any CAS traffic issue whenever we will introduce CAS 2013 servers in same site and traffic will be pointed to CAS 2010 and CAS
2013 both. Is it possible to add CAS 2013 in Exchange 2010 CAS array ? Please guide. Thanks in advance.

For mailbox that exist on Exchange 2010, EXCH2013 CAS will proxy the request to an Exchange 2010 Client Access servers that exists within the mailbox’s local site.
For mailboxes that exist on Exchange 2013, EXCH2013 CAS will proxy the request to the Exchange 2013 Mailbox server that is hosting the active copy of the user’s mailbox which will generate the Autodiscover response.
-->Is it possible to add CAS 2013 in Exchange 2010 CAS array ?
No. CAS Array is no longer exits in Exchange 2013. But concept of a single namespace for Outlook connectivity remains. Please check this and this. In
your case you dont need to worry as you have a HLB in place it will do the job
When a new exchange2013 is deployed Outlook Anywhere has been enabled on all Client Access servers within the infrastructure and the mail.contoso.com and autodiscover.contoso.com namespaces have been moved to resolve to Exchange 2013 Client Access server
infrastructure. In your case it is pointed to both as you have a load balancer in place but the same URL should be configured in exch2013
Make sure you have exchange2010-SP3 minimum as it is the prerequisite requirement for upgarding EXCh2010 to 2013.
Please check the exchange server deployment assistant
tool for moving mailboxes
After moving a mailbox check the URLs. Configure autodiscover,EWS,OAB URLs on exchange2013. Please check this as
well for checking URLs.
I hope you know MAPI/RPC (RPC over TCP) traffic is now replaced with RPC over HTTP/s instead in exch2013.
Thanks
MAS
Please don't forget to mark an answer if it answers your question or mark as helpful if it helps

Sync Sharepoint 2013 task on outlook running on Exchange 2010

Sync SharePoint 2013 task on outlook running on Exchange 2010,Getting error:
"We weren't able to sync your tasks. This could be because your mailbox is on an Exchange server that isn't supported for syncing tasks. Please contact your administrator for more help."..Please
help!!
SharePoint 2010 task list sync with outlook running on exchange 2010 works successfully without any error...But how to do with sharePoint 2013

Hi Mohit,
The "Sync to Outlook" button is a new feature in SharePoint 2013 and is different from the "Connect to Outlook" button in SharePoint 2010, and this feature also needs the Exchange Server 2013 installed in your environment, you can read the following article
for details.
You can get the "Connect to Outlook" button back (like SP2010) by disabling the "Exchange Task Sync feature" from CA without installing Exchange 2013, the following is extracted from the white paper.
"How to disable SharePoint Server and Exchange Server integration.
To disable it, you turn off the Farm Level Exchange Task Sync feature by going to Central Administration -> Manage farm features. This action deletes the timer job and disables the UI integration, bringing back the legacy sync behavior to Outlook. "
http://support.microsoft.com/kb/2876938
http://www.microsoft.com/en-us/download/details.aspx?id=38799
Thanks
Daniel Yang
TechNet Community Support

Problems with a shared calendar using Outlook 2007 and Exchange 2010

Hello all,
We are having a problem with sharing a calendar using Outlook 2007 and Exchange 2010.
I will start with some background. I have just started my position with this company. I have been working with networks for awhile at the small business level. I have not had much production experience with exchange. There is only myself and my supervisor
who has inherited a midsized network which was built by five previous techs that are no longer with the company. Of course, the previous techs did not leave much documentation, so the original hows and whys for our system setup has been lost.
One of the managers has a calendar she shares with some of our users. I believe this calendar has been in use since sometime in 2006. A mailbox was created to hold this calendar to keep it separate from the managers calendar. I am not sure what version
of exchange they were using at that time, but I assume there was one or two migrations of it getting to its current state on our exchange 2010 server. At some point it was observed that the other workers she was sharing with were not able to access it correctly.
I am not fully sure what the original problem was (possibly some people not being able to see or connect to the calendar), but it was decided to give everyone who needed access to this calendar full access permissions through exchange. Correct me if I
am wrong, but I believe that gave everyone connected the ability to do anything with the calendar. Of course the manager was not happy about that. This is where I started working on the problem.
I removed everyone, except the manager who wants to control the calendar, from having "Full Access Permissions". This did have the effect of making some people just able to see the calendar and not make changes. Though there were others that were
able to connect to the calendar who I thought would not be able to. The manager that originally created the calendar did try to manage access to it through the Outlook interface, though it currently does not seem to be fully in effect.
So, to get to the point of what we are trying to do, is there a way to get the original manager back into control of the calendar though Outlook? It would be preferred to be able to keep the history of what they tracked of this calendar, so starting a new
one would be something we would rather avoid. After that, getting all of the users that need to connect to the calendar reconnected with the correct access permissions and making sure they are all synchronized.
I realize this is a big mess, and your help would be greatly appreciated.

Hi Nigel,
How is the impact, just one user or all users, Outlook or OWA?
If just one user, it seems like an issue on the Outlook Client side.
Please trying to re-create new profile to fresh the caches.
Please runing Outlook under safe mode to avoid some AVs, add-ins and firewall.
Found a similar thread for your reference:
Calendar Sharing not available error message
http://social.technet.microsoft.com/Forums/exchange/en-US/d9b33281-d7bb-4608-8025-16fb26643d0d/calendar-sharing-not-available-error-message?forum=exchangesvrclientslegacy
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Outlook 2013 with Exchange 2010

Similar Messages

Maybe you are looking for