Migrating from Exchange 2010 to Exchange 2013

Hello Experts,

I need to migrate an Exchange 2010 server to Exchange 2013.  I have done 2003 to 2010, but 2010/2013 will be my first.

Can anyone recommend a step by step document or site?  

Thanks in advance.

Regards,
Real-Timer
realtimerAsked:
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.

Anthony H.Commented:
0
Zacharia KurianAdministrator- Data Center & NetworkCommented:
Well there is another well documented  e-book from http://exchangeserverpro.com. Find the attached, and it will guide you in detail.

Zac
Exchange-2010-to-2013-Migration-Guid.pdf
0
Austin RobCommented:
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

realtimerAuthor Commented:
Great links.  Thank you to all.
One final question before I close this case.  

Going through a migration document, it indicated that once you install Exchange 2013, workstations may automatically start prompting for credentials.  This because they are trying to use a connector on Exchange 2013 which may not have an SSL certificate in place yet.

Now, I can imagine this being the case when you move a mailbox to the new server, but not as soon as Exchange 2013 is introduced to the network.  Can anyone comment on this?

Thanks,
Real-Timer
0
Jeff GloverSr. Systems AdministratorCommented:
IF you follow the proper steps and set the Autodiscover URI, it should fix that. I used the exchangeServerPro.com site and it worked with few issues.
http://exchangeserverpro.com/exchange-2010-to-exchange-2013-migration/
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
realtimerAuthor Commented:
Lvjeff (or other Experts) - thanks.  But do you know if simply installing the Exchange 2013 on a separate server will automatically start prompting client workstations that are still on Exchange 2010 to be prompted for credentials?
0
Jeff GloverSr. Systems AdministratorCommented:
Yes, it it possible with newer versions of office. You need to set the Autodiscover URI (even if the traffic is not yet hitting the new exchange server). In the ExchangeServerPro
Set-ClientAccessServer =-identity (servername) -AutodiscoverServiceInternalURI (fqdn) d

Just look in TechNet for more info (Google Set-ClientAccessServer)
0
Jeff GloverSr. Systems AdministratorCommented:
A little confused now that I look at it. In the Directions on ExchangeServerPro, under the Installing Exchange 2013 server, they cover setting the Autodiscover Internal and External URLs. It is the best place to get the exact syntax you need to use. I would set both the internal and External URLs for your server. Remember to do this for each server you install.
0
realtimerAuthor Commented:
I'm a bit confused myself.  
I will be installing Exchange 2013.  Then I will be moving users' mailboxes in batches.  
I don't want a 250 user environment to suddenly start receiving prompts for the certificate or for credentials as soon as I install the server.  I will ensure the certificate is installed prior to moving mailboxes to the 2013 server.  Can someone clarify please?
0
Jeff GloverSr. Systems AdministratorCommented:
OK, here is the best explanation I can come up with. When you install Exchange 2013, it will automatically create a Service Connection Point (SCP) in AD for Autodiscover using the FQDN of the server. It does not change the current SCP for Exchange 2010 but adds another (each CAS role will have a SCP for Autodiscover)  Outlook may, depending on the service pack, look for the newest SCP and cause issues. This is default behavior for Outlook. You can mitigate this by setting the SCP using the Set-ClientAccessserver Cmdlet right after install. If you are concerned, you can install Exchange after hours and set the SCP for Autodiscover. You should set the Autodiscover internal and external URIs. Once set, even if the autodiscover record points to the old server, it will be fine. This is only dealing with the SCP. Really, the article by Paul Cunningham is the best I have found if you are not that familiar with Exchange 2013,
0
realtimerAuthor Commented:
Hello - thanks for the assistance!!
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.