Migration from SBS 2003 to Server 2012 dc and Server 2012 with Exchange 2010

I am trying to find information on how to migrate SBS 2003 to the following:
1. server 2012 acting as the new DC, DNS, DHCP and File server
2. a separate server 2012 with exchange 2010 installed for on premises email.

*I have found lots of good posts out there that cover most of this. this is the best i found
http://gillwald.co.uk/home/windows-server/sbs-2003-migration-to-server-2008-r2-and-exchange-server-2010
although it is not for server 2012 but server 2008.
I understand the joining to the domain, promo to a dc, dhcp, dns, even the file shares....
My biggest concern is the Exchange. I do not want to install Exchange on the 2012 DC, but have a seperate server for this.
Do I just follow the instructions on the post I have included, but run the AD prep with the exchange cd on the 2012 DC before installing exchange.
Also- are there any major gotchas with the exchange moving to 2010 from sbs2003- I have read and know that I cannot go to Exchange 2013 and I do not wish to do so....
I really need help on this part...
williamstechnologygroupOwnerAsked:
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.

Simon Butler (Sembee)ConsultantCommented:
You don't have to run prep seperately.
If you are in a single domain forest (which you will be with SBS 2003), just run setup.exe from the Exchange 2010 SP3 download and let setup do everything for you.

Simon.
0
Cliff GaliherCommented:
When you start talking about moving to non-SBS platforms, I've never liked monolithic walkthroughs. They make many assumptions (such as your example of installing Exchange on a DC) and are often riddled odd gotchas because the write-up was written for a specific environment and didn't account for any variability.

I know it may not sound like much to go on, but TechNet is really your friend here. They have migration documents for all of the major roles, so you can cherry-pick what you want to move and what you may want to skip over or make changes to during the migration process. DHCP, for example, is often a role that making substantive changes to reservations and expanding the scope and setting DHCP options makes sense.

Similarly, the Exchange guidance on TechNet is top notch. Microsoft has documents and downloadable tools that can help you plan a new topology best suited for your current size and planned growth. Because you are no longer constrained by SBS, this is the perfect time to perhaps make change such as breaking out the CAS role from the Mailbox role, and the assessment tools can help you make that decision where a simple walkthrough will make assumptions that may not fit your needs.

I know reading TechNet is more time consuming and there are definitely Microsoft docs that are dry and confusing (their CA docs and many of their MSDN docs fall in this category) ...but when migrating between server versions, I've found them to be clear and well worth the little extra time to help formalize a strategy before jumping in.
0
williamstechnologygroupOwnerAuthor Commented:
Thanks for the advice. One other question I had was regarding the version of exchange 2010. I downloaded an open license version of exchange 2010 (downgrades the license from 2013).
It does not say that it contains sp3- do I just run the version I have and then apply Sp3 or do I need to find the installation that includes sp3?
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

williamstechnologygroupOwnerAuthor Commented:
I have looked at technet, but all they seem to focus on is migrating to windows server 2012 essentials- not standard with exchange.... the instructions call for installing 2012 essentials in migration model.... not much help...
http://technet.microsoft.com/en-us/sbs/gg981878.aspx
0
Cliff GaliherCommented:
To my knowledge, there is no slipstreamed installers for Exchange.

As I mentioned, you won't find a monolithic document on TechNet. You will instead find multiple documents based on what you want to migrate.

http://technet.microsoft.com/en-us/library/jj134039.aspx
0
williamstechnologygroupOwnerAuthor Commented:
I guess  I still have questions about how all of this is going to pan out- especially ripping the sbs server out of the environment....I did find some good articles on technet and a tool which helps with exchange migrations.
I am also looking at third party tools, has anyone used a product by Priasoft? (priasoft.com)
0
Simon Butler (Sembee)ConsultantCommented:
Exchange service packs are cumulative. Therefore while volume licencing is SP1, you can just download Exchange 2010 SP3 and install that. It is the full product.

Simon.
0
williamstechnologygroupOwnerAuthor Commented:
Hi Simon,
I was told by the microsoft volume licensing center that the only volume license version of Exchange was Exchange 2010 with SP1 and that they did not have an open license version that included SP3. He said the volume license key would not work with any other downloads than what was on the VL site. I then asked if I could install Exchange 2010 with Sp1 and then apply SP3 only. He said that would be ok, but when I went to Microsoft's official download center I could not determine if there was a download for JUST SP3 ONLY> I downloaded Exchange 2010 SP3 download, but it was over 500mb which leads me to believe it is the full version. I don't want to install the Exchange SP3 from Microsoft's website and then find that it will not take my  Microsoft Volume license key....This is maddening. I got burnt last week trying to install OFfice 2010 pro plus- I had a download from technet or action pack and then tried to apply the Volume license key and it wouldnt take it.....
0
Simon Butler (Sembee)ConsultantCommented:
Oh dear.
There are only two keys for Exchange 2010. Everyone has the same keys, the only difference is one is for Standard Edition and one is for Enterprise edition.
If you download Exchange 2010 SP3 and install that, then your key will work fine.

For whatever reason Microsoft haven't bothered to update the VL download site with an ISO for Exchange 2010 SP3. The only difference between the two (other than one being SP1 and one being SP3) is the VL download contains the UM language packs. If you are deploying the UM role then you can download the language packs manually.

Simon.
0
williamstechnologygroupOwnerAuthor Commented:
Thanks Simon, I will try it on my test VM first to make sure it works. At this point I have setup my 2 windows 2012 servers and have joined the first one to the domain, installed Active Directory and promoted it to a DC in my current SBS2003 domain. Replication is working and everything looks good.
At this point my plan is:
1. move dchp/dns roles to new DC
2. move file shares from sbs 2003 to new DC
3. install 2nd 2012 server with exchange 2010
4. configure exchange 2010 and migrate mailboxes from sbs 2003 to 2010 (this is the one that I am having doubts about)
4b- uninstall exchange from sbs 2003
5. move printers from sbs 2003 to new DC
6. move FSMO roles from SBS2003 to new DC
7. retire SBS 2003 server....
I am  hoping I can find the correct and most accurate info to accomplish all of this.
unfortuently I feel like I am on my own. Microsoft will not help me unless something goes wrong, I talked with local IT companies and they all shrug their shoulders-- most are used to sbs to sbs migrations, but SBS is going away and my clients do not want it.
Server 2012 essentials is a joke- why would any business want to limit themselves to 25 users- Microsoft doesn't seem to have a clue what small businesses need. At least give them 75 like SBS.
0
Simon Butler (Sembee)ConsultantCommented:
Forget its SBS. Lose that thought.
The process for Exchange 2003 to 2010 migration is very well documented, on Technet and on other sites. You can use that to do the job.

Use the Microsoft guide for moving to SBS 2011, just ignore the bits that don't apply.
http://technet.microsoft.com/en-us/library/gg563801.aspx
That will be particularly useful when it comes to cleaning up all of the SBS junk in group policy.

You are not doing anything unusual, just need to think of it in the right way and you will find the information you need.

Simon.
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
williamstechnologygroupOwnerAuthor Commented:
Thanks Simon, i appreciate the encouragement and advice. I agree that I have to stop looking at it as SBS and take it one step at a time. I will keep moving here and keep you posted...
0
williamstechnologygroupOwnerAuthor Commented:
i put the project on hold due to other issues, but am going to be back at it now... thanks for your advice.
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
SBS

From novice to tech pro — start learning today.