This post is a step-by-step SCCM 2006 upgrade guide that covers the new features in Configuration Manager version 2006 and installation steps.
The Configuration Manager 2006 update is available as an in-console update. As a result if you are running ConfigMgr version 1810 and above, you can directly upgrade to SCCM 2006 in your production.
Most of all there is NO SCCM 2006 baseline version. The previous baseline version was Configuration Manager 2002. And if you are installing Configuration Manager from scratch, you can always download and start with version 2002.
Table of Contents
Configuration Manager 2006 Servicing Support
Configuration Manager current branch 2006 is the second current branch release of this year. Probably there could another current branch release (maybe version 2010) before the year 2020 ends.
As always, when you see a new current branch update version, it remains in support for 18 months from its general availability release date.
The Configuration Manager 2006 will receive Security and Critical updates for first four months (Up to November 2020). And for next 14 months, it will receive only Security Updates.
The below Configuration Manager 2006 servicing support pic should give you a clear idea of servicing phases.
SCCM 2006 New Features
The SCCM 2006 includes the following new features.
- Endpoint analytics data collection enabled by default
- New Boundary type – VPN boundary type
- Management insights to optimize for remote workers
- Improved support for Windows Virtual Desktop
- Intranet clients can use a CMG software update point
- Notification for Azure AD app secret key expiration
- Several CMPivot Improvements in SCCM 2006
- Install and upgrade the client on a metered connection
- Improvements to managing device restarts
- Improvements to available apps via CMG
- Microsoft 365 Apps for enterprise
- Task sequence media support for cloud-based content
- Improvements to task sequences via CMG
- Improvements to BitLocker task sequence steps
- New Management insight rules for OS deployment
- CMG support for endpoint protection policies
- Community hub and GitHub Feature
- Notifications from Microsoft
If you have been following ConfigMgr Technical preview posts, you will notice most of the features were already part of technical preview builds. Not all but very few make it to current branch builds.
I have listed out all the new features that are included with Configuration Manager 2006. However I will publish a separate post explaining all the ConfigMgr 2006 new features soon.
For now you can read about all the new features of Configuration Manager 2006 – https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/changes/whats-new-in-version-2006.
SCCM 2006 Upgrade Prerequisites Checklist
Here are some of the prerequisites checklist that you need to look into before you install Configuration Manager 2006 update.
- Update 2006 for Configuration Manager current branch is available as an in-console update. There is NO ConfigMgr 2006 baseline version.
- To apply this update on your sites, ensure you have installed SCCM version 1810 or later.
- If you’re running a multi-tier hierarchy, start at the top-level site in the hierarchy. First perform the CAS upgrade, later you can begin the upgrade of each child site. Complete the upgrade of each site before you begin to upgrade the next site.
- Ensure that you are running a supported Operating System and SQL Server version.
- If you’re running SCCM version older than 1810, check the SCCM In-place upgrade paths.
Configuration Manager 2002 Hotfixes – Install or Skip ?
After the release of Configuration Manager 2002, we saw several hotfixes released to patch the product. Some of them contained a single fix while most of them patched several bugs.
Probably you may not have installed any or installed just few hotfixes. Consequently when you open the SCCM console, you might see some additional SCCM 2002 hotfixes that are ready to install. If you are not sure whether to install these hotfixes first or directly install ConfigMgr 2006, here is the answer.
Answer – A hotfix contain either one individual fix or a bundle (a rollup of fixes). All the hotfixes released for Configuration Manager 2002 will be included in SCCM 2006. Therefore if you see any hotfixes in your console while installing version 2006 or even older versions, you may skip them and directly install 2006 update.
Alright now that you have decided to upgrade your Configuration Manager to version 2006, let’s look at the upgrade steps. This step-by-step upgrade guide contains all the information that should help you to upgrade to SCCM 2006.
This guide will be also added to SCCM Current Branch Guides and you can download the PDF file soon. I have a single primary site and I will be upgrading SCCM 2002 to SCCM 2006.
SCCM 2006 Generally Available
As of today September 1st 2020 Microsoft Endpoint Configuration Manager (MEMCM) 2006 is generally available. So this means you don’t need enableearlyupdatering2006.ps1 file to download the update 2006. You may skip the below step and directly jump to SCCM 2006 Prerequisite check.
Get Configuration Manager 2006 Update
First of all the Configuration Manager 2006 update will not be available for everyone yet. It should take few weeks while the Configuration Manager update 2006 gets rolled out globally.
Until then you can either wait for the update to be made globally available or run the EnableEarlyUpdateRing 2006 script. This script enables fast ring for 2006 update package in ConfigMgr Current Branch.
If you want to enable SCCM 2006 update, first download the EnableEarlyUpdateRing 2006 PowerShell script. This script will allow you to enable fast Update-ring in ConfigMgr Current Branch.
Run EnableEarlyUpdateRing 2006 PowerShell script
On your SCCM server, run the PowerShell as administrator and run the script. Enter the site server name (Top level site server name or IP address) and script gets the update 2006 in console for you.
You can monitor the update download by opening dmpdownloader.log file.
Note – At this point if your SCCM 2006 update gets stuck in downloading state, here is a post to help you – https://www.prajwaldesai.com/fix-sccm-update-stuck-downloading-state/.
Wait while the update 2006 downloads and extracts all the files required for upgrade. The update state changes from Downloading to Ready to Install.
The package GUID of the update 2006 is E150700D-0C89-4D3A-A6D9-849C155810CF.
Once we have the update 2006 ready to install, I always recommend you to run a prerequisite check. Performing a prerequisite check prior to installing a major current branch update is very important. You don’t want to directly install an update which halts at some point throwing an error.
SCCM 2006 Prerequisite Check
Here are the steps to perform SCCM 2006 Prerequisite Check.
- Launch the SCCM console.
- Navigate to Administration > Overview > Updates and Servicing Node.
- Right click Configuration Manager 2006 update and click Run Prerequisite check.
When you run a prerequisite check, it takes a while to actually begin the prerequisite check. Furthermore you can monitor the prerequisite checks in Monitoring workspace. In addition, you can also review the ConfigMgrPreReq.log to know the status of prerequisite check.
There are several ways to confirm if the prerequisite check has passed successfully or were there any warnings.
- Successful – Prerequisite Check Passed
- Warnings – Prerequisite Check passed with warnings
- Failed – Prerequisite check failed
First method is to check the prerequisite check status in console. In the Updates and Servicing node, the update state should show the prerequisite check state. In this example, we see the state as prerequisite check passed.
You can check the Prerequisite check status by monitoring the Update Pack Installation Status. In the Configuration Manager console, go to Monitoring > Overview > Updates and Servicing Status.
Right click Configuration Manager 2006 update and click Show Status.
The third method involves reviewing the ConfigMgrPrereq.log file. Any warnings or errors will be logged in this log file during prerequisite check.
If the prerequisite check completes without any errors or warnings, you see the below line.
******* Prerequisite checking is completed. *******
Solutions for ConfigMgr Prerequisite Check Warnings or Errors
The most common warning that most of us see is “Site Database has a backlog of SQL Change Tracking Data“. The solution is available in below links.
Listed below are some of common reasons why the prerequisite check fails. Sometimes your SCCM 2006 download might get stuck. Click the Solution to fix the warning.
- The site database has a backlog of SQL change tracking data – Solution.
- Configuration Manager Pending System Restart – Solution.
- SQL Server Native Client Version – Solution.
- SCCM Update Stuck at Downloading State – Solution.
We will now perform SCCM 2006 upgrade which involves installing the SCCM 2006 update over the previous version 2002.
SCCM 2006 Upgrade Guide
To begin the SCCM 2006 Upgrade process.
- Launch the SCCM console.
- Navigate to Administration > Overview > Updates and Servicing Node.
- Right click Configuration Manager 2006 update and click Install Update Pack.
The ConfigMgr update 2006 includes :-
- Configuration Manager Site Server and Console
- Configuration Manager clients
- Fixes for known issues
- New Features
You can enable the new features once the update is installed. Click Next.
Choose the required Client Update Option and click Next.
Accept the License Terms and click Next.
Verify the settings on Summary page and click Next.
Monitor SCCM 2006 Update Installation Status
To monitor the Configuration Manager update 2006 installation
- In SCCM Console, go to Monitoring node.
- Click Overview > Updates and Servicing Status.
- Select the Configuration Manager 2006 update and click Show Status.
- Ensure all the steps show as completed.
SCCM 2006 Console Upgrade
After installing the Configuration Manager 2006 update, it’s time to upgrade the console. Refresh the console once and the console upgrade box shows up.
Click OK to upgrade old console version (5.2002.1083.2900) to new version (5.2006.1026.1800).
Wait while the console upgrade completes. The new version of SCCM 2002 console will launch automatically.
Verify Configuration Manager 2006 Update Install
In the new console let’s verify the ConfigMgr 2006 update. In the Configuration Manager console, go to Administration\Overview\Site Configuration\Sites. Right click the site and click Properties.
On the Site Properties window, check the version and build number.
- SCCM 2006 Version – 5.00.9012.1000
- SCCM 2006 Build Number – 9012
In the Configuration Manager console, click About Configuration Manager.
- Version – 2006
- Console Version – 5.2006.1026.1800
- Site Version – 5.0.9012.1000
Update SCCM 2006 Boot Images
The Configuration Manager 2006 update installation is complete. Now you must update SCCM boot images.
- Update Boot Images to all the distribution points.
- Update Configuration Manager client package to all DP’s. You can check the content status to see last update.
- After the update install, the Boot Image version should be 10.0.19041.1.
Upgrade Configuration Manager 2006 Client Agents
To take full advantage of Configuration Manager 2006 new features, after you update the site, also update clients to the latest version.
Sometimes the admins skip this step and as a result, after the upgrade, they don’t see the new features. You can upgrade client agents using client upgrade feature.
To upgrade SCCM client agents to latest version.
- Go to Administration > Site Configuration > Sites.
- Click the Hierarchy Settings on top ribbon.
- Select Client Upgrade tab.
- Ensure Upgrade all clients in hierarchy using production client box is selected.
- Specify the number of days within which you want to automatically upgrade client agents.
- Click OK.
ConfigMgr 2006 Client Version Details
As mentioned earlier to take full advantage of ConfigMgr 2006 new features, you must update clients to the latest version. Take a look all the client version numbers of ConfigMgr current branch builds.
You can find the client version details from ConfigMgr console and by checking the version on client computers.
- Go to Control Panel > Configuration Manager > General.
- In the General tab, under client properties, look for client version.
After you upgrade to ConfigMgr 2006, the new client version is 5.00.9012.1015. You can use the below query to find out the devices without the latest SCCM client version 5.00.9012.1015.
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ClientVersion != '5.00.9012.1015'