Client side disabling of Outlook anywhere in Outlook 2013

Hi
Our admins recently had to disable external access for Outlook while keeping ActiveSync for Mobile Clients working. This was done by placing the autodiscover service (autodiscover.ourexternaldomain.com) behind a TMG with two factor authentication, and also
putting our mail.ourexternaldomain.com behind the same TMG. So, Outlook from outside the network can't connect anymore (it will show you the login/pass prompt but what it wants is the two factor credentials, not your domain credentials.. so essentially you
can't connect anymore), and mobile client still work.
In addition, they've disabled the "Outlook anywhere" options (specifically, "Connect to Microsoft Exchange using HTTP" is not only grayed out, it is forced disabled) by GPO.
Unfortunately, that doesn't work for the handful that's already using Outlook 2013. There, even when the "Connect to Microsoft Exchange using HTTP" option is unchecked, the client will query autodiscover.ourexternaldomain.com, and eventually gets
the response containing not only the EXCH protocol (which contains the internal urls), but also the EXPR protocol containing the public urls. That in turn re-enables "Connect to Microsoft Exchange using HTTP", so now clients, even when inside the
organization will try to access the mail.ourexternaldomain.com which is behind the TMG, resulting in perpetual login prompts being displayed (the login actually comes from the TMG, not Exchange).
So, is there a way to force disable "Connect to Microsoft Exchange using HTTP" for Outlook 2013, preferably without changing anything on Exchange and the GPO. I guess I'm looking for the registry key that is set for outlook 2010. I checked up on
the GPO for Outlook 2010 and it seems it sets HKCU/Software/Policies/Microsoft/Office/14.0/Outlook/RPC/ProxyServerFlags = 0. Doing the same for Outlook 2013 (so using the Office/15.0/Outlook/RPC key) results in outlook no longer being able to connect altogether.
When I manually remove the checkbox and restart Outlook, it first connects using the internal url, then after getting autodiscover it sets the checkbox "Connect to Microsoft Exchange using HTTP" again, and since the external url can be resolved
from inside the network, I get the password prompts again even from inside the corporate network.
Is there a registry key combination that keeps outlook connecting but never using the http proxy?

Hi Stephan,
How about the suggestion from Ed.
Feel free to contact me if there is any update.
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Similar Messages

Can't see the MS Outlook add-in side pane with Outlook 2013

We are on Outlook 2013 and I can't find a way of showing the side panel for the Cloud for Customer Outlook add-in. Everything seems to work fine with the add-in like exchanging emails, appointments, activities with the exception of the side pane which is not visible.
Does anybody know if there is any setting in Outlook to control it? Is Microsoft Outlook 2013 fully supported?
Thanks

Sorry Thierry if I wasn't clear enough.
I meant the Add-Ins tab in the Ribbon, not the Options:
SAP does provide the functionality to hide the pane, on the bottom right you can see the top of the pane and there is an X. It can close it but the add-in stays on.
Then in the Ribbon you can activate the "Add-Ins" tab and you will have the SAP Cloud for Customer menu command.
This is what I meant in my initial reply by saying that I do that often. I hide the pane and reactivate it by simply clicking on that button highlighter in black above.
At least in it's in Outlook 2010 but like you said in your initial post, maybe it is not available in 2013. Partho Guha will be able to confirm.
JB.

Disabled components enabled on client side don't update

If I set a component in my jsp as disabled, such as a checkbox, it shows up on the client side disabled as one would expect.
However, if I use javascript to enable it, and change it's value, then submit the page, the value is never updated as you would expect.
What's the scoop?
Thanks,
Mike.

C> If I set a component in my jsp as disabled, such as a checkbox, it
C> shows up on the client side disabled as one would expect.
C> However, if I use javascript to enable it, and change it's value,
C> then submit the page, the value is never updated as you would expect.
Here's one possible solution until we can figure out something more
clean.
You're using client JavaScript to modify the enabled/disabled state of a
component in the page, and you want that setting to be reflected when
the page is processed by JSF, right? Well, have you client javascript
generate a hidden field containing the enabled/disabled state of the
component. You install a PhaseListener for the before
ApplyRequestValues phase that looks for the hidden field and modifies
the component accordingly.
This isn't as hacky as it sounds when you consider that you can use such
a "before" phase to handle any and all JS mods and apply them to the
component tree before any decoding occurrs.
Ed JSR-252 Spec co-lead

Unable to expand public folder in Outlook 2013 and Exchange 2013 CU6

