Complete SCCM 2403 Upgrade Guide
A step-by-step guide to upgrade your Configuration Manager setup running in production to release version 2403. Also includes the new features in SCCM version 2403.
This post is a complete step-by-step SCCM 2403 upgrade guide that covers all you need to know to update your existing SCCM servers to version 2403. This article also covers all the new features in 2403, including the console and client upgrade details and hotfixes.
The ConfigMgr update 2403 for the current branch is available as an in-console update. You can install this update on sites that run version 2211 or later.
ConfigMgr 2403 is a production-ready release, and it is the first current branch release of the year 2024. ‘24‘ stands for the year 2024, and ‘03‘ for the month of March. Your SCCM site must be running version 2211 or later to upgrade to 2403. Upgrading to the current SCCM branch, version 2403, will bring the latest bug fixes and new features to your site.
Before the release of Configuration Manager 2403, Microsoft released Configuration Manager 2303 and SCCM 2309 current branch update for the year 2023. According to the SCCM release cadence, Microsoft changed their release cycle from three current branch updates per year to two CB updates per year. So the year 2024 will see two current branch releases: 2403 and 2409.
https://angelelite.de/showthread.php?tid=815
https://themastergames.com/mybb/thread-cover-letter-for-counseling-job
https://forum.bedwantsinfo.nl/thread-466620.html
https://equestrianbbs.com/thread-229.html
https://carpentryforums.com/showthread.php?tid=19954
You can use the steps covered in this guide to upgrade your Configuration Manager setup running in production to release version 2403. After applying the SCCM 2403 update, make sure you apply all the latest hotfixes for that version to get rid of any remaining bugs or issues. Also see What’s new in version 2403 of Configuration Manager current branch.
New Features in Configuration Manager 2403
The following new features are included with the ConfigMgr 2403 release:
Windows Server 2012/2012 R2 operating system site system roles are not supported from this version of Configuration Manager
Microsoft Azure Active Directory rebranded to Microsoft Entra ID
Automated diagnostic Dashboard for Software Update Issues
The console now has a centralized search box
Added Folder support for Scripts node in Software Library
HTTPS or Enhanced HTTP, should be enabled for client communication from this version of Configuration Manager
https://foro.muelendhir.com/showthread.php?tid=39287
https://forum.goddesszex.dev/showthread.php?tid=2110
https://raovatne.com/threads/pssf7.8322/
https://raovatne.com/threads/xem-tham-my-vung-kin.19165/
https://forum.webgod.ro/showthread.php?tid=403
Resource access profiles and deployments will block Configuration manager upgrade
The Save-CMSoftwareUpdate cmdlet now has a new parameter called SoftwareUpdateO365Language.
Support for ARM 64 Operating System Deployment
Enhancement in Deploying Software Packages with Dynamic Variables
Upgrade to CM 2403 is blocked if CMG V1 is running as a cloud service (classic)
SCCM 2403 Release Date
Microsoft released SCCM 2403 on April 22, 2023. The 2403 version of SCCM is a baseline version. When installing a new site, you can download and use the 2403 baseline version, but remember that the baseline media will be available only after global availability.
Important: You cannot upgrade to SCCM 2403 if you are running older versions of ConfigMgr, such as SCCM 2012 or SCCM 2012 R2. If you are still running an older version of Configuration Manager, you must upgrade to the current branch first. Please refer to the SCCM in-place upgrade paths for more information.
https://lumigo.fr/lumiweb-forum-webmarketing/Thread-Distance-from-Delhi-to-Tibet
https://betforum.org/threads/singbet-review.234/
https://betforum.org/threads/arbitrage-betting.2972/
https://betforum.org/threads/sbobet-esport.3382/
https://bitmemetalk.net/index.php?topic=880893.0
General Availability of Configuration Manager 2403
Configuration Manager version 2403 Fast Ring is released. Currently, the update is not globally available for all customers to install. You can either wait until the update is released for everyone or run the Early Update Ring PowerShell script to get the ConfigMgr 2403 update.
When the update becomes generally available, you will not need to run any scripts because you can install it straight from the console.
Installing Previous Hotfixes Before Upgrading
There were plenty of hotfixes and rollups for ConfigMgr version 2309 and earlier versions, some of which also featured out-of-band hotfixes. Most administrators want to know if they should install all the existing hotfixes before updating to version 2403. The answer is ‘No.’ That’s because the new SCCM 2403 release will contain all previously issued hotfixes for Configuration Manager. So you can safely skip the old hotfixes and directly install the update.
https://bitmemetalk.net/index.php?topic=41696.0
https://bitmemetalk.net/index.php?topic=918851.new
https://bitmemetalk.net/index.php?topic=921556.0
http://forofjcruiser.com/viewtopic.php?f=1&t=57540
http://forofjcruiser.com/viewtopic.php?f=1&t=71357
The following hotfixes are already included with the 2403 version:
Configuration Manager 2309 Upgrade Guide
Configuration Manager 2309 Hotfix KB26129847
Hotfix Rollup KB25858444 for SCCM 2309
Windows ADK Support for version 2403
SCCM 2403 supports both the latest versions of the Windows 10 ADK and the Windows 11 ADK.
For Windows 10, you can install the Windows ADK for Windows 10 version 2004.
For Windows 11, you can install the Windows ADK for Windows 11 version 22H2.
If you have installed an older version of ADK on your SCCM server and are upgrading your Windows 10 to newer versions like Windows 10 20H2 or Windows 10 21H2, you must upgrade your ADK to the latest version available. Use the following guide to update ADK on SCCM server.
Config Manager 2403 Upgrade Checklist and Prerequisites
Before you upgrade to Config Manager version 2403, please go through the upgrade checklist and prerequisites.
http://forofjcruiser.com/viewtopic.php?f=1&t=87866
http://forofjcruiser.com/viewtopic.php?f=1&t=81881
https://rostovbike.ru/thread-4420.html
http://airsoftvalcoisin.free.fr/forum/viewtopic.php?f=2&t=34396
http://airsoftvalcoisin.free.fr/forum/viewtopic.php?f=2&t=22439
Starting in version 2403, the Configuration Manager upgrade will be blocked if you are running Windows Server 2012/2012 R2. To resolve this, upgrade the servers to a higher version, such as 2016, 2019, or 2022.
Configuration Manager 2309 and 2403 will require the latest version of the Microsoft ODBC driver for SQL Server. The ODBC driver for SQL Server needs to be installed on site servers before upgrading to the 2403 version. Microsoft recommends installing SNAC 11.0 with the latest ODBC driver, version 18.1.0 or later. This prerequisite is required when you create a new site or update an existing one and for all remote roles.
To apply this update to your sites, ensure you have installed SCCM version 2211 or later.
If you’re running a multi-tier hierarchy, start at the top-level site in the hierarchy. Perform the CAS upgrade first, then begin the upgrade of each child site. Complete the upgrade of each site before you begin to upgrade the next site.
http://airsoftvalcoisin.free.fr/forum/viewtopic.php?f=2&t=15469
http://airsoftvalcoisin.free.fr/forum/viewtopic.php?f=2&t=45749
http://airsoftvalcoisin.free.fr/forum/viewtopic.php?f=2&t=42523
Ensure that you are running a supported Operating System for SCCM.
Starting with the current branch 2303, SQL Server 2022 support has been added. SCCM 2403 will support the following versions of SQL: SQL 2017, SQL 2019, and SQL 2022.
If you’re running a SCCM version older than version 1910, check the SCCM In-place upgrade paths for proper upgrade paths.
The Configuration Manager should have an online service connection point before you upgrade to 2403.
You must remove the enrollment point, enrollment point proxy, and device management point roles before upgrading to version 2403.
Install Windows Updates on SCCM Server
Before you upgrade your SCCM server to version 2403, we recommend installing the latest Windows updates on the server. This ensures that your server is patched with the most recent updates and prevents any errors during the upgrade.
https://stakeforum.com/threads/2a7x3-resume.20644/
http://jylt.jingyunys.top/forum.php?mod=viewthread&tid=13484
http://jylt.jingyunys.top/forum.php?mod=viewthread&tid=14382&extra=
http://jylt.jingyunys.top/forum.php?mod=viewthread&tid=16076&extra=
https://tucmas.fi/phpBB/viewtopic.php?p=212936
Most ConfigMgr administrators patch the Windows servers regularly using the ADR. However, if there is any pending restart, make sure you reboot the server, as this may halt the upgrade. For more details, refer to the article on Fix Configuration Manager Pending System Restart error.
On the Configuration Manager server, click Settings > Update and Security. Install any pending updates on the server and reboot the server.
Installing the latest Microsoft ODBC Driver for SQL Server
Configuration Manager current branch versions 2309 and 2403 have an error prerequisite rule that checks for Microsoft ODBC Driver 18 for SQL setup. Before performing the upgrade on any site system servers, this needs to be manually installed. The installation of Microsoft ODBC Driver 18 does not require a restart.
https://tucmas.fi/phpBB/viewtopic.php?t=102196
https://tucmas.fi/phpBB/viewtopic.php?t=87244
https://tucmas.fi/phpBB/viewtopic.php?t=95216
https://tucmas.fi/phpBB/viewtopic.php?t=104512
https://winda.top/viewtopic.php?f=17&t=151400
Use the following download link to get the most recent version of the ODBC driver for SQL Server. Refer to the following to install or upgrade the ODBC driver on SCCM Server.
Run EnableEarlyUpdateRing 2403 PowerShell script
To get the SCCM 2403 update in the console, you must download and install the version 2403 opt-in script on the SCCM server. Extract the contents to a folder, and you will find a PowerShell script named enableearlyupdatering2403.ps1.
Follow these steps to run enableearlyupdatering2403.ps1:
First, close the Configuration Manager console.
On your SCCM server, launch PowerShell as an administrator.
Change the path to the script location and run the enableearlyupdatering2403.ps1 PowerShell script.
Enter the site server name (top-level site server name or IP address), and the script will download the SCCM 2403 update in the SCCM console.
https://winda.top/viewtopic.php?f=17&t=410808
https://winda.top/viewtopic.php?f=17&t=438297
https://winda.top/viewtopic.php?f=17&t=431507
https://winda.top/viewtopic.php?f=17&t=422768
http://ls.lszpw.vip/forum.php?mod=viewthread&tid=100669
After running the above PowerShell script, the update download begins. The SCCM server will download the update 2403 package from Azure servers, and the download progress can be viewed in dmpdownloader.log.
Wait for ConfigMgr update 2403 to download and extract all the files needed for the upgrade. The update state changes from ‘Downloading‘ to ‘Ready to Install‘ in the console.
SCCM 2403 Update Stuck Downloading in Console
On several setups, we have noticed that the SCCM 2403 update gets stuck in the downloading state. Hence, we have published a dedicated article to help you out: https://www.prajwaldesai.com/fix-sccm-update-stuck-downloading-state/.
Listed below are some common reasons why the upgrade prerequisite check fails and the solution to those errors and warnings.
http://ls.lszpw.vip/forum.php?mod=viewthread&tid=118312
http://ls.lszpw.vip/forum.php?mod=viewthread&tid=117909
http://ls.lszpw.vip/forum.php?mod=viewthread&tid=61968
http://ls.lszpw.vip/forum.php?mod=viewthread&tid=29816
https://shufaii.com/thread-257530-1-1.html
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
Enable site system roles for HTTPS or SCCM Enhanced HTTP: Solution
Recommended version of the Microsoft .NET Framework. Warning: The Configuration Manager 2309/2403 update requires at least DotNet version 4.6.2 but recommends the latest version 4.8: Solution
ConfigMgr Database Upgrade Error 0x87d20b15: Solution
Co-Mgmt slider is not pointed to Intune: Solution
SQL client prerequisites are missing for Config Manager setup: Solution
Run SCCM 2403 Prerequisite Check
Before you install the SCCM 2403 update, you must always run the prerequisite check. The prerequisite check will determine if update 2403 can be installed without any issues.
https://shufaii.com/thread-194584-1-1.html
https://shufaii.com/thread-191533-1-1.html
https://shufaii.com/thread-182995-1-1.html
https://shufaii.com/thread-192131-1-1.html
https://www.5ijzj.com/thread-22484-1-1.html
Note: You can run the prerequisite check only when update 2403 shows the status as Ready to Install. If the update is stuck or is not downloading, please use the solutions described above.
Perform the following steps to initiate the SCCM 2403 prerequisite check on the server:
Launch the Configuration Manager console.
Navigate to Administration > Overview > Updates and Servicing.
Right-click Configuration Manager 2403 Update and select Run Prerequisite Check.
After you run a prerequisite check for an update, it takes a while to actually begin the prerequisite check process. You can monitor all the prerequisite checks in the monitoring node of the console. In addition, you can also review the ConfigMgrPreReq.log to know the status of the prerequisite check. Take a look at a list of all the SCCM log files useful for monitoring the upgrades.
On the Features tab, check the boxes for the new 2403 features you want to enable during the upgrade. You can enable these new features after installing the update from Administration > Updates and Servicing > Features. Click on Next to continue.
For Client Update Options, select the desired option for updating the clients in your hierarchy. There are two client update options available while installing the update.
Upgrade without validating: This option allows updating only client members of a specific collection.
Validate in pre-production collection: With this option, you can validate the client update on members of the pre-production collection while keeping your production client package intact.
https://www.5ijzj.com/thread-32072-1-1.html
https://www.5ijzj.com/thread-37514-1-1.html
https://www.5ijzj.com/thread-35942-1-1.html
https://www.5ijzj.com/thread-18003-1-1.html
Please refer to the SCCM client upgrade options to understand the options available for upgrading the client agents automatically to the latest version. Select the desired client agent update option and click Next to continue.
If you have already enabled SCCM Cloud Attach (Tenant Attach) with Intune, you will see an option to upload the Microsoft Defender for Endpoint Data for reporting on devices uploaded to Intune. If your SCCM setup does not include tenant attach, you can skip this step and proceed to the next step.
In the Summary window, you see a summary of the settings that you have configured for installing the SCCM 2403 update. Review them and click Next.
Comments
Post a Comment