Let’s check how to perform SCCM Client Upgrade Promote Pre-Production Client to Production. This is my second (2nd) post on the SCCM education series. Recently I received a couple of queries about the Promote Pre-Production Client on my SCCM 1902 upgrade post.
This post replies to those queries and doubts about promoting the pre-production SCCM clients. You will learn how about SCCM Client Upgrade in this post.
First of all, I would recommend you use the option to test client upgrades in a pre-production collection. This is the best option to select during every SCCM CB update or upgrade.
SCCM Education Series Posts
- Walkthrough of SCCM Console
- How to Promote Pre-Production SCCM Client to Production
- What is Collection? How to Create SCCM Static Collections
Why Use Test Client Upgrade in Pre-Production Collection?
In the SCCM CB version, you have an option to test the new client version with test devices. You can test the new SCCM client on a few machines using the pre-production collection option (SCCM Client Upgrade for pilot devices).
Only devices part of the test collection are upgraded when you do this. This helps you test the client issues before upgrading the other SCCM client devices in your environment.
Video Tutorial – Promote Pre-Production Client to Production (SCCM Client Upgrade)
Is Promote Pre-Production Client Upgrade to Production Applicable?
You need to perform a pre-production client upgrade to production when you select the following option two (#2 – as you can see in the below list) during the SCCM updates wizard – client update options page. When you select option one (#1), you don’t
SCCM Client Update Settings gives you two (2) options:-
- Upgrade without Validating:- Upgrade your clients immediately to the latest version (which I don’t recommend). The first option of SCCM Client Upgrade.
- Validate in Pre-Production Collection:- Select to validate this client in the pre-prod collection option from the wizard (SCCM update wizard – client update options page). This will help you test the client upgrade on selected devices before you can upgrade all your SCCM clients to the latest version. (This is the recommended option).
Once you select the second (2nd) option, you can install and validate the SCCM client upgrade on the pre-production device collection members. This won’t impact your production client package.
As explained below, you have an option to overwrite the production package using client update options in the updates and servicing node of the SCCM console.
You can perform this action when you complete the testing of the pre-production client upgrade. This action is known as Promote Pre-Production Client Upgrade.
How to Promote Pre-Production Client Upgrade?
You can promote the Pre-Production clients from SCCM console Updates and Servicing node. For example, You want to upgrade the SCCM pre-production client of 1802.
- Navigate via the following console path “\Administration\Overview\Updates and Servicing.”
- Right-click on the Configuration Manager 1802 Update package in the results pane.
- Select the option to promote the Pre-Production client (explained in the video tutorial).
- From Promote Pre-Production Client Windows, Click on Promote button to make the Pre-production client version available to production.
- Click on the YES button to confirm that you are sure and want to make the pre-production client version available to production.
You can use the ribbon menu to promote pre-production SCCM clients to the production version.
Click on the Promote button to start deploying the production client version to all the devices in the SCCM infrastructure.
Hierarchy Settings Configuration to Automatic Upgrade of SCCM Clients
Let’s check Hierarchy Settings Configuration to Automatic Upgrade of SCCM Clients after promoting the client package as explained in the above section.
This is more of a global setting to automatically upgrade the SCCM client version. You can follow the steps explained below to complete the process.
- Navigate to \Administration\Overview\Site Configuration\Sites.
- Select Standalone Primary Site and Click on Hierarchy Settings from the ribbon menu.
- Click on the Client Upgrade tab and select the production client upgrade behavior with a specified delay, as shown in the screenshot below.
- Enable the option Upgrade All Clients in the Hierarchy using Production Client.
- Select the appropriate delay (in days) using the drop-down options from the Automatically Upgrade Client within days option.
NOTE! – All the Clients in the SCCM hierarchy will get upgraded to the latest production version of the client within one day. So you need to be careful about the Dealy in days configuration.
How do you Verify and promote Pre-Production clients?
You can verify the promotion of Pre-Production client upgrade (SCCM Client upgrade for test devices) results from two (2) places. You can verify this from the monitoring node or the Site Configuration node. Also, this can be confirmed from SCCM client Package properties.
In the following section, I will explain how to verify the promotion of pre-production client action worked as expected.
- Navigate through the SCCM console patch via \Administration\Overview\Site Configuration.
- Click on the Sites node & Select the Primary or CAS server.
- Click on Hierarchy Settings from the ribbon menu/.
- Click on the Client Upgrade tab.
- Check Production Client Version and last modified date. The production client version should be equal to the Pre-Production client version.
You can promote the pre-production client from Monitoring > Client Status > Pre-Production Client Deployment.
How to Upgrade the SCCM client? SCCM Client Upgrade
I have a post about client upgrade process options. I recommend reading that post to know more about SCCM client upgrade options.
- Group policy installation
- Logon script installation
- Manual installation
- Upgrade installation
- OSD or IPU
How to test client upgrades in a pre-production collection – https://docs.microsoft.com/en-us/sccm/core/clients/manage/upgrade/test-client-upgrades
Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.