RichB Posted February 12, 2018 Posted February 12, 2018 Good Evening, Short side note - got a small ish job on for a company I know very well (evening type of job). Im sure the question has been asked many times before but I can not find the answer and know you people will know) System DC's - 2003 Multiple other servers from 2003-2016 VMWare 5.5 (will be upgrading this to 6.5 as well, but thats "quite straight forward")- 99% virtual system / hooked up to multiple SANs etc Question Can I direct upgrade from server 2003 R2 to 2012? Not the DC's they just want a couple of servers there are running a few bits of software on upgrading. Both are currently virtual machines. I know I can create a new server, move the file shares across, software etc. But was wondering if there is a direct path? Can not seem to find a straight answer.
AJWhite1970 Posted February 12, 2018 Posted February 12, 2018 As far as I can remember, no you can't as 2003 was only 32bit and 2012 was only 64bit so you can't in place upgrade it
3s-gtech Posted February 12, 2018 Posted February 12, 2018 64 bit Server 2003 existed, and it was rare! Worth a check, you can upgrade 64 bit 2003 R2 to 2008 R2, then go to 2012 R2. No route for 32 bit, and no direct path.
RichB Posted February 13, 2018 Author Posted February 13, 2018 There 32bit Server 2003 Standard!!!! Looks like its proper migration...
MatthewL Posted February 13, 2018 Posted February 13, 2018 I'd never upgrade, I would always build a fresh and migrate over. Always been taught to never upgrade a OS. 1
RichB Posted February 13, 2018 Author Posted February 13, 2018 File shares / live environment / time / cost all play a part in this one! What I'd give to be back in an education setting, where we have planned downtime, and time to plan something! not a few days and over 10,000 users worldwide accessing some of the data on these servers! Then time zones come to play for data copying / replicating!!! reboots / switch offs etc
richbrowncardiff Posted February 13, 2018 Posted February 13, 2018 Don't attempt an upgrade especially if the enviroment is as busy as you say. Build and migrate is the way forward to save hassle in the long run!
RichB Posted February 13, 2018 Author Posted February 13, 2018 Really confused at the "do not upgrade suggestions". If the option is there, its the quickest and safest way to go! Take a snapshot of the system Upgrade Test Revert back to old snapshot (downtime is in the seconds) If this were an upgrade from 08-12 or 12-16, I'd not think twice. Ive seen it go right and wrong in the past, but why not use the tools if they are there? Interested in everyone else's views on this? (Currently testing the upgrade paths in a VM lab, Ill report back). 1
richbrowncardiff Posted February 13, 2018 Posted February 13, 2018 Your going (in my opinion) too many versions forward from such a now legacy OS. I would not do it in a school so definately wouldnt do it for a business. but thats just my 2 pennies worth.
DJ-1701 Posted February 13, 2018 Posted February 13, 2018 Really confused at the "do not upgrade suggestions". If the option is there, its the quickest and safest way to go! Take a snapshot of the system Upgrade Test Revert back to old snapshot (downtime is in the seconds) If this were an upgrade from 08-12 or 12-16, I'd not think twice. Ive seen it go right and wrong in the past, but why not use the tools if they are there? Interested in everyone else's views on this? (Currently testing the upgrade paths in a VM lab, Ill report back). Personally, I don't see a problem with this, I feel it maybe a hang over from the old days.
Boredguy Posted February 13, 2018 Posted February 13, 2018 Faster to do a fresh install and copy than go through the multiple upgrades if the OS was compatible. The changes in 2003 to 2008 made it better to go the clean route. 2008 onwards it's not so bad but depends on what was running on the server and how easily it would be to reconfigure
Michael Posted February 13, 2018 Posted February 13, 2018 It's not possible even if it were Windows Server 2003 R2 x64 directly, as Windows Server 2016 requires a Domain/Forest Functional Level of 2008 Server, so you'd have to upgrade from 2003 R2 > 2008 R2, and then 2012 R2 or 2016. Unless there's a specific reason though, I would look at upgrading to 2016, seeing as 2012 R2 is supported until 2023 and 2016 until 2026. 2016 is definitely more 'polished' than 2012 R2.
RichB Posted February 13, 2018 Author Posted February 13, 2018 Licensing is the reason for not using 2016. Thanks for the great insights! We all have different thoughts on the above! If it was straight forward we'd not be doing the job! A clean install will 99% be the way forward for me on this on this! However with a multiple files shares / software / sch tasks it will not be as straight forward as I hoped.
RichB Posted February 13, 2018 Author Posted February 13, 2018 @Michael the upgrade is server 2003 to 2012. They have 2016 boxes though for RDS, Its a strange set up! Booming business / Forgotten IT.
jimmy_2k Posted February 27, 2018 Posted February 27, 2018 The 64bit edition of Server 2003 was the enterprise edition. I remember installing it for a SQL upgrade to SIMS.
cpjitservices Posted February 27, 2018 Posted February 27, 2018 (edited) We manage Business IT, and have done exactly this, in stages, leave 2003 live while you transfer everything over - then test on new server. Once your happy then demote the 2003 DC and use new server(s). Things like tasks, roles, shares etc can all be moved over in stages if you so wish. Although we have gone straight to 2016. Go 2012 R2 if you want to but going 16 means you wont have to have a planned upgrade when you need to move off of 2012. Edited February 27, 2018 by cpjitservices
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now