SCCM Reboot Task for Collection of Devices via Fast Channel Push Notification ConfigMgr MEMCM

SCCM Reboot Task for Collection of Devices via Fast Channel Push Notification ConfigMgr MEMCM? SCCM CB 1708 version added a new feature called “Reboot” action to the fast channel push client notification. SCCM CB preview version 1708 has been released. I have the pleasure of upgrading my lab environment to the SCCM CB 1708 preview version. 

We can use the SCCM console to identify client devices that are pending reboot. Once identified, the devices then use a client notification action to restart them. This video post will see the Video Experience of the SCCM Reboot Task for the Collection of Devices via Fast Channel Push Notification. YouTube video tutorial here.

How to Restart computers from SCCM console?

You can restart the computers in a device collection using SCCM CB 1708 previews version onwards. First step is to identify the computers which are in “pending restart” state in a device collection.

How to find out the restart/reboot pending devices?

SCCM Reboot Task for Collection of DevicesSCCM Reboot Task for Collection of Devices via Fast Channel Push Notification ConfigMgr MEMCM
SCCM Reboot Task for Collection of Devices via Fast Channel Push Notification ConfigMgr MEMCM

Once restart pending devices are identified then, right click on collection or device to initiate the REBOOT action. This reboot action is initiated via FAST client notification channel. We don’t have a deploy a reboot script to machines. Most importantly this “REBOOT” action is triggered via PUSH channel of SCCM CB client notification.

SCCM Reboot Task for Collection of Devices SCCM Reboot Task for Collection of Devices via Fast Channel Push Notification ConfigMgr MEMCM
SCCM Reboot Task for Collection of Devices via Fast Channel Push Notification ConfigMgr MEMCM

Restart Action Failed on a client Device?

I initiated a reboot action for Pending reboot machine and it didn’t work. Why? I checked the log files and ConfigMgr applet in Windows 10 machine. I realised that I have upgraded the SCCM CB server version (5.00.8549.1000) to 1708. We didn’t upgrade Windows 10 machine’s SCCM client version (5.00.8542.1000) to 1708.

CcmNotificationAgent.log is the best log to check for troubleshooting of fast channel push notification tasks.

Monitoring workspace – “Client Operations” node in the SCCM console is the place where you can check the status of REBOOT action. Operation name for REBOOT action is Task 17 ! But, I’m sure this will get changed in the production version of the release. The error logging can be improved because the following was the error – “Failed to execute task, error 0”.

CcmNotificationAgent LOG with Errors

<![LOG[NetworkInfo: IPAddress 20.20.20.23,fe80::b09e:95a3:172a:4212]LOG]!><time="21:07:18.726-330" date="08-26-2017" component="BgbAgent" context="" type="1" thread="6212" file="bgbconnector.cpp:124">
<![LOG[NetworkInfo: IPSubnet 255.0.0.0,64]LOG]!><time="21:07:18.726-330" date="08-26-2017" component="BgbAgent" context="" type="1" thread="6212" file="bgbconnector.cpp:147">
<![LOG[NetworkInfo: AccessMP SCCMTP1.Intune.com]LOG]!><time="21:07:18.757-330" date="08-26-2017" component="BgbAgent" context="" type="1" thread="6212" file="bgbconnector.cpp:155">
<![LOG[NetworkInfo: IsClientOnInternet 0]LOG]!><time="21:07:18.757-330" date="08-26-2017" component="BgbAgent" context="" type="1" thread="6212" file="bgbconnector.cpp:159">
<![LOG[Update the timeout to 900 second(s)]LOG]!><time="21:07:18.757-330" date="08-26-2017" component="BgbAgent" context="" type="1" thread="6212" file="bgbtcpclient.cpp:916">
<![LOG[Receive signin confirmation message from server, client is signed in.]LOG]!><time="21:07:18.851-330" date="08-26-2017" component="BgbAgent" context="" type="1" thread="6212" file="bgbconnector.cpp:221">
<![LOG[Receive task from server with pushid=1002, taskid=1007, taskguid=5AFF6AEA-67D5-4124-B04F-162FDB0E314E, tasktype=17 and taskParam=]LOG]!><time="21:13:36.115-330" date="08-26-2017" component="BgbAgent" context="" type="1" thread="6212" file="bgbconnector.cpp:312">
<![LOG[Failed to find action instance for task type 17]LOG]!><time="21:13:36.115-330" date="08-26-2017" component="BgbAgent" context="" type="3" thread="6212" file="bgbcontroller.cpp:682">
<![LOG[Failed to execute task, error 0]LOG]!><time="21:13:36.115-330" date="08-26-2017" component="BgbAgent" context="" type="3" thread="6212" file="bgbcontroller.cpp:646">

