Jump to content


surfincow

Client Settings: Reboot enforced for package, but not for Application

Recommended Posts

Hello,

 

I'm testing out the reboot policy and I'm having some issues with the reboot (forced by the configmgr client in the application deployment) timeframe configured in the Client Policy not being enforced.

 

I have a test collection set with a reboot window of 30 minutes, with the reminder displaying with 10 minutes left, and that client policy is deployed to that collection.

 

If I create a package and set it to have the configmgr force the reboot after install, all works as expected.

If I create an application and set it to have the configmgr force the reboot after install, it does not work as expected. I get the reboot notification, no count down. Only option to reboot or snooze (which it allows me to snooze 4 hours, which is way past the reboot setting)

 

I'm sure I'm missing something simple but not sure what it is.

 

Am I correct in asuming the Client Settings "Computer Restart" affects reboots triggered by Package/Application/Software Update installation that calls for a reboot?

 

The resultant Client Settings shows the 30/10 values.

There are no maint. windows configured, nor business hours.

 

What am I missing?

 

 

Thanks

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.