Exchange 2013 with Outlook on RDS Server is extremely slow

Exchange 2013 CU5 on Server 2012 R2 fresh install/new to domain; Outlook 2010 or 2013 on Remote Desktop server not in cached mode is slow to open, search and send messages with attachments. Opening messages and opening attachments runs quickly.
My test mailbox has 300kb worth of mail in it and sending a message with a 5Mb attachment locks up Outlook for close to 1 minute and takes another 30 to 90 seconds to disappear from the outbox and and move to sent items. This issue does not present
itself in OWA. My current testing RDS environment is a fresh install of Server 2008 R2 with Outlook 2013. No additional add-ins or AV running on the Exchange server or the test RDS server.
When cached mode is enabled, Outlook runs better as shown in Outlook 2010 (+ Exchange 2013) works extremely slow; however, I don't consider this an option because there isn't enough drive space on the RDS server to cache all of the user profiles.
Other Exchange environments - Outlook 2010 or 2013 in an RDS environment (non-cached) with Exchange 2007 or 2010 - don't show the same performance issues. Moving within Outlook and sending large attachments runs quickly.
I have checked Exchange throttling settings and monitored logs, but have not found cases where my test user is being throttled. I have also looked at turning off IPv6 based on another post's suggestion; however, I have seen conflicting information
about disabling IPv6 for Server 2012 R2, so I have not yet gone down this path.
The Exchange server is a VM on a new VMware host and has assigned 8 cores from Intel Xeon E5-2640 procs and 16GB RAM; 1TB thick provisioned database volume on a RAID 5 array with 6 x 10k RPM SAS drives. Disk queues are low on the Exchange server (in
the .20 to .70 range). My test RDS server is on the same VMware host on the same vSwitch. Another test system is on a different system, but exhibiting the same behavior.

Hi,
How about the suggestion from Festivalman?
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

Connection beetween Exchange 2013 with outlook client 2007 SP3

Hi All,
My company reinstall exchange 2013 when the previous mailbox DB error. When I implemeted a new server. I configured step by step carefully. if we use outlook 2010 connect to exchange server, send/receive work normally. But someone, uses outlook 2007 SP3,
they have somer error. They work with "cached mode", the connection from outlook to exchange server connected normally, but mail items sometime disappear in outlook client, when i check in the OWA, the mailbox item appear on this.
I tested with "online mode", the mailbox items push into outlook.I switched to "cached mode", this items haven't in outlook. Everybody who's meet the problem, please help me the solution can resolve the problem? Many thanks.
Quoc Dao

Hi,
Would you please let me know edition information of the Windows Server? Is it a Windows Server 2012, Windows
Server 2012 R2 or other?
On current situation, please refer to following KB and check if can help you.
Sometimes e-mail messages do not appear in your
Cached mode Inbox even though they were synchronized down from your mailbox
By the way. Based on your description, this issue seems to be more related to Outlook 2007. If this issue still
exists, I suggest that you should post in
Outlook forum. I believe we will get a better assistance there.
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Exchange 2013 with Outlook 2010 asking sometime for credentials

Hi Everyone,
I'm running Exchange Server 2013 on a Windows Server 2012.
Some of my user are sometime asked for credentials.
It happens both at outlook launch and when outlook is running.
And when we just cancel the credentials windows without password, outlook is connected to exchange again.
Everyone is running Office 2010 with SP1.
I have tried to put Outlook anywhere to NTLM and Negotiation authentication but it doesn't work either.
Any idea ?
Thanks in advance

I am getting this same problem. I checked all the steps in "Configure Mail Flow and Client Access" to no avail. When I click cancel in the credentials request popup, Outlook carries on and seems happy. Before long the credentials request returns
though.
We are running Exchange 2010 and have just added an Exchange 2013 Server. The errors I am getting are with new 2013 mailboxes and migrated mailboxes.
I ran "Test E-mail AutoConfiguration" and in the log, I see it first tries to contact our Exchange 2010 Server. After this fails, it then contact our Exchange 2013 Server.
SMTP=[email protected]
Attempting URL
https://smtp.domain.com/autodiscover/autodiscover.xml found through SCP
Autodiscover to
https://smtp.domain.com/autodiscover/autodiscover.xml starting
GetLastError=0; httpStatus=401
GetLastError=0; httpStatus=302
Autodiscover to
https://smtp.domain.com/autodiscover/autodiscover.xml Failed (0x800C8204)
Autodiscover URL redirection to
https://mail.domain.com:443/autodiscover/user..domain.com/autodiscover.xml starting
GetLastError=0; httpStatus=401
GetLastError=0; httpStatus=200
Autodiscover to
https://mail.domain.com:443/autodiscover/user..domain.com/autodiscover.xml Succeeded (0x00000000)
Any help will appreciated