Results of Successful REBOOT PUSH Task

Upgraded the client version to 5.00.8549.1000 and reinitiated the REBOOT Task by right clicking on a collection – Client Notification – Reboot. This action created a new task for the devices (pending reboot) in that collection through SCCM PUSH fast channel notification. What is the architecture flow of SCCM CB Fast channel push notification? I have explained fast channel architecture flow in the post here.

SCCM fast channel push client notification service will immediately notify the client about the task assigned. The client won’t get restarted immediately after receiving the task from notification server component. The SCCM client will check the policy settings for “Computer Restart”  and schedule the restart as per the policy.

By default the computer restart policy is 90 minutes and you can customise this policy from client settings tab. The reboot or restart notification is very well integrated with “Software Center” experience and this is the great advantage of this feature.

SCCM Reboot Task for Collection of Devices via Fast Channel Push Notification ConfigMgr MEMCM
SCCM Reboot Task for Collection of Devices via Fast Channel Push Notification ConfigMgr MEMCM

Resources :-

  • Update 1708 for Configuration Manager Technical Preview Branch – Available Now! – here
  • Capabilities in Technical Preview 1708 for System Center Configuration Manager – here
  • Video Guide to Troubleshoot SCCM CB Fast Channel Notification Issues – here

SCCM CB 1708 Preview Upgrade Video Guide New Features Configuration Manager ConfigMgr

SCCM CB 1708 Preview Upgrade Video Guide New Features Configuration Manager ConfigMgr. SCCM CB preview version 1708 has been released. I have the pleasure of upgrading my lab environment to the SCCM CB 1708 preview version. Upgrade to SCCM CB preview version 1708 will fail when you have an SCCM primary server in passive mode. 

It would help if you remembered that SCCM ConfigMgr CB technical preview version should not be deployed to a production environment. In this post, we will see SCCM CB 1708 Preview Upgrade Video Guide. YouTube video tutorial here.

What is the Importance of SCCM Preview Releases?

SCCM CB preview version is similar to Windows insiders program which helps SCCM admins to test the new features of SCCM CB. Before installing this version of the technical preview, you can go through the limitations of SCCM CB version here. We can’t install CAS version of SCCM CB with the preview version. The prerequisite for installing SCCM CB 1708 preview version is not changed.

SCCM CB 1708 Preview Upgrade Video Guide
SCCM CB 1708 Preview Upgrade Video Guide New Features Configuration Manager ConfigMgr

How to Download SCCM CB Preview Version

The upgrade process is explained in the video tutorial here. Have you installed an SCCM CB preview version? If not, you can download the latest baseline version of ConfigMgr SCCM CB Technical Preview from here. One particular version of SCCM preview has maximum validity only 3 months (90 days).

How to upgrade from SCCM CB 1707 to 1708 ?

The SCCM CB update and servicing process are same as before. Once the latest version of the preview is released then, the update will be available in SCCM console. The update will automatically get downloaded into your server. This behaviour depends on the Service connection point (SCP) mode. There are two modes for SCP, and those are ONLINE and OFFLINE.

The replication of new content to secondary servers is the next step of the upgrade process. Once replication is completed successfully, the update component will start the prerequisite checks on SCCM CB hierarchy. The prerequisite checks will run on all the site servers and site systems.

SCCM CB 1708 Preview Upgrade Video Guide SCCM CB 1708 Preview Upgrade Video Guide New Features Configuration Manager ConfigMgr
SCCM CB 1708 Preview Upgrade Video Guide New Features Configuration Manager ConfigMgr

Once prerequisite checks have been completed then, the update component will start the actual upgrade/installation process of SCCM CB 1708. After the upgrade process, the post installation or upgrade process will start. All these are explained in the video tutorial here.

New features of SCCM CB 1708 preview version

Create and run scripts with optional parameters is one of the newest feature added to SCCM CB 1708. This script deployment is done through the new fast channel of SCCM CB. No need to deploy script as a package or application rather you directly import the PowerShell script. This Script can be targeted to collection or devices without creating any deployment.

