Hello! In this blog I will walk through the steps of upgrading your Configuration Manager environment to the latest update Configuration Manager 1606.
Note: you can upgrade your environment from 1511 right to 1606. The updates are cumulative (all features in 1602 are in 1606) and you do not need to be at 1602 first.
Let’s get started
When opening the console, you may see the following message appear
Click OK. The console will continue to open
Browse to Administration>Cloud Services>Updates and Serving
You should see
the 1606 update available
To see if your environment is showing the update for 1602 click on the administration tab, cloud services. Click on Updates and Servicing.
If by chance you do not see the update even after running a check for updates, you can force the site server to grab the update.
To force check the update, you can download the script from this blog post.
Once you run the script restart the SMS_Exec service.
Within a few minutes you will see the latest update appear and start to download.
I looked at the EasySetupPayload folder to where the update is downloaded. This update is quite large (1.72 GB) so it will take some time.
The update will now say that it is available. Click on Install Update Pack.
Note: you may choose to run update prerequisite check first, however the install does this anyway.
A wizard will appear. Click Next.
Click I accept the license terms and privacy statement. Click Next.
Review the summary. Click Next.
Refer to the Updates and Servicing again.
You will now see that it is installing. You can refer to the CMUpdate.log for status.
After Several minutes you will see that the status is now changed to Installed.
Click on the Features node under Updates and Servicing. You will now see several features. Select Pre-release – Conditional access for managed PCs. Click Turn on from the ribbon on top.
When you click Turn on, the following message will appear. Click Cancel and close out of the Console and reboot your server before attempting the update. I ran into an issue trying to update the console before a reboot and it would never complete. After the reboot and you attempt to open the console. The same message will reappear. Click OK.
You may be prompted to restart your server. If not, it is a good idea to do so anyway as a lot of changes were just made to your Configuration Manager environment. After the reboot, open your console to confirm the console has been updated.
Also be sure to update-based client installation as this will have a new version
As I logged into my Configuration Manager Console this morning, I received a message that there is a new update available. This blog will walk through the steps to apply the new update. In this case it is a hotfix to 1602.
I opened up the Cloud Services under the Administration workspace and I say the update listed.
As a good rule of thumb I checked for pre-requisites.
By the time I got back with my morning coffee, I see that the pre-requisites passed.
Great! Now I chose to install Update Pack
This brought up the following install wizard. Click Next
Since I am in a lab environment, and I took a snapshot prior to this, I am going to upgrade without validating. In the real world, I strongly recommend to validate in a pre-production collection. Click Next.
Accept the license terms. Click Next.
Review the summary. Click Next.
The progress has completed successfully. Click Close.
The hotfix will begin to download. After a few minutes you should see that it is installing:
The install took a few minutes to complete. Verify its state to ensure the install completed.
In this post I will cover the servicing of Windows 10 1507 and updating Windows 10 to 1511. Within the next month or two, we will likely be seeing the anniversary update to Windows 10. The process should be the same as below.
Click on Software Library and then select Windows 10 Servicing. Below you will see the Windows 10 Servicing dashboard. In this example I have one system that is already running 1511 and one that is still running 1507.
Below is a calendar that shows the dates and end of life for 1507 and 1511. As you can see 1507 was nearing end of live on 2016/03…. Time to upgrade
Under Servicing Plans. Create a new servicing plan
Select a target collection
Configure a deployment ring
Select the language(s) that are needed
Configure a deployment schedule that meets your needs
Configure the user experience that meets your needs
Create or use an existing Deployment Package
Select the distribution points(s)
Choose a download location
Choose the language(s) needed
Review the summary
Take a look at the All Windows 10 Updates. In my lab I have 1 required.
Download the update, this will take some time.
Deploy the Update
Go back to the Service Plans and click Run Now.
The systems(s) will check in and see if they need to apply the update based on the policies of the servicing plan.
Prior to 1511 Update
After 1511 Update