Outlook 2007 with Exchange 2010SP3 Scheduling assistant "Server unavailable"

Windows Server 2008 R2
Exchange Server 2010
Windows 7 Clients
Outlook 2007(fully patched)
When a user clicks "Scheduling Assistant" in outlook 2007 you immediately get a message popup saying...
"The connection to Microsoft exchange is unavailable. Outlook must be online or connected to complete this action"
I will include a Screenshot when allowed
Outlook is connected and no other issues/symptoms are present. out of office assistant works, everything else works.
You CAN access and use Scheduling assistant from the OWA
I did a wire-shark capture to see if maybe some packet would tell me what was going on however im not sure what i was seeing, its a 3 packet response.
1 0.000000000
xx.xx.xx.Host xx.xx.xx.Server DCERPC
290 Request: call_id: 43, Fragment: Single, opnum: 7, Ctx: 0
Header checksum: 0x0000 [incorrect, should be 0x5066 (may be caused by "IP checksum offload"?)]
2 0.001848000
xx.xx.xx.Host xx.xx.xx.Server DCERPC
274 Request: call_id: 44, Fragment: Single, opnum: 9, Ctx: 0
Header checksum: 0x0000 [incorrect, should be 0x5075 (may be caused by "IP checksum offload"?)]
3 0.203054000
xx.xx.xx.Host xx.xx.xx.Server TCP
54 65082 > 6008 [ACK] Seq=457 Ack=265 Win=255 Len=0
Header checksum: 0x0000 [incorrect, should be 0x5150 (may be caused by "IP checksum offload"?)]

hi,
how u resolved that problem or what AD changes u done?
Thanks Regards,
Pradeep

Similar Messages

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

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 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

How can i sync my calendar in Outlook 2007 with iTunes 11.1.3.8 WITHOUT using iCloud?

How can i sync my calendar in Outlook 2007 with iTunes 11.1.3.8 WITHOUT using iCloud?

your link shows how to sync, i know how to do that.
i specifically wanted to sync my outlook calendar with my phone, not my outlook calendar with icloud calendar.
apparently you have to go into setup on phone and tell phone not to sync calendars with icloud so you can get choice to sync phone via itunes.
thanks anyways for trying.
feel free to reference my solution for similar questions.

Outlook 2007 with Vista 64bit

I'm curious if anyone else is having the same Outlook 2007 with their workstation?
Symptoms:
Sometimes, takes a while to load. will display "(Not Responding)" if fiddled with
Reading pane will sometimes blank grey, or simply display as a single bar with nothing in the pane.
Sometimes, will not send mail (although the settings have been tested to nausea, will send sometimes)
Sometimes, Send/Receive will stall and not recover.
Got the latest service pack. Reloaded the software. Tried the Office diagnostic utility. - not fixed. If anyone would recommend their favorite office help site, that would be nice too.
Solved!
Go to Solution.

For me, it turns out that the solution was to wait for Microsoft to come out with a fix.
Solution: Suffer and wait for Microsoft to eventually release an update that works.
Please also be aware that there are several add-ins that conflict with Outlook 2007.
Take a look at Tools > Trust Center... > Add-Ins. Google any non-Microsoft items to see if there's an issue
Here's a couple of sites that has a few good tips.
http://www.howto-outlook.com/
http://www.howto-outlook.com/
I hate Microsoft. If anyone has a recommendation for other good links, please post.

How to setup microsoft outlook 2011 with exchange server 2007

How to setup microsoft outlook 2011 for Mac with Exchange server 2007?

The folks who set up the Exchange Server should be happy to help you.

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.

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 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.
=============================================================================

Delete Button Disabled in Outlook 2010 with Exchange 2013

I recently switched from a 3rd party mail software to Microsoft Exchange. I have had some users ask me why the Delete button is disabled. I didn't enable any special policy to cause this, and the Delete key on the keyboard will delete messages.
The disabled Delete button I am referring to is in the Home ribbon and the right-click menu for selected e-mail(s). Is this standard behavior for Exchange, and can it be changed?

It so happens that I have an XP VM with Outlook 2007. That having been said, as previously mentioned, before testing, I (thought I) could confirm the same consistent behavior in the following configurations:
WinXP + Outlook 2003
Win7 + Outlook 2010
Each of these systems was using a different user account, and I have tried folderview repairs in EMC to no avail.
Strangely, WinXP + Outlook 2007 does not appear to exhibit the behavior. In this test case, the profile and OST were just created, but switching to folderview or moving the reading pane to the bottom did not affect the behavior.
Given that information, I proceeded to re-verify, and I hadn't checked winXP + Outlook 2003 because the computer in question had been upgraded to Outlook 2010. However, I verified the issue does still exist there. Next, I proceeded to check another
computer that I thought would be WinXP + Outlook 2003, but it had also been upgraded to Outlook 2010. This computer did not have the issue, and this leads me to a new theory about the cause (but no closer to resolution). For the record, of the
three computers (two exhibiting the issue, one not), only one has the Adobe plugin mentioned in my last post in response to Diane Poremsky, so the issue doesn't appear to be related to that.
That said, my theory follows: This is somehow related to IMAP in Outlook 2010. The computers that exhibit the issue were all previously running IMAP in Outlook 2010, and the IMAP PST filse were imported using the MailboxImportRequest feature.
I suspect this is related because of other issues that happen for these accounts. For instance, all new e-mail was only visible in OWA and not Outlook on all folders on these accounts, and I have had to have the users reset filters in the view settings
for each folder individually. I don't remember exactly which filter was somehow imported, but it definitely had to do with IMAP. This may be another red herring, but the behavior is consistent with it. I should also note that this behavior
did NOT exist when they were connected via IMAP to the old (non MS) server. I should also note that the filter behavior is somehow stored on the server (and therefore I imagine the delete button behavior could be as well), because creating a new Windows
Profile (and as such, a new Outlook profile and OST file) on a new computer did not make the IMAP filters go away.

