An in-place OS upgrade isn't support with for a ConfigMgr site server or site system (unless its 2012 to 2012R2). To be supported, that needs to be a backup and restore. Thus, each one of these steps should be treated separately and done one at a time with time (like days) in between. I would do the ConfigMgr upgrade first, then OS, and then SQL. I probably wouldn't even do the SQL upgrade as it doesn't buy you anything really but if you're determined to get off an older version of SQL you could but definitely do it last because full support comes with ConfigMgr 2012 R2 SP1 and I don't know off-hand whether Server 2008 R2 even supports 2014.
J From: [email protected] [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Thursday, October 22, 2015 5:54 PM To: [email protected] Subject: [mssms] Upgrade path from 2012 SP1 I asked this before, and I had a project that ended up getting back-burnered. Since then, there have already been numerous updates, and I need to revisit this issue. My environment is: 1) Single Primary site, with 14 secondary sites around the state. 2) Running Server 2008R2 3) Running SQL 2008R2 4) Running SCCM 2012 SP1 I want to upgrade. I want to end up with: Server 2012R2 SQL 2014 SCCM 2012 R2 SP1 (or whatever is latest by that time) Before, the plan was to upgrade in-place to the end result SCCM, then migrate to another server that had been setup with the end result OS, SQL and SCCM. Is that still the best plan, or is there another school of thought? Thanks, Joe Heaton Information Technology Operations Branch Data and Technology Division CA Department of Fish and Wildlife 1700 9th Street, 3rd Floor Sacramento, CA 95811 Desk: (916) 323-1284 Every Californian should conserve water. Find out how at: [SaveOurWater_Logo]<http://saveourwater.com/> SaveOurWater.com<http://saveourwater.com/> * Drought.CA.gov<http://drought.ca.gov/>
