Closed chriskuech closed 5 years ago
This issue has been automatically marked as stale because it has not had activity from the community in the last 30 days. It will be closed if no further activity occurs within 10 days. If the issue is labelled with any of the work labels (e.g bug, enhancement, documentation, or tests) then the issue will not auto-close.
I believe the point of xPendingReboot is to set $global:DSCMachineStatus = 1
if any of the three registry locations indicate that a reboot is needed -- regardless of whether the DSC needs a reboot otherwise...
This issue has been automatically marked as stale because it has not had activity from the community in the last 30 days. It will be closed if no further activity occurs within 10 days. If the issue is labelled with any of the work labels (e.g bug, enhancement, documentation, or tests) then the issue will not auto-close.
This issue has been automatically closed because it is has not had activity from the community in the last 40 days.
It is unclear in the docs why this resource is needed. Setting
$global:DSCMachineStatus = 1
in a script resource without using xPendingReboot will still cause the machine to reboot. Could you please describe the default case (where$global:DSCMachineStatus = 1
is set without xPendingReboot) and what value xPendingReboot provides over the default case?