Supported scenarios of Run script option  Scenarios:- 
- Create and run PowerShell scripts on collections of devices from the Configuration Manager console
- Create and run PowerShell scripts with parameters to devices and collections from the Configuration Manager console
- Create and run PowerShell scripts with optional parameters to devices and collections from the Configuration Manager console

SCCM Infra Management insights is another option in SCCM CB 1708. This will give you valuable insights into the current state of your environment based on analysis of data in the site database. This will provide the details of EMPTY collections and applications without any deployments of your environment.

  • Following is the place you can view the management insights – \Administration\Overview\Management Insights.
  • Scenarios: Review a management insight to understand your environment better and take action based on the insight
SCCM CB 1708 Preview Upgrade Video Guide SCCM CB 1708 Preview Upgrade Video Guide New Features Configuration Manager ConfigMgr
SCCM CB 1708 Preview Upgrade Video Guide New Features Configuration Manager ConfigMgr

The two new features added to SCCM CB 1708 are initiate Restart computers from the admin console and pending restart column. The restart computer action is also performed through SCCM fast channel notification.

Monitoring workspace in SCCM CB 1708 console shows a different name to Restart computer action, and that is Operation Name #17.

SCCM CB 1708 Preview Upgrade Video Guide SCCM CB 1708 Preview Upgrade Video Guide New Features Configuration Manager ConfigMgr
SCCM CB 1708 Preview Upgrade Video Guide New Features Configuration Manager ConfigMgr

References:-

  • Update 1708 for Configuration Manager Technical Preview Branch – Available Now! – here
  • Capabilities in Technical Preview 1708 for System Center Configuration Manager – here
  • What is SCCM CB Management Insights – here

SCCM Configuration Manager Application Creation Deployment Installation | ConfigMgr

SCCM Configuration Manager Application Creation Deployment Installation | ConfigMgr? SCCM CB application creation is the next step after the installation of SCCM CB 1702 installation, SCCM CB AD discovery and client installation.

Latest Post How To Deploy Zoom Application Using SCCM | ConfigMgr HTMD Blog (anoopcnair.com).

I already covered in the previous posts “Step by Step Video Tutorial of SCCM CB 1702 Baseline version Installation” and “Video Tutorial How to Perform SCCM CB AD Discovery and Install Client“. SCCM CB application creation is the first step in this process.

The second step is SCCM CB Application Deployment, and the third step is the installation of the SCCM CB application on the clients. We will cover all the scenarios in this post. I have already documented all these steps in the video tutorial which has more details about SCCM CB application creation (upload), deployment, and installation.

Application deployment is one of the features many corporate organizations are using to cater their business requirements. In SCCM CB, we will have the option to create packages and deploy those SCCM packages. Yes, packages are required in the some of the scenarios.

Apart from that, the packages are used to deploy old school win32 apps which got migrated to the SCCM CB environment from SCCM 2003/2007/2012. I would recommend taking advantage of SCCM CB applications rather than still using standard packages.

How to create/Upload SCCM Application – SCCM Configuration Manager Application Creation Deployment Installation | ConfigMgr

SCCM Configuration Manager Application Creation Deployment Installation | ConfigMgr
SCCM Configuration Manager Application Creation Deployment Installation | ConfigMgr

SCCM CB application creation is the first step in this process. The application can be created based on several types of installation files. These installation files are ranged from win 32 MSI apps, EXE and then the wide range of mobile (MDM) apps.

The best-preferred installation type for Windows devices is MSI, and we are going to cover MSI app creation in this post. I have already shown in the video that how to create a shared folder to store the application source.

The first point we need to make sure that SCCM CB application source should be stored in an UNC path (\\ServerShare\Sources\).

If we don’t provide the UNC path as a source location for the MSI app source, you will get an error in the wizard as you can see in the video tutorial.

SCCM Configuration Manager Application Creation Deployment Installation | ConfigMgr 3

SCCM CB application creation process will create a metadata in the console, and it will create the related DB entries. Apart from this, this process will create a bundle of files which this MSI installation file required for the complete installation of the application.

This bundle of files will be delivered to SCCM content stores called DPs. The client will download (if in case the deployment setting is to download the content from DP) and install it. All this process is covered in the video, and we will cover it in the following sessions.

How to Deploy SCCM CB application and Content?

Once SCCM CB application is created, and the app reference is there in the console then, we can go ahead deploy the application content (the source files) to the content store servers (Distribution Points). The entire process is explained in the video tutorial above.

