Exchange 2013 cached mode and Exchange 2010

Hi,
We have issues with Outlook 2013 not getting new emails in inbox unless its restarted. It works fine when cache is turned off. The users are on same LAN as single Exchange 2010 backend server.
Any ideas please?
Celtic

Hello,
Please describe your environment detailedly.
Please click send/receive to check the result when you use cached mode.
Please check if there is any sync issue.
Please open outlook, click folder list at the bottom of left panel.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Similar Messages

Exchange 2013 Transport Rules and Exchange 2007 Decommissioning

Hello,
I recently migrated from Exchange 2010 to Exchange 2013, I do have a few traces of Exchange 2007 in the Active Directory that I would like to completely remove. The Exchange 2007 server failed earlier and wasn't decommissioned properly. I read a few articles
on how to completely remove it from AD, I am still concerned to make the changes in "ADSI Edit".
Here is the error message I receive when creating transport rules in Exchange 2013:
"You are about to create a rule in an organization where Hub Transport servers running Exchange Server 2007
exist. To ensure the rule is applied consistently across all Hub Transport servers in the organization, you must create an equivalent rule from the Exchange Management Console on an Exchange 2007 server."
I also noticed that the version of the rules remain Version: 14.0.0.0 for any new rules that I am creating in Exchange 2013.
I would really appreciate if someone can provide their views and the best practices to remove the traces of Exchange 2007 in AD.

Hi Sathish,
How about the result after using ADSI Edit ?
Best regards,
Niko Cheng
TechNet Community Support

Setup a simple sales funnel with exchange 2013 public folders and outlook 2010 -2013

BCM for Outlook is big and has too many choices. What we want is a combination of contacts and tasks within a public folder so we can see what others are doing. If possible I want
to make a connection between an contact and a task. The task should have some extra fields like branches responsible organization members status etc. Does anyone have a simple solution which is easy to implement in a small organization of 10 people?

Hello,
First of all thank you for your answer. The Outlook version I'm using is 14.0.7113.5005 and the Exchange versuin is CU3. As I'm testing it on XP client it is probably the issue in the PS. I'll try it with Win7 client probably tomorrow. I wonder if there
exists any kind of workaround for XP clients.
Thank you in advance,
Peter

Exchange 2013 CU1 UM and Avaya SM R6

Hello! I have a problem integrating Avaya and Exchange 2013 CU1 UM.
In 2010 environment it works perfectly fine, however with Exchange 2013 I was unable to make it work.
I was looking into the packets sent by 2010 and 2013, the only difference is in 302 reply. Exchange 2010 sends
extension@ip:port as the Contact URI while Exchange 2013 sends
extension@fqdn:port
Avaya doesn't seem to recognize the format and instead of connecting to the specified within the contact field service just keeps querying TCP 5060 (Call Router Service).
Is there any way to force Exchange to use IP within the contact field instead of FQDN?
Pointing SIP Entity to 5065/5067 directly is not an option for obvious reasons well covered here on the forums.

To get this functioning u must do the following! The CM will handle the "302 moved" FQDN request with this setup. CM 5.2.1 with 6.2 SM.
1. Lockdown the CAS server worker port to 5065. A restart of the UM service every couple of days will take care of this because it defaults to 5065.
2. CM hunt group set "voice mail handle" to a name. EX: sipms
3. SM create SIP entity for CAS server with entity link SM TCP 5060 -> CAS TCP 5060
4. SM Create SIP entity for each MBX server and port needed.
EX: Entity MBX-1-5062 IP 10.10.10.1 with entity link SM TCP 5062 -> MBX-1-5062 TCP 5062
Entity MBX-1-5065 IP 10.10.10.1 with entity link SM TCP 5060 -> MBX-1-5065 TCP 5065
Note: IF the SM is not listening on 5060 for the 5065 link MWI and "play on phone" will fail. This is why you need to lockdown the worker port to 5065.
5. SM Create routing policies for each entity.
6. SM create regular expressions for the CAS server and each of the MBX server entities and assign to the appropriate routing policy. The examples below are for one CAS server and one MBX server. There are one CAS and six MBX servers in my environment,
so I have 13 routing policies and 13 reg expressions.
EX: "sip:sipms@example\.org" asign to CAS policy.
"sip:sipms@mbx1@example\.org:5062.*" assign to MBX-1-5062 policy.
"sip:sipms@mbx1@example\.org:5065.*" assign to MBX-1-5065 policy.
Hopefully this is enough to get you going. I would have killed to have this information when I started on my quest!