Hello,
we have just migrated Exchange 2010 to 2013. Everything works great, except public folders, which we are not able to expand in Outlook 2013. Public folders can be added to OWA without any problem, so just the Outlook 2013 is a problem (we never tried any
other version, as all the e-mail clients installed here are Outlook 2013).
The public folders are visible under node Favorities in Outlook 2013, but whenever we click any folder, the Public folders disappear completely from the left navigation pane or the message is shown on the right pane, that the public folder cannot be opened.
When Outlook is started, a dialog is sometimes opened, which contains prefilled Microsoft exchange server, mailbox, button Check name, which is disabled. The only thing which can be done with that dialog is clicking the button Ok.
Any help is appreciated, the desperation level starts to be reaching max threshold.
Kind regards,
John.

Thank you for your quick response. I have tried removing and creating new Outlook profile many times, without any effect.
1) When I switch to the online mode, only the node All Public Folders is displayed in the left navigation pane and after I start the Outlook the dialog mentioned above is displayed. The node Favourities is not visible.
2) In offline node, node App Public folders is visible and whenever I click it, message "Cannot expand the folder" is shown. After checking Download favourities, the list of public folders is available, but whenever I click any folder, it shows
"We didn't find anything to show here." and "The folder is up to date." in the bottom status bar. The content is rendered correctly in OWA and these public folders contain many e-mails and subfolders. None of these is rendered in Outlook.
Thanks in advance for any tips and inspiration, we start to run out of ideas. I am more than sure that it will be something simple, but we can't still figure it out.

[Outlook 2013] Apps for Office and Internet Explorer 11 (IE11)

We have the following configuration:
Windows 7 Professional,
Internet Explorer 11,
Microsoft Office 2013 (32-bit),
Microsoft Exchange 2013 CU6,
Symantec Enterprise Vault 11.
Patch level Microsoft Until 03-oct-2014, so very very recent.
What is the problem, in Exchange its possible to use "Office Web Apps" for integration with OWA. This works very good and we dont have any problems with OWA and the Office Web Apps within OWA Enterprise client.
But, in Outlook 2013, almost every "App for Office" crashes with a popup from Internet Explorer 11. When we open the App, we get a loading.... and after a while A popup with the message "Internet Exporer stopped working".
This is with every App i tested. And it can be reproduced.
What we tried:
Proxy settings;
Re-install Office 2013;
Internet Zone settings;
Browser compatibility modus with zones;
Reset internet explorer settings;
Various reg-hacks for IE security;
GPO settings for untrusted locations of Office Web Apps.
And lucky? No.
So we went back to IE9, and it works like a charm. No problems at all. But Unfortunately, IE9 is not an option due to company apps written for IE10+.
But when it works outside Outlook 2013 in IE11, but not inside outlook with IE11, there must be a problem somewhere with Outlook 2013/IE 11 integration. And actually, the currents Apps we don't need in Outlook 2013 (until snd quarter 2015, then we need them).
So for this time we configured "Block Apps for Office" GPO setting and depoyed it. And... In Every Office components Apps are disabled, but NOT in Outlook. So the GPO is not working for Outlook.
How to solve?

Here the procesmon dump where IE actually crashes...
0 ntoskrnl.exe MmUnmapViewInSessionSpace + 0x7a0 0xfffff80002e3d140 C:\WINDOWS\system32\ntoskrnl.exe
1 ntoskrnl.exe RtlSetSaclSecurityDescriptor + 0x4e5 0xfffff80002cf339d C:\WINDOWS\system32\ntoskrnl.exe
2 ntoskrnl.exe SeQueryInformationToken + 0xc48 0xfffff80002d8d878 C:\WINDOWS\system32\ntoskrnl.exe
3 ntoskrnl.exe ObOpenObjectByName + 0x306 0xfffff80002d8ea96 C:\WINDOWS\system32\ntoskrnl.exe
4 ntoskrnl.exe ObGetObjectSecurity + 0x57c 0xfffff80002d6079c C:\WINDOWS\system32\ntoskrnl.exe
5 ntoskrnl.exe ObGetObjectSecurity + 0x2a4f 0xfffff80002d62c6f C:\WINDOWS\system32\ntoskrnl.exe
6 ntoskrnl.exe KeSynchronizeExecution + 0x3a23 0xfffff80002a90e53 C:\WINDOWS\system32\ntoskrnl.exe
7 ntdll.dll ZwOpenKeyEx + 0xa 0x7781220a C:\Windows\System32\ntdll.dll
8 kernel32.dll GetSystemTimeAsFileTime + 0x232 0x775b3632 C:\Windows\System32\kernel32.dll
9 kernel32.dll GetSystemTimeAsFileTime + 0x575 0x775b3975 C:\Windows\System32\kernel32.dll
10 kernel32.dll RegOpenKeyExW + 0x1d 0x775b3a3d C:\Windows\System32\kernel32.dll
11 advapi32.dll RegOpenKeyExW + 0x13 0x7fefe924e43 C:\Windows\System32\advapi32.dll
12 iertutil.dll Ordinal650 + 0x7e4 0x7fefda3b054 C:\Windows\System32\iertutil.dll
13 iertutil.dll Ordinal650 + 0x853 0x7fefda3b0c3 C:\Windows\System32\iertutil.dll
14 iertutil.dll Ordinal63 + 0x77c0 0x7fefda3a800 C:\Windows\System32\iertutil.dll
15 ieframe.dll Ordinal231 + 0xe4c7 0x7fee5753497 C:\Windows\System32\ieframe.dll
16 ieframe.dll Ordinal170 + 0x8124 0x7fee56e2dc8 C:\Windows\System32\ieframe.dll
17 ieframe.dll Ordinal170 + 0x80ab 0x7fee56e2d4f C:\Windows\System32\ieframe.dll
18 ieframe.dll Ordinal170 + 0x8053 0x7fee56e2cf7 C:\Windows\System32\ieframe.dll
19 ieframe.dll Ordinal218 + 0xd83 0x7fee57ccc83 C:\Windows\System32\ieframe.dll
20 ieframe.dll DllUnregisterServer + 0x1174 0x7fee56a23a4 C:\Windows\System32\ieframe.dll
21 user32.dll TranslateMessageEx + 0x2a1 0x776d9bd1 C:\Windows\System32\user32.dll
22 user32.dll TranslateMessage + 0x1ea 0x776d98da C:\Windows\System32\user32.dll
23 ieframe.dll DllUnregisterServer + 0x15b 0x7fee56a138b C:\Windows\System32\ieframe.dll
24 ieframe.dll Ordinal159 + 0xa522 0x7fee56d8cf2 C:\Windows\System32\ieframe.dll
25 ieframe.dll Ordinal159 + 0xaae6 0x7fee56d92b6 C:\Windows\System32\ieframe.dll
26 ieframe.dll Ordinal159 + 0xaa19 0x7fee56d91e9 C:\Windows\System32\ieframe.dll
27 kernel32.dll BaseThreadInitThunk + 0xd 0x775b59ed C:\Windows\System32\kernel32.dll
28 ntdll.dll RtlUserThreadStart + 0x21 0x777ec541 C:\Windows\System32\ntdll.dll