We can initiate a distribute content option to start the application source replication process to remote DPs. SCCM CB application content distribution is mandatory before we deploy the application to SCCM client devices or users.

Once the application content is distributed to the DPs then, we can deploy or schedule the application installation to the device collection or user collection. There are a couple of decisions you want to make before the start of the SCCM CB application deployment process.

First one is to decide whether we should deploy apps to Device collections? If we are deploying it to device collection then, all the users in that device will get the application, and there could be some license implications as well. The second option is to deploy the application to user collection.

From my perspective, this should be the default deployment practice if you don’t have any specific requirements to deploy apps to devices.

SCCM Configuration Manager Application Creation Deployment Installation | ConfigMgr 4
SCCM Configuration Manager Application Creation Deployment Installation | ConfigMgr

The other important point in SCCM CB application deployment is about the behavior of application installation. We have two option in the application installation behavior. SCCM Configuration Manager Application Creation Deployment Installation | ConfigMgr?

First one is to empower the user experience by making the SCCM app as AVAILABLE. In the available scenario, the application will be deployed to the user, and it will sit in the software center until the user initiates the installation from software center app.

The second option is to deploy the application as REQUIRED and in this scenario, the application will automatically install on the device without any user intervention.

How to Install Application on End User Device?

Once you deploy the application to the collection as mentioned in the video tutorial above, the SCCM client will check for the new policies at the next scheduled interval.

On the schedule, the SCCM client will download the application source download, and installation will automatically start on the Windows device as you can see in the video tutorial. The installation behavior setting is very important and depending up that behavior the actual app install will kick off.

SCCM Configuration Manager Application Creation Deployment Installation | ConfigMgr
SCCM Configuration Manager Application Creation Deployment Installation | ConfigMgr

How to Perform SCCM ConfigMgr CB Production upgrade to 1702 Video Tutorial Configuration Manager

How to Perform SCCM ConfigMgr CB Production upgrade to 1702 Video Tutorial Configuration Manager? Microsoft released a new version of SCCM/ConfigMgr CB 1702 here. If your SCCM infrastructure is running with an ONLINE “service connection” point and your SCCM CB version is 1602 (and later) then, you will receive the SCCM CB 1702 update in the console.

For SCCM CB infra with an online service connection point, the SCCM CB 1702 update will automatically appear in the console once Microsoft release this for “slow ring“. Now, Microsoft released SCCM CB 1702 updates only for the “fast ring.” I have upgraded the standalone SCCM CB 1610 primary site to SCCM CB 1702. My experience of this upgrade was very smooth and robust.

I didn’t face any hiccups after downloading the SCCM CB 1702 source files automatically to the primary server. The above video will give a step-by-step walkthrough of the SCCM/ConfigMgr CB 1610 and 1702 upgrade process! More details about SCCM 1702 release note here.

Feature Comparison between SCCM CB production version 1610 and 1702 –

Video – Here

Don’t upgrade to SCCM/ConfigMgr CB 1702 version if your primary servers/CAS is running on Windows 2008 R2 server. The minimum OS requirement for SCCM CB 1702 upgrade is Windows Server 2012 and Later. More details here.

You need to make sure that you have a supported version of SQL installed on the primary servers/CAS. SQL 2008 R2 SP3 is not supported, and it should have minimum SQL 2012 R2. So, hold on with your SCCM CB 1702 to upgrade if you don’t have supported SQL and OS versions.

How to Perform SCCM ConfigMgr CB Production upgrade to 1702 Video Tutorial Configuration Manager
How to Perform SCCM ConfigMgr CB Production upgrade to 1702 Video Tutorial Configuration Manager

Issues with getting ConfigMgr SCCM 1702 updates available in SCCM CB console?

The SCCM/ConfigMgr CB 1702 update is still not available in SCCM CB console? How to Perform SCCM ConfigMgr CB Production upgrade to 1702 Video Tutorial Configuration Manager?