First Exchange 2013 server in an Exchange 2010 SP3 organization

I've read the documentation that states to install Exchange 2013 with CU2 as the first Exchange 2013 server in an organization running Exchange 2010 SP3. Maybe I over-read this to mean "Exchange 2013 with at least CU2" (meaning to start with Exchange2013-x64-cu3.exe),
but when I installed the CU3 version I ended up with Standard rather than Enterprise. I need to run 2013 with Enterprise. I've looked around for an Enterprise version of Exchange2013-x64-cu3.exe but cannot find one.
How do I install Exchange 2013 Enterprise into my Exchange 2010 SP3 organization? Thank you.

Please review
http://technet.microsoft.com/en-us/library/bb232170(v=exchg.150).aspx
These (Exchange 2013 Standard Edition and Enterprise Edition)
licensing editions are defined by a product key. When you enter a valid license product key, the supported edition for the server is established. Product keys can be used for the same edition key swaps and upgrades only; they can't be used
for downgrades. You can use a valid product key to move from the evaluation version (Trial Edition) of Exchange 2013 to either Standard Edition or Enterprise Edition.
You can also use a valid product key to move from Standard Edition to Enterprise Edition.

"Sent Items" folder can not be synced up in time for Outlook 2013 cache mode

Hi,
I found a strange problem in Outlook 2013 cache mode. Hope anyone can help me find out if it is the new design of outlook 2013 or outlook 2013 issue.
I am using Exchange 2013 and Outlook 2013 client. I created two outlook profiles in two machines separately with a same exchange user, the difference for the two profiles is one is in cache mode, and the other is in uncache mode.
I launched outlook using the profiles in the two machines, go to "Sent Items" folder, I assume there are some messages in this folder in your mailbox, do below steps:
1. modify one of the messages in the "Sent Items" folder from the profile in cache mode, in this case, the changes to the message will be synced up to the profile which is in uncache mode immediately.
2. modify another messages in the "Sent Items" folder from the profile in uncache mode, in this case, the changes will never be synced up to the profile in cache mode.
In the second action above, even if I clicked "Send/Receive" button, and waited for whole night, the changes was not synched up to the cached mode side. The way I can get the latest changes to the "Sent Items" folder is "clear
offline items" and click "Update folder" or I need to remove and create the profile again.
All in all, the changes to the items in "Sent Items" folder of Outlook 2013 which was did from cache mode will be synched up to exchange server side immediately, but the changes which was did from exchange server side will
never be synched up to the cache mode side unless the end-user clear the offline items and update folder or create a new profile again.
Any help would be appreciated, thanks in advance!
Best Regards, Emily

The first behavior is by design even in the previous version of Office.
"1. modify one of the messages in the "Sent Items" folder from the profile in cache mode, in this case, the changes to the message will be synced up to the profile which is in uncache mode immediately."
Uploading local changes ---- By default, when you make a change locally, that change is synced to the server after 15 seconds. When you make another change within those 15 seconds, then the timer is reset again. As now you
could in theory hold off synchronization indefinitely, there is the maximum timer. This timer is started after the first change that you made and when it reaches 60 seconds, then a synchronization will occur to upload all the changes that you have made thus
far, no matter how many seconds are left on the upload timer.
However, in second section, this should be a downloading server changes
behavior ---- When a server side mailbox change occurs, Outlook is notified by the Exchange server of this change. By default, Outlook will then wait 30 seconds before synchronizing these changes. If there are any other changes occurring
at the server level within these 30 seconds, then these changes are downloaded at the same time as well.
At this time, please directly modify the message in sender items folders through Web-based access and then wait over 30 seconds to check if the items changes from cache mode profile. Please also test if we can reproduce that in other folder.
Let me know the result. Thanks.
Cheers,
Tony 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 contact
[email protected]

