My SCCM 2007 SP2 Upgrade Path

Posted on Updated on

The upgrade path for my SCCM 2007 R2 to SP2 is as below.  I thought it may be helpful to someone out there…

  1. Disable any advertised OSD task sequences
  2. Make a backup copy of the default boot.wim files
  3. Ensure a recent sucesseful site backup by reviewing smsbkup.log
  4. Update server with any critical Windows and SQL updates
  5. Uninstall WAIK 1.1
  6. Reset all counts for status messages on the sites to make for easier troubleshooting post upgrade
  7. Upgrade WSUS to 3.0 SP2
  8. Install SCCM 2007 SP2
  9. Upgrade secondary sites from the console
  10. Upgrade Nomad Branch to the latest version (if you use it in your environment)
  11. Update the distribution points for any packaged SCCM clients
  12. Re-establish classifications for Software Updates – this is to correct a known issue where the classifications are reset during the SP2 upgrade.  This is done by going into Site Settings > Component Config > Software Update Point Component > Classifications tab.
  13. Re-establish products for Software Updates.  This is done by going in the same SUP Component, but on the Products tab.
  14. Re-establish customizations within the default boot images.  For example, we have trace32 in our boot images, so I needed to put them back.
  15. Re-establish customizations to SMS_def.mof and Configuration.mof
  16. Re-enable the disabled OSD task sequences

See the following post on my post upgrade tasks, which will occur in the months following the upgrade

