Outlook configuration for Exchange online kiosk plan

Hi,
I'm trying to configure outlook for kiosk user and only the mails in inbox is getting download. Mails in other folders are not getting download.
Please help...

Hi,
We have to use POP3 to setup Outlook when you want configure Exchange Online Kiosk in Outlook 2007/2010, and Outlook 2013.
Since this issue is related to Exchange Online, we recommend contact Office 365 team so that you can get more professional suggestion. For your reference:
http://community.office365.com/en-us/default.aspx
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

Similar Messages

Can't figure out how to use Amazon SES as a smart host for Exchange Online

Hi,
I have a problem that is proving very difficult to solve, and I'm hoping someone on here might know a bit more about this.
I am trying to configure MS Exchange Online to route all emails through Amazon SES as a relay server, however the problem is that SES seems to want you to pass it SMTP username and password credentials to authenticate with, and I don't think Exchange Online
allows for this?
I have checked all the options in Outbound Connector section and there doesn't seem to be any place where I can choose SMTP authentication. On Exchange 2013 and on-premise 365 Exchange solution I believe you can do this, but with pure Exchange Online
I'm not sure...
Does anyone know whether this is possible, and if not why Microsoft doesn't allow it / if they might be intending to enable this in the near future?
Thanks a lot in advance!
Tom

Hi,
Since your questions are Exchange Online related, I suggest we also ask it on the Microsoft Exchange Online forum:
https://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
Hope you can get your answer soon.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

MAPI/HTTP for exchange online?

Hi Guys
When Will Microsoft enable mapi/http for exchange online ?
Hope this happens soon :)

You might actually see this consuming more bandwidth.....
And yes, the connect/reconnect/cold start is waaaay faster than RPC/HTTPS
When it is enabled in o365, you will probably see it announced on the o365 Tech Blog.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

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

Configure send connector for exchange online protection

Hello Forum members,
I am trying to configure send and receive connectors for Exchange 2010 to route
on-premises mailboxes to Exchange OnLine Protection. The "help" info MS provides
is for Ex 2013 - and the EAC GUI and config does not lend a close fit to using the 2010
Exch Management Console. How can I configure connectors to properly connect to the Exchange Online Protection?
I have seen where the ip addresses are posted, etc. I am unclear how to configure the properties on the SBS 2011/EX 2010 server.
Any tips will help,
Thanks,
Eric H.
Network and Server Installs

Hello Wesleyhe,
You cannot use AD anything with EOP - if you mean exchange on-line protection.
you have to set a smart host on the SBS server to connect to EOP, you may need to add the EOP server ips to your network config
on the SBS server. the smart host line (for the send connector on SBS server) is something like: yourdomainname-com.mail.protection.outlook.com.
Then you need to configure the outside ip for your SBS server access in the EOP admin area.
Hope this helps.
eholz
Network and Server Installs

Outlook 2011 with Exchange Online

I have just subscribed to Exchange Online, and use Outlook 2011 for Mac as client. Email send/receive is working. However, Contacts and Notes on my Outlook don't sync with Exchange.

Hi,
Since Exchange Online is different from Exchange 2013, I suggest asking Exchange Online Forum for help so that we can get more professional suggestions.
For your convenience:
http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
Also post a thread on Outlook 2011 for Mac Forum:
http://answers.microsoft.com/en-us/mac/forum/macoutlook?tab=Threads
However I also found a KB for your reference:
How to sync calendars in Outlook for Mac 2011
http://support.microsoft.com/kb/2452489/en-us
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Office 365 version for Exchange online archive

hi,
i have a SBS 2011 and i use the exchange 2010 on it. At the moment I use Outlook 2007 to connect to my Exchange mailbox. A few days ago, I signed up for the Office 365 trial version and i am going to switch to Office 365 in a few days. I also have an Exchange
Enterprise CAL to use the online archive functionality.
my question is, what version of Office 365 (for business) do i need to be able to use the online archive in my outlook desktop version?
best regards
thomas