Outlook 2013 does not redirect emails to an external email address

I'm trying to redirect incoming outlook emails to my Hotmail account (or gmail) When I set a rule in ECP for my outlook account, it works. However, if I set a local rule from Outlook 2013 Desktop client, I receive in outlook 2013, but it does not redirect
(or forward) to my Hotmail or any non organization email address.
Is there something I should do on server side?
Thanks.

Hi,
I would suggest you to create the corresponding mail contact and select this from the outlook for the redirection rule
Regards from Visit ExchangeOnline |
Visit WindowsAdmin

Microsoft Office Outlook 2013 Synchronies, network bandwidth jammed Problem.

I have installed Microsoft Office Outlook 2013 (Standard Edition) in an about 5-6 Laptops, and I am facing issue that while synchronization is going on, my office network bandwidth is being affected. It utilises huge network bandwidth, and because
of that network gets jammed. I have configured using IMAP protocol and using my gmail account in that.
Can any one help me to resolve this issue.
Thanks in advance,
DIPAK AHIR.

Hi,
For your first question : YES network issue happen to all Laptops.
I will explain you the scenario, We are having some where about 80 machines (Including Desktops and Laptops) in our office network, all are working under same internet network. Out of this 80 Users We have 5-6 Laptop users who are using Microsoft
Office Outlook 2013 (Standard Edition). All these 5-6 Laptop Users are having different amount of mails (items) as well as folders. Once any of these user starts his / her mail client - Microsoft Office Outlook 2013, suddenly our network bandwidth gets chocked
and because of which my rest of the 80 users are not getting the Internet access. We have to ask them (Laptop user who has switched ON their Microsoft Office Outlook 2013) to close their mail client, Once Microsoft Office Outlook 2013 has been closed my network
gets stable. At first we thought that it is because of mails are getting downloaded from mail server and hence network is getting jammed, so we did another exercise that let their mails gets downloaded to their local machine and afterwords - next time when
they will start their mail client network should not be affected. But this network jammed scenario is still there, hence I ought to raise this issue.
For your information we have tried removing profile, deleted required folders and reconfigured Microsoft Office Outlook 2013 but still issue is being replicated.
Need your help for the same.
Thanks.
Dipak Ahir.

MSA Client side Outlook 2007 Integration

Hi
We currently run MSA 5.0 SP11 and Outlook 2007
We run server side groupware integration currently but have had a lot of problems with it.
Questions:
- Is MSA integration available for Outlook 2007? - I follow the instructions but see no tab in the Outlook options (Outlook was closed when I installed it)
- Is there any further documentation available on the CLIENT SIDE Integration?
Many thanks
James

