0% found this document useful (0 votes)
18 views3 pages

SCCM - MECM Upgrade - General Steps

This document outlines the general steps for upgrading an existing SCCM/MECM infrastructure. It includes ensuring backups are available, putting systems in maintenance mode, installing prerequisite software like the WADK, running the upgrade, testing functionality, and optionally upgrading additional third party tools. The process involves disabling services, backing up files, running prerequisites checks, installing updates, enabling services, and testing on client systems.

Uploaded by

piyaltaru.dutta
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
0% found this document useful (0 votes)
18 views3 pages

SCCM - MECM Upgrade - General Steps

This document outlines the general steps for upgrading an existing SCCM/MECM infrastructure. It includes ensuring backups are available, putting systems in maintenance mode, installing prerequisite software like the WADK, running the upgrade, testing functionality, and optionally upgrading additional third party tools. The process involves disabling services, backing up files, running prerequisites checks, installing updates, enabling services, and testing on client systems.

Uploaded by

piyaltaru.dutta
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/ 3

SCCM / MECM upgrade: general steps

For duration of upgrade, ensure that SCOM is set to maintenance mode for CAS and Primaries.

Copy software (MECM, Right-Click Tools, 1E products, etc.) to the CAS and Primaries on D:\Install

Quick steps

1. Check to make sure we have good SQL backup


 \\xspw50c383f\sqlbackup\pp0
 \\xspw50c383f\sqlbackup\pp1
 \\xspw50c378t\sqlbackup\pp2
 \\xspw50c379a\sqlbackup\pp3

2. Ensure no SCCM systems are set to patch/reboot during SCCM upgrade


a. This got me once when one of the primaries got patched/rebooted in middle of the
upgrade.

3. Disable SCCM maintenance tasks


a. Do we need to turn off SCOM alerting or put PREPROD in maintenance mode so we don’t
get bunch of alerts during upgrade?
b. Disable-CMSiteMaintenanceTasks.ps1 can be used to disable maint tasks

4. Stop/Disable SQL Server Agent (MSSQLSERVER) service


a. XSNW10W148A (PP0 SQL)
b. XSNW10W149F (PP1 SQL)
c. XSNW10W247A (PP2 SQL)
d. XSPW10T894F (PP3 SQL)

 Do we need to tell anyone from SQL team about this in case they are monitoring?

5. Backup D:\SCCMServer\inboxes\clifiles.src\hinv\configuration.mof
6. Run Prereq check from PP0 from SCCM console
a. Will copy content source down to all primaries

7. Remove WADK and WADK PE version 10.1.18362.1


8. Install WADK and WADK PE version 10.1.19041.1
9. Reboot CAS/SQL
10. Reboot Primary/SQL
11. Kick off SCCM install 2002
12. Wait until links are green before kicking off install of hotfix below -- let it cook!!
a. Configuration Manager 2002 Hotfix (KB4567007)
i. Resolves issues with PXE and task sequences taking long time to resolve
dependencies.

13. Compare backed up configuration.mof with configuration.mof in D:\SCCMServer\inboxes\


clifiles.src\hinv\

14. XSPW11B805K install SCCM 2002 Console


a. Install Right Click Tools from D:\Install\RightClickTools
b. Update SCCM console shortcuts for PreProd

15. Reach out to Workstation team to install 1E products


a. PP0, PP1, PP2, PP3
i. Install 1E products on XSPW11B805K

16. Reenable SCCM maint tasks


a. Enable-CMSiteMaintenanceTasks.ps1 can be used to enable maint tasks

17. Re-enable SQL Server Agent (MSSQLSERVER) service

18. Reach out to Workstation team for provision testing


a. Win10 (PREPROD/PROD)
i. Workstation team will need to update their boot images to inject the new WADK
2004
b. Win7 (PROD)
i. Workstation team will need to update their boot images to inject the new WADK
2004

19. Reach out to Wintel team for server testing (PROD)


a. Wintel team will need to update their boot images to inject the new WADK 2004

20. SCCM team to perform patch testing (PROD)


Optional: Upgrade of 1E products (after SCCM / MECM upgrade)

Note that SmartScreen and SEP should be disabled for before performing these steps. Once done,
enable SmartScreen and SEP again.

SmartScreen: Disable in Control Panel > Action Center > Security > Windows SmartScreen > Change
Settings, select “Don’t do anything (turn off Windows SmartScreen)”. Enable again by selecting “Get
Administrator approval before running an unrecognized app from the Internet (recommended)”.

SEP: To disable: Start Menu > Run, type smc -stop. To enable: Start Menu > Run, type smc -
start.

Download relevant 1E products from 1E – Workstation team will specify which products to download.
Products and hotfixes are zipped. Unzip to D:\Install on the CAS and Primaries, plus the Terminal
Servers.

Typical products include:

1E BIOS to UEFI
1E Task Sequence Tools
1E Nomad Branch Admin UI Extensions
1E Nomad Branch Tools

Perform upgrade from D:\Install on each server (upgrade software components first (in any order), only
then install any hotfixes).

In case no 1E product needs to be updated, the file osdinjection.xml needs to be edited to include 1E
entries, as this file is overwritten by the SCCM / MECM upgrade. This can be done by repairing the
Nomad installation. The Workstation team can assist.

Note Registry keys for 1E products are under HKLM\SOFTWARE\Wow6432Node\1E

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