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:
Note: In my case, it took about 10-15 minutes for this to appear
The install took a few minutes to complete. Verify its state to ensure the install completed.
With Configuration Manager moving to the “As a Service” model, we will be seeing newer client versions more frequently. Luckily there is a way to automate this process and ease the administration overhead of the Configuration Manager Administrator.
In the example I am running Configuration Manager 2012 R2 with the 1602 update. I want to be sure that my clients that report into Configuration Manager are updated within 7 days. From the Administration node, click on Hierarchy Settings.
The Hierarchy Settings window will open. Click on the Client Upgrade tab. You will see the Production client version. In this case I am running 5.00.8355.1000 which is the 1602 update version. Select upgrade all clients in the hierarchy using production client. Then select the number of days you need to have your clients up to date.
Note: the clients will not update all at one and should be staggered so there is not increased activity.
Hello! In this blog I will walk through the steps of upgrading your Configuration Manager environment to the latest update Configuration Manager 1602. Please note that in order to upgrade to 1602, you must first be on 1511. It is not supported going directly to 1602 from any other release.
To see if your environment is showing the update for 1602 click on the administration tab, cloud services. Click on Updates and Servicing. In my case I did not see 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. There is one that is turned off. 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