Exchange 2010 to 2013 migration

We're doing (trying to do) the final part of a dual swing migration from from 2003 to 2010 to 2013.   The following is our current situation:

The 2010 box has been up and running for a couple/few weeks now, and works fine, without any issues.
The 2003 box has been completely decommissioned and removed from the domain/network.
The 2013 box has been set up and running for a week or so, but is not "in use/production"; just sitting there.

We do not care one bit for "co-existence", for any length of time, we just want to move the mailboxes from the 2010 box, to the 2013 box and then remove the 2010 box from the network, altogether, leaving us on Exchange 2013, period. We only have 23 mailboxes, with at total dB size of about 15-20GB, so this is a pretty small scale project, compared to a lot of stuff I've read on here.

We don't really care about setting up Outlook Anywhere, for external use, even though I've set it up on the 2010 box, thinking we had to do so, to move to 2013 (still not sure about that!). Everyone accesses their email via OWA, when not in the office.

The more I've read up on the subject, the more confused I've become on what else I need to do. I tried to do a "test" move of one mailbox today, and it failed, so I've decided to call it quits for the day (possibly the weekend).

Can anyone help guide me with what I need to do next, to migrate from the 2010 box to the 2013 box, and get rid of the 2010 box? It would be greatly appreciated, as I'm just frustrated with it at this point, as I can't find any articles on what we want to do: they all seem to lean toward co-existence... Thanks.

Regards,

Ric J
ricjenkinsNetwork AdminAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Manikandan NarayanswamySecurity Specialist & IBM Security GuardiumCommented:
Hi,

Have you installed Exchange 2013 on the existing environment where Exchange 2010 exists or you have created a new organization for Exchange 2013. For moving mailboxes to exchange 2013 from exchange 2010 refer the below link

http://www.msexchange.org/articles-tutorials/exchange-server-2013/mobility-client-access/exchange-2013-local-mailbox-moves-part1.html
https://technet.microsoft.com/en-us/library/dn249849(v=exchg.150).aspx

Thanks
Manikandan
0
StuartTechnical Architect - CloudCommented:
Outlook anywhere is enabled by default on 2013 as this is how clients connect now. You just need to move the mailboxes then change your client access endpoints when your done (active sync, OWA etc) making sure to install your current certificates on 2013 and enable the correct firewall rules for them (443)

Both environments will work in coexistence by default, external client access will hit the 2010 server and will be routed to 2013 if the mailbox exists there.
0
Peter HutchisonSenior Network Systems SpecialistCommented:
When moving mailboxes to a new version of Exchange, you always use the tools on the newer version of Exchange, not the older version. So you use the Exchange 2013 web admin frontend to migrate mailboxes or you can schedule mailbox moves using powershell scripts and CSV file of the users to migrate.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

ricjenkinsNetwork AdminAuthor Commented:
Sorry for the delay, but I"ve been out sick...

Yes, the 2013 and 2010 servers are in the same organization/domain/forest. I also got the hidden system mailbox moved over. I had seen an article on that, but had forgotten about it... Grr... But I did finally get it moved, and was finally able to get the a couple of mailboxes moved over as well: mine being one of them.

Now I have a new problem: I cannot open my Outlook (2010) here at the office, & neither can the only other user whose mailbox I moved to the 2013 database. The mailbox move, allegedly went fine, but now neither of us can open our Outlook. Everything works fine if we hit our mailboxes via OWA, internally, but not in Outlook! Any ideas there??
0
Peter HutchisonSenior Network Systems SpecialistCommented:
Exchange 2013 and Outlook use Autodiscover from the new CAS servers to pick up the new location of user's mailbox. Check your DNS so that Autodiscover entry is pointing to your new Exchange 2013 CAS server(s). Makre sure IIS is working and all VirtualDirectories are available.
Also make sure Outlook / Office has latest Service Pack installed so that its fully compatible with Exchange 2013

Supported versions:
http://social.technet.microsoft.com/wiki/contents/articles/845.outlook-versions-supported-by-exchange-200720102013online.aspx
0
Manikandan NarayanswamySecurity Specialist & IBM Security GuardiumCommented:
Hi,

There is high probability that since your mailbox is moved but still the MAPI client might be pointing to old Exchange Server. Hence run the below command on exchange management shell if it returns the old cas server then run the below command to set to new CAS server

 Get-MailboxDatabase | fl name,*rpc*
Set-MailboxDatabase -Identity "Mailbox Database 0447493325" -RpcClientAccessServer ex2.domain.local

Refer the below link

http://exchangeserverpro.com/outlook-clients-unable-to-connect-to-exchange-2010-after-client-access-server-role-moved/

Thanks
Manikandan
0
ricjenkinsNetwork AdminAuthor Commented:
Peter - All Outlook 2010 Clients have SP2 installed, so they should be good to go, for use with Exchange 2013. And I added the A record for Autodiscover, and Outlook at least opened. It won't connect, or send/receive, but at least it opens. It's a start, i guess...

Manikandan - I ran the "Get-MailboxDatabase | fl name,*rpc*" command on the Exchange 2013 box, and it responds with the 2013 server name and database. and likewise, If I run the same command on the Exchange 2010 box, it returns the Exchange 2010 database and server name. So I'm not sure where this leaves us.
0
Peter HutchisonSenior Network Systems SpecialistCommented:
Open Outlook, press down the Ctrl key, then in the System tray (or notification area) , select the Outlook icon and two new entries will appear:
Connection status..
Test E-mail Autoconfiguration

Which you can use to debug why Outlook is not connecting.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ricjenkinsNetwork AdminAuthor Commented:
Peter - Your comments didn't directly resolve the issue, but they did lead me to double check some of my other DNS settings, where I realized that the internal DNS setting for "mail.domain-name.com" was still pointing to the Exchange 2010 box. Once I changed it to point to the '13 box, everything cleared up. So thanks for the nudge in the correct direction!

Regards,

Ric J.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.