Outlook 2013 cached mode "mail to keep offline" - does this setting affect archive mailbox or Office 365 hosted archive mailbox?

I have an Exchange 2013 Hybrid environment with Exchange 2007 in coexistance mode as well as Office 365. We are hosting the majority of our Exchange accounts on-premise (migrating them from 2007), and most (soon to be ALL) Archive mailboxes in Office 365.
I have through Group policy set the policy "Select Cached Exchange Mode sync settings for new profiles" to 6 months. This works fine for the contents of the regular mailbox, but the setting is NOT being set at all for the Online Archive mailbox,
whether or not it is hosted on-premise or in Office 365. Is this the expected behavior?
Another question: Is it possible to have the regular mailbox in cached mode and the archive in Online mode or vice versa?

Hi,
The key to your questions is: Archive mailboxes are online only, they cannot be cached for offline viewing, so you can keep your regular mailboxes offline(In Cached Exchange Mode) or Online, but cannot switch Archive mailboxes to Offline.
The whole idea of the archive mailbox is to keep your "online" mailbox with recent / important mails small and accessible on and offline. The archive mailbox is intended to store older / less important emails which are not neccessary to access immediately.
One important reason of archive mailbox is to prevent the growth of offline files.
Regards,
Melon Chen
TechNet Community Support

Migrating Users from Exchange 2007 to Exchange 2013 Without redirection through exchange 2013.

We have all our users and mailboxes on Exchange 2007 and I have introduced two Exchange 2013 servers in my organization and both have mailbox and CAS server installed on them.
With Exchange 2007 server, I had not modified any of the internal and external url/uri and had stayed with the defaults.
For migration most of the documents are suggesting of changing the default internal URL and Auto Discover Service internal URI values.
In my case, I want to migrate all the users and mailbox (everything that is on Exchange 2007) form 2007 to 2013 and decommission exchange 2007 completely from our organization.
I am in the phase of transferring users from Exchange 2007 to Exchange 2013 and do not want to change any settings on the existing 2007 servers.
I have created new dns entry mailx.abc.com with two IPs of both exchange 2013 and changed the Outlook Anywhere internal URL on both Exchange 2013 server to mailx.abc.com.
So by doing these, I think all existing clients will still connect to exchange 2007 and after moving their mailbox they will be connect to exchange 2013.
In short I am not redirecting or using 2013 as proxy for 2007 clients and clients whose mailbox is on exchange 2013 will directly connect to 2013 server.
Questions are, Is this the right way to migrate all the users to Exchange 2013?
Will it affect the operation of existing Exchange 2007 server?

Read the below blog on Client Connectivity in Exchange co-existence. There can't be better blog than this on this topic.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Clients connect to Exchange from Internal-Outlook, External-Outlook, Web & Active Sync.
For Internal the configuration that you have mentioned should work as clients would get Autodiscover information from Active Directory (SCP) and get connected to right server.
However, for external connectivity it makes sense to use External URL on Exchange 2013 servers (keep the Exchange exposed to Internet), configure legacy URL for exchange 2007 and use Exchange 2013 external URL for mailboxes that are Exchange 2007 and Exchange
2013 for standardization.
Refer article for configuring URLs -
http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/
- Sarvesh Goel - Enterprise Messaging Administrator

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.

Outlook Anywhere settings in a Exchange 2013 coexistence scenario with Exchange 2007

I have exchange 2013 and 2007 set up in a coexist environment. At the moment, the few mailboxes I am testing on Exchange 2013 are getting multiple pop ups in outlook and cannot connect to items like Public Folders on 2007. I found an article
that told me to change the authentication method from Negotiate to NTLM and that broke some of my Lync 2013 compatibility issues on users on exchange 2007 (ie conversation history and they got outlook integration errors.) I would like someone to confirm
if the change I am about to make from doing research will help me in my situation.
Current Setup:
Exchange 2007 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: NTLM
IISAuthenticationMethods : {Basic, Ntlm}
Exchange 2013 OA CAS Settings
ExternalClientAuthenticationMethod : Negotiate
InternalClientAuthenticationMethod: Negotiate
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
New Settings I am considering based on research:
Exchange 2007 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: Basic
IISAuthenticationMethods : {NTLM}
Exchange 2013 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: Basic
IISAuthenticationMethods : {Basic}
Will this work and eliminate my popups?

