[wpkg-users] Power preferences

[Dan Lawless]

If you add the /i switch into the update string this will allow it to run interactively in the "current" session not open an additional session.  May be a possibility the only disadvantage to this is it pops up an additional command prompt window.

Dan Lawless
IT Engineer
Boston Engineering Corporation
411 Waverley Oaks Road, Suite 114
Waltham, MA 02452
Direct: 781-314-0747
http://www.boston-engineering.com

----- Original Message -----
From: "Tomasz Chmielewski" <mangoo at wpkg.org>
To: "Anders Nilsson" <andersn at isy.liu.se>
Cc: wpkg-users at lists.wpkg.org
Sent: Monday, March 16, 2009 12:39:40 PM GMT -05:00 US/Canada Eastern
Subject: Re: [wpkg-users] Power preferences

Anders Nilsson schrieb:
> I run the wpkg.js client from Windows XP startup script, which means
> wpkg runs as the system user (I think), and try to install the following
> self-made package:
> 
> <package id="powerproperties"
>   name="Power properties for monitor and standby"
>   revision="3"
>   reboot="false"
>   priority="10">
> 
>   <install cmd='powercfg /S "Home/Office Desk"' />
>   <install cmd='powercfg /X "Home/Office Desk" /monitor-timeout-ac 15' />
>   <install cmd='powercfg /X "Home/Office Desk" /standby-timeout-ac 240' />
>   <upgrade cmd='powercfg /S "Home/Office Desk"' />
>   <upgrade cmd='powercfg /X "Home/Office Desk" /monitor-timeout-ac 15' />
>   <upgrade cmd='powercfg /X "Home/Office Desk" /standby-timeout-ac 240' />
> </package>
> 
> The problem is that the settings don't stick, that is nothing concerning
> power properties as changed. The client wpkg log file thinks everything
> is OK and that the package is successfully installed (or upgraded when
> applicable).
> 
> Running the very same commands logged in as Administrator things work
> just as expected. When nobody is logged on the monitor shuts down after
> 15 minutes and the system goes to standby in 4 hours.
> 
> As far as I can see these power property settings is not a user
> preference, or is that my problem here?

I think this is one of this rare commands which will work only if they 
are started on a proper "screen".
WPKG Client executes commands "in the background", which means, not on 
your primary display.
You can compare it to running these commands when logged in via Terminal 
Services - although technically you can change resolution or power 
setting there, it will have no effect on your primary display.

I think it's best to run such commands in autologin scripts.


-- 
Tomasz Chmielewski
http://wpkg.org
-------------------------------------------------------------------------
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