Ok so time for some upgrades!
Plenty of people have outlined the details for this procedure already (see references at the end) so I wont go into great detail but just do a screen by screen walk-through for you. I will be walking through Nicolaj Andersons post for the v1511 upgrade as it comes highly recommended, there are links in the references at the bottom of the page
- System Center Configuration Manager 2012 R2 SP1 with CU3 installed
- SQL Server 2012
- Server 2012 R2 Operating System
2012 R2 SP1 CU3 to v1511
- Latest Windows Updates run on the site server
- Verify that ADK for Windows 10 is installed
- Install KB3095113 on the Software Update Point
- Download v1511 ISO from VLSC
- Check Monitoring \ Overview \ System Status \ Site Status and Monitoring \ Overview \ System Status \ Component Status for errors.
- Uninstall non supported roles Out of Band Management Point & Service Health Validator Point. You can do that by navigating to Administration \ Overview \ Site Configuration \ Servers and Site System Roles.
- Backup your SQL before you begin.
2012R2SP1CU3 > v1511 - Step by Step
- Launch ‘splash.hta’ from the ISO.
- Click on Next from the “Before you begin” page.
- Ensure that “Upgrade the Configuration Manager Site” option is selected from the “Available Setup Options” page.
- Accept license terms & click Next followed by Accepting more license terms and clicking Next.
- Now we come to downloading the Prerequisites. On the Prerequisite Downloads page, select a folder to download them to and click Next
- On the Server language Selection page your currently installed languages should be selected so simply clicked Next.
- The same option is presented for the Client Language Selection page so again click Next.
- On the Usage Data page, read the information and click Next.
- On the Service Connection Point Setup page select “Yes, lets get connected (recommended) and click Next.
- Finally you hit the Settings Summary page, where you can click Next.
- Some more prerequisites are checked and supposing you pass them with no errors, click Begin Install (however please do review any Warnings they are there to help)
(as you can see from this it appears that from 2012R2 SP1 CU3 it no longer complains about the OS not being supported)
I then sat back and watched the log looking for errors until it completed successfully.
I can see from the upgrade that my management point has an error, so I suggest you go and check your site components after the upgrade. As a measure of good will I rebooted the site server just so that every component was cycled. Once it came back up everything was OK. One down, one to go.
v1511 > v1602
This time I’m going to walk through Rob Marshalls instructions (link in the references)
- Create a device collection Client Pre-Deployment (Validation of v1602) & add some devices to the collection
- Go here Administration \ Overview \ Cloud Services \ Updates and Servicing and check for the 1602 update.
- You can force it through by downloading EnableUpdateRing.txt, rename it to EnableUpdateRing.ps1
- Call the Powershell script using .\EnableUpdateRing.ps1 [your CAS or Primary Site Server FQDN]
- Restart SMS_EXECUTIVE component, should it not appear after a while (I just did it and it was instant thereafter)
v1511 > v1602 - Step by Step
Once its downloaded & extracted the state will become available
So we right click and select to Install Update Pack
On the General page click Next
Yes we would like all the features on the Features page, so we click Next
You should test this in a pre-production environment first which is what I would suggest and hope you do. In this example I’m going to move straight on clicking on Next and leaving the Upgrading without validating option selected.
Accept the License terms, review the summary and click Next. The wizard should complete without error/warning and if you return to the Administration \ Overview \ Cloud Services \ Updates and Servicing node of the console you should see it installing.
You can check out the Monitoring \ Overview \ Site Servicing Status node of the console to keep up with what’s going on in your hierarchy. First the content replicates, then the prerequisites are checked and the install takes place. Eventually the state will turn to Installed.
The first time you launch the console after the upgrade it will prompt you to upgrade it and any console installations elsewhere will also need to be upgraded.
Once you do that, you’re done.
Link... – Nicolaj Andersen wrote a great article about the 1511 upgrade as well as other additions such as enabling the new Software Centre.
Link... – Paul Winstanley also wrote a great blog about installing from scratch.
Link... – Steve Thompsons SQL Server back up for ConfigMgr page.
Link... – Robert Marshalls post on upgrading to 1602.
Link... – Russ Rimmerman 1602 Walkthrough.
Link... – Yvette OMeally | 1602 Announcement Page (With PowerShell).
Link... – What’s new in 1602.
I hope this was useful for you