Vista Biz \ DTM 4.7 \ Bold \ Outlook 2007 and Exchange 2003 Nightmare! Help Please

Hi
I am trying to sync my Exchange Pub Folder (Calendar and Contacts) to my BB 9000 and it fails when I select 'MAP' in the DTM sync process.
Vista Biz
DTM 4.7
Outlook 2007
Exchange 2003
Bold
I am local\admin perms and Owner perms on the Exchange \pub folders but it crashes as soon as I select the MAP button.
On my WinXP Pro, using Outlook 2003 and the same exchange it works out of the box, but with Vista and Outlook 07 it crashes. Has anyone experienced this?
Thanks
Karl

It would appear that at least in certain situations Exchange 2003 can't "understand" what Outlook 2007 pushes into the mail store, which is an issue when anything tries to connect via POP or IMAP as the server tries to "render" an Internet standard message, and fails.
Some info here, particularly the bit by Buddha377
http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/c63b871 3-9ef9-4076-a11b-5db08255689b
Sounds like your iPhone sync may be suffering the same way??
P.S. Simply reading a message with OWA can "repair" email messages, I've witness this myself seeing Mail.app show "garbage" for a certain message pulled via IMAP, OWA showing the message fine, then all of a sudden Mail.app showing a perfectly formed message.

Currupted "sent items" folder in Outlook 2007 (on Exchange 2007) causing Outlook to crash.

One user here has a problem when clicking on the "sent items" folder. Outlook hangs for 5 secondes and then crashes. If user logs into OWA, she can
access the "sent items" folder no problem. I thought it was a messege in the folder that was corrupted so I asked the user to move the messages to a temp folder from OWA. She did that, the folder is now empty but Outlook still crashes. Tried cache
mode and uncache.
I tried to delete her sent item folder using MFCMAPI (in the hope the it will recreate a new folder) : right click the folder, selected delete folder, check the
option "hard deletion" and I get
Warning:
Code: MAPI_W_PARTIAL_COMPLETION == 0x00040680
Function lpParentFolder->DeleteFolder(
lpItemEID->cb, (LPENTRYID) lpItemEID->lpb, lpProgress ? (ULONG_PTR)m_hWnd : NULL, lpProgress, ulFlags)
File .\MsgStoreDlg.cpp
Line 991
One more test I did: I copied the sent items folder to a pst, moved the pst to my computer and when I try to open the folder from the PST, my Outlook would freeze
and crash. Isn't interesting?
Am I missing something here? Has someone encounter this problem before? Any other idea on how it could be resolved?
This issue started on Exchange 2003. We are now moving to Exchange 2007. I moved her mailbox to the new server in the hope that any mailbox problem will be filtered
and removed. I still have the issue..
env:
Exchange 2007 running on Win2008
PC:
Windows Vista sp1, outlook 2007 (user was getting same issue under Win2k with Outlook 2003)

Couple steps you may apply...
1. Repair the offline file with a Microsoft utility called SCANOST.exe. I’ve seen this file reside in a number of different locations, mainly within Program
Files. It might be best to search for it with Windows or Google Desktop. SCANPST.exe will also work, though you’ll have to go digging for your outlook.ost, which should be near c:\Documents and Settings\ %profile%\ Local Settings\ Application Data\ Microsoft\
Outlook\ outlook.ost. If your file is significant in size, you’ll save a lot of time with the repair operation by not creating a backup. Because if the repair finishes successfully and Outlook still bombs, you’ll need to.
2. Shutdown Outlook completely, including any runaway outlook.exe processes in the task manager. Open Mail in the Control Panel and before you delete your
profile completely, write down the server settings! There’s no need to worry about backing up your mail as it’s stored on the Exchange server. (Essentially, you’re deleting that outlook.ost when you drop your mail profile.) Now, start Outlook and it will create
a new profile, where you’ll configure the server with the information you wrote down previously.
If steps above doesn’t work or you need to get more variants of .pst restoration, visit...
http://www.filerepairforum.com/forum/microsoft/microsoft-aa/outlook/1503-is-there-any-opportunity-to-recover-huge-pst-file-over-6gb
- multi functional user community where you may discuss methods and cases of .pst corruption
https://www.repairtoolbox.com/how-to-repair-outlook.html
Outlook Repair Toolbox - one of the accessible tools on the market, as a variant in case you can’t recover .pst file via ScanPST or manually solutions

Outlook 2007,Remove exchange account settings move to standalone mode

I have a Outlook 2007 client PC, somehow it attached to a exchange server on my LAN.
I want to remove exchange account settings in Outlook 2007 and move back to standalone mode
I removed the account in the account list, disabled any exhange addons, what else do I need to do?

Hi,
Please go through the steps to remove Exchange account profile.
1. Close Outlook.
2. Navigate to "Start-"Control Panel".
3. Find "Mail",click on it.
4. Click "Show Profiles".
5. Select the Exchange account profile and then click "Remove".
Note: If Exchange account is the default one,then profile name should be "Outlook".
After that,you can add new profile with non-exchange account.
Hope it helps.
Xiu

Outlook 2007 with Exchange 2010SP3 Scheduling assistant "Server unavailable"

Similar Messages

Maybe you are looking for