?
Solved

SBS 2003 (Domain and Exchange) migration to 2012 Standard with VMware

Posted on 2014-12-19
2
Medium Priority
?
91 Views
Last Modified: 2015-03-17
I am needing some guidance on the best approach for our migration. We currently have SBS 2003 running exhange 2003, Domain, and DNS. We also have a 2008 standard server with files and a database. Our corporate office has approved an upgrade and wants to virtualize using VMware 5.1 or 5.5 and 2012 Standard (single server). We are supposed to migrate the domain controller and dns to 1 VM, 2003 to 2013 using a 2nd VM, and the file share and database to a 3rd VM, a 4th VM could split the files and database or be used for future needs. I have already gotten pricing for the hardware and software to support these 4 VMs. My question is, What is the best way to approach this to have little down time. I know it is critical we do this in a particular order, and I am also aware a migration from 2003 to 2013 directly is not possible. Just looking for advice and feedback. Thank you for any advice you can lend.
0
Comment
Question by:ckleavitt2
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 35

Expert Comment

by:Seth Simmons
ID: 40509372
little down time?
unless you migrate to 2010 first, not really possible

the only other option is to export all mailboxes to pst files, delete the mailboxes, remove exchange, then install 2013, create new mailboxes and import everything.  that will have downtime
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 2000 total points
ID: 40509487
It can be done with no downtime, but you will need an interim system to hold Exchange 2010.
The route I would take is to find another system (a workstation will be fine), build a Windows 2008 R2 domain controller.
Then build a Windows 2008 R2 member server (high end workstation) and install Exchange 2010 on to it. (Exchange 2010 SP3 is the complete product, comes up in 120 day trial). Do the migration, removing all trace of SBS 2003 from the network. Don't forget the group policy objects!

Then build your live platform, Windows 2012 R2 DC and Windows 2012 E2013 CU7 and migrate again.
With care, no downtime involved. If you can remove public folders once you have removed SBS 2003 but before the Exchange 2013 server is introduced, then you will make life a lot easier.

Take your time though. Don't think it can be done in a weekend or anything like that.

Simon.
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

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

Find out what you should include to make the best professional email signature for your organization.
If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
In this Micro Tutorial viewers will learn how they can get their files copied out from their unbootable system without need to use recovery services. As an example non-bootable Windows 2012R2 installation is used which has boot problems.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
Suggested Courses

752 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