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.

Similar Messages

Free/Busy not working after mailbox migration to Exchange 2013

I'm in the process of migrating user mailboxes from Exchange 2007 to Exchange 2013
It seems that many of the users (not all) are having problems seeing free/busy once they have been migrated. If we remove the Outlook profile and recreate it, all is good. Problem is that this is happening to more and more people. Everyone
is on Outlook 2010
Test-OutlookWebServices -ClientAccessServer Ex2013 -identity MyName -MailboxCredential $cred    Results in:
Autodiscover: Outlook Provider Failure
Exchange Web Services          Failure
Availability Service           Skipped
Offline Address Book           Failure
The same if I run that command against the Exchange 2007 server.
What am I doing wrong?

I should have mentioned that. Yes, OWA works perfectly for the affected users. Just as deleting their Outlook profile and recreating a new one does.
Results of Get-WebServicesVirtualDirectory:
Identity    : Exch2007Srvr\EWS (Default Web Site)
InternalUrl : https://legacy.company.com/EWS/Exchange.asmx
ExternalUrl : https://legacy.company.com/EWS/Exchange.asmx
Identity    : Exch2013Srvr\EWS (Default Web Site)
InternalUrl : https://mail.company.com/ews/exchange.asmx
ExternalUrl : https://mail.company.com/ews/exchange.asmx
The URL you reference above is actually the site I used to perform migration.
What's interesting (at least to me) is that on my machine I did not have any issues with seeing calendars. The Test E-mail AutoConfiguration (without Guessmart), I get prompted for my password over and over; however, after clicking on cancel I
get:
Attempting URL
https://mail.company.com/autodiscover/autodisconver.xml found through SCP
Autodiscover to
https://mail.company.com/autodiscover/autodisconver.xml starting
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
Autodiscover to
https://mail.company.com/autodiscover/autodisconver.xml Failed (0x80040413)
Attempting URL
https://autodiscover.company.com/autodiscover/autodisconver.xml found through SCP
Autodiscover to
https://autodiscover.company.com/autodiscover/autodisconver.xml starting
GetLastError=0; httpStatus=200.
Autodiscover to
https://autodiscover.company.com/autodiscover/autodisconver.xml Failed (0x800C8203)
Autodiscover to https://company.local/autodiscover/autodiscover.xml starting
GetLastError=12029; httpStatus=0
Autodiscover to https://company.local/autodiscover/autodisconver.xml Failed (0x80004005)
Autodiscover to
https://autodiscover.company.local/autodiscover/autodisconver.xml starting
GetLastError=0; httpStatus=0
GetLastError=0; httpStatus=200
Autodiscover to
https://autodiscover.company.local/autodiscover/autodisconver.xml Failed (0x800C8203)
Local autodiscover for company.local starting
Local autodiscover for company.local Failed (0x8004010F)
Redirect check to
https://autodiscover.company.local/autodiscover/autodisconver.xml starting
Redirect check to
https://autodiscover.company.local/autodiscover/autodisconver.xml Failed (0x800C820D)
Srv Record lookup for hydraforce.ads starting
Srv Record lookup for hydraforce.ads Failed(0x8004010F)
However, when I did this on a system that cannot see any calendars, it all works perfectly.
Browsing to
https://autodiscover.hydraforce.com/autodiscover/autodiscover.xml does result in Error Code 600

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

Litigation Hold Mailbox Migration to Exchange 2013

Hello,
We have in our organization few mailboxes (Exchange 2010) which are enabled for Litigation Hold for a purpose. Now since we are moving to Exchange 2013, need to understand what happens to those mailboxes after migration.
Neilesh

Hi Neilesh,
Below cmdlet would give you the actual mailbox size including the deleted items(changed hold items etc)
Get-MailboxFolderStatistics -Identity contoso\chris | Select Name,FolderSize,ItemsinFolder
Recoverable Items 127.5 KB (130,553 bytes) 54
Deletions 0 B (0 bytes) 0
Purges 0 B (0 bytes) 0
Versions 0 B (0 bytes) 0
Reference:
Reporting Mailbox Folder Sizes with PowerShell
Regards,
Satyajit
Please“Vote As Helpful”
if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

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

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

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

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

OWA still redirects to Exchange 2007 (legacy) after mailbox-move to Exchange 2013

Hi,
I am in the process of implementing Exchange 2013 in coex with 2007. I am testing now in a copy of the production environment and have installed the Exchange 2007 SP3 RU11 prior to installing Exchange 2013 using the SP1 media.
We use a wildcard certificate and I prepared the Exchange 2007 internal/external URLs for OWA/OAB/etc to use the legacy.domain.com names and in Exchange 2013 I set them all to email.domain.com. Exchange 2013 has Outlook Anywhere configured.
All tests like autodiscover (internally via SCP) run fine and for a new Exchange 2013 mailbox the Outlook and OWA functionality is as expected. A mailbox still on 2007 also connects fine via Outlook and while connecting to OWA (using the htps://email.domain.com/owa
url) also redirects me to https://legacy.domain.com/owa just fine.
HOWEVER: after a successfull mailbox-move from 2007 to 2013 my OWA logon-request STILL get's redirected to the 2007 legacy URL. When I then logon again on the 2007 OWA I get the message that I should connect to the 2013 URL and end-up in a loop.
Anyone any tips where to search?
Many thanks in advance.
Best regards and many thanks in advance, Eric Vegter

