After my earlier post on the 1606 update process I have been exploring some of the new features in this build. A small yet nice change in 1606 is the cleaning up of the Updates and Servicing view.
With this release you will see only the most recently installed update and any new updates that are available for installation. The older entries will no longer be listed.
So after just installing 1606 in our environment it looks like this:
And what if we want to know what path this site has followed to come up to this level? Easy – just hit the history button and the answer to that question pops up:
Note : this only becomes available after your console has been updated also! If you still run an older version of the console you can simply close and then restart it to trigger the update process.
Until next time!
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!
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!