1,779 total views, 3 views today
SCCM 2010 is now available universally to everyone without having to opt-in.
Vacation 2nd day is perfect to blog about SCCM 2010 installation guide.
I am not going to reiterate more about the features released in SCCM 2010 as I am going to blog them separately.
SCCM 2010 is the third release this year under the new branding Microsoft Endpoint Configuration Manager
Few Things to be remembered before you opt for this Upgrade
- You must have 1910 or later installed.
- Check Out Supported Operating System
- Check out the Supported SQL version.
- Check out the Database Compatability level, using SQL query: SELECT name, compatibility_level FROM sys.databases
|SQL Server version||Supported compatibility levels||Recommended level|
|SQL Server 2019||150, 140, 130, 120, 110||150|
|SQL Server 2017||140, 130, 120, 110||140|
|SQL Server 2016||130, 120, 110||130|
|SQL Server 2014||120, 110||110|
This Blog is broadly classified into 3 categories:
SCCM SITE Backup
Before going with the actual upgrade, one should follow a few more steps so that in case if something goes wrong, it can be reverted.
Before I start with the upgrade make sure that I have the latest SMS Site Backup. To do that I shall start the “SMS_SITE_BACKUP” service on CAS (if you have) or else Primary Server.
You can check smsbkup.log to confirm if the backup completed successfully.
SCCM Reports Backup
I do manage many customize reports, so I intend to take a backup before I process to actual upgrade. Here we are using Powershell Script, Please feel free to test it out.
Also, find the link below and make sure to download and rename it to .ps1 before using, Script Name SCCMReports_Export.You need to provide the report server name and folder path where you want to export the data as shown below.
- Stop Maintenance Tasks
- Make sure that there is no Maintenance task running during the upgrade process, hence disabling them.
- Similarly, can take a backup of SCCM DB\SUS DB\Report server database backup using SQL Management studio.
Let’s begin with the pre-requisites check, but make sure you execute this on the top infra server in the hierarchy. If you have CAS then do start with it, or begin with the Primary server in case of no CAS.
Upgrade package content is replicated first across the hierarchy in order to run the pre-requisites. Navigate to \Monitoring\Overview\Updates and Servicing Status to check the Pre-Req status.
On Successful Completion of Prerequisites, you are good to proceed with Upgrade
Next Phase i.e Upgrade to be released tomorrow.
Let’s end this blog with a quote
Being wrong is not a bad thing like they teach you in school. It is an opportunity to learn something. There are no mistakes, only lessons. Growth is a process of trial and error. 🧠