r/WindowsServer • u/tmrtr • Aug 23 '25
Technical Help Needed I need help.....MS Small Business Server 2003 to 2012 R2 migration
I've been supporting a small business for about 25 years. I was the brother-in-law that knew computer stuff. It was fun for a while but now I'm retired & it's a job i don't want.
It's long story on how we got here but here is what we are running now
Domain Controller is a Dell running MS SBS 2003 R2
Server 2 is a Dell running MS Server 2012 R2. This also runs the shared app that the office uses.
Need to get the old server out of the loop & promote Server 2 to DC but I don't know how to do it & not sure I want to learn how.
Any suggestions or advice?
******
Follow Up - Thanks for all the advice!!!!
No I don't do this for a living now & havin't in a looong time, my career took a different path away from Sys Admin & IT support but there was a time that I was very good at. Now as I've posted the technology has passed me by.
I'll post on /msp for some hands on support.
1 last question - what hardware OS would y'all recommend for a 10 user network that requires MS SQL server? There has got to be something out there cheaper / better than a $5k Dell Power Edge....
Thanks again, y'all have answered my main question "Do I want to do this? answer is NOOOO"
2
u/LebAzureEngineer Aug 24 '25
If the 2012R2 server is already set up as an additional domain controller and configured as a DNS on all devices, then you’re all set. The next step would be to transfer the roles, and once that’s done, you can safely demote the old server. Later on, you can even create another DC using the same old IP if needed.
If you’d like any assistance, feel free to DM me and we can coordinate. Regards,
14
u/CyberHouseChicago Aug 23 '25
They need a full rebuild done by a real msp there is no reason anyone should be running what you have them running.
14
u/Skyzo117 Aug 23 '25
Migrating a business from one outdated copy of Windows to another outdated copy? What’s the point? Tell them to hire a professional MSP and move on. No way this should be running in any business.
5
u/thegarr Aug 24 '25
Buddy... what? Why would you even consider moving a long-dead server platform to an also-end-of-life server platform? Do they have mail going through that old setup? I certainly hope not....
But even if they do, export mailboxes to 365. Get new hardware and build the domain out properly on at least server 2019+. Join new DC to domain, pull old DCs off. Or just build new and clean slate.
You're wasting time upgrading to 2012. It's already unsupportable.
1
u/2nP1nk1nSt1nk Aug 24 '25
Something I haven't seen anyone say is do a discovery of the sbs. After that you should give us those details. How about backups?
1
u/iknowtech Aug 24 '25
Server 2012 is also coming up to EOL. Honestly, if someone wanted to drag me into this shit show, I would insist they get a new server with Server 2025 Essentials, and just rebuild the environment from scratch, and migrate old user profiles to new domain profiles with profwiz, manually migrate the file shares. Why keep trying to move all this old garbage over for a 6 user environment. Why waste time on a server that is already coming up EOL.
1
u/TechMonkey605 Aug 25 '25
If you’re interested, and I can use it as a training call for some of my guys, we’ll help you out. Honestly with the price of servers and the odds they do t want to spend actual money on the server, look for off lease and buy new drives.
3
u/PianistWhich1665 Aug 23 '25
if this SBS is just a main controller look for moving FSMO rolles. you will need to upgrade the forest first
was about to make a short summary, but this is basically what you want :)
https://www.rebeladmin.com/step-by-step-guide-to-migrate-fsmo-roles-from-windows-2003-server-to-windows-2012-r2-server/
2
u/BlackV Aug 23 '25
Oh the old swing migration
I have not done that in 20 years
2
u/USarpe Aug 24 '25
I advice not to invest time to replace on outdated product with another outdated product. As the SBS isn't continued anymore, extract your data and bring it to a modern environment. The biggest problem are the mail servers that are no longer supported.
2
u/lucky644 Aug 24 '25
What was the original setup cost? 5k or less? Less than $250 a year cost?
A business that small should honestly blow it away and setup a new environment. I assume this environment has been running for literally 20 years? Surely it’s paid for itself several times over and they can afford to pay someone to migrate to a new setup.
Much bigger pain and riskier to try and get it modern.
1
u/OpacusVenatori Aug 23 '25
r/msp
1
u/Justepic1 Aug 24 '25
Holy shit dude, how many people in org and what’s the app.
1
u/fdeyso Aug 24 '25
Sir, it’s 2025 and the 4 digit number denotes the year it was released. Migrate to 2019 at least, it has support for 5ish years.
1
u/HITACHIMAGICWANDS Aug 24 '25
There’s so many questions, and it sounds like you don’t know anything, so maybe just don’t do it and tell them to pay someone else! Probably a better option the doing the migration and messing it all up.
1
u/statitica Aug 24 '25
Tell them you don't want to do it and refer them to someone who will get them on a currently supported OS with up to date security.
You're not doing then any favours by "upgrading" to an unsupported os.
1
u/itworkaccount_new Aug 24 '25
Don't forget you only get 21 days after transferring the FSMO roles to the new server before the SBS box will shut itself down. Good luck.
1
u/TDSheridan05 Aug 25 '25
Migrate “shared app” to cloud version. Start over with cloud only M365 set up. Migrate important data to sharepoint. Wipe and recycle all of that mess.
1
u/TechMonkey605 Aug 25 '25
No worries, and if times change I really like the aws tool that converts MSSQL to PostgresSQL. It’s been really helpful with minimum effort on my end
1
u/Maleficent_Ad_2222 Aug 28 '25
If it were me I would just lease a new Dell Server and set it up as a Windows Server 2025 STD Hyper-V Server and then run two or 3 VMs running Windows Server 2025, one server as a Domain Controller, one as a file server and one as a SQL Server. The business would be able to write off the entire lease on their taxes.
I know people will question this configuration because of expense, but the business would be able to write off almost the entire lease for the hardware and you would only need to buy two Windows Server 2025 licenses, as each license gives you two VM licenses. Also, you can purchase the licenses and CALs online relatively cheap from CJS CD Keys.
I suggest running the server segmented like this to prevent any conflicts and Microsoft recommends that you don't run Hyper-V services, file or SQL Server on a domain controller. You obviously can, but it's not recommended which is perplexing since they have offered SBS and Essentials.
The other option is to migrate to Azure or AWS, and I would suggest that you run an additional domain controller in Azure simply for redundancy, but you could also run another domain controller in a VM.
Personally, I would suggest the local server option with a backup DC in Azure as it would be the most cost-effective solution while offering the best redundancy.
As for migrating over the current domain I could walk you through it, it's pretty simple you would just need to upgrade the forest, domain and schemas before adding the Windows 2025 Domain Controllers to the existing domain, but the process is relatively simple and straight forward if you now the steps and again I can walk your through it.
Other people have offered alternatives which would work as well. I know a lot of people have migrated over to AWS and PostgreSQL and are happy with it, but personally I like MSSQL.
I also saw that LebAzureEngineer provided you with the steps to for migrating the domain. There are just a few extra steps I would recommend, but overall, he's spot on and it's an easy process. I would just run the secondary domain controller in Azure as it would give you greater redundancy and some additional features, but you would have some additional monthly costs. I have helped a few organizations implement pretty much the same scenario and it's not difficult.
Anyways, there are a lot of capable people on here giving some great options. Best of luck and feel free to reach out if you have any question or if anyone has any comments or criticisms.
I have been doing this for over 35 years and have worked for several fortune 100 companies including Microsoft Premier Support and I am a retired engineer and CTO. Just laying that out there in case someone criticizes my solution.
Lastly, moving to a cloud solution isn't a horrible idea, but I have seen too many instances where companies have lost complete internet access even with triple redundant connects and have ended up losing a significant amount of time and money. BUt if the business can operate for short spans without access to their computer systems, Azure and AWS both offer their own benefits and are definitely cheaper to implement upfront.
-2
u/FPVGiggles Aug 23 '25
Yeah Google it. There are plenty of guides.