MECM Task Sequence App Deployment type not restarting computer

Question

Hello All,

I have a non-OSD task sequence that is being used to escrow a recovery password and uninstall encryption software on a number of endpoints in our environment. I have created an application with the TS deployment type and chosen the desired task sequence to be deployed as an application.

I chose to deploy as an application to make use of the restart pop up notifications configured in client settings under computer agent and computer restart to have the user prompted with a restart notification instead of rebooting the computer without the user's permission. So far, I am unable to get the computer to prompt with the restart notification. I know the client settings are configured correctly because other app deployments successfully show the pop up and when I look at the app in software center, it says restart required: yes. The task sequence completes successfully and everything works as expected except for the restart. RebootCoordinator does not show any attempts to reboot the computer and the maintenance window is configured correctly. I also have the "Configmgr will enforce a mandatory reboot" enabled on the App Deployment type User Experience settings.

Does anyone have experience doing something similar and had success with the restart notifications on Task Sequence deployed as an application? The CM version is 2111

Thanks for any help!

Answer 1

@Michael DiGregorio
Thanks for your posting on Q&A.

I found the following Official Document and I want to share with you.
https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/changes/whats-new-in-version-2111#net-version-462-prerequisite-check-is-an-error

When the Configuration Manager client updates to version 2111 or later, client notifications are dependent upon .NET 4.6.2 or later. Until you update .NET to version 4.6.2 or later, and restart the device, users won't see notifications from Configuration Manager. Other client-side functionality may be affected until the device is updated and restarted.

Please review the .Net Framework version on the affected client first.

Best regards,
Rita

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.