Following are the steps you need to follow for the FAST RING release of SCCM CB 1702:- More details are available in my previous post “SCCM ConfigMgr 2012 to CB upgrade Unofficial Checklist

  1. Download the PowerShell script to ENABLE the first wave of customers (Script is available in the above link here) – SKIP THIS STEP – NOT Required NOW
  2. Run the PowerShell Launch from an elevated command prompt (local admin access) PS Command – “EnableFastUpdateRing1702.ps1 <SiteServer_Name | SiteServer_IP>” – SKIP THIS STEP – NOT Required NOW
  3. Force a check for the update.  Go to \Administration\Overview\Cloud Services\Updates and Servicing and click “Check for Updates.”  You may need to try “Check for Updates” more than once if the package is not downloaded on the first try.
  4. Wait for some time. DMP Downloader component will start the Download via SCCM CB 1606 updates and Servicing channel (DMPdownloader.log for more details)
  5. SCCM CB 1702 Prerequisites check
  6. Start the installation and wait for the replication of source files to the server in the hierarchy if you have CAS and Primary servers (this is not covered as I don’t have SCCM CB hierarchy in the lab)
  7. Once installation is completed on CAS server then, automatic SCCM CB 1702 upgrade process will kick in for child Primary servers as per the service windows scheduled on the respective primary server

As you can see in the above screen capture the SCCM/ConfigMgr CB 1702 is already downloaded and available for the upgrade process on my SCCM primary server. Download process of SCCM CB 1702 still has some challenges and there is here is some room for improvement.

The SCCM CB 1702 download was stuck in downloading state for a long time. I had to restart the SMS Executive service to make the “in-console” 1702 update to an available state. Right-click on the Configuration Manager 1702 update and Install.

The SCCM/ConfigMgr CB 1702 upgrade experience was very smooth for me. The SCCM/ConfigMgr CB 1702 upgrade process can take time depending on several factors like hardware performance of server components and SQL DB size etc.. You can monitor the status of the upgrade from CMUpdate.log.

Also, check the Monitoring workspace for a more standardized status table with respective log file details of each stage of an upgrade. How to Perform SCCM ConfigMgr CB Production upgrade to 1702 Video Tutorial Configuration Manager?

The last stage of the ConfigMgr/SCCM CB 1610 to 1702 upgrade process is SCCM CB console upgrade. Once, the console is upgraded successfully then; you can see the latest version of the site server version.

Also, the SCCM CB 1702 version details will be updated in the primary servers or CAS server registry key.

Version

Version 1702
Console Version 5.000.8498.1400
Site Version:5.0.8498.1000
How to Perform SCCM ConfigMgr CB Production upgrade to 1702 Video Tutorial Configuration Manager
How to Perform SCCM ConfigMgr CB Production upgrade to 1702 Video Tutorial Configuration Manager

References :-

  • Now Available: Update 1702 for System Center Configuration Manager – here
  • Deprecated operating systems and SQL supports details for SCCM/ConfigMgr CB 1702 – here

How to Migrate SCCM CB Primary server to New Hardware Configuration Manager ConfigMgr Best Guide

How to Migrate SCCM CB Primary server to New Hardware Configuration Manager ConfigMgr? How to Migrate SCCM CB 1606 primary server to new hardware or new virtual server?

How to restore SCCM CB primary server from the full SCCM backup? I’ll try to answer these two questions in this blog post and the video. 

I used SCCM CB full backup to migrate the primary server into a virtual server. In this scenario, I’ve SCCM CB primary site server and Database server on the same box.

After the migration, Intune/cloud communication was not working and all the logs (CloudUserSync.log, DMPUploader.log, and DMPDownloader.log) filled with “Certmgr has not installed certificate yet, sleep for 1 minute.“.

The resolution was to remove Intune subscription and add it back. More details about “Migrate SCCM CB Primary server to New Hardware or to new virtual server”. How to Migrate SCCM CB Primary server to New Hardware Configuration Manager ConfigMgr.

Prerequisites Migrate SCCM CB Primary server to New Hardware

Following are the prerequisites which we need to follow while migrating SCCM CB primary server to new hardware:- How to SCCM CB Primary server to New Hardware Configuration Manager ConfigMgr.

  • FQDN Hostname Should be same :
  • Drive Letters should be same :
  • Installation Path should be same:
  • Should have same patch level:
  • Better to have the same IP:
How to Migrate SCCM CB Primary server to New Hardware Configuration Manager ConfigMgr
How to Migrate SCCM CB Primary server to New Hardware Configuration Manager ConfigMgr

