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 pending reboot. Once identified, the devices 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 do Restart computers from the SCCM console?

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

How do you find out the restart/reboot of 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, right-click on collection or device to initiate the REBOOT action. This reboot action is created via the FAST client notification channel.

We don’t have a deploy a reboot script to machines. Most importantly, this “REBOOT” action is triggered via the 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 the Pending reboot machine, and it didn’t work. Why? I checked the log files and ConfigMgr applet on Windows 10 machine.

I realized that I had 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 where you can check the status of REBOOT action.

The operation name for the 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 the 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 customize this policy from the client settings tab. The reboot or restart notification is very well integrated with the “Software Center” experience, which is a 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

Author

Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc……………