Import Calendar Entries to Exchange 2013 Causes Outlook Calendar View Problems

Today I was working on a way to import company holidays for 2014 into people's calendars. We're running Exchange 2013. Most users have Outlook 2010, but I'm on the bleeding edge with Outlook 2013.
The best method I found online for adding events to everyone's calendar involved creating a calendar in a PST file that contained all of the company holidays and then using the Exchange 2013 Management Shell to import the PST file into people's calendars.
I created the calendar in a PST using Outlook 2013. Each holiday is an all day appointment. I then used the management shell to import those appointments into my calendar. Outlook was running when I ran the import.
After the import completed, I went to look at my calendar and Outlook 2013 crashed. I restarted it, clicked on my calendar and it crashed again. After some digging, I found a suggestion that I start Outlook with /cleanviews. That seems
to have corrected the problem. All appointments appear as expected. Well, that was ugly. But I'm the only one on Outlook 2013 right now, so it's not a showstopper.
I then found a victim running Outlook 2010 for my next import experiment. Outlook 2010 didn't crash. But the calendar view did reset to a list view instead of whatever the user was running before. Strange... I ran the test again with
another person and was able to reproduce the result. All appointments are present, but Outlook feels the need to change views?
Does anyone have a suggestion for how to import these appointments without the calendar view being reset? I don't want to think about all the support calls we're going to get when people's calendar view gets changed to a list view.
Thanks
Patrick

Hi Patrick,
Is the use able to change the calendar view manually? Please check whether all calendar items are in list view both in OWA and Outlook? Please try to import the PST file from Outlook side to check whether the issue persists.
Thanks,
Winnie Liang
TechNet Community Support

Similar Messages

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

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)?

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-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 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

Unable to connect to Exchange 2013 using Outlook 2010/2013 with latest patch

Dear All,
I'm setting up Exchange 2013 CU2 coexist with Exchange 2010 SP3. Since we are still planning and testing, the internet is still pointing to 2010 for send/receive mails.
The 2013 environment are:-
2 X CAS server with MS NLB configured
2X MBX server with DA
Internal NLB/licent access: excas2013.int.my.domain
External access (current set on 2010 as well): webmail.my.domain
Certificate with valid subject name has been import to 2013 and 2010:
CN: webmail.mydomain
SAN: excas2013.int.my.domain
SAN: excas.int.my.domain (for 2010)
I am able to connect to my Exchange 2010 user thru 2013 CAS server and proxy to exhcnage 2010 by outlook. However, I cannot connect to Exchange 2013 user by outlook. During mail profile create of Exchange 2013 user by autodiscover (pointed to exchange 2013),
the process looks good:-
Establish network connection (checked)
Searching for [email protected] server settings (checked)
Log on to server
The process stop at "Log on to server" and a windows prompt, saying:
The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
Clicked OK, I can see:-
MS Exchange Server:
[email protected]
Mailbox:
=SMPT:[email protected]
WHen I click "Check Name", it said The name cannot be resolved.
I have no idea of what is going on. Just want some help~

I have checked the iis log:-
2013-09-23 06:58:29 10.144.144.71 POST /autodiscover/autodiscover.xml &cafeReqId=99ed5467-a294-481c-95eb-9b21d6530404; 443 mydomain\training101 10.144.85.4 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7106;+Pro) 200 0 0 8018
2013-09-23 06:58:29 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f4652a19-2e8e-4652-a007-0cf0b7fb792e&cafeReqId=f4652a19-2e8e-4652-a007-0cf0b7fb792e; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:29 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=c48cda77-6008-423b-8e8b-d6d40f4d1b39&cafeReqId=c48cda77-6008-423b-8e8b-d6d40f4d1b39; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:29 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=033f1ce4-43ba-49b1-b226-f4cc357e7702&cafeReqId=033f1ce4-43ba-49b1-b226-f4cc357e7702; 443 - 10.144.85.4 MSRPC 401 1 2148074252
15
2013-09-23 06:58:29 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=d2424d25-ca9e-4867-922f-e527b041d9db&cafeReqId=d2424d25-ca9e-4867-922f-e527b041d9db; 443 - 10.144.85.4 MSRPC 401 1 64 0
2013-09-23 06:58:31 10.144.144.73 POST /autodiscover/autodiscover.xml &cafeReqId=ff35f49b-e418-4d55-b66c-dbae509cc12f; 443 - 10.144.92.17 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6662;+Pro) 401 1 2148074254 0
2013-09-23 06:58:31 10.144.144.73 POST /autodiscover/autodiscover.xml &cafeReqId=033f8ed6-d7ce-41b2-8ed2-e275e22e53be; 443 mydomain\tkchung 10.144.92.17 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6662;+Pro) 200 0 64 15
2013-09-23 06:58:37 10.144.144.71 POST /powershell serializationLevel=Full;ExchClientVer=15.0.712.24;clientApplication=ManagementShell;TargetServer=;PSVersion=3.0&sessionID=Version_15.0_(Build_711.24)=rJqNiZqNgbqnsr3Py9GWkYvRlZqc0ZyQkoHOxsvOxsbJzczNgcbQzczQzc/OzN/Ixc/KxczI376y&cafeReqId=5350aa81-6668-489e-b099-3b3647115f10;
80 mydomain\Administrator 10.144.144.71 Microsoft+WinRM+Client 500 0 0 180040
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f961c596-efff-4696-9188-611a0d151601&cafeReqId=f961c596-efff-4696-9188-611a0d151601; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=753d8852-ce19-459c-ac78-849c3e51e0a1&cafeReqId=753d8852-ce19-459c-ac78-849c3e51e0a1; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=c9e86049-c883-4b03-8546-143909361a80&cafeReqId=c9e86049-c883-4b03-8546-143909361a80; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 64 78
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=327ace4c-b2c8-44c1-95ba-7871727f60ef&cafeReqId=327ace4c-b2c8-44c1-95ba-7871727f60ef; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 109
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=a7c8daa9-e458-4f2d-b388-7300e8679dcd&cafeReqId=a7c8daa9-e458-4f2d-b388-7300e8679dcd; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=c40afede-dd8f-4ac7-a3dd-827872bb2e76&cafeReqId=c40afede-dd8f-4ac7-a3dd-827872bb2e76; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=2dc56148-1900-4044-b72a-4b13e5e871f0&cafeReqId=2dc56148-1900-4044-b72a-4b13e5e871f0; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 64 15
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=9475aad3-9537-4dac-86cb-6fdb187fa148&cafeReqId=9475aad3-9537-4dac-86cb-6fdb187fa148; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 31
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=11a54e96-d8d8-4649-8e01-f8138ebf7b8d&cafeReqId=11a54e96-d8d8-4649-8e01-f8138ebf7b8d; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=b1a3e503-1077-4144-84df-fcdb65a7eea4&cafeReqId=b1a3e503-1077-4144-84df-fcdb65a7eea4; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=5b5639ba-4c91-4351-bda6-bcec46d6b218&cafeReqId=5b5639ba-4c91-4351-bda6-bcec46d6b218; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 0 15
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f200806f-3294-4210-8940-e3fee0385ccd&cafeReqId=f200806f-3294-4210-8940-e3fee0385ccd; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 46
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=675d6515-85da-43fa-9cd8-0a18ac06a71f&cafeReqId=675d6515-85da-43fa-9cd8-0a18ac06a71f; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=b97b2c3e-5309-4927-8330-fe0f339b5930&cafeReqId=b97b2c3e-5309-4927-8330-fe0f339b5930; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=504d462a-db21-4e4b-8568-79e4099d78c1&cafeReqId=504d462a-db21-4e4b-8568-79e4099d78c1; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 0 31
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=b4757b1e-8428-454a-91df-ca0a2153144f&cafeReqId=b4757b1e-8428-454a-91df-ca0a2153144f; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 46

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 - 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

