Home > Uncategorized > Updating to Configuration Manager Build 1606

Updating to Configuration Manager Build 1606

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 Next.

Click I accept the license terms and privacy statement. Click Next.

Review the summary. Click Next.

Click Close.

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

Categories: Uncategorized
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: