What would be the most efficient troubleshooting step in remedying a handful of devices which seem to be ‘stuck’ from updating any further. The procedure (which runs every night because the machines are way behind in updates) has all features and updates enabled. Most of the machines in the group have responded to the updates – but some of them are not progressing after multiple attempts, and do not have any device logs reflecting activity (although one is ‘in progress’ for over 3 days… In another words what is the most popular troubleshooting step to unfreeze hanging devices (from updating)---- perhaps just a reboot, which I’ll try doing, but maybe there’s something else that others have experienced. . . .
Also I have this procedure running every night- so I would expect to see always the previous nights date in the execution logs of this procedure. I don’t see the last 2 days present. How can I tell if ‘procedures’ in general are not running (via schedule)?. .
The first thing that comes to mind is to reboot the endpoint to make sure any pending installations are completed. Check one of the affected endpoints by performing a manual Windows update to see if there are any errors that would come up during the process. If there are error(s), you will need to address this so that the custom patch procedure will proceed according to schedule.
Status of custom procedures (or any procedures) can be found in that specific procedure’s Execution Log section. You can also see it in the Script Logs in one of the affected endpoints (all in ITSM). There is currently no method available to view procedure status via schedule.
Hey Rick, for some reason things kicked in this past Monday night – it stopped on the 21st and started up again on the 28th. I AM at least seeing Patch logs for the last two nights for each device, and most are catching up in the updates. Now, I still however have a couple of XP machines not progressing- but haven’t been able to log on to them to carry out your advice- thank you by the way. Do know why things kickstarted into play seemingly over the weekend or Monday?
Honestly, @evoevoevo I cannot say for sure what ‘kickstarted’ the patching process on your devices. It can be any number of factors (internal and external).
Now, for the XP machines though you will have to manually check the updates through a different method. This is mainly due to Microsoft’s end of support for WIndows XP.