Configuration Manager 1511 Updates and Servicing : a closer look at the updating experience
Earlier this week Microsoft has released update 1512 for Configuration Manager. In this post we will focus on the implementation experience and walk through the steps required to implement this update in an existing TP4 1511 environment. We will look at how an existing site becomes aware of updates, how to validate the prerequisites and update the site. After that we will also see how to update the other components like the console and clients.
Through the service connection point the site becomes aware of new updates. If any updates are available they are listed in the Sites and Servicing node in the Configuration Manager Console.
Behind the scenes you would find more details about this in the dmpdownloader.log file.
In the EasySetupPayLoad folder you will find the actual content that was downloaded.
We will not go to much into detail on this specific topic. If you want to read more details about the updating process I recommend this post by Kent Agerlund.
From the updates and servicing node you can first run a prerequisite check before installing the update.
As you trigger the check the state is changing
We noticed that CMUpdate.log is logging the prereq check process being triggered
Once all checks are finished the state in the console is again updated.
Details on failures and warnings are logged in the ConfigMgrPrereq.log, located at the root of the System Drive.
Now we have verified the prerequisites are in place, the next step is to install the Update Pack. This is also done in the console through the Updates and Servicing node.
The installation experience is wizard based – and there are only a few steps to walk through. The first window gives some more details on what changes are included. Notice that here you can also opt to ignore any prereq check warnings and run the update anyway. For now we leave this option disabled.
Client Piloting is a new feature which allows testing of the new client version on a set of pre-production systems first. Here we opted to do the validation and we are targeting a pre-production client collection which we had already created during the initial implementation of this lab enviroment.
We need to accept the license terms.
Review the summary
… and we are ready to run the update.
As we chose not to ignore any prereq check warnings the installation did not kick off. If you are confident that the warning(s) can be ignored or they have been resolved you can retry the installation.
In our case we wanted to ignore the warnings so we can click OK on the next dialog box.
This is also reflected in the CMUpdate.log file.
The state is now updated to Installing.
And approximately 10 minutes later the update was successfully completed.
As part of this update we also need to update the Configuration Manager console. As the update of the site was triggered in the console it has not been closed during the entire process. So how do we trigger the console update? In our lab this was triggered by trying to open the site properties (one of the first places we wanted to visit in order to verify the build number). The following dialog box popped up:
Clicking OK automatically closes the console and launches the update.
Once completed the console is automatically started again and shows the What’s new workspace. This is also a new element in this build which we will discuss in detail in a later blog post.
Note: At this point we have no remote console(s) to test but I would assume similar behavior there.
Next we need to get our clients up to par. Remember that we already opted to update our pre-production clients during the setup wizard earlier.
As a result an advertisement is automatically created to update the clients in the pre-production collection. Details about this are logged in the hman.log.
Note though that no client will update before you have distributed the content of the client packages to your distribution points.
Details on the client upgrade are logged in the ccmsetup.log file (on the client itself)
Updated clients should show version 5.00.8336.1000 in the control panel
… or in the console
For sure there are a lot more details to check and elements to uncover but for now and based on this first experience we can conclude that the new updating process is really an improvement: straightforward, covering all infrastructure aspects, and pretty fast.
And one more thing: happy to see that the update has also reset the time bomb mechanism. This means we get more time to play in this lab!
Until next time!