From SCCM 2012 SP1 to 1702

  • Resolve SCCM site monitor issues
  • Resolve hardware and/or software deficiencies (storage, horsepower, etc.)
  • If not virtualized, virtualize now.  Anyone who insists physical is only way to go, must be eliminated (quietly, of course)
  • Upgrade Windows Server**
  • Upgrade SQL Server**
  • Upgrade to 1606
  • In-console update to 1702

From SCCM 2012 R2 to 1702

  • Same as above

From SCCM 1511

  • Why are you still on 1511?  Did you think “IT” implied sitting around and never keeping up with current technology?  What were you thinking? You’re so close, don’t stop now!

From SCCM 2007

  • Install parallel site hierarchy on 1606
  • In-console update to 1702
  • Migrate DPs, packages, etc. from 2007 to 1702 environment
  • Attach suitable explosives to 2007
  • Maintain safe distance
  • Detonate

From LANDesk, Tivoli, Kasaya, etc.

  • Locate person who selected that platform
  • Cover this person thoroughly in fresh steak juice, garnish with fresh chunks of steak
  • Drop person into tank filled with starving crocodiles
  • Capture and upload video to (don’t waste it)
  • Oh yeah, install SCCM 1606 site
  • In-console update to 1702

** follow Microsoft guidelines for ‘supported operating systems‘ and ‘supported SQL versions‘ under ‘supported configurations’.  Pay careful attention to what “supported version” means while you transition from 2012, 2012 R2 up to current branch, as well.


3 thoughts on “SCCM Upgrade Scenarios

  1. Hi

    See i get easy confused :0( this link about 1702 says “You must use a baseline version to upgrade from System Center 2012 Configuration Manager”. 1702 is a baseline upgrade, but from what I see a lot of folk saying is that I need to go 2012 > 1522 > 1602 > 1702″. The 1606 notes only mention upgrading from 1511 or 1602… Just trying to clarify how many hoops need jumped through for 2012 > CB…

    1. Whatever version is posted in your VLSC download portal, that’s what you can upgrade to, from whatever (supported) existing version you have. For example, if you have 2012 SP1, or 2012 R2, etc, and the portal has 1606,that’s where you make the jump. Once you get to that baseline version, the rest is in-console upgrades. Of course, Microsoft is free to change this at any time. But that’s how it works so far.

      The thing is, at some point, it’s very likely that Microsoft will cut off support for in place upgrades from anything below a newer version than 2012 R2. That would mean a parallel migration or new installation, and more work (with additional risk).

      The best course of action for anyone right now is to upgrade asap. And once upgraded, to stay current with each new release and hotfix. The days of sitting idle on the sideline are going away.

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s