33 thoughts on “My SCCM 2007 SP2 Upgrade Path

    Jay Connor said:
    November 9, 2009 at 3:14 pm

    Check configuration.mof and sms_def.mof aswell, I think SP2 replaced mine, had to restore from backup

      Nicolas Moseley responded:
      November 10, 2009 at 8:34 am

      You’re absolutely right Jay, thanks for the tip! M$ apparently still hasn’t figured out how to NOT replace an organization’s MOF customizations. Fortunately, my upgrade path was based upon my work in the lab, so I can add a step for this prior to my production upgrade. Thanks again!!

        Jay Connor said:
        November 15, 2009 at 2:24 pm

        Hi Nick,

        I just realised I didn’t check whether MS added anything new to the mof’s. I restored from backup. :S Do you know if they have?

        Jay Connor said:
        November 15, 2009 at 2:28 pm

        Dont worry, I’ll check another backup!

    Neil said:
    November 13, 2009 at 5:59 am


    DO you have to upgrade to WSUS SP2? I cant see that listed as a pre-req or was it something you just done as matter of course?
    Also did you notice if you had auto client deployment turned on would it then automaticaly upgrade the clients ?

    Reuvy said:
    November 23, 2009 at 3:18 am

    What do I need to do for this step “Update the distribution points for any packaged SCCM clients” and how?

      Nicolas Moseley responded:
      November 23, 2009 at 6:34 am

      If you created a standard software distribution package to distribute the SCCM client or for use during OSD, then you’ll need to update the distribution points of that package in order to begin installing the SP2 client and not the older client. Below is a link to the admin workflow for updating distribution points

    Miellie said:
    December 23, 2009 at 3:08 am

    I upgrade my Central and Primary servers to Server 2008 R2, installed SCCM 2007 SP1, restored DB, upgraded to SP2 and installed R2.
    I’m having an issue that I’m net getting status messages on my Primary server and all the Threads States = Stopped even though all the Services are running when you look at the Config Manager Service manager. Any ideas what I can do next. I have rebuild my environment a few times now and every time I get this. My Central Site Server is 100% now issues.

    Karl said:
    January 14, 2010 at 1:48 am

    Hi Nick,

    In point 9 you are talking about the secondary sites. If they have PXE roles (WDS installed) do I have to delete WAIK and reinstall the new version of WAIK or can this be done from the central/primary server console?

    Point 14 is good but how do you import trace32 into your boot.wim, by choosing create new boot image from MDT or by editing the boot.wim afterwards? Can you also edit the keyboard layout to another country with dism.exe? What’s the command?

    We want to upgrade our whole sccm infrastructure but I heard that the newest SCCM, SMSv5 will be out in 1 year I will only upgrade to SP2 and R3 but not the OS.

    Dave said:
    February 3, 2010 at 7:55 am

    Hi, If I understand right you upgraded directly from R2 to SP2, right?
    Or was it from SP1 to SP2?



      Nicolas Moseley responded:
      February 3, 2010 at 7:59 am

      Correct. My site server was already at SP1 with R2 before I upgraded to SP2.

    Santos said:
    February 23, 2010 at 3:23 am

    Hi Nick,

    This is a great guide. Just one think to add if you’re running SCCM in Native Mode. SP2 upgrade will remove your PXE boot certificate and you will have to import it again to make your OSD working.
    The certificate is still on the server (Certificate store) but you can’t see it in Certificates\PXE store in SCCM console.


      Nicolas Moseley responded:
      February 23, 2010 at 6:34 am

      Thanks for the feedback and the additional tip!

      Michael Yuen said:
      June 16, 2010 at 4:15 pm

      Also note that the previously-installed cert will also show up right afterwards and be in “Blocked” status.

      I haven’t been able to figure out how to remove Blocked certificates from the SCCM Console (for housekeeping purposes)

        Nicolas Moseley responded:
        June 16, 2010 at 4:17 pm

        Thanks for the tip Mike!

    Karl said:
    April 2, 2010 at 3:27 am

    Point 11-> do you mean building a new sccm client package or can I just do an update/upgrade. How…?
    Point 14-> I use also trace32 but what else are you using?

      Nicolas Moseley responded:
      April 2, 2010 at 7:50 am


      If your existing SCCM client package source files are pointing to \\ServerName\c$\Program Files (x86)\Microsoft Configuration Manager\Client\, then yes I mean update the DP as the SP2 upgrade will automatically update the client install files. Otherwise you will need to build a new client install package.

      The only other customization I had to my boot images (at the time) was a custom image – this you will also need to readd to it. Recently I implemented HTA support into my boot images, so if I were to do the upgrade at this time, I would need to reimplement that functionality.

      p.s. If you’re interested in HTA support, you can see my post

    Karl said:
    April 30, 2010 at 3:29 am

    You talk about uninstalling WAIK but at what stage do you install the newest version? Right after?

      Nicolas Moseley responded:
      April 30, 2010 at 7:55 am

      Thanks for asking Karl…that is a good question. If I remember correctly, the installation of SP2 automatically installs the latest WAIK, so there was no need to have a specific step to reinstall WAIK. With that said, the reason for having the specific step to manually uninstall WAIK first is because SP2 couldn’t do it.

    NLS said:
    June 22, 2010 at 3:26 am

    I have some stupid questions (are related). In MSDN there are (among other things):

    1- SCCM 2007 released 9 Oct 2007 as DVD image (clear)
    2- SCCM 2007 with SP1 released 10 Jul 2008 as DVD image (also clear)
    3- SCCM 2007 R2 released 13 Oct 2008 as a tiny CD image (?)
    4- SCCM 2007 with SP2 released 3 Dec 2009 as DVD image (possibly clear)
    5- …two “international client packs”

    OK I don’t get many things…

    1) Why SCCM 2007 R2 is so small? Does it need SCCM 2007 with SP1 first?

    2) What about SCCM 2007 with SP2? Why is it not mentioned as SCCM 2007 R2 with SP2? Is it for BOTH pre-R2 and R2?

    3) What is the proper path to follow for a clean installation?

    4) What are those international client packs?


    NLS said:
    June 25, 2010 at 1:44 am

    Thanks Nicolas.

    NLS said:
    June 25, 2010 at 1:53 am

    there is a small difference in that guy’s post from your reply – for new deployments he recommends pure SP2 NOT R2 over that (or even before that)…

    any ideas when R3 RTM is coming? (will clear things a bit)

    David said:
    July 25, 2010 at 10:45 pm

    Hi Nicolas,

    Did you just upgrade the already existing sites via the SCCM console sitting on the primary server, via the standard “upgrade secondary site” option?

    Just want to confirm this before doing anything.

    David said:
    July 28, 2010 at 10:29 pm

    sweet, thanks for that.

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