Exchange 2013 with Outlook 2010 anywhere - Public Folders disappear from Outlook favourites

Hi,
we have a 3 server Exchange 2013 SP1 DAG published with Forefront TMG.
Outlook 2010 anywhere connection works fine (only anywhere connection is possible, there are no clients in the exchange server AD).
The users are adding public folders to their local Outlook favorites. In about 10% of the Outlook starts, those public folders are missing in the favorites. Local favorites folders are still there, public folders are connected.
After restarting the Outlook a few times, the favorites are back.
Deleting the outlook.xml brought no success, the favorites seem to be saved somewhere on the exchange server.
Outlook 2010 is up to date, all hotfixes are installed.
There are no related entries in servers or clients eventlogs, the logs of the TMG server are normal.
Does anyone have a simular behavior?
Thanks in advance!

Hi,
According to your description,it is clear that something got corrupted, but it is hard to say directly what caused it. However, there are a few troubleshooting steps to determine what caused it and you can also make a backup of your Favorite Folders list
so you can easily restore it when it still happens.
Pleaser refer to the following article:
Favorite Folders empty upon restart
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.
Hope this helps!
Thanks.
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Niko Cheng
TechNet Community Support

OWA receives mail long before Outlook (Exchange 2013 with Outlook 2010 and 2013)

I recently upgraded my Exchange environment to Exchange 2013 SP1. The Outlook users are now experiencing a delay when receiving email. When they do arrive they appear in batches, often 20-45 minutes after they were sent, from a mailbox on the same server.
Additionally, the mail appears instantly when you monitor the inbox using OWA. The users are experiencing this on both Outlook 2010 and 2013 clients configured in both cached and non-cached modes. This appears to be a problem with Outlook connecting to Exchange.
Any suggestion about how to correct this would be greatly appreciated. Thanks!

Hi,
From your description, when users use OWA, they can receive emails normally. But if they use Outlook 2010 or Outlook 2013, there is a delay in receiving emails.
I recommend you use the Outlook safe mode to determine whether the problem is caused by add-ins. Also, please make sure users have installed the Outlook latest Service Pack.
If the issue persist, please create a new profile and check the result.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2013 with Outlook 2013 - Not getting pop-up or mail tips for attachments exceeding max size

Our environment is Exchange Server 2013 CU3 and Outlook 2013 in cached mode. We have a transport rule that sets the max attachment size to 20 mb.
If someone sends an attachment larger than 20 mb they receive an NDR letting them know the message wasn't delivered because it exceeded the max attachment size. We would like for the user to be prevented from sending the message at all or to at least
get a mail tip before they try to send the message. The Outlook pop-up message that says "The file you're attaching is bigger than the server allows. Try putting the file in a shared location ..." isn't being generated for us. Not sure if that's
because we're running Exchange or not. If that pop-up isn't going to work it would be nice if the user could at least get a mail-tip warning them that the attachment exceeds the limit. But it doesn't look likes there's a mail-tip for attachment size, only
for message size. And, I've found that the message size mail-tip only works if the limit is set on the user. It doesn't seem to work if the limit is set via a transport rule.
Has anyone else gotten Outlook to present the pop-up or a mail-tip when exceeding attachment size? Any help you can offer would be greatly appreciated.

Thanks but I performed all of those trouble shooting prior to posting to the forum. But, I have found the answer!
After referring to this article;
http://technet.microsoft.com/en-us/library/bb124345(v=exchg.150).aspx
I removed the 10mb default limits from the organization config and chose to set the attachment and message size limits in our environment via transport
rules instead. That is the only way you can actually set an attachment size limit.
I had read this article several times searching for an answer;
http://support.microsoft.com/kb/2813269#appliesto
The key is here;
"If you are using an Exchange Server account, the 20-MB attachment
limit for Internet email accounts is not used by Outlook 2013. Instead, Outlook uses the limit that is configured on your Exchange server. To modify the setting that is used to control the size of a message that is sent through an
Exchange Server account, follow these steps."
The steps that follow are for Exchange 2010 but they show setting organization limits not server limits. And note that it
says the size of a message, not the size of an attachment. Since mail-tips for message size are not displayed when the limit is set via the transport rules I thought it
was possible that the same inconsistency might apply to the attachment pop-up warning. I set the organization limits and voila! The pop-up now displays when an attachment that exceeds the message size limit is added to a message.
This is exactly what I wanted. Now users won't fill up their sent items trying to send large attachments that just bounce anyway.
It would be wonderful if Microsoft would provide information about what features of Outlook are affected when you apply message size limits at the
various levels.