Outlook in Office 365 ProPlus，
Outlook in Office 365 Enterprise E3， Outlook in Office 365 Midsize Business
https://support.office.microsoft.com/en-us/article/Outlook-license-requirements-for-Exchange-features-46b6b7c5-c3ca-43e5-8424-1e2807917c99?CorrelationId=25f2a475-9f26-4920-b8b3-11e2f9fa9592&ui=en-US&rs=en-001&ad=US

Creating a new address list for Exchange Online (Office 365) by two parameters

Good day!
I need to create two new address list in Exchange Online 2013 (Office 365) that users will choose the two parameters.
Address sheet1: No staff
Address Sheet2: Staff
Parameters address sheet not staff:
Parameter 1: Company
It must match the value - MyCompany
Parameter 2: job title
it must be different from the value - Staff
Parameters address sheet Staff:
Parameter 1: Company
It must match the value - MyCompany
Parameter 2: job title
It must match the value - Staff
Problems:
1) Is it possible to filter user mailboxes on the parameter of discrepancy?
2) Can not find the parameter values for the script field job title
https://technet.microsoft.com/ru-ru/library/aa996912%28v=exchg.150%29.aspx
https://technet.microsoft.com/en-us/library/bb738157%28v=exchg.150%29.aspx
While on the side of 365 in the user properties such parameter is:
http://joxi.ru/MAj0Jj7hGyDbme
Company option too.

