Installing Configuration Manager Update 1606
With the release of Update 1606 today I decided to update one of my lab environments and document the experience. This particular lab environment has a single primary with a few clients and has been running on current branch 1602 for quite some time already.
Enabling the update ring
As I looked at the sites and servicing node the 1606 update was not yet listed.
To get the update we first need to run a script that will put the site into the early update ring.
Run the script from an elevated command prompt following the instructions documented on Technet.
Then from the console we can check for updates in the updates and servicing node once again.
You can check the dmpdownloader.log for details on what is happening under the hood.
Click refresh in the updates and servicing node and the 1606 update should be listed.
Prior to running the upgrade we can run a prerequisite check. This is also done from the sites and servicing node.
To see the outcome of the check we need to go to the monitoring workspace and select Site Servicing Status. Select the 1606 update and then click the show status button to see the details.
For the under the hood details we can check the ConfigMgrPrereq.log on the root of the system drive.
Once we have passed all prerequisite checks we are now ready to install the 1606 update.
This is done from sites and servicing also.
Click next when the wizard starts.
Select or deselect any features and click next.
Configure the options for client updating and click next. In our site we do use preproduction clients to run some tests first.
Accept the license terms and click next.
Review the summary and click next.
Click close once the wizard has completed successfully.
While the installation process in ongoing you can see some more details in the site servicing status node in the monitoring workspace. More details can also be found in the cmupdate.log.
Upon successful installation the state in the sites and servicing node should also change to installed.
The site version should be 5.0.8412.1000. The can be checked in the About dialog box.
Or you can also validate it in the site properties (on the General tab)
To upgrade the console all we need to do is close it and launch it again.
A message will be displayed indicating a newer version of the console is available. Click OK to install the new version.
This will take a few minutes. A progress dialog box is shown during the update process.
More details can be found in the ConfigMgrAdminUISetup.log and ConfigMgrAdminUISetupVerbose.log files on the root of the system drive.
The console is launched automatically as soon as the installation is completed.
The console version should be 5.0.8412.1003
Updating clients in this lab will be done in two phases by using the built-in client piloting features. For now we upgrading pre-production clients only.
Once we have verified no issues occur on the clients we will approve the upgrade for all clients in the hierarchy.
In the meantime we can track progress in the client deployment nodes in the monitoring workspace.
That’s it for the update installation in our lab – as you can see again a very smooth experience!
Make sure to come back in the upcoming days for more details on this release and its features!