Exchange 2013 and Outlook 2007

Is there a new way to connect EX2013 to Outlook 2007 SP3?
MSB

Hi Baker,
According to the description, I notice that you want to migrate from Exchange 2010 to Exchange 2013 and want to know how to connect Exchange 2013 with Outlook Client 2007.
Following is an article about the migration, for your reference:
Upgrade from Exchange 2010 to Exchange 2013
http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
Outlook client uses Autodiscover and Outlook Anywhere to connect to Exchange server, please make sure services’ URLs configured correctly.
If you want to communicate with external users, you need to apply a certificate issued from a Public CA.
After configuring all the points above, please run “Get-Mailbox –Identity allen | FL *GUID*” in EMS to get mailbox GUID of allen’. Input the GUID into server name filed.
More details on “Manual configuration guide for Outlook 2010 (Exchange 2013)” for your reference:
http://support.sherweb.com/Faqs/show/manual-configuration-guide-for-outlook-2010-exchange-2013
Disclaimer:
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.
Best Regards,
Allen Wang

Exchange 2013 w/Outlook 2013 "The name of the security certificate is invalid or does not match the name of the site"

I've completed an upgrade from Exchange 2003 to Exchange 2013 and I have one last SSL message that I can't get rid of. I've installed a 3rd party cert that is working great for webmail and cell phone access but for some reason the Outlook 2010/2013
clients get prompted for a security warning. I just implemented the SSL cert yesterday and I've noticed that new installs of Outlook seem to work just fine. My Outlook 2013 client doesn't prompt me with the message but I have other users who are
still getting the "The name of the security certificate is invalid or does not match the name of the site" error. The domain on the cert error show up as server.mydomain.local. I've gone through all the virtual directories and pointed
all of my internal and external URL's to https://mail.mydomain.com. This made one of the two warnings go away but not the second. I've dug around on google and gone through everything I could find here and as far as I can tell my internal
and external url's are configured properly and I can't figure out where this error is originating from. Any ideas on where I should look outside of the virtual directories?
I'm including a good link I found that contains all of the virtual directories I updated. I've checked them through both CLI and GUI and everything looks good.
http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
http://jaworskiblog.com/2013/04/13/setting-internal-and-external-urls-in-exchange-2013/

Hi,
When the Outlook connect to Exchange 2013/Exchange 2010, the client would connect to Autodiscover service to retrieve Exchange service automatically from server side. This feature is not available in Exchange 2003 Outlook profile.
Generally, when mailbox is moved to Exchange 2013, the Outlook would connect to server to automatically update these information. It needs time to detect and update the changes in server side. I suggest we can do the following setting For autodiscover service:
Get-ClientAccessServer | Set-ClientAccessServer –AutodiscoverServiceInternalUri https://mail.mydomain.com/autodiscover/autodiscover.xml
Please restart IIS service by running IISReset in a Command Prompt window after all configuraions.
Regards,
Winnie Liang
TechNet Community Support

Lync 2013 with outlook 2010 meeting error

I have installed lync basic 2013 with outlook 2010. The meeting add in is in place, but I get an error when trying to set up a Lync meeting "unable to identify the calendar owner"
What to do to correct this?

Hi,
You seem to get the error “Unable to identify the calendar owner. Please contact your support team.”
This is caused if the Online Meeting Add-in for Lync 2010 cannot determine the Simple Mail Transfer Protocol (SMTP) or Session Initiation Protocol (SIP) address of your Microsoft Outlook account. You need to contact your Exchange administrator.
If you mail server does not support online meeting(such as a pop3 server), you can join the meeting as anonymous user through the meeting URL.
You can also create a new profile to check the result:
http://support.microsoft.com/kb/829918/en-us
Regards,
Melon Chen
TechNet Community Support

Exchange 2013 with CAS and HLB in different sites

Hello...
Coming son, we'll deploy Exchange 2013 with high availability in all roles. The CAS and Hub Transport roles, are with a HLB; and the Mailbox with DAG. The infrastructure is formed by:
Citi1:
- AD Site 1
- 1 Hardware Load Balance: HLB01 to load balance the CAS and Hub Transport of Exc01 and Exc02
- 2 Exchange: Exc01 and Exc02 multiroles Exchange Server 2013
- 1 DAG for Citi1 databases: conformed by the Exc01 and Exc02
Citi2:
- AD Site 2
- 1 Hardware Load Balance: HLB02 to load balance the CAS and Hub Transport of Exc03 and Exc04
- 2 Exchange: Exc03 and Exc04 multiroles Exchange Server 2013
- 1 DAG for Citi2 databases: conformed by the Exc03 and Exc04
The Active Directory is one forest with one domain. The Domain Controllers are Windows Server 2012. The Site1 and Site 2 are connected by a WAN link. The accepted domain is domain.com. The smtp address is @domain.com
How to make that users of Citi1 always connect throught the HLB01 to their mailboxes; and the users of Citi2 always connect throught the HLB02 to their mailboxes if the autodiscover.domain.com is the same for all users?
I have not found documentation about
this architecture. Please help me.
Thank you very much.
Best regards, Javier Uribe

Hi javier,
In this issue, I guess you can try to use site affinity for the Autodiscover service for intranet-based traffic.
To use site affinity, you specify which Active Directory sites are preferred for clients to connect to a particular Autodiscover service
instance.
You configure site affinity by using the
Set-ClientAccessServer cmdlet. This cmdlet lets you specify the preferred Active Directory sites for connecting to the Autodiscover service on a specific Client Access server. After you configure site affinity for the Autodiscover service,
the client will connect to the Autodiscover service as you specified.
According to your needs, you might want to allow users in the site1 to use site1, users in site2 to use site2 to access the Autodiscover Service.
You can configure site scope for Client Access servers in the Site1 by following command.
Set-ClientAccessServer -Identity "site1-cas" -AutodiscoverServiceInternalURI "https://internal.domain.com/autodiscover/autodiscover.xml" –AutodiscoverServiceSiteScope “site1”
The Command for Site2.
Set-ClientAccessServer -Identity "site2-cas" -AutodiscoverServiceInternalURI "https://internal.domain.com/autodiscover/autodiscover.xml" –AutodiscoverServiceSiteScope “site2”
Hope it helps
Best regards

Can i upgrade exchange 2007 to exchange 2013 on same small business server 2008 machine?

Hi,
I have small business server 2008 with exchange 2007 installed in my organization,
Now I need to upgrade exchange 2007 to exchange 2013 on same small business server 2008 standard edition.
I already tried to upgrade but not successful.
can i upgrade exchange 2007 to exchange 2013 on same small business server 2008 machine or any alternate through which it is possible.
Please share any MS article if it not possible.
Thank you in advance
Regards
arun av

Hi Arun,
Its really great that you want to move and upgrade old Exchange to new Exchange server. The manual steps and guide is already recommended to you.
Moreover, I would like to recommend you to use an automated tool to upgrade your Exchange server 2007 to exchange 2013. I have tried and test tool to do Exchange Migration 2007 to 2013. You can follow the link
http://www.exchange2007to2013migration.exchangemigrationtool.com/. It will also help you to do Intra-Cross forest migration if you required.
Hopefully my recommendation will surely help you.
Thanks,
Walter

Exchange 2013 Issue: Outlook 2010 auto populating the From Tab when forwarding email

Exchange 2013 Issue: Outlook 2010 auto populating the From Tab when forwarding email
I am running Exchange 2013 and I have an end user who connects to it via Outlook 2010. All was going well till he went to forward an email and he noticed that the From button appeared and auto populated the sender's email address.
I have clicked the Empty Auto Complete List in Outlook's Send messages... still displayed the From tab when forwarding.
I recreated the profile in outlook... same thing.
I created the profile with outlook 2013... same thing.
There is only one user profile setup in Outlook.
(I know the from tab usually appears when you have multiple profiles setup in Outlook and/or when you configure the "From" tab.)
I opened the end user's email in Exch 2013's OWA... what was different here was when I clicked on the email and it opened, it did NOT have the Reply or Forward option... and it displayed as a "Draft" email.
Does anyone have any ideas?

