• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 94
  • Last Modified:

migrate from sbs2003 to 2012 standard with exchange 2013

i have a sbs 2003 server running exchange for 10 users
i have bought a 2012 standard server with exchange 2013
what is the easiest way for me to migrate
can i install server alongside and just migrate mailboxs etc
0
dougdog
Asked:
dougdog
  • 6
  • 4
  • 4
  • +1
1 Solution
 
Cliff GaliherCommented:
Unfortunately the migration path is rather convoluted. Exchange 2003 and 2013 have no direct coexistence support. You'll need to introduce an intermediate exchange server such as 2007 or 2010, move the mailboxes, then introduce 2013 and move them again.

Alternative you can export mailboxes to PST and then import them. But that has the downside that significant metadata is lost and the DR scenario if something goes wrong is more complicated.

And finally there are 3rd party services than can automate a direct migration from 2003 to 2013. But the cost is not cheap. If it were me, I recommend the first path. Keeping control of your data, making regular backups, and having a way back is worth its weight in gold.

As far as migrating the other stuff, TechNet has plenty of guidance for migrating ADDS, file servers, DHCP, etc. All that is straightforward and SBS doesn't introduce any particular challenges. Exchange (and SharePoint if you'd use it) will be the big hurdles. And because of that, there are no easy-to-follow "thus just works" migration docs. Migrating from that many old products to new ones takes skill and knowledge that sadly can't be condensed into a simple guide.
0
 
dougdogAuthor Commented:
can i install the new 2012 dc into the existing domain
then migrate printers
then migrate data
then migrate dhcp dns
then install exchange import psts
demote sbs 2003
0
 
IvanSystem EngineerCommented:
Hi there,

beside exchange, there is a mid step that needs to be done, regarding migrating sbs2003 domain to windows 2012.
You have to install windows 2012 essentials (get trial from somewhere) in transition mode first. That is going to allow you to migrate AD domain services to windows 2012. When you install Essentials, you will get wizard to add new domain controller to a existing domain, next, next..wait till it is done, and you have new AD DC wich run 2012.

 After that you can simple, via power shell or cmd, upgrade essentials to standard edition. One command with serial key of windows standard.

To prepare SBS for migration: http://technet.microsoft.com/en-us/library/jj200136.aspx

After that is done, you install dhcp, and reconfigure dhcp to give new dns server to clients.
Migrate FSMO roles, printers, etc...

Now you can install new exchange 2010 or 2007 (trial) and migrate exchange 2003. This is mid step, as Cliff said.

Link i used when I did this migration myself: http://technet.microsoft.com/en-us/library/jj200112.aspx
There are few other steps, but this will get you started.

Regards,
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Simon Butler (Sembee)ConsultantCommented:
"then install exchange import psts"

To install Exchange 2013 you would have to completely eliminate all traces of Exchange 2003.
That means you lose everything inside Exchange - the PST files are just the data.

- permissions
- email addresses
- links between calendars
- nickname contents (they will not work for internal recipients without additional work).

The double hop migration as already outlined is the best way to do this, as you will not lose all of the information. While you can document the settings, you will miss things. You are looking at documenting 10 years of changes, even with a small number of users that will be difficult to do 100%.

Don't try and shortcut the migration. Do it as outlined and it will not cause much business disruption. PST migration method is very disruptive.

Simon.
0
 
dougdogAuthor Commented:
once i install server 2012 in migration mode
will i be able to access the onld sbs2003 server as normal for 21 days?
i will need time to migrate the exchange
0
 
Cliff GaliherCommented:
If you are installing 2012 standard as your original question suggests then there is no migration mode and you'll only start a 21 day countdown on SBS when you transfer the FSMO roles... so that could be the very last thing you do before retiring the SBS server. A fairly common practice truthfully.
0
 
dougdogAuthor Commented:
i was going to install essentials in migration mode as per spriggan13
do i not need to do this
0
 
dougdogAuthor Commented:
do i need to install essentials to be able to migrate active directory etc
0
 
IvanSystem EngineerCommented:
Yes,

you install essentials in migration mode, and then procede with migration of AD, exchange.

Regards,
0
 
IvanSystem EngineerCommented:
Link i used when I did this migration myself: http://technet.microsoft.com/en-us/library/jj200112.aspx

Regards,
0
 
dougdogAuthor Commented:
yes so i do need to install the essentials version as a mid step
or can i just install stabdard and do the same thing?
if i use standard do i need to setup everything from scratch
0
 
Cliff GaliherCommented:
Essentials is not required to migrate Active Directory. Only install Essentials if you plan on keeping it or want the essentials features.
0
 
IvanSystem EngineerCommented:
Well, I just followed MS guide, on that link, that used essentials. It was easy to install and required only 1 command to upgrade it to standard.

That is how I have done it, with no problem. Did not try with some other versions of win.

Regards,
0
 
dougdogAuthor Commented:
so what would the steps be to migrate using standard
0
 
Cliff GaliherCommented:
0
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.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 6
  • 4
  • 4
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now