Thanks Abishek
I had already found this documentation, but it is more the installation of MSA that I wanted to check on first.
In the instructions:
"Choose Tools ® Options in Microsoft Outlook.
The Options dialog box appears ....................
2.      Choose the SAP CRM Calendar Properties tab page to set values for automatically synchronizing the mobile client and Microsoft Outlook calendars.
If you choose more than one option, the synchronization process affects performance.
If you do not choose any settings on this tab page, you would have to trigger synchronization manually.
3.      Choose Optionsu2026.
The SAP CRM Calendar Synchronization Settings dialog box appears.
4.      Perform the steps described in the "Common Synchronization Settingsu201D section."
In Outlook 2007, we certainly do not see this tab which shoudl be independant of what has been configured server side
Any ideas?

Some Outlook clients getting internal FQDN of newly installed Exchange 2013 CAS server as Outlook Anywhere Proxy address

Hello Folks,
I have this problem and is making me crazy if anyone have any idea please shed some light on this:-
1. Working Outlook 2010 and 2013 clients with webmail.xyz.com as Outlook Anywhere proxy address.
2. Installed new Exchange 2013 server (server02)with CAS and Mailbox role, Exchange install wizard finished and server is rebooted.
3. Server came up online started changing internal and external FQDN's of Virtual Directories and Outlook Anywhere to webmail.xyz.com
4. As soon as Fqdn's changed some outlook clients create support request that Outlook suddenly white's out and after reopening it is giving error cannot connect to exchange. upon checking Clients Exchange Proxy address is set to http://server02.xyz.com,
even though OA/OWA/ECP/OAB/EWS/Autodiscover/ActiveSync FQDN's Point to webmail.xyz.com, on all servers if i create new outlook profile for same user it picks up correct settings through autodiscover and connects fine, this is happening to about 20% of outlook
clients every time i am introducing new Exchange 2013 server in Organization. we have around 2000 users and planning on installing 4 exchange servers to distribute load and everytime changing outlook profile of close to 150-200 users is not possible.
Any help is greatly appreciated.
Thanks
Cool

Here are the EXCRA results
Here IP (x.x.x.x) returned is my Load Balancer IP (Webmail.xyz.com).
Connectivity Test Successful with Warnings
Test Details
    Testing Outlook connectivity.
    The Outlook connectivity test completed successfully.
       Additional Details
    Elapsed Time: 9881 ms.
       Test Steps
       The Microsoft Connectivity Analyzer is attempting to test Autodiscover for [email protected].
    Autodiscover was tested successfully.
       Additional Details
    Elapsed Time: 2063 ms.
       Test Steps
       Attempting each method of contacting the Autodiscover service.
    The Autodiscover service was tested successfully.
       Additional Details
    Elapsed Time: 2063 ms.
       Test Steps
       Attempting to test potential Autodiscover URL https://xyz.com:443/Autodiscover/Autodiscover.xml
    Testing of this potential Autodiscover URL failed.
       Additional Details
    Elapsed Time: 186 ms.
       Test Steps
       Attempting to resolve the host name xyz.com in DNS.
    The host name couldn't be resolved.
       Tell me more about this issue and how to resolve it
       Additional Details
    Host xyz.com couldn't be resolved in DNS InfoNoRecords.
Elapsed Time: 186 ms.
    Attempting to test potential Autodiscover URL https://autodiscover.xyz.com:443/Autodiscover/Autodiscover.xml
    Testing of the Autodiscover URL was successful.
       Additional Details
    Elapsed Time: 1876 ms.
       Test Steps
       Attempting to resolve the host name autodiscover.xyz.com in DNS.
    The host name resolved successfully.
       Additional Details
    IP addresses returned: x.x.x.x
Elapsed Time: 338 ms.
    Testing TCP port 443 on host autodiscover.xyz.com to ensure it's listening and open.
    The port was opened successfully.
       Additional Details
    Elapsed Time: 173 ms.
    Testing the SSL certificate to make sure it's valid.
    The certificate passed all validation requirements.
       Additional Details
    Elapsed Time: 318 ms.
       Test Steps
       The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.xyz.com on port 443.
    The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
       Additional Details
    Remote Certificate Subject: CN=webmail.xyz.com, Issuer: CN=VeriSign Class 3 Secure Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US.
Elapsed Time: 219 ms.
    Validating the certificate name.
    The certificate name was validated successfully.
       Additional Details
    Host name autodiscover.xyz.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=webmail.xyz.com, OU=Terms of use at www.verisign.com/rpa (c)05,.
    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=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign,
Inc.", C=US.
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 = 1/3/2013 12:00:00 AM, NotAfter = 11/16/2015 11:59:59 PM
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: 289 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: 756 ms.
       Test Steps
       The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.xyz.com:443/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>Test Exch1</DisplayName>
