Outlook 2013 freeze in citrix session

We have Exchange 2013 in DAG and F5 for load balancing.
Very few users (randomly) daily complaints outlook freeze inside citrix.
We do not see any error in event viewer or RPC log of Exchange servers.
Please shed some lights on things which need to be checked
SAH

Hi,
Many people have the same issue, Outlook freeze in citrix environment.
Please check if there is any Add-In for Outlook. If there is , please open Outlook without add-ins to check result.
And you can use Performance monitor to monitor the RPC connections.
Best regards,
Belinda Ma
TechNet Community Support

Similar Messages

  • Exchange Outlook 2013 freezes when deleting shared calendar for employees who have been removed

    Hi,
    I am removing users' shared calendars from my outlook 2013 in exchange environment. The problem is, that the shared calendars belong to users who have left the company and have been removed from the domain, this is causing outlook to freeze because i think
    it's trying to find the entry then delete it, rather than delete it.
    There is no problem deleting a shared calendar for an user who still is in the domain. This seems to be strictly affecting users who have left the domain.

    Hi,
    Generally, if the shared calendar owner is removed from the Exchange environment, the shared calendar which was added before should be removed from Outlook client normally.
    Please use Outlook with Exchange cached mode, and make sure the shared calendar was not added in Advanced tab in Account Settings. Please start Outlook in safe mode and remove the shared calendar to have a try.
    If the issue doesn’t happen in safe mode, please disable the third-party add-ins one by one to find out the cause.
    Regards,
    Winnie Liang
    TechNet Community Support

  • MS Access Freezes and Closes when I save a draft email via Outlook 2013

    I have Access 2013 Office 365.  When I email a report from access via Outlook 2013 I have problems.  Outlook opens fine. If I hit send everything is fine. However if I save the email as a draft Access freezes and then closes after a 10- 15 sec delay.
    The email is saved as a draft in Outlook but very annoying to have to reopen my Database .
    The message I get is : MS Access has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available
    I tried compact and repair but that didn't help. Also tried turned of add ons. That didn't work.
    Never had this problem with office 2010.  What can I do?
    I just discovered the same thing  is happening in Excel and Word.

    Hi all,
    Thanks for visiting our forum and sharing your experience here. It'll be benefited to our communicator.
    Have a good time.
    Regards,
    George Zhao
    TechNet Community Support

  • Outlook Anywhere, Office 2013 + Exchange 2013 freezes

    Hi.
    I'm pulling my hair out with this problem as it seems to make no sense.
    I have a client using outlook 2013 through outlook anywhere to their new server running Exchange 2013. when outlook is opened it seems to work for about 10 mins or so then after that if you go to send an email it freezes and says it trying to contact the
    server. you wait for 10 mins then it works again for a while.
    I've changed the timeout settings on the server and everything, they are currently experiencing this in their Spanish office which connects back to the UK.
    No if they dial up the vpn ( no settings changed at all) and run outlook, it all works perfectly..... No one in the UK office (about 10 users) have any issues its only the 2 people in Spain, and one of them uses the laptop in the UK office that they have
    in Spain with no issues.
    I have a CA certificate from slls so not using a self certified one. however its not a wildcard so I haven't set-up on the external domain dns and instead just manually enter the settings (which works fine)
    Its almost as if after 10 mins some connection drops but then takes ages to reconnect again.
    There are a lot of schannel errors appearing on the machines which suggests they are looking at the wrong ports for connection on a couple of attempts, but the questions is why? and whether this has anything to do with the OA problem.
    If anyone has some fresh ideas or any thoughts i would be very grateful as this is driving me round the bend, and i have 2 other clients who have a very similar set-up but have no issues.
    Router Spanish side is a Comcast router and UK side is a draytek 2820
    Exchange is running on Server 2012 with both the CA and Mailbox roles on the same server.
    heeeellp before I go bald :)

    Hi,
    Please have the users in Spain open Outlook, go to FILE
    -> Account Settings -> Account Settings -> Double click the account name ->
    More Settings -> Connection tab -> Select
    Connect to Microsoft Exchange using HTTP, and click Exchange Proxy Settings, tick
    On slow networks, connect using HTTP first, then connect using TCP/IP
    -> OK.
    We can also have the users in Spain test the connectivity to Exchange via Remote Connectivity Analyzer to find if there's any error.
    https://testconnectivity.microsoft.com/
    Regards,
    Melon Chen
    TechNet Community Support

  • Outlook 2013 send & receive is very slow or freezes

    Hello. I recently purchased Office 2013 to install on my new laptop at the beginning of February. Everything was working fine up until a couple weeks ago. I am having issues in Outlook 2013, specifically I am not getting emails or when I send
    emails they show as being sent but the customer never receives them. I have 2 email accounts setup and both are scheduled to automatically send and receive every 1 minute but even if I hit send & receive manually nothing works. Eventually the send/receive
    window will open and freeze, showing "processing" or that there are 60 minutes left in trying to receive a message! I have never had an issue like this before and I need it to be fixed so I can continue to communicate with my customers! Please help!

    Does it throw any error code? Make sure the internet/network doesn't have any issues? Check whether the same mailboxes can be accessed in their webmail interfaces (say, OWA) and see you don't face any send/receive issues with that?
    Do check whether you can repro the issue by opening Outlook in safe mode or not (Outlook.exe /safe)? If issue is not reproduced, then I would suspect one of the Outlook add-in may be causing this above issue.
    You can check the send/receive groups. For more info, you can refer:
    http://office.microsoft.com/en-us/outlook-help/why-use-send-receive-groups-HA102749372.aspx
    Let me know how it goes.
    DeVa, M.S., {MSFT} Please remember to mark the replies as answers if they help

  • Outlook 2013 running on Parallels micro-freezes with every action

    Hi there, 
    I am experiencing an issue with Outlook 2013 that is having a massive detrimental effect on my productivity. I have tried a number of different fixes but the issue keeps returning.
    Symptoms are that I get a micro freeze and a blue spinning wheel on almost every action I take including opening emails, replying to emails, clicking on a flag, pretty much anything. The freeze lasts for about 5-10 seconds. 
    - I have used 1GB of my 2GB capacity so mailbox is not overloaded. 
    - I am running Parallels Version 10.1.3 on a Macbook Air (mid-2011) with 4GB Ram, 1.6GHz Intel Core i5 and Yosemite 10.10
    - I don't have excessive programs running which would be chewing RAM. 
    - Other programs including other Office programs (OneNote, Word, Excel) are responding just fine, it's just Outlook. 
    This has been a recurring problem. I have tried fixing by:
    - Deleting and archiving folders to minimise size of mail boxes
    - Removing all subfolders from the inbox to separately contained folders in the general mailbox instead
    - Resetting the .OST file
    - Restarting both Windows (Parallels) and Mac. (This actually does work for a while, about a day, then problem returns)
    - Disabling all outlook extensions 
    - Disabling graphics acceleration in Outlook advanced options
    There have been a number of threads on this topic, which I have read, but the answers tend to include suggestions for all sorts of remedies making it difficult to get a definitive fix. Surely others must have experienced a similar problem, and have tried
    all the usual suggested fixes, yet still have the problem? I suspect the problem may be related to something specific to running Office on Parallels?
    I am hoping that someone will be able to please give an enlightened answer, or a suggestion that will provide a fix or workaround, because my productivity is declining rapidly having to wait 6-10 seconds for each email, when typically I send scores of emails
    every day and speed is of the essence. I would even appreciate an honest response along the lines of "This is a common problem with Outlook on Parallels computers and there is no definitive answer" as this will allow me to move on and start using
    a different program.
    Thanks in advance!

    Hi,
    Do you test with an Exchange account? If yes, Switch to Exchange Online Mode, can you send/receive emails properly?
    Please create a new Send/Receive group in Outlook and check if it helps:
    Click File, and then clickOptions.
    Click the Advanced tab.
    In the  Send and Recieve section, clickSend/Recieve.
    Under Group Name, click the group, and then clickCopy.
    Under Send/Receive Group Name, type the new group name, and then clickOK.
    Under Group Name, click the old group name.
    Under both When Outlook is Online andWhen Outlook is Offline, click to clear the check box forInclude this
    group in Send/Receive (F9).
    Click Close.
    Quit Outlook, and then restart Outlook.
    If the above step fails, create a new profile for Outlook and check if the issue occurs in there:
    http://support.microsoft.com/kb/829918
    Thanks,
    Melon Chen
    Forum Support
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please click
    here

  • Sent messages aren't saved in the Sent Items folder in Outlook 2013

    When we send a message in Outlook 2013, a copy of the message should be saved in the Sent Items folder by default. If Outlook doesn’t save a copy of the sent message, it may be caused by any one of the following
    reasons:
    The “Save copies of messages in the Sent Items folder”
    option in Outlook is disabled.
    The save location for sent messages was changed to another folder.
    There is a custom view set on Sent Items folder, or the view on
    Sent Items is corrupt.
    Outlook Data File may be damaged.
    To resolve the issue, use the appropriate method for your situation.
    Enable the Save copies of messages in the Sent Items folder
    option
    To configure Outlook 2013 to save copies of your sent messages in the Sent Items folder, please follow these steps:
    1. Click File tab > Options.
    2. Click Mail on the left pane.  
    3. Scroll to the Save Messages section, select the check box before “Save copies of messages in the Sent Items folder”.
    4. Click OK.
    If it is the replying message that is not saving to the Sent Items folder, we need to disable the “When replying to a message that is not in the Inbox, save the reply in the same folder” option in the location mentioned above.
    If you’re using an IMAP account, please also make sure you didn’t select the “Do not save copies of sent items” in Account Settings. To check this, Please refer to the following steps:
    1. In Outlook, click File tab > Info.
    2. Click Account Settings > Account Settings, and then double-click your IMAP account to open the
    Change Account wizard.
    3. Click More Settings button.
    4. Under Sent Items heading, clear the check box before “Do not save copies of sent items”.
    5. Click OK and click Next to complete the configuration.
    Make sure there is no rule or anything else to redirect sent messages to other folders
    To check if it is caused by Outlook rules, please follow these steps:
    1. In Outlook 2013, click Home tab.
    2. Click Rules > Manage Rules & Alerts.
    3. In the rules list, check if there is any rule that applied to the sent messages may cause this issue.
    In addition, some rules may be corrupt or hidden and we cannot see them from the rules list. We need to use the MFCMAPI tool to find and delete the corrupt/hidden rules. To do this, we can use the following steps:
    1. Download MFCMAPI tool from: http://mfcmapi.codeplex.com/
    2. Start MFCMAPI tool.
    3. Click Session menu >
    Logon, select the Outlook profile you are using and click OK.
    4. Double-click the mailbox that contains the inbox rules that you want to delete.
    5. A new window will open. In the new window, expand
    Root Container or Root – Mailbox, and then expand
    Top of Information Store or IPM_SUBTREE.
    6. Right click on Inbox and select
    Open associated contents table.
    7. In the Inbox window, locate and then right-click the items that have the
    IPM.Rule.Message message class, and then click Delete Message.
    To identify a specific rule, you’ll have to select the rule in the top pane in MFCMAPI and then scroll down in the lower pane and look at the
    Property name(s) column. Find the ptagRuleMsgName property name and check the value against the rule name you were trying to delete in Outlook.
    8. In the Delete Item dialog, select
    DELETE_HARD_DELETE from the Deletion Style drop-down menu.
    9. Click OK.
    Reset the view settings on Sent Items folder
    If you accidently changed the view settings on Sent Items folder, this may cause some sent messages not visible in the folder. To check if you’ve set any view settings on Sent Items folder, please follow:
    1. In Outlook, select Sent Items folder.
    2. Click View tab from the Ribbon.
    3. Click View Settings button. If you notice the
    Reset Current View button is clickable, it means the view settings for Sent Items have been changed before.
    4. Click the Reset Current View button and then check the Sent Items folder again.
    Scan and repair the Outlook Data File
    To repair the .pst file, please follow:
    1. Find and start the Inbox Repair Tool in the following path:
    For Outlook 2013 on a 32-bit version of Windows:
    <disk drive>\Program Files\Microsoft Office 15\root\office15
    For Outlook 2013 on a 64-bit version of Windows:
    <disk drive>\Program Files(x86)\Microsoft Office 15\root\office15
    2. In the Inbox Repair tool, click Browse to locate the PST file by using the Windows file system.
    3. Click Start.
    4. After the analysis scan has completed, it will present you with a scanning report and options for the next step. Click Repair button.
    To repair the .ost file, since this type of data file is a copy of information saved on your mail server, we can just delete the OST file and restart Outlook to re-create a new one.
    For more information about repair Outlook data files, please refer to this article:
    Repair Outlook Data Files (.pst and .ost).
    If you have any comments on this topic, please feel free to post here.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Same problem here, connecting to a Groupwise (not latest) server. Whenever Mail.app 3 tries to upload/save a new messsage to the server, it would not save and completely lose the message!
    I found slightly more information by turning off the "Save to server" option for Sent and Drafts, created a new message that I saved as draft, and then tried to manually move items to the Drafts or Sent folder on the IMAP server.
    The error I received was: The message <message> could not be moved to the mailbox <mailbox>-<account>. The IMAP command "APPEND" (to <mailbox>) failed with server error: APPEND NotJunk.
    To my inexperienced eyes, it looks like the latest version of Mail changed it's default IMAP handling commands that may be incompatible with older IMAP servers. Anyone else have more insight or know how I can get back Mail.app 2.x from Tiger?

  • Frozen out menu ribbon in Word 2013 and cannot preview word documents in Outlook 2013

    I seem to be having a recurring problem with Word 2013 from Office Home Edition single user. When I try to put a caption on a table, the entire document page layout changes from portrait to something close to landscape and then the entire menu ribbon freezes
    out. I usually have to save the file, close and reopen using the open and repair feature as the document only opens in read only after this incidence happens. Since the first time I experienced this in early July, I haven't been able to preview Word files
    in office outlook 2013 and the protected mode feature hasn't worked since then either.
    Can I get some help with this please? I reinstalled, did online fixing and tried a few other fixes to no avail. Could it have started as a result of my installing a trial version of Office Visio which comes as a totally different package from my Home edition?
    Thank you

    ... When I try to put a caption on a table, the entire ...
    Is this the only action that will result in the issue? Does this happen to any Word documents?
    The first thing that I'd suggest you to do is to install any available updates to your system and Office installation, and then verify result.
    Then, please check if you have any add-ins integrated with your Word 2013 (please note that some programs might install add-ins automatically), try in safe mode and see if issue was caused by some add-in conflicts:
    http://office.microsoft.com/en-us/excel-help/work-with-office-safe-modes-HP010354300.aspx
    A Windows clean boot is also worth trying, it will help to determine whether background programs are interfering with your program:http://support.microsoft.com/kb/929135/en-us
    Thanks,
    Ethan Hua CHN
    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.

  • 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&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=cadcom.us</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-sms>
    <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=cadcom.us</EcpUrl-publish>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-photo>
    <EcpUrl-connect>Connect/Main.aspx?rfr=olk&amp;exsvurl=1&amp;Provider=&lt;Provider&gt;&amp;Action=&lt;Action&gt;&amp;realm=cadcom.us</EcpUrl-connect>
    <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tm>
    <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tmCreating>
    <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tmEditing>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;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&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=cadcom.us</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-sms>
    <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=cadcom.us</EcpUrl-publish>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-photo>
    <EcpUrl-connect>Connect/Main.aspx?rfr=olk&amp;exsvurl=1&amp;Provider=&lt;Provider&gt;&amp;Action=&lt;Action&gt;&amp;realm=cadcom.us</EcpUrl-connect>
    <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tm>
    <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tmCreating>
    <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tmEditing>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;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&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=cadcom.us</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-sms>
    <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=cadcom.us</EcpUrl-publish>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-photo>
    <EcpUrl-connect>Connect/Main.aspx?rfr=olk&amp;exsvurl=1&amp;Provider=&lt;Provider&gt;&amp;Action=&lt;Action&gt;&amp;realm=cadcom.us</EcpUrl-connect>
    <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tm>
    <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tmCreating>
    <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tmEditing>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;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&amp;p=customize/voicemail.aspx&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-um>
    <EcpUrl-aggr>?rfr=olk&amp;p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-aggr>
    <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=cadcom.us</EcpUrl-mt>
    <EcpUrl-ret>?rfr=olk&amp;p=organize/retentionpolicytags.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-ret>
    <EcpUrl-sms>?rfr=olk&amp;p=sms/textmessaging.slab&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-sms>
    <EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&amp;exsvurl=1&amp;FldID=&lt;FldID&gt;&amp;realm=cadcom.us</EcpUrl-publish>
    <EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&amp;chgPhoto=1&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-photo>
    <EcpUrl-connect>Connect/Main.aspx?rfr=olk&amp;exsvurl=1&amp;Provider=&lt;Provider&gt;&amp;Action=&lt;Action&gt;&amp;realm=cadcom.us</EcpUrl-connect>
    <EcpUrl-tm>?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tm>
    <EcpUrl-tmCreating>?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tmCreating>
    <EcpUrl-tmEditing>?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=cadcom.us</EcpUrl-tmEditing>
    <EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&amp;exsvurl=1&amp;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.
    =============================================================================

  • AutoComplete not working properly in Outlook 2013

    The AutoComplete List is a feature which displays suggestions for names and e-mail addresses as you begin to type them. These suggestions are possible matches from a list of names and e-mail addresses from the e-mail messages that you have
    sent.
    AutoComplete is a convenient feature when we send an email message, if it suddenly stops working, it becomes a real pain to the sender. If you encountered this problem, you can use the steps below to troubleshoot it and make it work again.
    1. Check if the AutoComplete feature is turned on.
    By default, the AutoComplete feature is enabled. If it isn’t working, of course the first thing to check is whether the feature is enabled. To check it, go to
    File tab> Options > Mail, scroll down to the
    Send Messages section and make sure the “Use Auto-Complete List to suggest names when typing in the To, CC, and Bcc lines” option is selected.
    2. Check if AutoComplete works in OWA
    Since Outlook 2010 and Outlook 2013 doesn’t store nicknames in .NK2 file, it stores the autocomplete cache in the user’s mailbox and caches to a local cache file. So, the OWA uses the same autocomplete list, we can log into OWA and check if AutoComplete
    works.
    If it works in OWA, it means the autocomplete list is OK. The problem lies in the Outlook client side. If the autocomplete doesn’t even work in OWA, the autocomplete list could be corrupt.
    3. An Add-in may cause AutoComplete to not work correctly.
    Problematic add-in may cause a number of issues in Outlook. If an add-in cause Outlook to crash, the AutoComplete lists could be affected and become corrupt.
    To determine if a problematic add-in is the culprit, go to File > Options > Add-ins, disable all add-ins and then check if the problem continues. If the problem is gone with all add-in disabled, we can try re-enabling add-ins one-by-one to isolate
    the problematic add-in:
    (1) Start Outlook.
    (2) On the File tab, click Options,
    then click Add-Ins.
    (3) In the bottom of the Outlook Options dialog box, make sure the
    Manage drop-down shows COM Add-ins, and then click
    Go.
    (4) In the COM Add-Ins dialog box, select to enable an add-in and then click
    OK.
    (5) Repeat step 4 until you have all of the required Outlook functionality and Outlook remains stable.
    If Outlook becomes unstable after re-enabling a particular COM add-in, disable that COM add-in and then contact the add-in vendor to see if they have an updated version that is more stable with Outlook.
    For detailed steps about this, you can refer to the following KB article and look at the “Re-enabling COM add-ins one-by-one” section.
    http://support.microsoft.com/kb/2934538
    4. Reset the AutoComplete list.
    If AutoComplete is enabled but still not working in OWA, it could be that the corruption within the AutoComplete list is causing auto-complete not to work correctly. You’ll need to manually delete the AutoComplete list to fix the issue.
    Note: You will lose all addresses stored in AutoComplete.
    If there is only one or several AutoComplete entries are corrupt, we can remove them by clicking ‘X’ or pressing
    Delete key.
    If all entries are corrupt, we can use one of the following two methods to delete the AutoComplete lists:
    Method 1: Use the Empty Auto-complete List button.
    1. Open Outlook.
    2. On the File tab, click Options > Mail
    tab.
    3. Under Send Messages, click Empty Auto-Complete List.
    It’s also recommended to untick the “Use Auto-Complete List to suggest names when typing in the To, Cc, and Bcc lines”.
    4.  Restart Outlook and tick the “Use Auto-Complete List to suggest names when typing in the To, Cc, and Bcc lines” box again.
    Test if the issue persists.
    Method 2: Use the /CleanAutoCompleteCache switch.
    1. Exit Outlook.
    2. Press Windows key + R to open the Run command.
    3. Type Outlook.exe /CleanAutoCompleteCache in the Run box and press
    Enter.
    5. Reach the maximum number of AutoComplete entries
    Outlook limits the number of entries that you can save in the AutoComplete list. If you find some names unexpectedly removed from your autocomplete list, you may consider this situation.
    Outlook 2013 has a limit of 1000 entries for the AutoComplete list. After you reach this limit, Outlook uses an internal algorithm to determine the best names to remove from the list. It does this based on a usage weighting. To avoid
    this situation, you can use one of the following two methods:
    Method 1: You can manually remove some AutoComplete entries that you no longer use. We can remove them by clicking ‘X’ or pressing
    Delete key as we mentioned in portion 4.
    Method 2: You can change the limit for the AutoComplete list by modifying the registry.
    Because this configuration is untested, we do not recommended it. If you have a larger AutoComplete list, you could also lose a larger number of cached entries if your AutoComplete cache becomes unusable because of corruption. Given this disclaimer,
    you can use the following registry data to increase the AutoComplete list limit in Outlook.
    Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these
    steps carefully. For added protection, back up the registry before you modify it.
    1. Exit Outlook.
    2. Start Registry Editor. Press the Windows key, type regedit and then press
    Enter.
    3. Add the following value:
    HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\AutoNameCheck
    DWORD: MaxNickNames
    Value: Type the number in
    decimal form.
    Note: Try increasing the limit by only a marginal amount to test the new limit. For example, to create a 20 percent increase in the limit in Outlook 2013, you would specify 1200 for the
    MaxNickNames value.
    4. Exit Registry Editor and restart Outlook.
    More information
    To avoid the risk of losing your AutoComplete list entries, it’s recommended to back up them regularly. In Outlook 2013, the AutoComplete list entries are stored in a hidden message in your default message store. To back up the entries, please follow
    these steps:
    1. Exit Outlook, and then close Outlook Web Access or Outlook Web App (OWA) on all workstations that are connected to your mailbox.
    2. Download and install MFCMAPI here:
    http://mfcmapi.codeplex.com
    3. Run mfcmapi.exe.
    4. Click Session > Logon.
    5. Select your profile, and then click OK.
    6. Select the data file that use your email address as the filename, and then double-click it.
    7. Expand Root Mailbox, and then expand IPM_SUBTREE.
    8. Find Inbox and right-click on it, and then click Open Associated Content Table.
    9. In the newly opened MFCMAPI window, under the Subject column, right-click the item that has the subject
    IPM.Configuration.Autocomplete, and then click Export Message.
    10. In the Save Message To File window, select
    MSG file (UNICODE) from the drop-down list, and then click
    OK.
    11. Select a folder location to which you want to save the message, and then click
    Save.
    If you have any questions and comments on this topic, please feel free to post here.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Hi,
    I'm marking the reply as answer as there has been no update for a couple of days.
    If you come back to find it doesn't work for you, please reply to us and unmark the answer.
    Regards,
    Melon Chen
    Forum Support
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please click
    here

  • Outlook 2013 XLS Attachments cannot be opened in Excel 2013 due to Trusted Center restrictions with Outlook Secure Temp Folder

    Dear all,
    I'm having some serious issues with Office 2013's Trusted Center settings. In Outlook 2013 XLS Attachments cannot be directly opened in Excel 2013 with double-clicking due to Trusted Center restrictions for Excel 2013 regarding Outlook's Secure Temp Folder.
    I tried to adjust the corresponding Office 2013 Administrative Template within my GPOs but to no prevail.
    I did find out that Outlook 2013 places an attachment within the Outlook Secure Temp Folder located at "C:\Users\a.ollischer\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.Outlook\PPIU10RW” before passing it to Excel 2013 in order to
    open it. It fails due to not trusting this location though I added the corresponding path to my Trusted Locations.
    What can I do in order to make this work without having to tediously save each and every attachment to "My Documents" prior to opening it? Any help would be greatly appreciated.
    Alex
    Alexander Ollischer Diplom-Wirtschaftsinformatiker (FH) Citrix & Microsoft Certified Engineer (CCEA, CCEE, MCSA, MCSE, MCDBA, MCTS) Afontis IT+Services GmbH Baierbrunner Straße 15 81379 München Deutschland Telefon (089) 74 34 55-0 Fax (089) 74 34 55-55
    mailto:[email protected] http://www.afontis.de http://www.itganzeinfach.de Amtsgericht München, HRB 109 005 Geschäftsführer: Thomas Klimmer

    Hi Maurice 7785,
    Deal and customize attachment security behavior to access such kind of blocked file format. Usually, Outlook does not allow users to open such unsafe type of attachments. It means they are blocked them by default, so you need to unblock such items using REG
    values.
    Take more help from the similar thread:
    http://social.technet.microsoft.com/Forums/en-US/53563c4b-d27f-4866-a5a8-95eb1ad1a3e6/hide-attachements?forum=outlook
    Note: Improve community discussions by marking the answers helpful otherwise respond back for further help.
    Thanks
    Clark Kent

  • Outlook 2013 is crashing almost immediately upon opening it, on multiple computers.

    So, I've got this client.  He's a lawyer, he runs a small law office with four employees to help him in his day-to-day work.  I'm his IT guy, and I recommended that he purchase Office 365.
    I am beginning to regret making that recommendation.
    Now, obviously, in a small law office, e-mail is a pretty essential part of the office workflow.  The lead guy usually corresponds with his office from his home office 45 miles away.  He does so via e-mail.  He's not exactly a stellar typist,
    either, so much to my chagrin, he's more-or-less stuck with Outlook.  If he wasn't so dead-set on using handwriting and ink, I would have him using Mozilla Thunderbird in a heartbeat, because my experience with Outlook tonight has been unbelievable. 
    Thunderbird downloaded, and displays 10,000+ e-mails without skipping a beat, and it's free.  Your product costs $100/year, and is crashing on EVERY SINGLE MACHINE.
    Each employee has their own IMAP e-mail account from our webhost, InMotionHosting.  My client has three IMAP e-mail accounts -- his main, public-facing account, his internal private correspondence account, and an account to which all newsletters and
    such are going to.  Each employee has everyone else's e-mail account on each of their machines, so they can all easily correspond with eachother and keep track of eachother's progress on one matter or another.
    The problem:
    I fire up Outlook, at which point, it begins to Send/Receive from all accounts.  This lasts about a minute, before I am informed that "Microsoft Outlook has stopped working."  If I try to click on ANY other inbox, again, Outlook crashes. 
    I have tried outlook.exe /safe.  I have tried outlook.exe /cleanviews.  I have ensured that I have the latest Windows updates.  I have ensured that I have the latest Office updates.  I have tried the ScanPST.exe utility.  I have tried
    deleting my client's profile, and manually re-adding each and every e-mail account.  I have tried a repair install of Outlook.
    Nothing.  Works.  Eventually, it gets to a point where Outlook just crashes, and will not stop crashing whenever I open it.  I can only hope that this is happening to millions of other users, and the woeful lack of action on Microsoft's part
    will lead to someone, ANYONE, presenting a valid alternative to Outlook.  Your monopoly on office productivity software is obvious to anyone who uses these.

    Hi, in case the antivirus software conflicts with Outlook, please disable your security AVG/Firewall, especially the mail scanner module to check whether it would happen again.
    For the further steps, please perform a clean boot to troubleshoot the problem:
    http://support.microsoft.com/kb/929135/en-us
    You may also try Selective Startup to identify problems with conflicting applications.
    We can find more information about "Outlook 2010 or Outlook 2013 not responding, hangs, freezes or stopped working" in the link below, in which you can find some possible reasons and the selective startup steps
    http://support.microsoft.com/kb/2652320
    I hope the suggestion is helpful.
    Regards.
    Melon Chen
    TechNet Community Support

  • Items not visible in Cached Exchange Mode Outlook 2013

    Outlook 2013, exchange 2010 14.2.247.5. I know it's an older version and I'll update if I need to. 
    So this is a tough one. I noticed one day while on a conference call that I was not receiving into my inbox an email that was just sent to me with a power point presentation. When I took it out of cached mode I saw the emails, 3 that were sent in total.
    So I toggled cached mode, online mode a few times and adjusted the sync period and they started showing up in my inbox in cached mode.
    Problems never go away that easy!!!!!!
    So today I went into a shared account and in a particular folder there were missing items. Mostly items with attachments. There were a few emails listed about 15 or so but there are close to 2,000 emails in that folder mostly all with attachments. I deleted
    the OST and there is no difference, still the same number of emails as before.
    Tried the toggle routine but that didn't have any effect.
    So I right click on the folder and go to properties and click the synchronization tab. It says "Last synchronized on: Never" , though there are items displayed, even after deleting the OST. It also says "Server folder contains 2,007"
    and "Offline folder contains 12".
    So I click filter and more choices and none of the options will allow me to sync all types of emails so I chose "Only items with:" and selected "one or more attachments".
    All the emails with attachments are now visible and now the properties still says "Last synchronized on: Never" but now "Server folder contains: 2,007" and "Offline folder contains: 1,998".
    Well I then clear the filter and low and behold, "Last syncronized on: Never" "folder contains: 2,007" and "Offline folder contains:" wait for it..................     "2,007"! And new items with attachments
    are coming in.
    WHAT THE _____. This is BAD because I am tasked with rolling out Office 2013 and caching is a must for my environment! But I cannot go live with such a bug or misconfiguration.
    I've seen a few threads around the interweb about similar situations but nothing very clear and no real troubleshooting details.

    Ok, I did more digging this time on the exchange server. I get see this error in the event viewer.
    Log Name:      Application
    Source:        MSExchangeIS
    Date:          5/2/2014 1:59:24 PM
    Event ID:      9646
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      contoso.com
    Description:
    Mapi session "5fa396f3-d773-457a-8cfb-1e4d49bff426: /o=/ou=First Administrative Group/cn=Recipients/cn=myself" exceeded the maximum of 500 objects of type "objtFolder".
    So Why is this happening. I read it will cause all kinds of sync problems. Is it because I have a whole bunch of shared accounts in my folder list? I know I certainly don't have 500 folders!
    I also just stumbled across this sub folder "Sync Issues" and "Local Failures" when looking at the number of folders I have and a whole bunch of errors.
    13:43:34 Synchronizer Version 15.0.4605
    13:43:34 Synchronizing Mailbox 'Me'
    13:43:35 Synchronizing local changes in folder 'Sync Issues'
    13:43:35 Uploading to server 'exchagne.contoso.com'
    13:43:35 Error synchronizing message 'Synchronization Log: '
    13:43:35                               
     [80040305-54A-4DE-324]
    13:43:35                               
     Your server administrator has limited the number of items you can open simultaneously. Try closing messages you have opened or removing attachments and images from unsent messages you are composing.
    13:43:35                               
     Microsoft Exchange Information Store
    13:43:35                               
     For more information on this failure, click the URL below:
    13:43:35                               
     http://www.microsoft.com/support/prodredirect/outlook2000_us.asp?err=80040305-54a-4de-324
    13:43:35 Moved a message that failed synchronization to 'Local Failures'. Message subject -> 'Synchronization Log: '. You can view this message in your offline folder only.
    13:43:35 Done

  • Online Archives for Outlook 2013 do not appear in Outlook 2013 running on Terminal Server

    Hello,
    We are currently attempting to get our users away from using PST files and instead use the Personal Online Archive feature but have come across a problem
    Environment
    Windows 2008 R2 Remote Desktop Services (Terminal Server)
    Office 2013
    Citrix 6.5 XenApp
    So on the Exchange side I went through the steps of setting up my PST use as a guinea pig for testing.  I was able to setup the Archive database, enable archiving on my mailbox, and import my PST into the Archive database.  
    I then opened Outlook 2013 on my stand-alone PC and there was my Online Archive. Great!
    I then double checked and also saw it on the OWA site on the Exchange server.  Super!
    I finally logged into our RDS (Terminal) server and opened Outlook 2013 there.  But the Online archive was not there.  Hmmm..
    I did some researching and this article about Outlook 2010 suggested it was a permission issue:
    http://social.technet.microsoft.com/Forums/office/en-US/1e8d5d4b-e26b-4be6-b646-eb6e796c6295/exchange-2010-mail-archive-missing-in-outlook-2010-shows-in-owa?forum=outlook
    So I ran through those steps in Powershell but no change.
    I also don't think it's a licensing issue because the license I have on my stand-alone PC is the same volume license keys (MAK) as on my Terminal Server.
    Soo... I'm a bit stuck and was hoping for some help.  I can't proceed with migrating other PST files to the online archive until I get this resolved.
    Thanks

    Hi,
    In theory,
    Outlook reads the
    msExchDelegateLink attribute of the user in AD to display the additional mailbox (Online Archive folder).
    Since the standalone client can display the archive mailbox properly, it seems this attribute is available in AD. I suspect the issue locates on the way that the terminal
    clients access the server. I suggest we check whether the client has properly permission to connect to AD when accessing remotely.
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Outlook 2013 - cannot use RoomLists and Suggested Times

    Hi,
    maybe someone has a clue on what is wrong here.
    In OWA, we can use the new features RoomList and Suggested Rooms when using the Calendar Assistant to plan a new meeting. The room list can be first be chosen, and the fields for the rooms are then populated as expected, you can choose one of the rooms.
    The following is true for every Outlook Session on PCs/virtual Clients, they are configured to use Online Mode: In Outlook 2013, when using: New Meeting - Scheduling Assistant, the feature "Choose an available room" stays complete empty and
    does not show the room list. Also the box below that, labeled "suggested Times", does not load or display content. Instead, an error message is displayed in it: "Suggestions cannot be provided because free/busy data could not be retrieved."
    Laptops use the exact same Outlook version, but run in cached mode. Here, if you deconfigure "Communication using http" in the OL profile, the lookup for suggested times works _once_ until Restart, then the button is automatically added, the
    profile automatically made good again, and the suggestion function is broken again.
    If you deconfigure the button "Connect to Microsoft Exchange using http" in the Outlook Profile under the connection tab on an _online mode PC_, the profile is broken and not automatically made good again. So no temporary workaround is possible
    here.
    We do not run policies that may keep Outlook 2013 from using the functions. In fact we do only rule cached or online mode.
    Our Room List is free of special characters and short enough, so no problems that other people have found in their environments.
    We have found some older articles reporting broken functionality, when applying or not applying hotfixes. We have checked several of that and it is not the source of our problem.
    Also, we are currently within one domain, so no complicated setup using one or more forests or even other domains, configuration of free/busy accounts should not be an issue here.
    Our best guess is it may have to do with using Exchange webservices or MAPI for the connection, see both ways described communicating over http or not above, but we have not found an error or wrong configuration here.
    Can you please advise on where to search next?

    Hi,
    Which version of Exchange server are you using?
    Does the free/busy information display correctly if we click the Rooms button and select a room from GAL?
    Are you trying to start a meeting in which either the Start time or the
    End time is outside your working hours? If this is the case, this issue may happen. Please have a look at the following KB article and check if it applies:
    http://support.microsoft.com/en-us/kb/2932395
    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]

Maybe you are looking for