SCCM as a Service – Upgrade Checklist

Posted on Updated on

As System Center Configuration Manager (SCCM) matures into an “as a Service” model, the ability to rapidly upgrade an infrastructure has come a long way. It used to be complex and time consuming to upgrade SCCM as you would have to download all the prerequisite media test everything in your lab and then schedule the downtime in your production environment. With the advent of SCCM Current Branch (CB) the ability to upgrade directly from the console has made this much less complex and in theory less error prone. This doesn’t mean you shouldn’t take precautions and test before rolling to production. Here’s some advice on how to manage the risk associated with the upgrade:

  1. Backup your environment and test the restore in case you need to rollback. You do this regularly anyways right? There are several supported backup options for you select from based on your particular requirements. Here is some backup and recovery guidance just in case
  2. Check your site and component status to make sure you don’t have any unresolved issues that might impact the upgrade. Check them again post upgrade.
  3. Perform the prerequisite check
  4. Test everything in your lab, sandbox, or test environment before upgrading in production. You don’t have a test environment. Well you do you just like to call it “production”. You can setup a really simple and inexpensive virtual lab in Azure that you can spin down when not in use.
  5. Use Pre-pilot collections to test client agents. This is a great way to minimize the impact of client agent defects.
  6. Check that all of your site systems have been upgraded
  7. Test basic functionality such as HW and SW inventory and Software Updates. This puts the basic components such as MPs, DPs, SUPs and client agents through a smoke test.
  8. Test task sequences especially if there was an ADK upgrade involved
  9. Check if there is a newer version of MDT available / required in order to work with particular ADK you are using and to support any required servicing branches
  10. Test the console update and any extensions such as Report Builder
  11. Test any pre-release features that you were previously using. Are they now released? Do you need to reenable the functionality as pre-release?
  12. Is this version available as a baseline build? Do you want to keep an ISO handy?
  13. Check for any post upgrade hotfixes.

Leave a Reply

Fill in your details below or click an icon to log in: 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