<LegacyDN>/o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=add423106fbb47d5bf237462f52b8dab-Test Exch1</LegacyDN>
<DeploymentId>4ec753c9-60d9-4c05-9451-5b24e2d527a7</DeploymentId>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol>
<Type>EXCH</Type>
<Server>[email protected]</Server>
<ServerDN>/o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]</ServerDN>
<ServerVersion>73C0834F</ServerVersion>
<MdbDN>/o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]/cn=Microsoft Private MDB</MdbDN>
<ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
<OOFUrl>https://webmail.xyz.com/ews/exchange.asmx</OOFUrl>
<OABUrl>https://webmail.xyz.com/OAB/6a6a06ad-4717-4636-bd98-0b4fa3aaf4a5/</OABUrl>
<UMUrl>https://webmail.xyz.com/ews/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<PublicFolderServer>webmail.xyz.com</PublicFolderServer>
<AD>DC-03.domain.xyz.com</AD>
<EwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsUrl>
<EmwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EmwsUrl>
<EcpUrl>https://webmail.xyz.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=domain.xyz.com</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=domain.xyz.com</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=domain.xyz.com</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=domain.xyz.com</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=domain.xyz.com</EcpUrl-sms>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=domain.xyz.com</EcpUrl-photo>
<EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=domain.xyz.com</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=domain.xyz.com</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=domain.xyz.com</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=domain.xyz.com</EcpUrl-extinstall>
<ServerExclusiveConnect>off</ServerExclusiveConnect>
</Protocol>
<Protocol>
<Type>EXPR</Type>
<Server>webmail.xyz.com</Server>
<ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
<OOFUrl>https://webmail.xyz.com/ews/exchange.asmx</OOFUrl>
<OABUrl>https://webmail.xyz.com/OAB/6a6a06ad-4717-4636-bd98-0b4fa3aaf4a5/</OABUrl>
<UMUrl>https://webmail.xyz.com/ews/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>On</SSL>
<AuthPackage>Ntlm</AuthPackage>
<EwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsUrl>
<EmwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EmwsUrl>
<EcpUrl>https://webmail.xyz.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=domain.xyz.com</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=domain.xyz.com</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=domain.xyz.com</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=domain.xyz.com</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=domain.xyz.com</EcpUrl-sms>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=domain.xyz.com</EcpUrl-photo>
<EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=domain.xyz.com</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=domain.xyz.com</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=domain.xyz.com</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=domain.xyz.com</EcpUrl-extinstall>
<ServerExclusiveConnect>on</ServerExclusiveConnect>
<EwsPartnerUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsPartnerUrl>
<GroupingInformation>Default-First-Site-Name</GroupingInformation>
</Protocol>
<Protocol>
<Type>WEB</Type>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<Internal>
<OWAUrl AuthenticationMethod="Basic, Fba">https://webmail.xyz.com/owa/</OWAUrl>
<Protocol>
<Type>EXCH</Type>
<ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
</Protocol>
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba">https://webmail.xyz.com/owa/</OWAUrl>
<Protocol>
<Type>EXPR</Type>
<ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
</Protocol>
</External>
</Protocol>
<Protocol>
<Type>EXHTTP</Type>
<Server>webmail.xyz.com</Server>
<ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
<OOFUrl>https://webmail.xyz.com/ews/exchange.asmx</OOFUrl>
<OABUrl>https://webmail.xyz.com/OAB/6a6a06ad-4717-4636-bd98-0b4fa3aaf4a5/</OABUrl>
<UMUrl>https://webmail.xyz.com/ews/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>On</SSL>
<AuthPackage>Ntlm</AuthPackage>
<EwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsUrl>
<EmwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EmwsUrl>
<EcpUrl>https://webmail.xyz.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=domain.xyz.com</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=domain.xyz.com</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=domain.xyz.com</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=domain.xyz.com</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=domain.xyz.com</EcpUrl-sms>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=domain.xyz.com</EcpUrl-photo>
<EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=domain.xyz.com</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=domain.xyz.com</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=domain.xyz.com</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=domain.xyz.com</EcpUrl-extinstall>
<ServerExclusiveConnect>On</ServerExclusiveConnect>
</Protocol>
<Protocol>
<Type>EXHTTP</Type>
<Server>webmail.xyz.com</Server>
<ASUrl>https://webmail.xyz.com/ews/exchange.asmx</ASUrl>
<OOFUrl>https://webmail.xyz.com/ews/exchange.asmx</OOFUrl>
<OABUrl>https://webmail.xyz.com/OAB/6a6a06ad-4717-4636-bd98-0b4fa3aaf4a5/</OABUrl>
<UMUrl>https://webmail.xyz.com/ews/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>On</SSL>
<AuthPackage>Ntlm</AuthPackage>
<EwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EwsUrl>
<EmwsUrl>https://webmail.xyz.com/ews/exchange.asmx</EmwsUrl>
<EcpUrl>https://webmail.xyz.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=domain.xyz.com</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=domain.xyz.com</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=domain.xyz.com</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=domain.xyz.com</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=domain.xyz.com</EcpUrl-sms>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=domain.xyz.com</EcpUrl-photo>
<EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=domain.xyz.com</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=domain.xyz.com</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=domain.xyz.com</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=domain.xyz.com</EcpUrl-extinstall>
<ServerExclusiveConnect>On</ServerExclusiveConnect>
</Protocol>
</Account>
</Response>
</Autodiscover>HTTP Response Headers:
request-id: 9d325a80-f1fd-4496-ac48-2be6bb782c28
X-CalculatedBETarget: Server01.domain.xyz.com
X-DiagInfo: Server01
X-BEServer: Server01
Persistent-Auth: true
X-FEServer: Server01
Content-Length: 11756
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Date: Mon, 25 Aug 2014 19:12:25 GMT
Set-Cookie: X-BackEndCookie=S-1-5-21-1293235207-2459173341-1304346827-14544=u56Lnp2ejJqBypqcnsfJx5nSy8ucnNLLnJzP0sfKz8/Sy5nHmsiamZrMyZrLgYHPxtDNy9DNz87L387Gxc7Nxc3J; expires=Thu, 25-Sep-2014 00:12:26 GMT; path=/Autodiscover; secure; HttpOnly
Server: Microsoft-IIS/8.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Elapsed Time: 756 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 RPC over HTTP connectivity to server webmail.xyz.com
    RPC over HTTP connectivity was verified successfully.
       Additional Details
    HTTP Response Headers:
