Switching to WS2003 SBS to WS2012R2?

[riahc3]

I want to change a server from WS2003 SBS to WS2012 R2.

The problem is that the WS2003 SBS is VERY buggy with broken updates, broken features, etc. I did not make the server so I have no idea what is wrong with it.

We are going to buy a new WS2012R2 and I want to know how to go with the transition. We have about 15-20 PCs connected to that domain.

How is the process? This is my first time with this so bear with me. I do NOT want to do a upgrade. Fresh install of everything.

 

[owensdj]

I've switched a domain from WS2003 to WS2008 R2 before. I think it would work the same way if you're using 2003 SBS.

Make sure you're at Windows 2003 level for both the Domain Functional Level and the Forest Functional Level before you start. Set the DNS server for the WS2012R2 machine to be the IP address of your existing WS2003SBS machine. Add the new WS2012R2 machine into your existing domain. Run ADPREP(see below), then promote it to Domain Controller. Force a domain replication. Add DNS Server as a role on the new machine and set the DNS servers on the new machine to be the old machine for Primary and the loopback address for Secondary. Force a domain replication. Change the DNS Server setting on the new machine to use itself as DNS server. Transfer all FSMO roles to the new server. Demote the old server to member server(no longer a DC). Raise the Domain and Forest Functional levels to Windows 2012. You can now copy any file share data from the old to the new server. If your old server is the DHCP server for the network, set up DHCP service on the new server. Remove the WS2003SBS machine from the domain.

Here's an article about running ADPREP: http://technet.microsoft.com/en-us/library/dd464018(v=ws.10).aspx

 

[IndyColtsFan]

I've switched a domain from WS2003 to WS2008 R2 before. I think it would work the same way if you're using 2003 SBS.

Make sure you're at Windows 2003 level for both the Domain Functional Level and the Forest Functional Level before you start. Set the DNS server for the WS2012R2 machine to be the IP address of your existing WS2003SBS machine. Add the new WS2012R2 machine into your existing domain. Run ADPREP(see below), then promote it to Domain Controller. Force a domain replication. Add DNS Server as a role on the new machine and set the DNS servers on the new machine to be the old machine for Primary and the loopback address for Secondary. Force a domain replication. Change the DNS Server setting on the new machine to use itself as DNS server. Transfer all FSMO roles to the new server. Demote the old server to member server(no longer a DC). Raise the Domain and Forest Functional levels to Windows 2012. You can now copy any file share data from the old to the new server. If your old server is the DHCP server for the network, set up DHCP service on the new server. Remove the WS2003SBS machine from the domain.

Here's an article about running ADPREP: http://technet.microsoft.com/en-us/library/dd464018%28v=ws.10%29.aspx

I'm afraid it isn't that simple. IIRC, SBS2003 includes Exchange 2003 (and may include SQL and ISA as well, depending on version) and if the OP is using it, the steps above could potentially break it as Exchange 2003 is not officially supported in a Windows 2012 functional level or above:

http://technet.microsoft.com/library/ff728623(v=exchg.150).aspx

And that doesn't consider the necessary migration paths if SQL and ISA are used.

OP, no offense intended, but if you're asking this question and this is the first time you've tried something like this, you should really consider having an outside resource help you. It isn't a simple "Do Step 1, click Next, do Step 2, click Next" conversion. If you're using Exchange, for example, you're going to need to purchase a new Exchange license since I presume you've only purchased a Windows 2012R2 OS license and you'll need to worry about the Exchange migration as well. And I haven't mentioned anything about SQL or ISA, which you may or may not be running and using.

 

[Dahak]

In addition to what was said above, it might be best to start from scratch as well.
There was never really any good way to migrate off a SBS system(2008) to the full server.

I would setup the 2012 as a new domain, removed the computers from the old and add into the new.

 

[riahc3]

I do not use Exchange so it seems like it was a good idea

The SQL portion of it is one of the many buggy things on this server.

About reaching a outside source, we do have to take in account that getting it from a outside source, is very expensive so that's why we prefer to buy the license and I set it up myself. Ive practiced in a couple of VMs just in case and everything MORE OR LESS looks easy.

Lets see how it goes in the summer and from there, a choice will be made.

 

[takeru]

just curious. if you are not using exchange, what are you using?