Configuration Manager 2012 SP1 – Part 2: Site Servers Upgrade

In Part 2 of my Configuration Manager 2012 SP1 series I will explain how to upgrade the SCCM 2012 Site Servers to Service Pack 1.

David Stein By David Stein - Mon, March 4, 2013 - 0 comments google+ icon

David is an author and consultant, working for Endurance IT Services in Virginia Beach, Virginia, specializing in Microsoft enterprise systems and Business Process Automation.

Articles in this series

Configuration Manager (SCCM) 2012 SP1 upgrade

Depending up on how your Configuration Manager 2012 infrastructure is designed, you will need to follow some fairly simple steps in order to accomplish a successful upgrade to SP1. I say “fairly simple” because the steps, the order are pretty straightforward, however, that does not mean the procedure within each step is really quick. In many aspects, it involves some waiting for things to finish, so block out a few hours at least just to practice the upgrade in a lab environment. That will give you a rough estimate of how long it will take to perform the same tasks in your production environment.

Site hierarchy considerations

If you have a Central Administration Site, or CAS, in your hierarchy, that will need to be the first to be upgraded to Service Pack 1. After that is done, you can upgrade your Primary Sites and then, if you have any, you can upgrade your Secondary Sites.

Configuration Manager 2012 SP1 Setup

Configuration Manager 2012 SP1 Setup

Replacing WAIK with ADK

One of the changes in SP1 is that WAIK (Windows Automated Installation Kit) is replaced by the Windows Assessment and Deployment Kit, or “ADK”. This also means you have to remove WAIK and install ADK before you can do the upgrade to Service Pack 1.

To uninstall WAIK, open Control Panel, and go to into Programs and Features. Select the Windows Automated Installation Kit and click Uninstall.

Automated Installation Kit Uninstall

Automated Installation Kit Uninstall

Installing the ADK

Uninstalling WAIK is only part of the battle, since ADK provides additional components that are required for the upgrade to Service Pack 1.

Locate the ADK installer (adksetup.exe) and launch it using Run as administrator. Select the desired Install Path when prompted. I recommend not installing it on the Windows operating system partition if possible, but it won’t necessarily hurt anything if you do. It’s just a standard precaution I prefer to keep such things on a different partition if possible.

When you start the ADK installation, it will prompt for the folder path to install to. It will also verify the available disk space on the target drive, so pay attention to that as well! If all is good, click Next.

ADK Setup - Specify Location

ADK Setup – Specify Location

Choose whether or not you want to participate in the CEIP and click Next.

ADK Setup - CEIP

ADK Setup – CEIP

Read the License Agreement, and if you’re okay with it (and really: who isn’t?), then click Next.

ADK Setup - License Agreement

ADK Setup – License Agreement

If you are certain you don’t need all of the ADK features installed, select the ones you know are required. The only required features for Configuration Manager 2012 SP1 are Deployment Tools, Windows PE, and USMT. I usually select all of the Features, but I’m aware that some of you may have special considerations. When ready, click Install.

ADK Setup - Select Features

ADK Setup – Select Features

 

ADK Setup - Installing Features

ADK Setup – Installing Features

When the installation is finished, you can close the confirmation form. I would also recommend a reboot after this before you proceed.

Installing WSUS hotfixes

If you have any Software Update Point servers in your hierarchy running on WSUS 3.0 SP2, you will need to make sure two (2) hotfixes are installed before you attempt the SP 1 upgrade process: KB2720211 and KB2734608. These will need to be installed on each WSUS server in your environment which is participating as a Software Update Point. Site Servers hosting the SUP role on Windows Server 2012 will have WSUS 6.2, which does not require these hotfixes.

If you already extracted these two updates, you should be ready to go. If you want to run these from within a script you can do so very easily. This makes the overall upgrade process smoother. To run them silently you can append the /Q (or /q) parameter as shown below…

Upgrading to SP1

Now, assuming everything is ready, we can begin the actual upgrade. In this example I will be performing the upgrade on my one and only Primary Site server. If you have a CAS, it must be upgraded first, but the same process applies as far as checking prerequisites, backing up, and downloading required software in advance.

One more suggestion I would make is to temporarily disable any antivirus or antimalware application services on your Site Servers during the upgrade process.

Insert the System Center Configuration Manager 2012 with Service Pack1 DVD installation media, or, if you downloaded it to a folder, navigate to the folder/share and launch the splash.hta application.

Configuration Manager 2012 SP1 Setup

Configuration Manager 2012 SP1 Setup

One More Check

Click the Assess server readiness link under Tools and Standalone Components. You might be wondering why I’m suggesting you run this again, since we ran it in Part 1 already. It doesn’t hurt to double-check things before diving in, especially when it doesn’t take very long to do. If all you see are warnings double-check them to be sure they’re not serious. The most common warning is about SQL Server memory allocation, or about total available memory (8 GB or more recommended). If everything looks good, we can now move on.

