Warning updating the currently checked out branch
Before installing, check if your site is ready for the update: We’ve done numerous SCCM upgrades.Some installation start a couple of minutes after you complete the wizard but we’ve seen some installation starts after a 10 minutes delay.
There’s actually no officially documented methods by Microsoft to fix that. As a previous Cumulative update, the console has an auto-update feature. Based in Montreal, Canada, Senior Microsoft SCCM Consultant, 5 times Enterprise Mobility MVP. His specialization is designing, deploying and configuring SCCM, mass deployment of Windows operating systems, Office 365 and Intunes deployments.Keeping your infrastructure up to date is essential.You can benefit from the new features and fixes issues, which some of them can be related to your SCCM.At console opening, if you are not running the latest version, you will receive a warning and the update will start automatically.build number of the console. If the console upgrade was successful, the build number will be X and the version is now Version 1802. Read about the support end date of the prior version of the following Technet article.
Before installing, make sure that you are running a supported Operating System and SQL version.
Beginning with 1802, this is a new version nomenclature for the console.
The console will no longer include the main build number (8634). For example, in Configuration Manager version 1802 the initial site version is 5.0.8634.1000, and the initial console version is 5.1802.1082.1700.
Until all sites in your hierarchy are upgraded, your hierarchy operates in a mixed version mode.
Before applying this update, we strongly recommend that you go through the upgrade checklist provided on Technet.
You will be able to install 1802 if you are running SCCM 2012, this new version is a new baseline version.