[wpkg-users] WPKG and Windows SteadyState Disk Protection

[mscdex]

I ran into a similar situation when I was working with a small network that
was using deep freeze. I ended up modifying wpkg.js in the relevant places
where a successful package installation/removal/upgrade/downgrade has been
detected, etc. In those places, I had it call a custom jscript function of
mine to do the freezing (and reboot possibly, I can't remember now) of the
hard disk after all was said and done. I also put in a call to a custom
jscript function to do a thaw (and reboot) first only if wpkg detected that
work needed to be done (packages needed to be removed, installed, etc).

That may not be the most elegant solution, but I couldn't find any neater
way to do it.

On 1/5/09, Josh Frome <jfrome at maildev.slcpl.org> wrote:
>
> Hello,
>
>      I'm new to WPKG and was wondering if anyone had tips for integrating
> Microsoft's SteadyState disk protection.  More specifically, SteadyState is
> configured to remove any changes the the hard drive (a la Deep Freeze, etc)
> and requires a registry change and reboot to write/save changes to the hard
> drive.  I have a script that will perform the registry modification and
> reboot, but I am looking for a way to only call the script when WPKG has
> made a change (install/uninstall, etc) and not every time WPKG runs (i.e.
> using a post-action).
>
> What would be the best approach to find out if WPKG has
> installed/uninstalled packages and if so, enable a reboot script?
>
> Thanks,
>
> Josh
>
> --
> Josh Frome
> Network Administrator
> Salt Lake City Public Library
> 801.524.8282
> -------------------------------------------------------------------------
> wpkg-users mailing list archives >>
> http://lists.wpkg.org/pipermail/wpkg-users/
> _______________________________________________
> wpkg-users mailing list
> wpkg-users at lists.wpkg.org
> http://lists.wpkg.org/mailman/listinfo/wpkg-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/wpkg-users/attachments/20090105/58a38b5a/attachment-0002.html>