request-id: 835acf95-78b7-40ae-b232-117318d1577e
Server: Microsoft-IIS/8.5
WWW-Authenticate: Basic realm="webmail.xyz.com",Negotiate,NTLM
X-Powered-By: ASP.NET
X-FEServer: Server01
Date: Mon, 25 Aug 2014 19:12:26 GMT
Content-Length: 0
Elapsed Time: 7817 ms.
       Test Steps
       Attempting to resolve the host name webmail.xyz.com in DNS.
    The host name resolved successfully.
       Additional Details
    IP addresses returned: x.x.x.x
Elapsed Time: 107 ms.
    Testing TCP port 443 on host webmail.xyz.com to ensure it's listening and open.
    The port was opened successfully.
       Additional Details
    Elapsed Time: 180 ms.
    Testing the SSL certificate to make sure it's valid.
    The certificate passed all validation requirements.
       Additional Details
    Elapsed Time: 303 ms.
       Test Steps
       The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server webmail.xyz.com on port 443.
    The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
       Additional Details
    Remote Certificate Subject: CN=webmail.xyz.com, OU=Terms of use at www.verisign.com/rpa (c)05, Issuer: CN=VeriSign Class 3 Secure Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign,
Inc.", C=US.
Elapsed Time: 224 ms.
    Validating the certificate name.
    The certificate name was validated successfully.
       Additional Details
    Host name webmail.xyz.com was found in the Certificate Subject Common name.
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=webmail.xyz.com, OU=Terms of use at www.verisign.com/rpa (c)05,
    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=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign,
Inc.", C=US.
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: 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 = 1/3/2013 12:00:00 AM, NotAfter = 11/16/2015 11:59:59 PM
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: 298 ms.
    Testing HTTP Authentication Methods for URL https://webmail.xyz.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, Negotiate, NTLMHTTP Response Headers:
request-id: 835acf95-78b7-40ae-b232-117318d1577e
Server: Microsoft-IIS/8.5
WWW-Authenticate: Basic realm="webmail.xyz.com",Negotiate,NTLM
X-Powered-By: ASP.NET
X-FEServer: Server01
Date: Mon, 25 Aug 2014 19:12:26 GMT
Content-Length: 0
Elapsed Time: 296 ms.
    Attempting to ping RPC proxy webmail.xyz.com.
    RPC Proxy was pinged successfully.
       Additional Details
    Elapsed Time: 454 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 0 ms.
Elapsed Time: 1007 ms.
    Testing the MAPI Address Book endpoint on the Exchange server.
    The address book endpoint was tested successfully.
       Additional Details
    Elapsed Time: 2177 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 906 ms.
Elapsed Time: 918 ms.
    Testing the address book "Check Name" operation for user [email protected] against server [email protected].
    The test passed with some warnings encountered. Please expand the additional details.
       Tell me more about this issue and how to resolve it
       Additional Details
    The address book Bind operation returned ecNotSupported. This typically indicates that your server requires encryption. The Microsoft Connectivity Analyzer will attempt the Address Book test again with encryption.
NSPI Status: 2147746050
Elapsed Time: 825 ms.
    Testing the address book "Check Name" operation for user [email protected] against server [email protected].
    Check Name succeeded.
       Additional Details
    DisplayName: Test Exch1, LegDN: /o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=add423106fbb47d5bf237462f52b8dab-Test Exch1
