Scribd
Upload
52 views7 pages

SCCM Upgrades

Uploaded by

fareed ahmed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
52 views7 pages

SCCM Upgrades

Uploaded by

fareed ahmed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

SCCM CB: Why to upgrade (Deep Dive)

Current CB life cycle...

SCCM CB: New Features

Higher version of SCCM CB offers features badly required... Look for the new features in the latest
version. Below is the list of few major features in some of the latest releases of SCCM
SCCM CB support lifecycle is divided into two categories called “Security and Critical
Updates servicing phase“ and "Security Updates (Only) servicing phase"

There are two kinds of support for new SCCM/ConfigMgr Current Branch versions. First, one is
“Security and Critical Updates servicing phase” and the second one is “Security Updates (Only)
servicing phase”.

The latest current branch version is always in the Security and Critical Updates servicing
phase. This support statement means that if you encounter a code defect that warrants a
critical update, you must have the latest current branch version installed in order to receive
a fix. All other supported current branch versions are eligible to receive only security
updates.

All support ends after the 18-month lifecycle has expired for a current branch
version.
In-Pace upgrade: In-console vs Baseline
Question: How does upgrade path works?

Current Branch Vs Technical Preview

Question: What is the difference between CB and TP


A technical preview installation never has the option to upgrade to a current branch installation

The technical preview is licensed for use only in a lab environment. Microsoft may not
provide support services and certain features may not be available in technical previews.
Additionally, technical preview software may have reduced or different security, privacy,
accessibility, availability, and reliability standards relative to commercially provided
software.

 Each install is active for 90 days before it becomes inactive.


 English is the only language supported.

The following features are not supported with the technical preview branch:

 Migration to or from this preview branch.


 Upgrade to this preview branch.
 Site recovery from the cd.latest folder.
 The site supports up to 10 clients.
 It only supports a standalone primary site.

Microsoft supports each technical preview version up until three successive versions are available

When you install an update to the technical preview, you update your preview installation to
that new technical preview version. A technical preview installation never has the option to
upgrade to a current branch installation.

SCCM CB: Upgrade planning


A site update can fail because of existing operational problems. Before you update a site,
resolve all operational issues for the following systems:

 The site server, SQL DB health checkup, Disk-space, Pending reboots

https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/configs/support-
for-sql-server-versions
Starting with version 1702, Configuration Manager does not support SQL Server 2008 R2.

 The site database server health checkup


Setup.exe /testdbupgrade CM_TST_backup

https://msendpointmgr.com/2013/09/09/perform-a-test-upgrade-of-the-database-
before-configmgr-2012-r2-installation/

 Site Server Full VM backup & SQL backup of DB: Discuss

 Adequate Disk space: Discuss ( moving sources dir to another location)

 ADK & DOTNOT (min 3.5 or higher) versions: Discuss

 Pending or stuck reboot: reboot the server once. If it keeps saying to reboot again,
reboot it a couple of times. Normally it gets resolved by rebooting a couple of times

 All SCCM server components are green. If there are errors and warnings, please fix
them

 Backup relevant SCCM registry key hives

How to Upgrade

 Start the installation from your central administration site (CAS) or from your stand-
alone primary site.
 Child primary sites install the update automatically after the CAS finishes the
installation of the update.
 Manually update each secondary site from within the Configuration Manager console
after the primary parent site finishes the update installation. Automatic update of
secondary site servers is not supported.
 After a site server updates, all affected site system roles automatically update
Upgrade Errors

 DB errors: don’t modify the DB, open a case with CSS


 Download Errors: CMUpdateReset.exe

https://stevenbart.com/en/2019/01/15/update-reset-tool/

 Access denied: Most AV issues


 site_master_key_is_not_found: Re-download the setup files
cmupdate.log, dmpdownloader.log, ConfigmgrSetup.log, ConfimgrPrereq.log

Post Upgrade Considerations

 Site Server components health


 Console update
 Boot image update if ADK was upgraded at the time of upgrade
 SCCM OSD and software distribution are running ok
 SCCM client upgrade

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy