As part of the process of upgrading my lab environments from Windows 2012 and System Center 2012 to Windows 2012 R2 and System Center 2012 R2 I have posted the steps that I’ve taken (or colleagues of mine have taken) in the following blogs posts so far in this series. The next step I took was to upgrade my Configuration Manager 2012 SP1 environment to 2012 R2.
- Converting a Hyper-V cluster from Windows 2012 to Windows 2012 R2 step by step (upgrading to 2012 R2 series)
- Upgrading Operations Manager from 2012 SP1 to 2012 R2 step by step (upgrading to 2012 R2 series)
- Upgrading a Hyper-V host from Windows 2012 to Windows 2012 R2 step by step (upgrading to 2012 R2 series)
- Upgrading Orchestrator 2012 SP1 to 2012 R2 step by step (upgrading to 2012 R2 series)
Based upon the process I took and the lessons I learned instead of documenting the steps that I took I’ll document the steps that would have been a better approach in hind-sight.
The following are the high levels steps that were required.
1) Removal of the existing installation of the Windows Assessment and Deployment Kit
2) Re-installation of the Windows Assessment and Deployment Kit
3) Upgrading Configuration Manager 2012 SP1 to 2012 R2
Removal of the existing installation of the Windows Assessment and Deployment Kit
The first thing that needed to be done was to remove the existing installed version of the Windows Assessment and Deployment Kit.
The steps to remove the Windows Assessment and Deployment Kit are shown below.
Open the programs and features portion of the control panel and filter it as shown below. Uninstall the Windows Assessment and Deployment Kit for Windows 8.1.
After the uninstallation it was required to reboot to restart the upgrade.
Re-installation of the Windows Assessment and Deployment Kit
This kit is available for download at: http://go.microsoft.com/fwlink/?LinkId=301570. The re-installation steps are shown below.
Specify the installation location (default shown below).
Choose to join or not join the customer experience improvement program.
The next step is the license agreement.
When choosing the features to install make sure that you install at least the Deployment Tools, Windows Preinstallation Environment (Windows PE), and User State Migration Tool (USMIT). The screenshot does not show the addition of USMT – but that is a requirement.
Upgrading Configuration Manager 2012 SP1 to 2012 R2
After successful installation of Windows Assessment and Deployment Kit, load the configuration manager 2012 R2 media and ran the installation.
The next screen shows the requirements to consider before upgrading.
I was happy to see that the option to upgrade the Configuration Manager site was available as shown below.
Enter the product key next (all of System Center uses the same product key, so don’t plan to look for an Orchestrator 2012 R2 specific key).
Accept the software license terms to continue.
Accept each of the prerequisite licenses to continue.
To download the prerequisites, create a new directory and download the files to the new directory.
Next choose the appropriate server language.
And the appropriate client language.
The setting summary shows this process to be an upgrade.
The prerequisite check is next. In my environment there were prerequisite issues in four areas:
Warning: WSUS on site server issues (needed to be patched), SQL Server Process memory allocation (need more memory on the SQL instance)
Failures: free disk space on site server, User State Migration Tool (USMT) installed.
USMT installed: (This is part of the Windows Assessment and Deployment Kit and should have been chosen as an option when installing to avoid this issue)
Re-ran the prerequisite checker after freeing up some disk space, installing USMT and applying the WSUS updates.
The upgrade was started as shown below.
On thing I learned early on is that my SQL disk subsystem needs an upgrade as was quite apparent during the upgrade process… The disk queue snapshot from Operations Manager shown below.
The installation ran for just under two hours as shown in the screenshots below.
To verify the upgrade I opened the Configuration Manager console and checked the version information as shown below.
Summary: The upgrade process was pretty straightforward after removing the existing version of the Windows Assessment and Deployment Kit and re-installing with the new version and the correct components. The upgrade was in-place and did not require uninstallation of Configuration Manager components.