Tomasz Chmielewski wrote: > WPKG service runs in the background, and it shouldn't matter if the user > is logged in or not. It *shouldn't* - because if the user runs a > program, its upgrade will likely fail. You could forcibly log out the > users, but you risk loosing the work they didn't save etc. > > That's why running it during bootup makes most sense. > If you have the users who do not reboot their workstations, you have to > take additional measures. What would the difference be between stopping/starting the wpkg service via the task scheduler versus running wpkg.js via the task scheduler? |