Solved

What are the steps to replace a SBS 2003 server with a Windows 2012 R2 Server?

Posted on 2014-01-30
3
1,298 Views
Last Modified: 2014-03-22
What are the steps to replace a SBS 2003 server with a Windows 2012 R2 Server? I will not be running exchange on the new server.
0
Comment
Question by:rmills8387
[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
3 Comments
 
LVL 3

Accepted Solution

by:
BertSublime earned 500 total points
ID: 39821384
As such there is no whitepaper for the migration, but in general,  the following steps will be needed,

install the new server, join the domain,

promote to a Domain controller (this will involve upgrades to schema,  on the sbs box using the 2012 cd) remember to allow time for replication,

you would then need to transfer the FSMO roles to the 2102 box,

I would then install DHCP, and create an identical scope on the 2012 box, then turn off SBS and turn on 2012.

Migrate data, printers etc.

Decommission sbs 2003,  Uninstall exchange, DC promo Server off domain shut down.

you haven't mentioned what you are doing with email which may make add a few steps to the process.
0
 
LVL 9

Expert Comment

by:Zenvenky
ID: 39821521
If you are referring to SBS 2003 to Server 2012 R2 Standard then BertSublime is correct. If you are referring to SBS 2003 to Server 2012 R2 Essentials then check below link.

http://technet.microsoft.com/library/jj200112

http://technet.microsoft.com/en-us/library/dn408634.aspx
0
 
LVL 58

Expert Comment

by:Cliff Galiher
ID: 39821533
Since you aren't installing exchange, you'll be best served following the technet migration docs for individual roles. There is migration guidance for for servers, for example.

A few special considerations:

1) Consider taking advantage of the virtualization rights in 2012 R2. If you run LOB apps... even something as simple as quickbooks... keeping that off your DC is well worth the effort of virtualizing.

2) Keep the FSMO roles on SBS as long as possible. Transfer hem as one of the last steps in your migration. This keeps SBS licensing happy and you won't feel the clock running out on SBS shutting down.

3) Remember to uninstall exchange. There are AD changes that are tough to do manually if you forget to uninstall exchange before decommissioning SBS.

4) Make a plan. Audit your SBS server, and make a detailed plan of how you will mograte roles and settings and the order you will do it. The most broken environments I've seem come from IT where the tech decided to "wing it."

5) Make backups often during the process. It is much easier to roll back one step than it is to have to restore all the way back to the beginning of the migration if something goes wrong.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

A project that enables an administrator to perform actions within a user session context not just at the time of login but any time later on day(s) or week(s) later.
A hard and fast method for reducing Active Directory Administrators members.
In this Micro Tutorial viewers will learn how to restore their server from Bare Metal Backup image created with Windows Server Backup feature. As an example Windows 2012R2 is used.
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

628 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