Hi,
The following TechNet article indicates that:
“In order to support access for Outlook Anywhere clients whose mailboxes are on legacy versions of Exchange, you will need to make some changes to your environment which are documented in the steps within the
Exchange Deployment Assistant. Specifically,
you will need to enable Outlook Anywhere on your legacy Client Access servers and enable NTLM in addition to basic authentication for the IIS Authentication Method.”
Client Connectivity in an Exchange 2013 Coexistence Environment
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
As for the Autodiscover service, please make sure the Autodiscover.domain.com is pointed to your Exchange 2013 in Internal and External DNS. For more detailed information about Exchange 2013 coexistence with Exchange 2007, please refer to:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
Regards,
Winnie Liang
TechNet Community Support

Autodiscover after deploying Exchange 2013 CAS in a Exchange 2007 organization

I am deploying Exchange 2013 CAS in a Exchange 2007 organization. Will all the clients be directed to the Exchange 2013 CAS servers for autodiscover. Will there be any issue with outlook clients connecting to their mailbox servers in Exchange 2007

All clients should be pointed to the Exchange 2013 CAS for the autodiscover service. This means:
A. For local clients
You need to modify the autodiscover Internal URI on the Exchange 2007 server and point it to Exchange 2013. For example, if you are using split-brain DNS on the Local Network and mail.yourdomain.com is resolved to Exchange 2013 local IP, the Exchange 2007
Autodiscover Internal URI should be "https://mail.yourdomain.com/Autodiscover/Autodiscover.xml"
Exactly the same way, you should modify the Exchange 2013 Autodiscover Internal URI and use the same address "https://mail.yourdomain.com/Autodiscover/Autodiscover.xml"
B. For remote clients - all clients will hit the Exchange 2013 CAS first (ex. mail.yourdomain.com)
If the user's mailbox is on Exchange 2007 server, the correct XML will be generated and provided, and the user will be proxied for Outlook Anywhere/ActiveSync and redirected for OWA/WebServices
If the user's mailbox is on Exchange 2013 server, the correct XML will be generated and provided
Bottom line - based on the location of the user's mailbox, Exchange 2013 will generate and provide the correct XML file (there is not proxying involved in providing the Autodiscover info).

Outlook 2007-2013 doesn't connect in non-cached mode to Exchange 2013.

Hello!
I have organization Exchange 2010 + Exchange 2013 in one AD site (hybrid organization)
Mailboxes based on Exchange 2010 servers work fine. But after moving one of mailboxes to
Exchange 2013 database, Outlook doesn't connect to mailbox in
non-cached mode. If I turn on cached mode this mailbox is connecting perfectly (OAB, Folders, PublicFolders, Addresslists).
I cleaned parameter "PublicFolderDatabase" for Exchange 2013 database, but the problem didn't solve.
In CAS
RpcHttp
log:
2015-01-22T12:08:12.720Z,MBXDB13,RpcHttp,S:Stage=BeginRequest;S:AuthType=Negotiate;S:HttpVerb=RPC_IN_DATA;S:UriQueryString=?MBXDB13.DOMAIN.local:6001;S:RpcHttpUserName=DOMAIN\USER;S:ServerTarget=[email protected];S:RequestId=267b0bf2-4361-4efb-9865-7f8d664b6e00;S:ClientIp=10.10.10.111
2015-01-22T12:08:12.720Z,MBXDB13,RpcHttp,S:Stage=PostAuthorizeRequest;S:UserName=DOMAIN\MBXDB13.domain.local:6001;S:RpcHttpUserName=DOMAIN\USER;S:ServerTarget=[email protected];S:RequestId=267b0bf2-4361-4efb-9865-7f8d664b6e00;S:ClientIp=10.10.10.111
Exchange Server 2013 Cumulative Update 7 (CU7)
are installed.

