Error upgrading form exchange 2010 to exchange 2013

Hello,
I have Exchange 2010 sp3 running on win server 2012 R2 sp1 standanrd. I would like to upgrade to exchange 2013 and I read that installation of exchange 2013 is coexistent with exchange 2010 already installed. But When I try to install exchange 2013 I keep
getting this error :"Exchange server is in an inconsistent state. Only disaster recovery mode is available. Please use Setup /m:RecoverServer to recover this Exchange server." But after closing set up the server is still running
fine.

Hi,
Based on my research, the issue can occur when the Exchange server object already exists within Active Directory.
Thus, I’d like to confirm the following information:
1. Does your new Exchange 2013 server have the same server name with the previous one?
2. Have you change your Exchange 2010 server name to legacy.domain.com?
Here is a similar thread you can refer to:
http://social.technet.microsoft.com/Forums/exchange/en-US/20bab6f7-56e6-49b9-94df-48707fb915f7/installation-errorfresh-install-on-a-fresh-clean-server-2012?forum=exchangesvrgeneral
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Similar Messages

Exchange 2013 - can no longer move mailboxes from Exchange 2010 to Ex 2013.

Migrating to Exchange 2013 from Exchange 2010. Created Ex 2013, moved some mailboxes OK. Then could no longer move mailboxes. No errors. The Migration email says complete. Synced: none, Total Mailboxes: none.
Tried several mailboxes. Same result.
Ex 2010 is SP3 RU6, (at least it says RU6 is installed in Programs/Features. The build is for SP3 w/o RU6???)
Ex 2013 is SP1 aka CU4.
How to proceed???
john11

After many attempts to fix the issue (move remaining 4 mailboxes from Exchange 2010 to Exchange 2013) I contacted Microsoft and we resolved the issue. Here's how.
btw - Thanks for the suggestions from Ed. However, they did not seem to move us forward.
What did work:
1. On the Exchange 2010 box, create a new database. (Someone else suggested this also). Then move the remaining Exchange 2010 mailboxes to this new db. Then after that, move the 4 mailboxes to Exchange 2013 using the GUI on Ex 2013. This only worked for one
of the four mailboxes. The other 3 failed.
2. Apparently, we need to restart the Microsoft Exchange Mailbox Replication service on the Exchange 2013 after several failed move attempts to clear cache related to the moves.
3. Then on the Exchange 2013 box, use this Exchange shell command:
New-MoveRequest -identity "[email protected]" -TargetDatabase "Exchange 2013 DB name" -BadItemLimit '500' -verbose
This moved the remaining 3 mailboxes including the Discovery mailbox. It took some time. But we could check the progress using
Get-MoveRequest
The MS Tech was terrific. Really knew his stuff. And all mailboxes are on Exchange 2013. Well, the last one is still moving, but I am optimistic.
Thanks for the suggestions. I had to get this done and the MS Tech made that happen.
john11

Exchange 2010 to Exchange 2013 mail flow?

We are planning to migrate Exchange 2010 to Exchange 2013.
I understand that we need to upgrade the CAS to 2013 for Internet Facing.
What about mail flow. Currently, Internet mail flows to Exchange 2010 (single site). Can I keep it for sometime after introducing 2013 and do the cutover of HUB once all the mailboxes are moved to 2013? Or I have to get the mail flow to 2013 first.
Also, how does HUB 2010 transfer mail or receive mail from 2013? Does it get from the CAS proxy in 2013 or from HUB?
Thanks!!!

Yes, you can. But my preference is to move the mail routing early in the migration, usually even before moving mailboxes, because I believe it reduces the risk of a service interruption.
I believe it goes through the front-end transport on the CAS, since that is the TCP port 25 service.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2010 to Exchange 2013 Migration and Architect a resilient and high availability exchange setup