Mailboxes migrated to Exchange 2013 - some Outlook profiles do not auto-update

** EDIT WITH SIMPLIFIED QUESTION:
Should I be able to manually create a profile in my Exchange 2013 environment without knowing the
GUID@DOMAIN server name? When I specify the Ex2010 server name and Outlook Anywhere settings, the server name does not auto-resolve to the GUID as other threads suggest. I am curious whether others are able to manually
create a profile without knowing the GUID@domain.
Hi all,
Our computers have Outlook configured to automatically configure a profile without any intervention. The profile is pointing to Exchange 2010, which is still running in our environment with Exchange 2013. When a user logs into a computer and
launches Outlook for the first time, Outlook fails to connect and a "Cannot open your default-email folders" error occurs.
I have verified that the Outlook Anywhere settings are configured correctly.
If I delete the profile and create a new one using Autodiscover, everything works fine.
Occurs on all clients - 2007, 2010, 2013, fully patched).
To troubleshoot, I attempted to manually create a new profile. I supplied the Exchange 2010 server name, and configured Outlook Anywhere. When hitting "Check Name", the server name stays to Exchange 2010 (does not switch to
[email protected]). When I launch Outlook, the connection fails. Again, an autodiscovery succeeds.
From my reading, it appears that Outlook should be updating the profile with the new GUID server name when it attempts to connect. The RPCClientAccessServer setting on the Exchange 2013 databases points to the Exchange 2010 CAS Array names.
Any ideas?
Thanks for your hel

Thanks for the reply .
AutodiscoverInternalURI is pointing to the Exchange 2013 environment, and is working fine when auto creating the profile. The Test Autodiscover function returns the correct URL for the mailboxes. The problem comes when manually creating
a profile. Other threads indicate that a manually created profile should auto change the server name when the Check Name option is selected, but mine remains with the Ex2010 cas name listed on the database, and the creation fails.
However, if the user had previously connected to Ex2010 prior to the mailbox move, the profile successfully changes to Ex2013. Only during manual creation does it fail, which is a problem because our existing PCs are configured to create
profiles without autodiscover.

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 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

How do i connect manually to Exchange 2013 from Outlook 2007/2010 in another forest?

Hello All,
I have a source organization: Windows 2003 domain + Exchange 2010 SP3 + smtp domain acme.com
Target organization: Winows 2012 R2 domain + Exchange 2013 CU3 + smtp domain acme.com
We are migrating to target organization.
I want to connect Outlook 2007/2010 to their target mailbox (Exchange 2013) from a machine which is joined to Source DOmain.
I couldn't use autodiscover, because as the machine is joined to source domain, autodiscover it's mapping to Exchange 2010.
It only works when I machine is joined to target domain.
Any idea how to connect manually to eXCHANGE 2013 mailbox from a machine which is joined to source domain?
Regards
José Osorio

Hi,
Firstly, I’d like to explain, Autodiscover service can be used cross forest:
1. the two forests must be trusted.
2. configure a mail contact in the original forest.
For more information, please refer to the partition named how to configure the Autodiscover service for cross-forest moves in the following article:
http://technet.microsoft.com/en-us/library/jj591328(v=exchg.141).aspx#BKMK_ConfigureForCrossForestMoves
Thanks,
Angela Shi
TechNet Community Support

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

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

Import Calendar Entries to Exchange 2013 Causes Outlook Calendar View Problems

Similar Messages

Maybe you are looking for