Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Computers not rebooting after patches

I'm running into an issue where (despite the task being set to Post-Reboot Computer only if Windows Update Agent requires), I've got systems that will not reboot. Most typically, this is happening when a user is logged into the machine at the time. Is there any solution to this?

Find more posts tagged with

Accepted answers

jrouviere

Hello shelbyj,

Typically you don't want Patch Manager or a related system rebooting on a user who is signed into the computer. I could expound on the reasons why and how to deal with them, but there's a pretty good write up here that delivers it almost exactly how I would:

https://technet.microsoft.com/en-us/library/gg537354.aspx?f=255&MSPPError=-2147217396

The update task has a reboot if required, as you stated the option selected, but this is similar to a "polite" shut down in the sense that it's not going to typically interrupt active use on the machine (a logged in user). You can set up a reboot/shut down task if you would like, or as the article states, generate a script to do this for you if you need.

If you select the node you're having issues with, there's a Shutdown or Reboot action in the Actions pane (or right click) which you can also schedule for a group of machines if you want to follow up with a more direct reboot (such as on the weekend or outside of office hours).

All comments

jrouviere

Hello shelbyj,

https://technet.microsoft.com/en-us/library/gg537354.aspx?f=255&MSPPError=-2147217396

shelbyj

So, my options are to create a separate reboot task in patch manager (would this be a "polite" shutdown as well?) or create a separate script to reboot? There is no way to force an impolite shutdown following patching within the patch manager task?

jrouviere

You can review the task for any options I overlooked, but that's the sum of it and there are additional suggestions in the material I shared. The Shutdown or Reboot task that I shared previously is similar to running shutdown /i from a command prompt and has similar options available there.

shelbyj

Thanks. Not the answer I wanted to hear, but at least it means I wasn't missing something obvious.

frgpugs

Ive been using a scheduled shutdown task at 3:30 am every night for the past few years. The way I do it is created a group and add or remove computers as needed and then point the shutdown with a 5 minute grace period. The only pain in the butt about it is that I have to recreate the task every time I add or remove a computer, but it does work.

rbullard

Actually you can work around that by creating a WSUS group instead of a PM group. Then you do not need to recreate the task with your adds/deletes.