Hi,
I currently have a single Exchange 2010 Server that has all the roles supporting about 500 users. I plan to upgrade to 2013 and move to a four server HA Exchange setup (a CAS array with 2 Server as CAS servers and one DAG with 2 mailbox Servers). My
goal is to plan out the transition in steps with no downtime. Email is most critical with my company.
Exchange 2010 is running SP3 on a Windows Server 2010 and a Separate Server as archive. In the new setup, rather than having a separate server for archiving, I am just going to put that on a separate partition.
Here is what I have planned so far.
1. Build out four Servers. 2 CAS and 2 Mailbox Servers. Mailbox Servers have 4 partitions each. One for OS. Second for DB. Third for Logs and Fourth for Archives.
2. Prepare AD for exchange 2013.
3. Install Exchange roles. CAS on two servers and mailbox on 2 servers. Add a DAG. Someone had suggested to me to use an odd number so 3 or 5. Is that a requirement?
4. I am using a third party load balancer for CAS array instead of NLB so I will be setting up that.
5. Do post install to ready up the new CAS. While doing this, can i use the same parameters as assigned on exchange 2010 like can i use the webmail URL for outlook anywhere, OAB etc.
6. Once this is done. I plan to move a few mailboxes as test to the new mailbox servers or DAG.
7. Testing outlook setups on new servers. inbound and outbound email tests.
once this is done, I can migrate over and point all my MX records to the new servers.
Please let me know your thoughts and what am I missing. I like to solidify a flowchart of all steps that I need to do before I start the migration.
thank you for your help in advance

Hi,
okay, you can use 4 virtual servers. But there is no need to deploy dedicated server roles (CAS + MBX). It is better to deploy multi-role Exchange servers, also virtual! You could install 2 multi-role servers and if the company growths, install another multi-role,
and so on. It's much more simpler, better and less expensive.
CAS-Array is only an Active Directory object, nothing more. The load balancer controls the sessions on which CAS the user will terminate. You can read more at
http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx Also there is no session affinity required.
First, build the complete Exchange 2013 architecture. High availability for your data is a DAG and for your CAS you use a load balancer.
On channel 9 there is many stuff from MEC:
http://channel9.msdn.com/search?term=exchange+2013
Migration:
http://geekswithblogs.net/marcde/archive/2013/08/02/migrating-from-microsoft-exchange-2010-to-exchange-2013.aspx
Additional informations:
http://exchangeserverpro.com/upgrading-to-exchange-server-2013/
Hope this helps :-)

Exchange 2010 to Exchange 2013 work order

Hi ,
Can anyone help me on below points.
I have installed exchange 2013 , and able to view all mail box form existing server 2010.
And move successfully some mail box from 2010 to 2013.
My question are :
Pls let me know the sequence for below reimaging task……
Move all mailbox from 2010 to 2013
Change connectors (received /Send)
NAT the IP in Router (private to Public)
Change the IP address in service provide site. ( OWA for external users)
Need to create or change MX record in internal DNS as well ?
How to change MX record for external DNS.
Note: 2010 is exchange 2010 & 2013 is exchange 2013.
Regards,
Dilip T

Hi,
Based on my experience, here are the steps of migration from Exchange 2010 to Exchange 2013:
Exchange 2013 Deployment
Digital Certificates Configurations
Configure Exchange-related virtual directories
Configure offline address book (OAB)
Move Internet mail flow from Exchange 2010 to Exchange 2013
Move Client Access from Exchange 2010 to Exchange 2013
Move mailboxes from Exchange 2010 to Exchange 2013
Move public folder data from Exchange 2010 to Exchange 2013
Decommissioning Exchange 2010
Thanks,
Angela Shi
TechNet Community Support

Exchange 2010 Migration to 2013 Coexistence url's

Hello,
What exactly is required for the virtual directory url setup for Exchange 2010 coexisting with Exchange 2013? I have been searching online a lot preparing for my Exchange 2013 deployment and can't see to find a clear answer. The information
I have come across from TechNet and other sources is all over the place with some stuff saying the external url needs to be empty while others say it should match Exchange 2013's setup. Others say the internal url should be empty while
only the external should be populated. And I have even seen others say nothing on Exchange 2010 has to be touched and that Exchange 2013 will figure proxying out on its own once I configure the new url's on it.
So what is supposed to be setup for the ExternalUrl and InternalURL to in Excahnge 2010 for coexistence with 2013? Currently my
existing Exchange 2010 is internet facing with the plan of moving that to Exchange 2013 once that goes in as per Microsoft directions on implementing coexistence.