Hi Allen!
Thank you for reply!
Outlook cannot connect to all mailboxes on Exchange 2013 server.
>Get-OutlookAnywhere | FL Name,*auth*,*host*Name : Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic}
ExternalHostname : exchange2010.contoso.com
InternalHostname :
Name : Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic}
ExternalHostname : exchange2010.contoso.com
InternalHostname :
Name : Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic}
ExternalHostname : exchange2013.contoso.com
InternalHostname : cas1302.domain.local
Name : Rpc (Default Web Site)
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic}
ExternalHostname : exchange2013.contoso.com
InternalHostname : cas1301.domain.local
Outlook error message:
"Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The attempt log on to Microsoft Exchange has failed."
This error reproduced even in new profile. Repair does not help.

Auto-Mapping Exchange 2013 Mailboxs in an Exchange 2010 Mailbox

We're in the middle of migrating mailboxes from Exchange 2010 to Exchange 2013. Many of our users have Auto-Mapped mailboxes as well. In my testing, I've found that I cannot Auto-Map a mailbox that's on Exchange 2013 in a Exchange 2010 mailbox. I can manually
add it and it works fine. Is this by design with this type of coexistence or is there a fix for it? Our current Exchange 2010 environment is at SP3 with UR2.
Orange County District Attorney

This issues is fixed in UR5 so suggest you to upgrade Exchange 2010 to SP3 UR5.
Reference Thread: http://social.technet.microsoft.com/Forums/exchange/en-US/a2aa4163-f74b-401f-aec5-13324e6b29c8/exchange-2010-mailbox-not-able-to-access-automapped-exchange-2013-cu3-mailbox?forum=exchangesvradmin
Blog |
Get Your Exchange Powershell Tip of the Day from here

Applying CU4 for Exchange 2013 SP1 in a mixed 2010 / 2013 Environment

We're planning to apply Exchange 2013 SP1 CU in our mixed 2010 / 2013 environment. We'd also like to apply Exchange 2010 SP3 Rollup 5 as well. Are there any gotchas or best practices on what update to apply first?
Orange County District Attorney

We are planning to update our 2013 from CU5 to CU8
and 2010 SP3 to Rollup 9
I cant find any official documentation from MS concerning the upgrade path. Example.
Exchange 2013 first, then 2010. Like the above post outline.
I see 2010 being upgraded first thus bring version numbers closer together, reducing incompatibilities.
Do you still feel this is the appropriate install procedure?
Have you done this?
Djoe

Exchange 2013 Online mode slow performance

Hello,
We recently moved mailboxes (180 or so) from Exchange 2007 to Exchange 2013. We are noticing that Outlook navigation seems to be very slow compared to the last server. Changing folder views, switching from Inbox to Calendar, Deleting items, etc.
Also we used to be able to send 40MB HTML emails very quickly. This now takes about 5 min just to open a reply. (These are tripwire reports.) Most users are using Outlook in Online mode on the new server and were using Online mode on the old server
Environment: Exchange 2013 SP1 on Server 2012r2 Standard (6 cores 24 gigs of RAM, VMWare VM.) Old server is Exchange 2007 8.3.348.2 on Server 2008x64 Standard SP2 (8 cores 12 gigs of RAM.
Physical.)
I have a ticket open with MS but didn't really get anywhere after 9 hours yesterday.
Thanks.

Hi everyone,
Here we have exactly the same thing. We did the same migration from Exchange 2k7 to Exchange 2013. We run on a VMware 5.5 infrastructure. We have a lot of users running on a VM, but I can also tell you that I'm experiencing the problem even on a physical
PC. So the problem about the client side infrastructure is maybe not that much related.
I also found an old thread talking about a known issue with the grouping option in Outlook and online mode, but this is supposed to be only for Exchange and Outlook 2007, so i'm not able to prove this problem is exactly and only related to this issue.
however, I tried to disable the grouping option for some folder in my Outlook and I saw an improvement immediately. Here is the thread talking about this issue and the knowledge base associated from Microsoft:
http: //blogs.technet.com/b/mikelag/archive/2008/08/31/slow-outlook-online-mode-performance.aspx
http: //support.microsoft.com/kb/948828
Sorry, I cannot post the real link since my account is not verified yet... simply remove the space.
If anyone finally found an answer please post-it, thanks.

Exchange 2013 cached mode and Exchange 2010

Similar Messages

Maybe you are looking for