After migration to Exchange 2013 the old outlook clients do not automatically reconfigure

After migration to Exchange 2013 the old outlook clients do not automatically reconfigure
we use outlook 2013

Hi ,
I hope you would be having exchange 2013 coexistence environment with exchange 2010 or 2007.
Autodiscover is the feature which will make the outlook profiles to configure automatically.So please make sure the following things are in place.
1.Autodiscover record on the internal dns need to be configured and it has to be resolved properly to the cas servers or else to the LB if you have.
2.Please check the autodiscover internal url.
get-clientaccessserver -identity "server name" | fl *internaluri*
3.Make sure the name used for the autodisocver and internal outlook anywhere are available on the SAN certificate installed in exchange.Same time we need to enable the installed SAN certificate for the exchange services like iis,pop,imap,smtp.
4.You need to have the autodicover name and internal outlook anywhere name on the internet explorer proxy exceptions when you have proxy servers available on your network for internet access.
Note : moreover we need an additional information's from your side about your environment.
Thanks & Regards S.Nithyanandham

Similar Messages

Outlook 2007 on Terminal Server cannot manage Public Folder Favorites after Migration to Exchange 2013

Hi,
we are running a Server 2008 R2 as a Terminal Server with Outlook 2007 SP3 (incl Nov 2012 Update 12.0.6665.5000) which is known as fully supported with Exchange 2013.
With Exchange Server 2007 we did not have any issues. But after having successfully migrated to Exchange 2013 we cannot manage our public folders favorites from these clients anymore.
As we are running Outlook 2007 on a WTS we can not use Exchange Cache Mode and so we can also not download Public-Folders-Favorites as an option. Whenever we try to delete existing favorites or when we try to delete public folders with content or subfolders
there will be an error msg that says that it cannot be deleted and that there may be no sufficient permissions. But this IS NOT the issue NOR the solution as I have full admin rights and am owner of the public folders.
On single fat clients with Outlook 2007 with Exchange Cache Mode enabled we can manage the favorites and the public folders without problem.
We need to be able to manage the favorites of all users (circa 50-60 users) from the WTS with Outlookm 2007. I have no more ideas right now. Does anyone know how to get this settled?
Thanks, Paula

Hi,
Based on the description, users could access public folders successfully, but when they tried to manage public folder favorites or wanted to remove specified folders, they got error message of no sufficient permissions.
Is it right?
You mentioned on single fat clients with Outlook 2007 with Exchange Cache Mode enabled, user can operate normally. Is this a WTS with Outlook 2007 installed?
If possible, please switch this Outlook client from cached mode to online mode to check result.
Best regards,
Belinda Ma
TechNet Community Support

Users cannot access calenders from outlook after migration to exchange 2013

I have a strange situation after upgrading to exchange 2013 some users are reporting that they cannot open or create calender appointments for calenders they used to be able to manage. we currently are using outlook 2010. also when the users access the calenders
with the webmail they are reporting that they can access the calenders and are able to do all the things they need to do.
i have tried reinstalling office and adding their exchange accounts but this does not help.
another stange thing is that to be sure i had setup the correct access policy i have reset all the security entries on all the calendars with the help of powershell. this seemed to have helped but after a couple of hours some users started reporting that they
could not access calendar items again!

Hi,
Is there any error description when the problematic users cannot open or create calendar items? Since the issue only happens to some users instead of all users and all calendars can work well in OWA, I think the calendar in the mailbox
should be configured properly.
Please configure the problematic user’s Outlook account in a clean computer with new installed Outlook to check whether the issue persists.
Thanks,
Winnie Liang
TechNet Community Support

After Migrating To Exchange 2013 All Outlook 2010 Users Constantly Prompted For Password (BUT OUTLOOK WORKS).

I have two servers. One is Exchange 2010 and the other is Exchange 2013.
Three of our users had mailboxes on Exchange 2013 for the last few weeks with no problems. They used Outlook 2013 and Outlook 2010. After moving the rest of our ~25 users to Exchange 2013 the users with Outlook 2010 began to be prompted for their
password constantly.
They try entering it and it immediately reappears.
The odd thing is it shows connected and they are able to send and receive emails correctly.
I've tested our exchange connectivity using www.testexchangeconnectivity.com and all is well there.
I'm not really sure what's going on.
Any help is appreciated.
Luke
Thanks, Luke Pickard