Elapsed Time: 433 ms.
    Testing the MAPI Referral service on the Exchange Server.
    The Referral service was tested successfully.
       Additional Details
    Elapsed Time: 1808 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 953 ms.
Elapsed Time: 949 ms.
    Attempting to perform referral for user /o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=add423106fbb47d5bf237462f52b8dab-Test Exch1 on server [email protected].
    We got the address book server successfully.
       Additional Details
    The server returned by the Referral service: [email protected]
Elapsed Time: 858 ms.
    Testing the MAPI Address Book endpoint on the Exchange server.
    The address book endpoint was tested successfully.
       Additional Details
    Elapsed Time: 626 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 156 ms.
Elapsed Time: 154 ms.
    Testing the address book "Check Name" operation for user [email protected] against server [email protected].
    Check Name succeeded.
       Additional Details
    DisplayName: Test Exch1, LegDN: /o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=add423106fbb47d5bf237462f52b8dab-Test Exch1
Elapsed Time: 472 ms.
    Testing the MAPI Mail Store endpoint on the Exchange server.
    We successfully tested the Mail Store endpoint.
       Additional Details
    Elapsed Time: 555 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 234 ms.
Elapsed Time: 228 ms.
    Attempting to log on to the Mailbox.
    We were able to log on to the Mailbox.
       Additional Details
    Elapsed Time: 326 ms.

Outlook 2013 Clients certificate has expired warning or not yet valid

Hello,
We had been through a migration from exchange 2010 to 2013 in the last year but have had an ongoing issue with
some Outlook clients getting a certificate warning after they launch the client. Not all Outlook clients experience this. We've just recently uninstalled exchange from our 2010 servers and shut them
down. What we have left are two 2013 servers in a DAG. The certificate these Outlook clients are complaining about had expired in 2012. Here is the warning they are getting:
"Certificate has expired warning or not yet valid"
I've been through numerous threads/sites regarding this error but it always ends up that there was an expired cert hanging out somewhere. I cannot seem to find an expired cert anywhere...
I've ran the 'Get-ExchangeCertificate | fl' cmdlet and I see 7 certs listed, none of which match the thumbprint on the Cert Warning on Outlook.
When I check the registry of the Exchange servers here: HKLM>Software>Microsoft>SystemCertificates>My>Certificates
I can see 7 certificate entries listed there and the thumbprint matches those of the cmdlet ran from
EMS.
OWA shows the correct cert expiring in 2015 and Outlook clients are pointed to the 2013 servers. We do have a load balancer that AutoDiscover, OWA, SMTP are going through.
It seems like some of these Outlook clients are still looking at the decommissioned 2010 Exchange servers' old certificate. Any ideas on how I can get outlook to point to the new certificate/server?
Thanks.
Rory
Rory Schmitz

Hi Rory,
If possible, could you please post the Get-ExchangeCertificate | FL results about the certificate which is assigned with IIS service here?
If the issue only happens for some users instead of all users, please create a new Outlook profile for the problematic user to check whether the issue persists. Please make sure the certificate name which is reported as expired or not valid is included
in the IIS service certificate in your Exchange 2013.
In Exchange server side, please restart IIS service by running IISReset /noforce from a command prompt window to have a try.
Regards,
Winnie Liang
TechNet Community Support

MAPI over HTTP not working correctly, Outlook 2013 clients prompting for credentials during profile creation or opening depending on security of virtual directory

ENVIRONMENT
-1 Exchange 2013 SP1 CU7 server with all roles that is also a hybrid server with Office 365 tenant, mailboxes are all on premise only LYNC online is being utilized right now.
-Exchange 2013 public folders
-Mix of Outlook 2013 SP1 and Outlook 2010 SP3 clients all fully update to day as of Feb 2015
Outlook anywhere is working perfectly across all clients both internally and externally using autodiscover. Both Outlook 2013 and 2010 clients can open the program and create a profile automatically via autodiscover and no additional logon prompts
are seen.
We set the internal and external mapi virtual directory URLs to a valid URL that also matches the Exchange 2013 SSL certificate. We set the security to ntlm, negotiate on the mapi virtual directory. We reset IIS and enabled mapi over http in
the org config. We run in to problems here.
Outlook 2010 clients appear to be working fine. We can create a new profile and open and close Outlook without any logon prompts and verify that MAPIHTTP and Negotiate are used to connect to Exchange.
Outlook 2013 clients are having problems. As soon as we try to create a profile it says your administrator has made a change that requires you to restart outlook and then a windows logon prompt appears. If we authenticate Outlook will open and connect.
This logon prompt should not occur. We can confirm that it is connecting via MAPI HTTP and Negotiate.
If we set the mapi virtual directory to NTLM only then a logon prompt also appears during every open of Outlook 2013. We can confirm that it is trying to connect with MAPIHTTP via NTLM in the outlook connection test screen.
I do not understand this behavior by Outlook 2013 which was supposed to be designed with MAPI HTTP in mind. I would think the same issues would occur with Outlook 2010 but they do not. I am not sure how to resolve this and I am looking for help.

