I was just about to write something similar to Jason. Upgrade the OS (patch it up, reboots in between everywhere you think you need them) and wait a few days making sure everything is good. Upgrade SQL to the latest Supported version for CM12 R2 SP1. Again, wait a day or two (don't need that much baking time for the SQL upgrade, it's pretty boring really). Upgrade CM to Current Branch.
For paranoia, I personally wouldn't want to (all in 1 night or 1 weekend) do all three--if there's something "interesting" that happens after you update all 3 things quickly it might be hard to figure out which 1 of the three updates were the cause. On Wed, Oct 5, 2016 at 12:46 PM, Jason Sandys <[email protected]> wrote: > First a quick note, if you’re on Server 2012, then you don’t have WSUS 3. > > > > I would never recommend a migration unless you have some external > constraint. > > > > Upgrading SQL in-place is almost trivial and works quite well. > > > > Upgrading ConfigMgr in-place works well as well. > > > > If you want to build new, site backup and restore to the new server is the > best path and involves the least disruption. You can perform all of your > in-place upgrades on the existing server and then backup and restore to the > new server with like version of everything installed but no remnants of > anything old. > > > > J > > > > *From:* [email protected] [mailto:listsadmin@lists. > myitforum.com] *On Behalf Of *Kent, Mark > *Sent:* Wednesday, October 5, 2016 11:45 AM > *To:* '[email protected]' <[email protected]> > *Subject:* [mssms] Question on migration > > > > We are currently on SCCM 2012 R2 SP1. It runs on a Server 2012 (nonR2) > server with SQL 2012 on box. We also run WSUS 3 and MDT (latest) on the > same box. We also have three Server 2012 R2 servers running DP’s (including > PXE) and MP’s. > > > > We need to make the move to SCCM CB, for obvious reasons, and I’m > wondering what the consensus would be on a migration strategy. Do we > attempt to update the server to R2, and then update SCCM, and the various > pieces (SQL, MDT, etc.) after that. Or is it advisable to build a new 2012 > R2 server (2016?) and try and migrate over to it? > > > > I’m looking to minimize downtime (who doesn’t). I’m a little concerned > about running numerous upgrades, sometimes it’s like rolling dice, but if > that’s the best route I’ll do that. I’d love to build new if possible, I > just don’t know how complex that would make the migration and if that would > take longer. > > > > I should mentioned our Db had some minor corruption a few times, requiring > repair with data loss. From what we gathered, it was due to the fact we > were gathering too much process data which was filling up the Db quite a > bit. Once we removed the amount of info that was being gathered from > processes, the Db size went down and the corruption ended. > > > > Just looking for some pointers from anyone who has done this already, > thanks! > > > > Mark Kent > > Manager, Client Systems Engineering > > Technology Support Services > > Resources for Information, Technology and Education (RITE) > > http://rite.buffalostate.edu > > > > > > -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, http://www.smguru.org
