Rollback SCCM Version from 1906 to 1802
Question
Good Day,
I am planning to upgrade sccm version from 1802 to 1906 version, can you help me what is process to rollback SCCM version if something goes wrong.
Thanks
Raj
Rajesh Kumar 
Leave an answer
Sorry, you do not have permission to answer to this question .
Answers ( 4 )
I am trying to upgrade sccm server but it looks stuck.
cmupdate.log :- Waiting for changes to the “C:\Program Files\Microsoft Configuration Manager\inboxes\cmupdate.box” directories, updates will be polled in 600 seconds…
Status :- [Completed with warning]:Monitoring database replication initialization. Check cmupdate.log and rcmctrl.log for details.
The asynchronous command finished with return message: [A .NET Framework error occurred during execution of user-defined routine or aggregate “spDRSActivation”: ~~Microsoft.ConfigurationManager.DataReplicationService.ServiceException: Exception has been thrown by the target of an invocation. —> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.Data.SqlClient.SqlException: The conversation handle “032AD4E4-C6A0-EA11-910D-005056BB6EC5” is not found.~~System.Data.SqlClient.SqlException: ~~ at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)~~ at System.Data.SqlClient.SqlInternalConnectionSmi.EventSink.DispatchMessages(Boolean ignoreNonFatalMessages)~~ at System.Data.SqlClient.SqlCommand.RunExecuteNonQuerySmi(Boolean sendToPipe)~~ at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)~~ at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()~~ at Microsoft.ConfigurationManager.DataReplicationService.Conversation.EndConversation(SqlConnection connection, SqlTransaction transaction)~~ at Microsoft.ConfigurationManager.DataReplicationService.MessageHandlerService.ProcessErrorMessage(Message msgReceived, SqlConnection connection, SqlTransaction transaction, Int32 logLevel, SqlCommand command)~~System.Reflection.TargetInvocationException: ~~ at Microsoft.ConfigurationManager.DataReplicationService.Service.Run(SqlConnection connection, SqlTransaction transaction, Int32 logLevel, SqlCommand command, Int64 poisonMessageSequenceNumber)~~Microsoft.ConfigurationManager.DataReplicationService.ServiceException: ~~ at Microsoft.ConfigurationManager.DataReplicationService.Service.Run(SqlConnection connection, SqlTransaction transaction, Int32 logLevel, SqlCommand command, Int64 poisonMessageSequenceNumber)~~ at Microsoft.ConfigurationManager.DataReplicationService.MessageHandlerSe…].
Once you upgrade, you need to commit to it and if there’s an issue, focus on fixing them. Don’t roll back as it’ll just create a bigger mess.
Rollback seems to be very very rare use case …. have not come across so far.
Technically the best option for rollback is to have healthy SQL and site backup and restore.
I have not seen any with any of the SCCM CB upgrades which made someone to recover the entire site. Most of the issues during the upgrade is handled via support tickets with Microsoft. More details https://howtomanagedevices.com/sccm/1151/sccm-1906-upgrade-walkthrough/
The only supported rollback option is to take the SCCM backup (+ SQL DB) and restore it from the backup.
More details about SCCM backup and recovery is explained https://www.anoopcnair.com/sccm-backup-restore-video-guides-in-details/
Also, pls note that there are the unsupported way which most of the organization which I work follow and it works just fine in most of the scenarios is
– Take a snapshot of the entire SCCM + SQL server (Site servers) and restore or recover to the previous state before the upgrade.