So are you saying that the from button is filling the option with the original senders address (eg the person who sent the message to your user), or that it's filling in the your users address (in which case I don't understand what the issue is, since
it IS going from your user)?

Migration Exchange 2010 to Exchange 2013 with CAS Array and DAG

Dear All,
I am starting the migration of Exchange 2010 2 servers (CAS/Mailbox) with DAG no CAS Array to Exchange 2013 with 2 servers CAS array and 2 Mailbox servers with DAG. I read on some blogs that no requirement of CAS array on Exchange 2013. My concern how to
configure NLB on CAS servers for the client to connect.
Please guide and have any deployment guide for this, kindly share.
Thanks

Hi ,
As you said there is no use and meaning of having the cas array in exchange 2013 and also thanks a lot to Microsoft for introducing an single namespace facility in exchange 2013.
My suggestion and Microsoft recommendation should be to go with hardware load balancers for exchange 2013 rather than using the windows NLB and round robin method.
Why we need to go for HLB ?
Disadvantages
of some load balancing methods :
Windows
NLB :-
If you use Windows NLB then it can provide redundancy on server level failure and not on application level.
DNS
round robin :-
In case if we use the windows round robin method for load balancing then it wouldn't provide server level
and application level redundancy during the failures.At the Same time we need to manually adjust the DNS records during the server failure but on the client end dns caches will create the issues.
Configuring NLB for exchange 2013 :
http://msexchangeguru.com/2013/08/14/windowsnlb/
NLB configurations for exchange 2010 and 2013 will be same.
Configuring round robin for exchange 2013 :
http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
Advisable method is to have the CAS and MBX roles on the same box if NLB not comes it to play.Because windows failover clustering and NLB cannot be configured on the same box.In exchange 2013 cas role is a stateless server role so there is no need to have
that role on a separate box.
Thanks & Regards S.Nithyanandham

Exchange 2013-SP1/Outlook 2013 connectivity issue.

We couldn't make Outlook 2013 (latest updates) to connect to our Exchange 2013-SP1 through the Internet.
Any PC inside the LAN (on the domain or outside the domain) can connect normally.
Any PC outside the LAN (WAN) cannot connect, it keep showing this error:
"The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
OWA is working fine from the WAN, smartphones (Android & Apple) are also working fine from the WAN.
Port 443 is open on the firewall.
So what we are missing!

Hi,
Firstly, I'd like to say, in Exchange 2013 SP1, Outlook 2013 SP1 clients may use MAPI over HTTP to connect to the server.
Before going further, let's confirm if they use MAPI over HTTP: Get-OrganizationConfig | FL MapiHttpEnabled
If the value of the above property is true, I recommend the following troubleshooting:
1. Check if your Exchange 2013 SP1 server is running on Windows Server 2012 R2.
2. Check MAPI virtual directory settings: get-MapiVirtualDirectory |fl
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 - Prevent Outlook Clients From Connecting To A CAS Server In A Different AD Site

Hi all,
I could really do with your help!
We have 3 physical sites, A, B & C, with sites A & B having a really fast low latency links between them, so from an AD point of view they are 1 site. Site C has links to both sites A & B, but the link is a lot slower.
We have an exchange design with 3 servers (one located at each physical site) that will form a DAG spread over the 3 physical sites. Ideally we will separate the CAS and mailbox server roles out and have them controlled by a hardware load balancer,
however we can have both roles on the same server if required.
What we want, is to prevent is a situation where an outlook client in site C connects to a CAS server in site A/B with the mail being hosted on a mailbox server in site C therefore traversing the network twice to get its mail.
From doing the Microsoft training course, my understanding is that in Exchange 2013, the CAS server only proxy's the request on to the mailbox server and does not redirect the request to the CAS server in the site where the mailbox server resides.
I have seen information online stating that a single namespace is the way to go as long as your site links/network bandwidth is good, but nothing to help with our scenario.
Has anyone else come across this situation and how did you get round it?
Thanks in advance :)

Hi Johnson,
Based on my knowledge, Outlook Client will connect to the CAS server which in local first.
Please check whether the CAS server that in site C is healthy.
If the CAS server in site C is healthy, please disable the CAS Load Balance for testing.
Also found a useful blog for your reference:
Exchange 2013 Client Access Server Role
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2013 with Outlook on RDS Server is extremely slow

Similar Messages

Maybe you are looking for