Tips – Migrate SCCM CB Primary server to New Hardware

  • The following steps will help to complete the migration steps easily  
  • 1. Document local SMS group memberships of existing server 
  • 2. Perform differential Robocopy of the backup folders to the new server (Package Source\DP files\WSUS) 
  • 3. Shutdown Current SCCM CB Server 
  • 4. Delete AD object of existing SCCM Server from Active Directory Users and Computers 
  • 5. Rename the new server to the old SCCM CB server name 
  • 6. Give New Server OLD IP address (Optional) 
  • 7.  Perform Domain Join of new SCCM CB server. Provide FULL ACCESS to new SCCM CB computer object in System Management container and also add to respective AD groups wherever required. 
  • 8. Install all the prerequisites – ADK, WSUS, SQL, etc…. 
  • 9. Run the setup from CD.Latest folder to get the latest binaries of the existing CB site.

Video

(1) How to Migrate ConfigMgr SCCM CB Primary Server to New Hardware – YouTube

References

SCCM Related Posts Real World Experiences Of SCCM Admins (anoopcnair.com)

SCCM ConfigMgr CB How to Plan Backup Recovery | Configuration Manager Best Options

SCCM ConfigMgr CB How to Plan Backup Recovery | Configuration Manager Best Options? What are the changes therein backup and recovery options in SCCM ConfigMgr CB 1606? Nothing much changed in terms of backup apart from taking backup of CD.Latest folder.

CD.LATEST folder is also getting backed up as part of SCCM CB full backup. Why do we need the CD.LATEST as part of SCCM CB full backup? It’s because this is a source file when you want to recover an SCCM CB site server!

Why can’t we use the baseline version which can be downloaded from MSDN/Volume Licensing sites? Those binaries can’t be used because that is not the same version of SCCM CB which is installed in your primary server/CAS.

The baseline version of SCCM CB production is 1511 and if you upgraded/updated the site to SCCM CB 1606 using Updates and Servicing then you can’t use 1511 version source files to recover the primary site.

When do you want to Run SCCM CB Setup from CD.LATEST Folder?

Only when you are trying to recover a site !! In the following video, I try to explain the process of the back and restore. Also, when to select which option during the recovery process.

There is always a question of whether to use SCCM full backup or just use SQL backup to restore the functionality of SCCM sites. So my answer to that question would be “it depends”.

SCCM CB supports both the scenarios mentioned above however in some of the scenarios you may need full SCCM CB backup to complete the restore. The SCCM restore and recovery come with loads of permutations and combinations as I explained in the below table and the above video.

SCCM ConfigMgr CB How to Plan Backup Recovery | Configuration Manager Best Options

I hope, you will get some clarity about those scenarios after watching the video. What are the changes in SCCM CB 1606 Backup and Recovery options – YouTube.. SCCM ConfigMgr CB How to Plan Backup Recovery | Configuration Manager Best Options?

SCCM ConfigMgr CB How to Plan Backup Recovery | Configuration Manager Best Options
SCCM ConfigMgr CB How to Plan Backup Recovery | Configuration Manager Best Options

Table 1 : SCCM CB Site Server and Site Database Recovery options

SCCM ConfigMgr CB How to Plan Backup Recovery | Configuration Manager Best Options
SCCM ConfigMgr CB How to Plan Backup Recovery | Configuration Manager Best Options
 Installation      Site Server                               Site Database
 Setup only part of recoveryRecover Site ServerReinstall the site serverRecover DB using CM backupCreate a new DBManually Recovered DBSkip DB Recovery
CASInstall setup from CD.LATEST FolderOnly when you’ve SCCM Full BackupReconfigure the settingsOnly when you’ve SCCM Full BackupOnly When you’ve a hierarchyUse SQL Backup or any other backup. Changes made retrieved from PrimaryOnly valid when the site DB is on a different computer
Stand-Alone PrimaryInstall setup from CD.LATEST FolderOnly when you’ve SCCM Full BackupReconfigure the settingsOnly when you’ve SCCM Full BackupNot ApplicableUse SQL Backup or any other backup. Lose site changes after the last backupOnly valid when the site DB is on a different computer
Child PrimaryInstall setup from CD.LATEST FolderOnly when you’ve SCCM Full BackupReconfigure the settingsOnly when you’ve SCCM Full BackupOnly When you’ve a hierarchyUse SQL Backup or any other backup. Changes made retrieved from CASOnly valid when the site DB is on a different computer
SecondaryUse CM Console to recover Secondary SiteNo recoveryNo recoveryNo recoveryNo recoveryNo recoveryNo recovery
SCCM ConfigMgr CB How to Plan Backup Recovery | Configuration Manager Best Options

Reference :-

here