Read the article below from Ross Smith. There can't be better article than this:
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
If exchange 2010 and 2013 are on same site, then you need to:
1. Remove External URL from Exchange 2010 CAS servers, retain the Internal URL
2. Move the SSL certificates from Exchange 2010 to Exchange 2013
3. Point the external URL to Exchange 2013 instead of Exchange 2010
4. Of course, you would need to re-configure Autodiscover, Web Services URLs on Exchange 2013 CAS servers.
Once this is done, for any mailbox that is hosted on Exchange 2010, Exchange 2013 would proxy the connections and deliver the content.
- Sarvesh Goel - Enterprise Messaging Administrator

Planning a migration from Exchange 2010 to Exchange 2013

Hello,
I am planning a migration from Exchange 2010 to Exchange 2013 and I was wondering if there was a good guide on the UM migration. I haven't found one that isn't confusing as heck.

Hello,
Is there any update?
If
you have any feedback on our support, please click here
Cara Chen
TechNet Community Support

Comparing-the-differences-between-anti-spam-agents-from-exchange-2010-to-exchange-2013

http://social.technet.microsoft.com/wiki/contents/articles/23582.comparing-the-differences-between-antispam-agents-from-exchange-2010-to-exchange-2013.aspx
Sathish

Hello,
This forum is for discussions and questions regarding profiles and Microsoft's recognition system on the MSDN and TechNet sites. It is not for products/technologies.
As it's off-topic here, I am moving the question to the
Where is the forum for... forum.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book: Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C40686F746D61696C2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

Exchange 2010 to Exchange 2013 Public Folder Problem

Dear Experts,
I am in a face of migrating Exchange 2010 to Exchange 2013. Below are my infrastructure details,
1) Parent Domain in Site A (abc.com)
2) One Child domain in Site A named child1.abc.com and Exchange 2007 is running in Site A child domain
3) One Child domain in Site B named me.abc.com and currently Exchange 2010 is running in Site B.
I have installed Exchange 2013 in Site B in coexistence scenario now Exchange 2013 users in Site B trying to attempt connection with a public folder store in the Site A Exchange 2007 servers instead of Site B Exchange 2010 servers.
Anyone help will be highly appreciated.
Thanks & Regards,
ZB

so you want users to access the PF in site B.
Check the setting of Databases in Exchange 2013 and find out what is default Public Folder setup for those Database. You will basically need to change the default Public Folder in Exchange 2013 from Site A PF to Site B,, the way you have explained the scenario.
run this for Exchanger 2013 DA
Get-mailboxDatabase -Identity Exchange2013DBNAME | fl
Get-MailboxDatabase -Identity e15-db1 | fl *PublicFolder*
Where Technology Meets Talent

Issue with list saving data after sites upgrade from sharepoint 2010 to sharepoint 2013

Issue with list saving data after sites upgrade from sharepoint 2010 to sharepoint 2013
Newform.aspx of list:-
Custom List is not saving data sometimes in the new form after 15 minutes and only blank entry record got created without saving data, even though some columns are mandatory fields?

Hello dcakumar,
Sounds like a strang issue. If you can reproduce this can you see some errors in the ULS logs?
- Dennis | Netherlands | Blog |
Twitter

OST corrupt when moving Mailbox from Exchange 2010 to Exchange 2010

Anyone come across this?
Moving a mailbox on Exchange 2010 to Exchange 2013 - the outlook client wont connect, if you remove the OST and allow outlook to recreate it comes good again.
outlook client knows the mailbox has moved as it connects to the new server
Not happening to every mailbox
thak=nks

Hi,
After you move mailbox from Exchange 2010 to Exchange 2013, Outlook should still work.
Is there any error message when these affected users try to connect? If there is, please post here for further analysis.
I saw someone failed to connect to the new Exchange server after they moved mailbox, then they restarted the Microsoft Exchange Information Store service and restarted Outlook, it worked.
If you haven't tried this, you can restart the Microsoft Exchange Information Store service to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Copy UM settings and prompts from Exchange 2010 to Exchange Online

