SCCM Primary Server Upgrade to 2006 | ConfigMgr | Step-by-Step Guide
In this post, I will explain the SCCM Primary Server Upgrade to 2006. Microsoft released the latest version of Microsoft Endpoint Configuration Manager 2006; the 2006 version of ConfigMgr is generally available. This step-by-step guide provides all the details required to perform the SCCM Primary Server Upgrade to 2006.
The 2006 update for Configuration Manager’s current branch is now accessible as an in-console update. Make sure to apply this update to sites running version 1810 or later. Always check the latest checklist to install this update.
It’s essential to update the site and the clients to the latest version to take advantage of the new Configuration Manager features. Although new functionality becomes available in the Configuration Manager console after updating the site and console, the complete scenario won’t work correctly until the client version is updated.
It would help if you upgraded the operating system of your site system server before upgrading to ConfigMgr 2006 or a later version of the current branch. Server 2008 R2 DP and PXE are no longer supported. More details are here.
- How to Learn SCCM ConfigMgr Intune | Start Learning Microsoft Configuration Manager Endpoint Manager
- Windows 11 Edition Upgrade using SCCM Policy
- SCCM 2303 Upgrade Step-by-Step Guide | New Features
- SCCM 2211 Upgrade Step-by-Step Guide | New Features
- FIX SCCM Client Inactive Issue after the Upgrade SCCM Notification Server Component Issue
New Features of the ConfigMgr 2006 production version (a.k.a WFH Release) are available here.
Video Experience of 2006 Upgrade
This video provides a step-by-step guide for upgrading the SCCM primary server to the latest version of ConfigMgr 2006, the fast-ring version.
Prerequisites of 2006 Version
- The following SCCM versions are supported for the upgrade to 2006.
- 1810, 1902, 1906, 1910, or 2002
- Read More details about the SCCM Life Cycle.
- Install update 2006 at the top-level site of your hierarchy (CAS or Standalone Primary)
- The SCCM version should have an online Service Connection Point.
- Evaluate Checklist
- Evaluate SQL Requirements for SCCM 2006 Upgrade – here
- Evaluate Windows Server OS Requirements for SCCM 2006 site server – here
- Evaluate Supported OS versions for clients and devices – here
- Evaluate Supported OS versions for ConfigMgr consoles – here
- Evaluate Recommended hardware – here
- Support for Windows features and networks – here
- Evaluate Support for virtualization environments – here
- Evaluate the Firewall Rules – More details here and here
NOTE! – use the service connection tool to download the update when your service connection point is offline.
Upgrade Check List
The following is Microsoft’s high-level checklist. Review this list before upgrading the SCCM 2006 primary server in a production environment.
- All sites run a supported version of Configuration Manager
- Review the status of your product licensing
- Review Microsoft .NET versions
- Review the version of the Windows ADK for Windows 10
- Review SQL Server Native Client version
- Review file and data replication between sites
- Database replication
- File-based replication
- Install all applicable critical Windows updates
- Disable database replicas for management points at primary sites
- Set SQL Server AlwaysOn availability groups to manual failover
- Disable site maintenance tasks at each site
- Temporarily stop any antivirus software
- Back up customized files
- Plan for client piloting
- Plan to use service windows
- Review supported extensions
- Run the setup prerequisite checker (I recommend running the prerequisite check 3-4 days before the production upgrade)
- Update sites
More detailed information about the ConfigMgr 2006 installation checklist is below: https://docs.microsoft.com/en.
Download ConfigMgr Version 2006
Let’s use the PowerShell script to initiate the download of the early ring version of Configuration Manager 2006. Once the update is downloaded, you can start installing the 2006 version of SCCM.
- This 2006 version of SCCM is generally available in all applicable ConfigMgr Consoles.
- Opt-in using the PowerShell command.
- Launch ConfigMgr console & navigate through \Administration\ Overview \Updates and Servicing.
- Check whether 2006 Fast or the opt-in version update of ConfigMgr is already available.
- If not, click the “Check for Updates” button from the ribbon menu.
- Click OK to continue
- Configuration Manager 2006 update is available and Downloading.
NOTE! – Check the DMPDownloader.log to get more details.
SCCM 2006 Download Stuck
The update getting stuck during the downloading stage is common in enterprise organizations and LAB environments—a proxy or other internet-related issues mainly cause this issue.
If the issue is unrelated to a proxy or the internet, there are a couple of ways to fix it. For example, you can refer to previous blog posts on solving Update Download stuck problems.
More troubleshooting help on Configuration Manager 2006 Download stuck and upgrade issues here and here.
Microsoft Doc: https://support.microsoft.com/en-us/help/4490424/understand-and-troubleshoot-updates-and-servicing-in-configmgr
Log Files are Your Friend
- DMPDownloader.log for SCCM 2006 source file download issues
- ConfigMgrSetup.log for Redist Files Download Issue
- CMUpdate.log for all the upgrade-related activities
- If the update displays as Downloading and doesn’t change, review the hman.log and dmpdownloader.log for errors.
- The dmpdownloader.log may indicate that the dmpdownloader process waits for an interval before checking for updates. To restart the download of the update’s redistribution files, restart the SMS_Executive service on the site server.
- Another common download issue occurs when proxy server settings prevent downloads from
silverlight.dlservice.microsoft.com,download.microsoft.com, andgo.microsoft.com.
- For more information about installing updates, see In-console updates and servicing.
- For more information about current branch versions, see Baseline and update versions.
Start – SCCM Primary Server Upgrade to 2006
- SCCM 2006 download is completed successfully
- The 2006 update is Ready to Install
- Right Click on the Update “Configuration Manager 2006” Update
- Select PreRequisite Check
- Once the Prerequisite Check is completed successfully, proceed to the next step.
- Right Click on the Update “Configuration Manager 2006” Update
- Click on Install Update to start the SCCM 2006 installation
ConfigMgr 2006 Update Prerequisite Check Stuck
The Configuration Manager upgrade prerequisite check can take many hours, depending on your hierarchy/infra. When you have CAS and many primary servers, the 2006 update source files will be copied to primary servers.
You can check the status of the prerequisite checks from the monitoring node. More details about SCCM prerequisite checks are here.
Microsoft Documentation – https://docs.microsoft.com/en-rerequisite-checker
NOTE! – Ensure you start the prerequisite checks 3-4 days before the production update/upgrade of SCCM infra.
Configuration Manager Update Wizard
Let’s continue with the SCCM 2006 update wizard:
- Click on the “Ignore any prerequisite check settings and install the update regardless of missing requirements” box.
- Click on the Next button.
- Select the features you want to enable after the upgrades from the Features Included in the Update Pack page.
- Click on Next to continue.
- Client Update Settings page configuration
- Upgrade without validating (Direct Production Upgrade)
- Validate in pre-production collection (Test the client before the upgrade)
- Click the NEXT button to continue
Client Update Settings Option
Client Update Settings is another important option in the Configuration Manager Update Wizard for the SCCM 2006 upgrade. SCCM Client Update Settings include an update for the SCCM clients. You can upgrade your clients immediately or validate this client in the pre-production collection before you upgrade all your SCCM clients.
I recommend validating the client version with pre-production collection devices before directly upgrading the SCCM 2006 client package for all your clients.
Upgrade Without Validating
Selecting the SCCM client upgrade without validating the option overwrites your current SCCM client package with the new SCCM client update. All new client installations and client upgrades use this new client update.
Validate in Pre-production Collection
Suppose you select the “Validate in Pre-production collection” option. In that case, you can validate the new client update on members of the pre-production collection while keeping your production client package intact.
Later, once you are confident with the new client package, you can overwrite the production package using Client Update Options in the Updates and Servicing node of the SCCM console.
NOTE! – More details about SCCM Client Upgrade options “SCCM Client Upgrade Promote Pre-Production Client to Production.”
License Agreement
Click on “I accept these License Terms and Privacy Statement.”
- Click on the NEXT button to continue.
Summary
Click Next and Next to continue.
- Click on Close to continue the installation process of 2006 and close the wizard.
Installation Status Primary Server
Once you complete the Configuration Manager update wizard, the ConfigMgr 2006 upgrade process will kick off. The updates and servicing node in the ConfigMgr console will show that the update is installed.
You can start monitoring the ConfigMgr 2006 upgrade from this stage.
- You can click on the link “Show Status” from related objects.
- Show status will show you the details about the installation status in the monitoring workspace.
I recommend following the screenshot below to see the real-time updates of the SCCM upgrade. Let’s monitor the installation Monitoring workspace:
- Navigate to – \Monitoring\Overview\Updates and Servicing Status
- Check for Configuration Manager 2006.
NOTE! Remember to check CMUpdate.log for more detailed information about the SCCM Primary server upgrade to 2006.
Upgrade Completed
The following sections have been completed as part of the 2006 installation.
- Download – Completed
- Replication – Completed
- Prerequisite Check – Completed with some warnings
- Installation – Completed
- Post Installation – Completed
Console Upgrade to 2006 Version
The last step of the ConfigMgr 2006 installation is upgrading the consoles of the Primary servers and CAS server.
You must ensure all your remote SCCM console installations are upgraded to the latest version. This is not critical if your remote SCCM console already runs with the n-1 version (where n = 2006 in this scenario).
But if your remote SCCM console is not n-1, you must ensure it is updated; otherwise, you won’t be able to connect.
ConfigMgr 2006 Version Numbers
Let’s see the Configuration Manager 2006 version numbers.
- Site Server Full Version Number – 5.00.9012.1000
- Site Server Version Number – 5.0.9012.1000
- Console Version Number – 5.2006.1026.1800
- Client Version Number – 5.00.9012.1015
Resources
We are on WhatsApp. To get the latest step-by-step guides and news updates, Join our Channel. Click here –HTMD WhatsApp.
Author
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 a Blogger, Speaker, and Local User Group HTMD Community leader. His primary focus is 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.
Thanks for the guide this is super useful,
After the upgrade though, it takes an awful long time to deploy the clients.
Is there some way we could cancel the “In Progress” clients & push install using the right-click “Install Client” in devices? Will that be quicker?
Thanks
Dear Sir.
You have a great site here that will help me a lot. I am very new to SCCM / ECM and i need to update my main server and one site server from 1910 to 2006. I made a prerequisite check today just to see if there is some work to do before i can do the update and the check failed with the message “disk space on site server”. I found no information how much disk space i need on the site server, i checked a few websites from microsoft. Do you know how much diskspace is needed to pass the prerequisite check ?
Staff15 gb minimum free space is required