Troubleshooting Reboot Processes in SecureDX

Some users discussed the process of rebooting devices during remediation in SecureDX, as well as the possibility of configuring this in the template. One user mentioned being unable to click on "pending restart" to filter and select devices to restart. Others chimed in with troubleshooting suggestions. Discussions also included details of how certain updates may require a reboot.

Read the entire ‘Troubleshooting Reboot Processes in SecureDX’ thread below:

Am I missing something…when remediating devices/apps etc in SecureDX and it is an update that requires a reboot, do I really have to go back to the devices / details / select the device(s) and reboot from there?

Currently not at my desk, but I think you can configure this as part of the template?

Also when in SecureDX should this chart be a clickable filter?

Will look at the template…

There’s some things you can configure in the remediation step like a user message, if the user can pause the update to a later time as well as reboot behavior. But I’m doing this from memory. Will check when I have a chance

Looking at the template, you get choice to auto-remediate that will enable an auto reboot as part of it. I just found it strange that I could not click on the ‘pending restart’ to filter and then select those in the filter to restart.

Ok, so you did a manual remediation and are looking at the jobs tab where you see this?

Just trying to understand your scenario so I can have a look here

• look at dashboard

• identify item to remediate, cumulative update/vmtools for example

• create remediation job

• run immediately and it runs

obviously some updates require a restart, VM tools for example may need C++ runtimes as part of its update, this then requires a reboot if versions too old, then VMtools also requires a reboot for replacing a driver or two

Continue reading and comment on the thread ‘Troubleshooting Reboot Processes in SecureDX’.  Not a member? Join Here!