I got to build a team that I need (describes the necessary conditions)
and successfully held in PS 4.0 after connecting to the office 365:
1) Set-ExecutionPolicy unrestricted
2) $ UserCredential = Get-Credential
(Data Entry Administrator 365)
3) $ Session = New-PSSession -ConfigurationName
Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $ UserCredential -Authentication Basic -AllowRedirection
Import-PSSession $ Session
4)
PS C:\Windows\system32> New-AddressList -Name 'TEST1234' -RecipientFilter {((RecipientType -eq 'UserMailbox') -and ((Com
pany -eq 'Company1') -and (Title -ne 'Student')))}
Name DisplayName RecipientFilter
TEST1234 TEST1234 ((RecipientType -eq 'UserMailbox')
-and (((Company -eq 'Company1...
As a result, the new address list TEST1234 immediately appears. (When creating a new letter in the menu "To"), but on the inside
it is empty (although there is 1 user which is fully consistent with those described in the filter conditions.).
= (
Tried a simple version:
Office365
не отображается в адресном списке.">The same thing - the only user with such parameters in AD -> Office365 is not displayed in the address list.
(After running for a list TEST123 more than two days)
Tell me what could be the problem?

Incremental Sync For Exchange Online Staged Migration

While doing an Exchange Online staged migration, the on-premises mailboxes get synchronized to the cloud, along with the targetAddress attribute being rewriten in the on-premises environment in order for all new mails to be delivered to the cloud. I'd like
more control over the whole process and would like to better control when the "switch" is being done - namely when the user starts using his cloud mailbox instead of the on-premises one.
By using New-MigrationBatch, the migration of the mailboxes can be done so that the targetAddress attribute doesn't get rewritten, allowing for the user to keep receiving new mails on his old mailbox. However there is no incremental sync that happens periodically
(as in the
case for cutover and IMAP Exchange migrations) to allow the cloud mailbox to be kept in sync. Is there a workaround to enable this feature for batches belonging to staged migrations as well ?

Hi,
I recommend you refer to the following articles:
High Availability and Business Continuity
Exchange Online mailboxes are continuously replicated to multiple database copies, in geographically dispersed Microsoft data centers, to provide data restoration capability in the event of a local messaging infrastructure failure. For large-scale failures,
service continuity management procedures are initiated.
Thanks.
Niko Cheng
TechNet Community Support

Prepare schema for Exchange Online

Hi,
My company is going to use Microsoft Exchange Online and I first need to prepare schema for this (that's what I was told).
I have downloaded Microsoft Exchange 2013 and tried to run "setup.exe /PrepareSchema" but it says it needs WMF 3.0 to run the setup. But I have problems with installing it on my windows 2008 R2 SP1 server. Is it ok to try to install WMF 4.0 instead
of WMF 3.0?

Hi,
From your description, I would like to clarify the following things:
1. Exchange Online is different from Exchange 2013.
2. If you want to install WMF 4.0, the Exchange version should be Exchange 2013 SP1, Exchange 2013 is not supported.
Here is a thread for your reference. Please see the System Requirements.
Windows Management Framework 4.0
http://www.microsoft.com/en-us/download/details.aspx?id=40855
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

OIM Support for Exchange Online

Hi,
We are finding out the feasible options for the integration of OIM with Exchange Online.
Any pointers on this.
Regards
Vicky

Hi Kevin,
Thanks for your response.
We are looking at Email Service ( Microsfot Exchange on cloud ). I have seen the architecture of Exchange Cloud in terms of provisioning at microsoft site.
It says that , Microsoft will pull the data from the customer AD, for the accounts using DirSynch. So, will it be sufficient if we provision users only into customer AD Forest.
My understanding from that doc says, they will pull the data from the customer Forest to Microsoft Managed AD forest, which will then link accounts to Exchange on Microsoft managed servers.
Correct me if I am wrong.
Regards
Vicky

Certificate configuring for exchange 2013 and office 365 hybrid deployment

Please advise on what digital certificate requirements for hybrid deployment and to configure it.

Hi sphilip,
If you want to deploy AD FS with Single Sign-On(SSO), we need use certificate to establish secure trust between on-premises Exchange 2013 and Office online.
We can use and configure a trusted third-part CA within all on-premises Exchange 2013 Mailbox and Client Access servers to ensure secure mail transport, more details about
Office 365 Hybrid Configuration Certificate Planning, for your reference:
http://blogs.technet.com/b/neiljohn/archive/2011/08/25/office-365-hybrid-configuration-certificate-planning-adfs-exchange-web-services-owa-oa.aspx
Best Regards,
Allen Wang

DNS Configuration for Exchange 2013

I have a stand alone server 2012 with AD, DHCP, DNS and Exchange on it and started getting DDoS attacks
I installed a firewall had to change the subnet of the server from 10.0.0.0/24 to 192.168.1.0/24 and after re-configuring the Servers IP, DHCP and DNS found that I had no incoming email. (invalid Security Certificate)
I found that mail traffic was directed to the Router instead of Exchange and being rejected with the routers security certificate. I have since fiddled with the DNS so many times I don't know what is right and wrong
Anyone have any ideas where I have gone wrong what is in the tables that shouldn't be there and what is missing.
email address is user.mail.domain.com
Geotrust SSL Security Certificate is mail.domain.com autodiscover.domain.com server01.domain.com
**Forward lookup for domain.com
Same as parent SOA
[28]server01.domain.com, hostmaster.domain.com
Same as parent NS
server01.domain.com
Same as parent NS
ns1.domain.com
Same as parent NS
ns2.domain.com
Same as parent MX
[10]mail.domain.com
Same as parent MX
[20]mail.domain.com
server01 MX [10]mail.domain.com
Same as parent HostA
192.168.1.10
Same as parent HostA
139.130.XXX.YYY
server01 HostA
192.168.1.10
mail HostA 192.168.1.10
mail HostA 139.130.XXX.YYY
localhost HostA
127.0.0.0
Properties SOA ns1.domain.com 139.130.XXX.YYY
ns2.domain.com 139.130.XXX.YYY
server01.domain.com 192.168.1.10
**Forward lookup for mail.domain.com
Same as parent SOA
[1]server01.domain.com, hostmaster.domain.com
Same as parent NS
server01.domain.com
Same as parent HostA
192.168.1.10
Same as parent HostA
139.130.XXX.YYY
Properties of SOA server01.domain.com
192.168.1.10
**Reverse Lookup
1.168.192.in-addr.arpa
Same as parent SOA
[1]server01.domain.com, hostmaster.domain.com
Same as parent NS
server01.domain.com
Same as parent NS
ns1.domain.com
192.168.1.10 PTR
domain.com
192.168.1.10 PTR
mail.domain.com
OWA and Outlook 2013 work incoming and outgoing from within the subnet, both internal emails and external emails
But users off site can't log in to outlook 2013 and get blocked with OWA by invalid security certificate.
**Testconnectivity.microsoft.com results
autodiscover failed
resolved host domain.com successful with both correct IP addresses returned
Port 443 open
SSL Certificate incorrect it is the routers Certificate not the Geotrust certificate.
**This is the real issue, and I can't figure out why
Thanks Alan

Thanks Luke
Yes you are right , I get alternate WAN and LAN Ip addresses when I flushdns
I suspected I had additional entries ans/or wrong entries in the DNS Zones
i reformatted to show up in columns in the post
I hope you can point out which are wrong
**Forward lookup for domain.com
Same as parent----- SOA----[28]server01.domain.com, hostmaster.domain.com
Same as parent----- NS -----server01.domain.com
Same as parent----- NS -----ns1.domain.com
Same as parent----- NS -----ns2.domain.com
Same as parent----- MX -----[10]mail.domain.com
Same as parent----- MX -----[20]mail.domain.com
server01-------------- MX----- [10]mail.domain.com
Same as parent----- HostA --192.168.1.10
Same as parent----- HostA --139.130.XXX.YYY
server01-------------- HostA --192.168.1.10
mail --------------------HostA-- 192.168.1.10
mail --------------------HostA-- 139.130.XXX.YYY
localhost-------------- HostA --127.0.0.0
Properties SOA --ns1.domain.com 139.130.XXX.YYY
----------------------ns2.domain.com 139.130.XXX.YYY
----------------------server01.domain.com 192.168.1.10
**Forward lookup for mail.domain.com
Same as parent----- SOA------[1]server01.domain.com, hostmaster.domain.com
Same as parent----- NS--------server01.domain.com
Same as parent -----HostA---192.168.1.10
Same as parent -----HostA---139.130.XXX.YYY
Properties of SOA server01.domain.com
192.168.1.10
**Reverse Lookup
1.168.192.in-addr.arpa
Same as parent----- SOA-----[1]server01.domain.com, hostmaster.domain.com
Same as parent----- NS-------server01.domain.com
Same as parent----- NS-------ns1.domain.com
192.168.1.10-------- PTR------domain.com
192.168.1.10-------- PTR------mail.domain.com
do I need an autodiscover record?
I setup 2 forward lookup zones domain.com and mail.domain.com
From memory the mail.domain.com was for external access but I don't think that was how it turned out
Thanks

Outlook Clients for Exchange 2013 Prompt for Password

I have a co-existence of versions 2007 and Exchange Server 2013 CU2 and currently have the following problem:
- Customers now where I performed the migration to the 2013 version, when starting Outlook is always asking for password. The settings for Outlook Anywhere are as follows:
RunspaceId : b43cd829-a81f-4b00-bb4d-73389c9df50d
ServerName : EXCH-HTCA13
SSLOffloading : False
ExternalHostname : webmail.first.pt
InternalHostname : exch-htca13.first.pt
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
XropUrl :
ExternalClientsRequireSsl : True
InternalClientsRequireSsl : True
Can anyone help me identify the problem?

Hi,
Agree with Andy,you can change the ExternalClientAuthenticationMethod to NTLM,
In addition, I recommend you refer to the following article:
Users Constantly Prompted for Credentials after Being Migrated to Exchange 2013
Thanks.
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality,
safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Niko Cheng
TechNet Community Support

Configuring for Exchange

We have a Exchange 2007 server (with IMAP enabled) setup in our organisation and I'm trying to setup some users iPod's with exchange.
For example to setup exchange in outlook we type in "examplesvr01" into the Exchange server field and then the users name and hey presto there connected to our exchange system.
Exactly what are we supposed to type into the Incoming/Outgoing Mail Server Host Name field..? I've tried a few different conbinations but none seem to work.
Any Help...?

What barra_240t's response does not state (though it's implied) is that the current version of the IPT/iPhone software *does not* work with MS Exchange servers. So, you can stop trying...and wait for v2.0 in June (which will be a paid upgrade for the IPT).
Hope this helps...

Outlook configuration for Exchange online kiosk plan

Similar Messages

Maybe you are looking for