This can appear if Outlook clients are trying to connect to OAB virtual directory, and don't succeed for some reason. Mailbox and mailflow will work, but password prompt will appear when Outlook tries to contact OAB. Try to investigate in that direction.
Also, perform Outlook Configuration test (right click Outlook icon in task bar while holding CTRL and select Test email autoconfiguration.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Damir

Mailbox sizes increase dramatically after migration to exchange 2013

After I migrate mailboxes from exchange 2010 mailbox to 2013, the size increases.
For example -
On exchange 2010 I run get-mailboxstatistics: TotalItemSize : 6.706 GB
On exchange 2013: TotalItemSize : 9.374 GB
Anand_N

Hi Anand,
Please note that the actual space used by the mailbox database will not increase. This only refers to the attribution of space used by each individual mailbox. Actually, this happens due to the inclusion of all item properties into quota calculations, providing
a more accurate computation of space consumed by items within their mailbox. However, you can adjust mailbox size and increase mailbox quota by 40% before moving.
You can follow below cmdlet in order to increase "ProhibitSendQuota" value for all users that are not using the database quota defaults:
Get-Mailbox -ResultSize Unlimited -Filter {UseDatabaseQuotaDefaults -eq $False} |
Where {$_.ProhibitSendQuota -ne "unlimited"} | ForEach {Set-Mailbox $_ -ProhibitSendQuota "$($($_.ProhibitSendQuota).Value.ToMB() * 1.4)MB" -WhatIf}
You can have a look on this link to prevent the cause :
Mailbox migration from 2010 to 2013
Hope, this will be helpful for you.

Cross-forest migration to Exchange 2013 SP1 and Outlook 2013 SP1

Hello! I have two forest: Exchange 2010 SP2 RU5 - resource forest and Exchange 2013 SP1 - account forest. I make cross-forest migration from resource forest (linked mailboxes with account forest) to forest with Exchange 2013 SP1.
I have moved mailbox from resource forest exchange 2010 to exchange 2013 sp1 forest.
Outlook 2010 connect to migrated mailbox without any problem, but outlook 2013 sp1 cannot connect to migrated mailbox.
Error look like - cannot find exchange server.
I created new mailbox in Exchange 2013 organization and can connect to it with outlook 2010 and outlook 2013 sp1.
Someone have the same problem with migrated mailbox? How to solve it?
Truly, Valery Tyurin

You can use New-MoveRequest to perform a cross-forest move. Here is a well post and step-wise explanation you can check for cross forest migration from exchange 2010 to exchange 2013(http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/).
Moreover, you can try this utility (
http://www.exchangemigrationtool.com/ ) to accomplish this task.

ActiveSync Failures After Migration to Exchange 2013

Hi all,
I am having an issue with ActiveSync a single mailbox that has been migrated from Exchange 2007 to 2013. After the mailbox was migrated to 2013 it continued to sync as normal for a week or so. After removing the exchange 2007 server (uninstalled exchange) from
the topology, the user could no longer sync.
This is not the inherit permissions in AD issue. I had a user with that issue but this one is different.
It appears to have something to do with the app pools. The following article provides a script to recycle the app pools, when I run this, the issue is resolved but only temporarily. Within 20 mins or so, the issue returns for the user. Running the script
again works but again, it is only temporary.
http://www.expta.com/2014/04/fix-for-exchange-activesync-failures.html
Can anyone tell me why this fix only works momentarily? Is there any way (besides running the script constantly) to make the fix stick?
Any help is much appreciated.
Thanks!

Instead of restarting App pool, I would suggest looking at the IIS logs on the Client Access Server and check for the entries for this user.
If you notice either throttling/something wrong with this user's connection, troubleshoot in that direction.
also look at Event logs to see if there are any problems with App pools creating Watson dumps. (event ID 4999, 1003 etc)

ActiveSync stops working after migrating from Exchange 2007 to Exchange 2013

We have started the migration from Exchange 2007 to Exchange 2013. We've followed best practices and everything is working great except ActiveSync. I've performed Exchange migrations in the past so this is nothing new for me. I've also been referring to
a great guide which has been a big help,
http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part1.html.
Once a user is migrated from Exchange 2007 to 2013, ActiveSync stops working properly. Email can be pulled to the device (Nokia Lumia 625 running Windows Phone 8) by performing a manual sync. But DirectPush is not working. The strange part is it's not affecting
everyone who's been migrated. Anyone who is still on Exchange 2007 is not affected.
At first I thought it was our wildcard certificate. 99% of our users are running Outlook 2013 on Windows 7 or higher but we do have a few terminal servers still running Outlook 2010. Outlook 2010 was giving us certificate errors. I realized it was the wildcard
certificate. Rather than making changes to the OutlookProvider I simply obtained a new SAN certificate. Although that resolved the issues for Outlook 2010 users, ActiveSync was still a problem.
Rebooting the phones and removing the email account from the user's device and re-adding it didn't resolve the issue either.
Then I performed an iisreset on the CAS server. This didn't help either. I didn't know it at the time, but I was getting closer...
I tried using the cmdlet Test-ActiveSyncConnectivity but it gave me the following error:
WARNING: Test user 'extest_0d9a45b025374' isn't accessible, so this cmdlet won't be able to test Client Access server
connectivity.
Could not find or sign in with user DOMAIN.com\extest_0d9a45b025374. If this task is being run without
credentials, sign in as a Domain Administrator, and then run Scripts\new-TestCasConnectivityUser.ps1 to verify that
the user exists on Mailbox server EX02.DOMAIN.COM
I started reviewing how Exchange 2013 proxied information from the CAS to the mailbox server and realized the issue may in fact be on the mailbox server.
I performed an iisreset on the mailbox server and all of a sudden ActiveSync started working again. Awesome!
I can't explain why. The only thing I can assume is when some users were migrated from 2007 to 2013 something wasn't being triggered on the Exchange 2013 side. Resetting IIS resolved the issue. I guess I'll have to do an IIS reset after I perform a batch
of migrations. Disabling ActiveSync and re-enabling it for the affected users didn't help - only the IISRESET resolved the issue.
If anyone has any information as to why this happens, please chime in. Also, if anyone knows why I can't run the Test-ActiveSyncConnectivity cmdlet, I'd appreciate the help.
Thanks.

Hi,
In Exchange 2013, the Public Folder is changed to Public Folder mailbox instead of Public Folder in Exchange 2007 database.
Due to the changes in how public folders are stored, legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 servers. However, user mailboxes on Exchange 2013 servers or Exchange Online can connect to legacy
public folders. Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously. This effectively means that
there’s no coexistence between versions.
For this reason, it’s recommended that prior to migrating your public folders, you should
first migrate your all legacy mailboxes to Exchange 2013. For more information about migrating public folder from previous versions, please refer to:
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
(Please note the What do you need to know before you begin part in this link)
Regards,
Winnie Liang
TechNet Community Support

Can only access emails through OWA after migration from exchange 2007 to 2013

can only access emails through OWA after migration from exchange 2007 to 2013, in other words unable to access mails through outlook or from other Applications services.
needed RCA ... plz help..

Hi,
From your description, you can send and receive messages only when you use OWA after migration from Exchange 2007 to Exchange 2013. If I have misunderstood your concern, please let me know.
In your case, I recommend you create a new test mailbox in your Exchange 2013 and check if you can send and receive messages on Outlook. If yes, it is recommended to create a new profile to solve this issue.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

New User cannot access OWA after migrate from Exchange 2007 to Exchange 2013

Dear all,
I recently migrate the Exchange server from Exchange 2007 on Windows Server 2003 to Exchange 2013 on Windows 2012 R2. I can open the mailbox moved from Exchange 2007 without any problem. However when I created a new user in Exchange 2013, the user cannot
login the OWA, the browser will throw out following screen. Can anyone help me in this case. Thanks a lot!

Hi Winnie,
Thank for your reply. Below is the result, please note there has four exchange servers, HKAD and HKEX are the existing Exchange 2007 server. HKCAS1 and HKCAS2 are the new Exchange Server 2013 - both of xchange server 2013 are using owa.ksi.com.hk
as the external URL.
Identity                      : HKAD\owa (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           : {}
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
https://hkad.ksi.com.hk/owa
ExternalUrl                   :
Identity                      : HKAD\Exchange (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           :
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
ExternalUrl                   :
Identity                      : HKAD\Public (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           :
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
ExternalUrl                   :
Identity                      : HKAD\Exchweb (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           :
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
ExternalUrl                   :
Identity                      : HKAD\Exadmin (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           :
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
ExternalUrl                   :
Identity                      : HKEX\owa (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           : {}
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
https://hkex.ksi.com.hk/owa
ExternalUrl                   :
Identity                      : HKEX\Exchange (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           :
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
ExternalUrl                   :
Identity                      : HKEX\Exadmin (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           :
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
ExternalUrl                   :
Identity                      : HKEX\Public (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           :
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
ExternalUrl                   :
Identity                      : HKEX\Exchweb (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           :
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
ExternalUrl                   :
Identity                      : HKCAS2\owa (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           : {}
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
https://hkcas2.ksi.com.hk/owa
ExternalUrl                   :
https://owa.ksi.com.hk/owa
Identity                      : HKCAS1\owa (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           : {}
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
https://hkcas1.ksi.com.hk/owa
ExternalUrl                   :
https://owa.ksi.com.hk/owa

I would like to see all my contacts in my old outlook acount, after loading the cloud I I can only find them in the new cloud acount. How do I get them back in the old outlook acount

I would like to see all my contacts in my old outlook acount, after loading the cloud I I can only find them in the new cloud acount. How do I get them back in the old outlook acount?

In Outlook, export your contacts to a .pst or .csv file. Keep the exported file
How to export contacts from Outlook for Windows.

Exchange 2007 migrate to Exchange 2013

Dear MS Support,
I did migrate Exchange 2007 to Exchange 2013
The install complete, the exchange 2007 and 2013 can work together successful
DAG has created and work fine
Below is capture on exchange group after migrate
The exchange 2007 work fine with outlook anywhere, all the users can connected and send and receive mail in 5 year
The cerificate enroll with
Alternative Names: mail.biendongpoc.vn
The autodiscover on exchange 2007:
[PS] C:\Windows\system32>Get-ClientAccessServer | ft Identity,*uri* -AutoSize
Creating a new session for implicit remoting of "Get-ClientAccessServer" command...
Identity AutoDiscoverServiceInternalUri
BDPOC-SERVER1 https://mail.biendongpoc.vn/Autodiscover/Autodiscover.xml
I have created new certificate for Two exchange 2013
The certificate enroll with
Alternative Names: cas.biendongpoc.vn
I have create cname cas point to dag on DNS server
I have create A record autodiscover.biendongpoc.vn point to IP of dag.biendongpoc.vn
I did migrate mailbox from exchange 2007 to exchange 2013, the migrate successful , the outlook can
connected to Exchange 2013 and working perfectly
Our problem, the account exchange 2007 work not stable ,
sometime it connect to mail.abc.com, sometime it connect to cas.abc.com
If the outlook connect to cas.biendongpoc.vn, the request put password and i can't connect to exchange 2007, if outlook connect to mail.biendongpoc.vn i can connect
It is not stable for current exchange 2007
Anyone who can help me ?
Thanks

Hi
huynhtrongnhatminh,
I suggest you please go through this article.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Please check this for step by step guide.
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Please point your autodiscover and commonname to Exchange2013 CAS
Please configure your URLs. There is no CAS array in Exchange2013 but the concept of single name space remains.
You need to have an A record (e.g. legacy.domain.com) in yout external DNS and add that name (legacy.domain.com) in your certificate for exchange 2007 users to have access externally.
Configure your commonname URLs in Exchange2013. Point commonname and autodiscover to exchange2013 in both external and internal DNS servers
Configure URLshttp://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
No CASARRAY in 2013http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
Please configure splitdns or pinpoint DNS in your internal DNS server if not configured
http://exchange.sembee.mobi/network/split-dns.asp
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Object-Owner missing in Public Folder Calenders after Transition to Exchange 2013 SP1

Hi there,
we transfered all Public Folders from Exchange 2003 to 2010 to 2013 SP1. We have some Calendars with PublicFolderClientPermission Author witch includes EditOwnedItems and DeleteOwnedItems
Unfortunately the Author Rights wont work after migration. it seems like the creator of the object got lost.
since i never notices that in transitions from exchange 2003 to 2010, i think that should be related to the exchange 2013 transition.
Can anybody approve or disprove that behavior?
thanks alot

Noticed now in the Exchange 2013 Event Logs that we're getting quite a few of these warnings:
"Process <Select one exchange releated process>.exe (PID=<whatever>). Object [CN=Public Folder Database,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Contoso,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=contoso,DC=local]. Property [PublicFolderDatabase] is set to value [contoso.local/Configuration/Deleted Objects/Public Folder Database
DEL:ca62a715-05b2-4b08-ae0f-7f7c4b7e4cc3], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible."
If i take a look at that mailbox database it's obvious that it's pointing towards the old Public Folder Database, which is quite interesting as Exchange 2013 isn't supposed to used that value at all (according to http://technet.microsoft.com/en-us/library/bb123971(v=exchg.150).aspx):
[PS] C:\Windows\system32>Get-MailboxDatabase -Identity "Mailbox database" | fl
PublicFolderDatabase : contoso.local/Configuration/Deleted Objects/Public Folder Database
DEL:ca62a715-05b2-4b08-ae0f-7f7c4b7e4cc3
I'm assuming this is what happens when messing around with ADSIEdit :) So, further ADSIEdits to set that value to null on the existing Mailboxdatabases, or anyone have any other suggestions?

Office mail merges are extremely slow after upgrade to Exchange 2013

Ever since we migrated from Exchange 2007 to 2013 SP1, our employees have reported that mail merges are taking triple the amount of time to send messages. What used to take an hour is now 3 to 4 hours. Some offices are required to send upwards of 6,000
messages at a time. I know Exchange 2013 handles throttling differently than previous versions however the default (global) ThrottlingPolicy was sufficient with our previous 2007 installation. I've never had to deal much with Throttling so I'm not exactly
sure of what settings I should be looking at....also I'm not sure if this would even be related to throttling. Has anyone experienced this issue before with Exchange 2013 and could you provide any recommendations or settings that I need to be focusing on in
relation to Outlook client connections? We are currently using the GlobalThottlingPolicy for all users.

Hi,
What’s the version of Office?
The following Outlook client versions are fully supported by Exchange server 2013.
Outlook 2013
Outlook 2010 SP1 with November 2012 Cumulative Update ( available from
http://support.microsoft.com/kb/2687623 )
Outlook 2007 SP3 with November 2012 Cumulative Update ( available from
https://support.microsoft.com/en-us/kb/2687404 )
I suggest to upgrade one office client to Outlook 2013 (with word 2013) to check this issue.
Best Regards.
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]
Lynn-Li
TechNet Community Support

MS Exchange 2010 Sp3 Ent Migration to Exchange 2013

Hello,
We currently have 2 Exchange 2010 SP3 servers in 1 DAG. Both servers host CAS, Mailbox and Hub Role.
I want to introduce a 3rd Exchange 2013 Server and slowly move users onto a new DAG I build in Exchange 2013.
Can I create a 3rd Exchange 2013 Server with CAS and Mailbox Server Role and make the 3rd Exchange server (2013) a member of the existing (2010) CAS array then slowly perform local move requests for users mailboxes
from my Exchange 2010 DAG to the Exchange 2013 DAG without any disruption to my outlook, OWA and AS clients?
Exchange 2010 (Windows 2008 R2)
Exchange 2013 (Windows 2012 R2 DataCenter)

Hi,
In Exchange 2013, all Outlook connectivity (Internal and External) takes place over Outlook Anywhere(RPC/HTTP). Thus, CAS array which is used internal for RPC/TCP protocol (MAPI) no longer exists in Exchange 2013.
For your coexistence environment and the plan to migrate all mailboxes to Exchange 2013 in the future,
we need to set all virtual directories for CAS 2013 and enable Outlook Anywhere for Exchange 2010. If the mailbox is moved to Exchange 2013, the Outlook client would connect to the server which is set in Outlook Anywhere External host name
and Internal host name instead of CAS array. If all configurations are proper, CAS 2013 would also proxy the service requests for Exchange 2010 users.
Here are some reference about 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
Exchange 2013 Client Access Server Role
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Exchange Server 2013 Client Access Server High Availability
http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
Exchange 2010/2007 to 2013 Migration and Co-existence Guide
http://msexchangeguru.com/2013/05/10/exchange2013-migration/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please
make sure that you completely understand the risk before retrieving any suggestions from the above link.
Regards,
Winnie Liang
TechNet Community Support

After migration to Exchange 2013 the old outlook clients do not automatically reconfigure

Similar Messages

Maybe you are looking for