This seems to be an outstanding issue.
We just performed a fresh install of Exchange 2013 on a Windows Server 2012 R2 operating system. We're migrating from our existing Exchange 2007 server. At the moment we have everything properly setup in a co-existence state. All we lack is to complete the
migration of our mailboxes from the 2007 DB to the 2013 DB.
In performing the first mailbox move, to test the migration process and make certain mail flows as expected, we noticed this same problem. Before reading through this thread, I was able to assign Full Access to a delegate user and then perform the "Open
Mailbox" feature from a 2013 user's account. This was successful in opening the mailbox within OWA 2013. However, I still could not access the account by simply logging into the Outlook Web App. It would login, then proxy back to OWA 2007 with the message,
"Use the following link to open this mailbox with optimal performance:
http://mail.domainname.com/"
After reading about cycling the OWA app pool, I immediately tried it as a workaround and it worked. It is a little frustrating going about it in this way. Hoping to see more activity on this thread.
-Lorne

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 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 2010 dag migration to exchange 2013 help

If I want to use the Same mailbox servers and upgrade them to exchange 2013, what is the recommended way? I have a 4 member exchange 2010 DAG.
I was thinking (where A,B,C,D are mailbox servers, A,B are in one site and C,D another active directory site):
A B -------------- C D
Remove A and C from the 2010 DAG, Format and install Exchange 2013 on both, and create a 2013 dag :
A1 ----------- C1
B ------------- D
Then move across all mailboxes from B to A1. Upgrade B and D to exchange 2013 and put them in the DAG
A1 B1 ----------- C1 D1
Does this make sense ? I am trying to do this while having as much high availability as possible during the transition. I have no extra servers so I have to use the existing server hardware.
Anand_N

Hi,
When you want to migrate a DAG from Exchange 2010 to Exchange 2013, you should first remove the mailbox server from the DAG in Exchange 2010 and then move mailboxes from database in this mailbox server to Exchange 2013. After all mailboxes have been migrated
to the Exchange 2013 mailbox server, when the new server is ready, it can become a member of the Exchange 2013 DAG.
Here is an article about migration DAG from Exchange 2010 to Exchange 2013 for your reference.
Migrating an Exchange 2010 DAG to Exchange 2013
http://windowsitpro.com/blog/migrating-exchange-2010-dag-exchange-2013
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.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Migrating AD Exchange 2013 Objects to a new AD Domain

I have a client 'new company' (NC) who is splitting from the 'parent company' (PC). They are using a 3rd party tool to conduct the AD migration/split.
The PC AD domain is on Windows 2012 Servers and has trust relationship with the NC AD domain also running on windows 2012 server. The users and computers have been successfully migrated/stubbed to the NC domain, however, the Exchange 2013 objects
are not migrating over to the NC AD domain using the 3rd party AD migration tool.
Question, does any one have suggestions on how to migrate the exchange 2013 objects from the PC AD to the NC AD ?
What techniques can be used ?
Thanks in advance
RK

What 3rd party tool are you using and have you contacted their support already? You can use the native tools to migrate mailboxes (I do all the time) but I wouldn't try and mix the native tools and a 3rd party tool on the same migration unless I was sure
what the end result would be.

Configure legacy public folders where user mailboxes are on Exchange 2013 servers

Hello all,
I have mailboxes on an exchange 2013 server than need access to public folders on a 2010 server before I migrate them over. I followed the commands in the TechNet article with the subject "Configure legacy public folders where user mailboxes
are on Exchange 2013 servers" (sorry, I wasn't allowed to insert a link because I wasn't verified?). The problem is when I run the last command of "Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes ProxyMailbox1,ProxyMailbox2,ProxyMailbox3"
on the 2013 server, using the mailbox name I had created, it says it cannot be found. Of course I checked and the mailbox exists, is configured properly, and so is the new database. The 2013 EAC also sees the mailbox with no issues.
Can someone tell me why I am getting this error?
Thanks,
Shaibal

Hi Mavis,
Thank you for your response. I am the full domain admin, and check and was part of both groups mentioned above. Also, I have only one 2010 server with public folder, and so the command I am running on the 2013 looks like this: Set-OrganizationConfig
-PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox1. I even just created a second user and mailbox using the console instead of the shell, and still no luck.
Below is the error I get:
[PS] C:\Windows\system32>Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox2
Couldn't find object "PFMailbox2". Please make sure that it was spelled correctly or specify a different object.
    + CategoryInfo          : NotSpecified: (:) [Set-OrganizationConfig], ManagementObjectNotFoundException
    + FullyQualifiedErrorId : [Server=ZOR-EXCHANGE01,RequestId=cc567b2f-34d8-41ba-9261-143223566e06,TimeStamp=3/5/2015
    4:36:10 PM] [FailureCategory=Cmdlet-ManagementObjectNotFoundException] 2EF24201,Microsoft.Exchange.Management.Sys
temConfigurationTasks.SetOrganizationConfig
    + PSComputerName        : zor-exchange01.zubatkin.lan

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

Similar Messages

Maybe you are looking for