Hope this post finds you in good health and spirit. You all know that Microsoft has changed the way new features were introduced in SCCM. They call it “Current Branch” model which they first introduced in SCCM 1511 (in YYMM format). 1702 is the latest SCCM release.
In this post we will see how to upgrade from SCCM 2012 R2 to 1702 which was not possible some time ago as its baseline media was not available.But here is good news, now 1702 baseline media is available so upgrade is possible. BTW, why you should upgrade to 1702 is compiled here:
Before you start upgrading, there are few consideration which need to be taken care of:
- Upgrade should start from top-level site of the hierarchy. It could be either a central administration site or a stand-alone primary site. After the upgrade of a central administration site is completed, you can upgrade child primary sites.
- Your database version of your database should be supported by 1702. For eg. SQL Server 2008 R2 SP3: Standard, Enterprise, Datacenter are not supported for 1702.
- Disable SQL Replication and Maintenance tasks before you start upgrade operation.
- Install supported ADK version. Most probably, you will have old Windows ADK version 8.1 running for SCCM 2012 R2 . This version of ADK is not supported by SCCM 1702. So you have to uninstall old ADK version from site server (Control Panel > Programs > Programs and Features) and install ADK version 1702 prior to upgrade.
Here is detailed upgrade guideline from Microsoft:
Ok, so once you have meet all the prerequisites, its time for actual fun. I have SCCM 2012 R2 installed on my site server which we will upgrade to 1702.
These are the upgrade steps:
- Mount the SCCM 1702 media, run the setup and on the setup window, click Install. It will provide Getting Started wizard. Since there is existing installation of SCCM on site server, install configuration manager primary site is greyed out. Select Upgrade this configuration manager site, click Next.
- In next screen, provide your product key and click Next.
- In Product License Terms page, accept all the License Terms and Privacy Statement and click Next.
- Next page is of Prerequisite Download. You can download perquisites directly from internet as in my case, or choose previously downloaded files. Click Next. Download may take sometime and in meanwhile you can view the progress.
- In next console select language for server (For me it’s English) and click Next.
- In next step you will select client language (again English for me) and click Next.
- Next console is of Diagnostics and Usage data. Microsoft collects data from our computer to improve its product. Click Next on this console as setting can be done post installation.
- Next step is to setup Service Connection Point role which is used to download updates. I selected to skip it now as it can be done post upgrade. Click Next.
- In Settings Summary windows you should get Upgrade. Click Next.
- In next windows, prerequisites are checked. Hopefully everything should be fine for you. Click Begin Install. You can view result/activity of prerequisite checkup in ConfigMgrPrereq.log
- Once setup is completed, close the console and start SCCM console. Lets check the version of SCCM post upgrade.
Wow. So we have got our SCCM upgraded to 1702. Mission completed. Post upgrade perform these steps:
- Reconfigure any database maintenance tasks you disabled prior to the upgrade.
- Upgrade clients by enabling Automatic client upgrade.
- Enable SQL replication (in case if you have stopped it).
- Redistribute the boot images to distribution points.
These are logs which you can check for activity progress and troubleshooting:
ConfigMgrSetup.log – This log records detailed output from site server setup. This is most important log to check for SCCM setup.
As in log, our upgrade was successfully completed.
Here are few more relevant logs:
ConfigMgrPrereq.log – This log records prerequisite component evaluation and installation activities.
ConfigMgrSetupWizard.log – This log records information related to activity in the Setup wizard.
Ok, so this was all in this post. I will see you soon with some other tech stuff. Stay tuned 🙂