I have the same problem. Exchange and Outlook are both up to date. After creating a new profile Outlook prompts for username/password. A lot of users also get this prompt while
working - the profiles have been "migrated" from Exchange server 2010. <o:p></o:p>
Niko, as i can see in your screenshot you do not have Mapi over HTTP enabled. Why? You can change settings in the security tab – if you have Mapi over
HTTP enabled all options are grayed out (please correct me if I
am wrong):
This is a very annoying thing – does anybody else have the same problem?
Any suggestions on this?
Marc

Outlook 2013 set as default mail client but still shows error box saying it isn't?

We have recently installed Office 2013 64-bit on 4 servers. We previously used Outlook 2007 64-bit.
We set Outlook 2013 as the default mail client and do not have another mail client installed on the servers. However when you first login you get an error message box that says you have no default mail client 'either there is no default mail client or the
current mail client cannot fulfill the messaging request'.
I have checked all defaults to be for Outlook 2013.
How can I solve this issue? I am an administrator.

Try different Method to set Outlook 2013 as the default mail client to check the result. Thanks.
Method 1:Set as default within outlook.
-File > Options > General Tab > select the "Make Outlook the default program for E-mail, Contacts, and Calendar"
check box.
Method 2: Set as default from the internet explorer.
-Tool > Internet Options > Programs Tab > Set programs
Method 3: Set as default from control panel.
1.Navigate to Control Panel\Default Programs\Set Default Programs
2.Click on the outlook icon on the left hand side.
3.Set as default.
We may also try to create anther windows user profile in the same machine to check if the issue still persists. Thanks.
Tony Chen
TechNet Community Support

Outlook 2013 Client - missing random sent items, not happen in owa.

Hello,
We are working in our company with Exchange 2007 SP3 CU13.
We are experiencing some problems with one Outlook 2013 client installed on Windows 8.1.
He lose some random mails from "sent items" folder. But if you check the OWA, all mails are ok.
I have readed that there is some bug about this, but these comments are for two years ago. And I didn't find any great solution.
I don't think that the solution is to make a new rule to re-copy these sent mails to that folder.Re-create the user outlook profile don't seem to be another good fix. It's only a new start point.
I have activated client side troubleshooting.
I would appreciate your help.

Hi,
For Exchange Accounts in Outlook, the emails should sync between the client and the server. Since on the server the emails are there but some are lost on Outlook client, this makes me suspect there is a custom view applied on Outlook.
Start Outlook with the /cleanviews switch:
Press Win + R, type "outlook.exe /cleanviews" in the blank box, press Enter.
This will restore default views. All custom views that you created will be lost.
Check the result then.
Regards,
Melon Chen
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 Anywhere Prompts for Credentials only for Outlook 2010, not Outlook 2013

I'm having a heck of a time with this one. We have Exchange 2010 on premise, with our filtering through EOP. Clients that are using Outlook 2010 Professional Plus are continuously getting prompted for credentials when off network and relying
on Outlook Anywhere.
I've read many threads about configuring credential manager appropriately for the internal domain and our external domain. I can get them to authenticate just fine, and email flows, but they continue to be prompted everytime they connect again.
Here is the kicker: When I install Outlook 2013 on the same computer, outlook anywhere functions just fine, no problems, no authentication prompt.
Like I said I have read a plethera of articles and threads about this, I have gone through all settings on Exchange, our edge server, our firewall, our certificate. The MSSTD string matches our "Issued To" string. NTLM authentication
is configured on both the client and the server. Appropriate settings are configured on the firewalls.
Anyone know why Outlook 2010 would have this problem, but not Outlook 2013 on the same computer, same user, same mailbox database?
Thanks in advance!!!

I'd still Echo Ed's original question.
Do you have Outlook 2010 patched up? At this time you need to be on SP1, and SP2 by October the 14th.
Also I expect you to have a recent update ontop of that as well.
http://blogs.technet.com/b/rmilne/archive/2014/04/14/office-2010-sp2_1320_-do-you-need-to-upgrade_3f00_.aspx
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.

Can Outlook 2013 cached mode disabled work offline?

Hello
I would like to please someone help me to resolve a concern. I have a client Outlook 2013 cache mode disabled by policy, however when you need to open Outlook without connecting to any network, is not possible and a message that the server is not online.
Is there a way to change this behavior and that an Outlook client that has disabled the cache can work offline?
Many thanks

Hi
No, that is what cached mode is used for.
You can use OWA offline if you are disabling cache mode with policy.

Client side disabling of Outlook anywhere in Outlook 2013

Similar Messages

Maybe you are looking for