When I migrated UM from Exchange 2007 to Exchange 2010, there is a script called "MigrateUMCustomPrompts.ps1"
that would copy over all the customized greeting files.
We are now migrating from Exchange 2010 to Exchange Online and will be using Exchange Online UM. Is there a similar script to copy over the files just like
the on-prem?

Sorry, I don't share code examples in most cases because they're generally one-off customer-specific scripts and I'm not in a position to answer lots of follow-up questions about them.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Moving from Exchange 2010 to Exchange Online: AD issue

Dear All,
Our company will moving from Exchange 2010 to Exchange Online and we have a on-premise WinSer 2008R2 for AD.
Currently, user have to login to our domain and use the same ID and PW to access their outlook.
1.If we move to Exchange online, do we have to do anything with our on-premise AD server?
2.If user prefer using only one ID and PW for PC to access domain and Exchange online, what should we do?
3.Is there any point or do we still need current on-premise AD server after we moved to Exchange Online?
Thank you so much for your attention and help!
Best regards,
Shiloh

Hi,
There are a lot of corrupted items. You can try raising the baditemlimit to 999 to workaround this issue
Get-PublicFolderMigrationRequest | Set-PublicFolderMigrationRequest -baditemlimit 100
To resumed the PublicFolderMigrationRequest
Get-PublicFolderMigrationRequest | Resume-PublicFolderMigrationRequest
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Simon Wu
TechNet Community Support

Upgraded to Exchange 2010 now outlook 2013 can't connect externally

Outlook 2013 used to connect to my exchange server via our TMG before upgrading to 2010. At first the clients were changed back to NTLM all the time but I fixed that and we now see basic with SSL. Now we get repeated logon.
I have used rpc connectivity analyser and it tells me that my (self issued) certificate doesn't chain properly - but the signing certificate is loaded on the client (by Enterprise CA policy) and looking at the mail server certificate in the certificate manger
reports the certificate to be good and correctly shows the chain (so is this a problem in the anyalyzer or does outlook constrcut its certificate chain using a different code library than say IE?).
Oddly Windows 8.1's mail cient works flawlessly when outlook 2013 goes into loops?
Any suggestions?
ICHC

Hi ICHC,
Just as Ed said, we should create new rule on TMG during the upgrading.
Found an blog for your reference:
Upgrade from Exchange 2007 to Exchange 2010 - Part II
https://www.simple-talk.com/sysadmin/exchange/upgrade-from-exchange-2007-to-exchange-2010---part-ii/
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 of information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above link.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Microsoft Exchange 2010 / Office Pro 2013 - Contact Issues

Good Morning Everyone.
We are running MS Exchange 2010 and have recently upgraded all our clients to MS Office 2013 Pro from Office 2007.
We've had problems with people being able to access previously accessible share folders etc. but we've managed to resolve them. What we are having problems with are peoples personal contacts....
Within Outlook If we click "New Email", then we click "To", choose address book and select "Contacts" (Personal contacts) we receive the error:
"The Address list cannot be displayed. The contacts folder associated with this address list could not be opened; it may have been moved or deleted, or you do not have permissions. For information on how to remove this folder from
the outlook address book, see Microsoft Outlook Help"
The unusual thing is, if we go to the people tabs at the bottom (Mail, Calender, People etc") Then we can access the address book without issue?
Any help would be appreciated, this problem is on every single client...
Regards
Steve Skingle

Hi,
Please make sure the Contact folder is enabled as an email address book in Outlook. We can check this by right-clicking on the personal contact folder, select
Properties, then Outlook Address Book tab.
Check if the “Show this folder as an email Address Book” option is ticked. If not, tick it and restart Outlook to check the result.
Please let me know the result.
Steve Fan
TechNet Community Support

Error upgrading form exchange 2010 to exchange 2013

Similar Messages

Maybe you are looking for