Solved

Upgrading Exchange 2010 to Exchange 2013 Issues

Posted on 2016-08-30
7
46 Views
Last Modified: 2016-09-27
Hi.

We want ot upgrade our Exchange 2010 server to Exchange 2013. The problem I ma having is that the Exchange 2010 server is running SP2 not SP3. We are having issues with the SP3 upgrade failing. I learned this the hard way mid way through the upgrade after all the checks had passed but the installer quit mid way due to not having the correct permissions on an OWA folder. By that time the old installation had already been removed and the installer would not move forward. My Exchange server was dead in the water and I had to use our backups to restore the entire VM.

So now I'm very hesitant to try this again. What are my options for an upgrade to Exchange 2013? Is it possible instead of going through the official migration process (which requires 2010 to be at SP3) to just spin up a new instance of 2013 and do an export of the mailboxes (PST) on the 2010 machine and import them onto the 2013 box? What are the limitations or potential gotchas going this route.
0
Comment
Question by:spinoza156
7 Comments
 
LVL 11

Expert Comment

by:Tej Pratap Shukla ~Dexter
ID: 41777608
Hi,
There will not be any Gotchas in Export Exchange mailboxes into PST and import PST to Exchange 2013. If you think that there might occur situations like this then you can use any third party tool like Exchange ExportExchange Import and the support team will help you throughout the up-gradation process.
0
 
LVL 16

Expert Comment

by:Ivan
ID: 41777610
Hi,

You cant install 2013 in organization where 2010 is not on SP3, as posted on https://blogs.technet.microsoft.com/exchange/2013/02/12/released-exchange-server-2010-sp3/

This means that you will have to export mailboxes to .pst, remove exchange 2010, deploy 2013 and then create mailboxes, import data and so on...
That would be risky since you have no idea will uninstall go well, and also will install 2013 go ok, so if you get stuck with it your users wont have access to email for some time (or long time)...
That sounds bad :)

I personally would try with upgrade to SP3, and from there, continue normally with migration to 2013.


Regards,
Ivan.
0
 
LVL 7

Expert Comment

by:CodeTwo Software
ID: 41779745
Hi,

If you are not ruling out third party solutions, check out CodeTwo Exchange Migration.

The program supports migration of users' mailboxes (no downtime during the migration process) from Exchange 2010 SP2 to Exchange 2013.

In case of any questions, give me a shout.

Best regards,
Adam
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 27

Expert Comment

by:davorin
ID: 41780779
I must say that you are not in nice situation and as Ivan said - you need to successfully remove exchange 2010 from your organization prior to install exchange 2013. Or the second option is to create a new AD and do (cross-forest) migration. I'm not familiar with your environment, but in most cases I would rather  shoot myself in a knee than do the second option. That does not mean just migrating mailboxes, but migrating everything. Keep it like your last resort.
I would try to fix exchange 2010 first, hoping that it is only owa and not AD problem, and try to install sp3 again.
Resetting owa is not so difficult procedure:
https://technet.microsoft.com/en-us/library/ff629372(v=exchg.141).aspx
0
 

Accepted Solution

by:
spinoza156 earned 0 total points
ID: 41810950
Just to let everyone know that I was able to identify and correct the permission on the OWA folder. It was a matter of taking ownership (from System to Domain Admins) and then letting all the permissions inherit from the parent folder to that folder and all sub folders. Once this was done I was able to successfully install SP3.

I tested this all in a test environment twice before doing it in production.

Thanks everyone for your contribution.

spinoza
0
 
LVL 27

Expert Comment

by:davorin
ID: 41811252
I'm glad you have solved the problem. Thank you for feedback.
0
 

Author Closing Comment

by:spinoza156
ID: 41817515
I found my own solution
0

Featured Post

Gigs: Get Your Project Delivered by an Expert

Select from freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely and get projects done right.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
Read this checklist to learn more about the 15 things you should never include in an email signature.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

813 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now