SCCM upgrade Change request.
Question
Hi All ,
We are planning to upgrade SCCM from 1910 to 2002 .
To raise a Change in ticketing tool for SCCM upgrade can anyone share the template ?
Thanks in Advance
Ketan Kamble 
Leave an answer
Sorry, you do not have permission to answer to this question .
Answer ( 1 )
Hello, It totally depends on environment, you can try to use below template.
1. Environment (Live,QA,Test):
Prod – SCCM Environment
2. Operations/Project (Project Name):
Operations
3. Description of Change
This change is to upgrade current SCCM environment from version 1906 to 1910.
The change will be implemented by performing the upgrade from top to bottom SCCM Infrastructure i.e. First CAS (central Administration Site) then Primary followed by secondary Sites.
SCCM Top to down Hierarchy-(mention your server names from top to down)
Implementation Team:Team name who will be implementing change
Implementation TimeLine:
This change will be implemented following Top to down approach as recommended by Microsoft.
(mention the timeline at what time you will be upgrading which depending on your Infrastructure)
Implementation Plan:
All below mentioned steps have been studied in detailed from the articles released by Microsoft for SCCM Upgrade procedure:
1. Taking Full Backup of Site Servers prior to upgrade.
2. Taking Full Backup of Databases SQL Database and checking for scheduled backup for Secondary Sites.
3. Taking Application Level backup of CAS and Primary Site prior to upgrade.
4. Checking all prerequisites required for upgrade, disabling necessary maintenance tasks required prior to upgrade.
5. Upgrading SCCM environment at Top of the hierarchy.
6. Post upgradation of CAS Site, primary sites will get automatically upgraded.
7. Manual Upgradation of all four secondary sites needs to be done.
8. Checking SCCM Console Version post Upgrade i.e. 5.1910.1067.2100.
9. Checking All Site and Component Status, Database replications between SCCM Site Servers.
10. Testing SCCM Client upgrade on few machines.
11. Testing for distributing package on SCCM DP’s.
12. Enabling Site maintenance tasks disabled in step 4.
4. Justification for Change
SCCM Current branch 1910 version was released on ‘xxxxxxxxxx’ and we need to upgrade SCCM infrastructure to get continuous support from Microsoft.
There are also new features added to version 1910 which will be helpful for SCCM Administrator to perform day to day operations. Few important features which are available in new version:
1. Product Name change from SCCM to MECM – Starting 1910 onwards System Center’s current branch new name will be Microsoft Endpoint Configuration Manager (MECM).
2. Bitlocker Management SCCM MBAM – Now MBAM is part of the SCCM 1910 production version. MBAM will be helpful for Bitlocker management.
3. Deploy Microsoft Edge Browser – Application for MS Edge Browser can be deployed on MECM clients.
4. Microsoft Connected Cache Options – Microsoft Connected Cache is designed for cloud era which helps to cache the required content on cloud DP’s. It is helpful in optimising network bandwidth.
5. Application Groups – User Deployment – With the latest version of MECM we can create a group of applications and send that to a user or device collection as a single deployment. We can also perform the sequencing of the apps in the group so that the SCCM client installs them in a specific order.
6. Copy Paste Task Sequence Condition – Now condition of one task can be copied and paste in another task.
7. New Right Click Option Client Diagnostics – 1910 version of SCCM introduced a new device action called Client Diagnostics. We can use this option to enable, disable verbose logging on target machine or group.
8. Teams Chat Option MECM 1910 Console Connections – It is useful when console is being operated other than Site server. We can connect directly from console to connected console admin.
9. Custom Compliance Policies – Need to explore once upgraded, as per article If organization is having a special requirement to check a special condition on the device before providing access to corp resources then custom policies baseline can be created and deployed for assessment.
10. Additional options for third-party update catalogues –Starting MECM 1910 now we can create sync schedule for third party update catalogue independently.
5. Adverse Impact & Risk of the Change
Since there is no test environment this activity needs to be performed in live production, if the upgrade process fails there is an impact on the SCCM services like software deployment, patching and inventory etc for all machines. Server Backups and Database backup will be taken to be able to restore the services in case of any issues.
If we do not upgrade SCCM then in sometime Microsoft will stop supporting our current version as per Microsoft Servicing Support Plan.
6. Testing & Results:
There is no test environment available for SCCM and same has been highlighted to customer, we will take all precaution steps prior to upgrade like backing up Servers, backing up SQL database, Application level backup to avoid any issues.
Please note similar upgrade was performed for SCCM version upgrade from (mention any previous similar change for SCCM Upgrade)
7. Roll Back Plan:
All required backup will be taken prior to upgrade so that if anything goes wrong it can be restored by opting either of the 2 options as given below:.
.
A) Restore SCCM referring the latest application backup following below steps.
1) SCCM admin has to Logon to SCCM server and run the SCCM installer setup.
2) Choose restore from application level backup.
3) Navigate through the installation wizard and wait for it to complete.
B) Restore SCCM by Restoring server with server & Database level backup
1) DCH Backup team can restore the servers with latest backup.
2) Database admin will restore databases with latest DB backup.
3) SCCM team to verify application functionality
Rollback Implementation Team:mention the rollback/recovery team
8. Service downtime window (dd/mm/yy hh:mm UK Time):
SCCM console & application services will not be available during upgrade process. Planned Downtime window will be between xxxxxxxxxxx.