From the Setup form, click the Install link. Click the release notes link (item number 4 in the list) to read the latest Service Pack 1 Release Notes. I know many of you won’t bother, but trust me: it’s worth reading.

Configuration Manager 2012 SP1 Release Notes

Configuration Manager 2012 Service Pack 1 Release Notes

After you’ve read the Release Notes, click Next. Then make sure the option Upgrade this Configuration Manager site is selected, and click Next.

Configuration Manager 2012 SP1 Setup Wizard

Configuration Manager 2012 SP1 Setup Wizard

Enter your Product Key and click Next.

Configuration Manager 2012 SP1 Product Key

Configuration Manager 2012 SP1 Product Key

Review the Software License Terms, check the acceptance box (if you agree), and click Next.

Configuration Manager 2012 SP1 Software License Terms

Configuration Manager 2012 SP1 Software License Terms

The Prerequisite Licenses confirmation confirms your acceptance of licensing terms for SQL Server 2012 Express (used by site server roles when needed), SQL Server 2012 Native Client, and Silverlight 5. Once you have checked all three boxes, you can click Next to continue.Configuration Manager 2012 SP1 Prerequisite Licenses
Configuration Manager 2012 SP1 Prerequisite Licenses

Hopefully you heeded my advice and downloaded Updates for Configuration Manager 2012 earlier and have them stored in an accessible folder. If so, enter the folder path (or click Browse, to located it), and click Next to continue.

Configuration Manager 2012 SP1 Prerequisite Downloads

Configuration Manager 2012 SP1 Prerequisite Downloads

The Setup process will now verify the integrity of each of the update files, which only takes a few minutes (much quicker than waiting for them to download and then verify them). When it finishes, click Next to continue.

Verifying downloaded prerequisite components

Verifying downloaded prerequisite components

Select the Server Languages to suit your needs, and click Next.

Configuration Manager 2012 SP1 Server Language Selection

Configuration Manager 2012 SP1 Server Language Selection

Select the Client languages to suit your needs, and click Next.

Configuration Manager 2012 SP1 Client Language Selection

Configuration Manager 2012 SP1 Client Language Selection

On the Settings Summary form, click Next.

Configuration Manager 2012 SP1 Settings Summary

Configuration Manager 2012 SP1 Settings Summary

The Prerequisite Check process will run again automatically to ensure the server is ready to be upgraded. Again, verify that any warnings aren’t serious, and no Failed items appear. If all is good, click Next to continue. Otherwise, chase down any issues and get them resolved before returning to re-run the Setup process.

Configuration Manager 2012 SP1 Prerequisite Check

Configuration Manager 2012 SP1 Prerequisite Check

If everything checks out well, the Begin Install button will be enabled. Then click Begin Install to start the Upgrade process! As the Upgrade process does its thing, you should see each of the Site Server components checked off in green to indicate a successful upgrade and restart of the associated service.

Configuration Manager 2012 SP1 Upgrade

Configuration Manager 2012 SP1 Upgrade

You can view the Upgrade progress by clicking the View Log button. By default it will open the log file in Windows Notepad, but if you have CMTrace.exe handy, you can open it with that for a much better experience.

Configuration Manager 2012 SP1 Upgrade Log

Configuration Manager 2012 SP1 Upgrade Log

When the Upgrade is complete, you should see a confirmation form with a link to Post-Setup Configuration Tasks. Click this link for more information about what to do after the upgrade is finished, or you can simply click the Close button.

Configuration Manager 2012 SP1 - Core Setup has completed

Configuration Manager 2012 SP1 – Core Setup has completed

Verifying a successful upgrade

The quickest way to verify you have upgraded to Service Pack 1 is to view the Site server Build Number from the Site Configuration form within the Administration section of the management console. That was a mouthful indeed. If it shows 7804 you are good, but it’s always better to review all of your site system status messages and system logs as well.

Configuration Manager 2012 SP1 - Build Number 7804

Configuration Manager 2012 SP1 – Build Number 7804

What about CAS upgrades?

You may be wondering why I didn’t discuss upgrading a Central Administration Site (CAS). Most of the clients I’ve seen and had contact with do not use a CAS. There are indeed situations that may warrant having a CAS in your hierarchy, but the Service Pack 1 upgrade process is pretty much the same as process for upgrading a Primary Site.

Resources

Microsoft: Upgrade from Config Manager with No Service Pack to Config Manager with Service Pack 1

Coming up next

In Part 3 of this series, we will explore upgrade process for Secondary Sites, and some of the new features SP1 brings to the table.

Series NavigationConfiguration Manager 2012 SP1 – Part 1: New features and Preparation - Configuration Manager 2012 SP1 – Part 3: Upgrading Secondary Sites

-1+1 - Rate this post
Loading ... Loading ...
Your question wasn't answered? Ask in the new 4sysops forum!
===Leave a Comment===

Login

Lost your password?