Microsoft released the latest version of Microsoft Endpoint Configuration Manager 2006. And the 2006 version of ConfigMgr is Generally available. This step-by-step guide provides all the details that you require to perform SCCM Primary Server Upgrade to 2006.
New Features of the ConfigMgr 2006 production version (a.k.a WFH Release) are available here.
You need to plan to upgrade the operating system of your site system servers before the upgrade to the ConfigMgr 2006 or later version of the current branch. Server 2008 R2 DP and PXE are not supported anymore. More details – are here.
Video Experience of 2006 Upgrade
Prerequisites of 2006 Version
- The following SCCM versions are supported for the upgrade to 2006.
- 1810, 1902, 1906 or 1910, or 2002
- Read More details about SCCM Life Cycle
- Install update 2006 at the top-level site of your hierarchy (CAS or Standalone Primary)
- 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! – To download the update when your service connection point is offline, use the service connection tool.
Upgrade Check List
The following is the high-level checklist provided by Microsoft. Let’s go through this list before starting the upgrade of 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 day before the production upgrade)
- Update sites
More detailed information about the ConfigMgr 2006 installation checklist is given below https://docs.microsoft.com/en.
Download ConfigMgr Version 2006
Let’s go through the steps to initiate the download of the early ring version of Configuration Manager 2006
using the PowerShell script. Once the update is downloaded, you can start the installation of the 2006 version of SCCM.
- As this 2006 version of SCCM is generally available in all applicable ConfigMgr Consoles.
Opt-in using PowerShell command.
- Launch ConfigMgr console & navigate through \Administration\ Overview \Updates and Servicing.
- Check 2006 fast or Opt-in version update of ConfigMgr is already available or not?
- If not, click on 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 a common scenario in enterprise organizations and LAB environments. This issue is mostly because of proxy or some other internet-related issues.
There are a couple of ways to fix this kind of issue if it’s not related to proxy and the internet. You can refer to the previous blog posts to solve 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 is waiting 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
- 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
- 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! – Make sure you start the prerequisite checks 3-4 days before the production update/upgrade of SCCM infra.
Configuration Manager Update Wizard
Let’s continue with 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 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 Configuration Manager Update Wizard for 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 pre-production collection before you upgrade all your SCCM clients.
I would recommend validating the client version with pre-production collection devices before upgrading the SCCM 2006 client package to all your clients directly.
Upgrade without validating
If you select the SCCM client upgrade without validating the option, this 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
If you select the “Validate in Pre-production collection” option, then you will get an option to validate the new client update on members of the pre-production collection while you keep 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.”
- Click on “I accept these License Terms and Privacy Statement“
- Click on the NEXT button to continue
- Click Next, and Next to continue
- Click on Close to continue to 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 start. And the updates and servicing node in the ConfigMgr console will show that the update is in installing state.
You can start monitoring ConfigMgr 2006 upgrade from this stage.
- You can click on a link “Show Status” from related objects.
- Show status will show you the details about the installation status in the monitoring workspace.
I would recommend following the below screenshot 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! – Don’t forget to check CMUpdate.log to get more detailed information about SCCM Primary server upgrade to 2006.
The following sections have been successfully 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 by upgrading the console of the Primary servers & CAS server.
You need to make sure all your remote SCCM console installations are upgraded to the latest version. This is not very critical if your remote SCCM console is already running with the n-1 version (where n = 2006 in this scenario).
But, if your remote SCCM console is not n-1 then, you need to make sure your console is updated otherwise you won’t be able to connect to the SCCM console.
ConfigMgr 2006 Version Numbers
Let’s see what are 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
3 thoughts on “SCCM Primary Server Upgrade to 2006 | ConfigMgr | Guide | Step by Step”
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?
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 ?
15 gb minimum free space is required