Paul McGrath-2 wrote:
Hi Simon,
I was wondering why you don't run WPKG as a service as it is designed?
I've been using WPKG for a long time (originally on Win98 with linux SMB
servers) so I've just kept things simple with running it as a all users
startup bat file :)
AFAIK this saves
Hi - long time since I last posted here (as WPKG just works :) )
I use WPKG in 6 schools but all XP machines.
I'm now trying to use it on Win7 but its a bit of a fight :)
I run WPKG on logon from shortcut in allusers program startup folder.
(All users have administrator rights)
I've created a
Marco Gaiarin wrote:
I use the same command, but on pre/post WPKGClient scripts, and works
flawlessy...
I'm getting the same problem as the OP.
I'm just trying out my old scripts on a Win7 pro machine and this is one of
the problems - I get:-
Exit code returned non-successful value (2)
Chris Mortimer-2 wrote:
Hello,
For info, I use the following for my Win7 clients:-users
Quite :)
Bit of an overkill just so I know when its the right time to go home :)
Simon
--
View this message in context:
http://old.nabble.com/Synchronize-with-Timeserver-tp31918389p31954176.html
I'm trying to write a package to deploy some files and then run an
install.bat files afterwards
[code]
install
cmd='xcopy %PACKAGES%\heliumfrognet\*.*
c:\apps\Helium_Frog_Netbook /c
/e /f /i /y' /
install
cmd='%COMSPEC% /C
David Abilleira wrote:
Perhaps you could make a couple of simple scripts:
· One that writes today's date on a registry key
· One that checks that registry key to see if matches today's date
You can add *the first as a install command to all* installation tasks ,
and the second as a
I've a need for some sort of mechanism to just deploy one package at a time
at each run of wpkg.js.
Some packages (Anti-virus, service packs etc) can take a long time to
install and I'd like to have WPKG just do one of these packages on one run
of wpkg.js (e.g. one package the 1st time and then
Kevin Keane-2 wrote:
The first request should be fairly easy to do: just add only one
application at a time to your profiles.
My main issues are machines that for one reason or another haven't run WPKG
each day - e.g wireless machines that have failed to connect to the wireless
since the
Vesion 3 uploaded
Now outputs the packages that would be installed and not just the ones
already installed :)
Also, the comptuer Event log was being flooded by debug information so I
disabled Event logging when /hppcheck invoked
Modifled version available here
I've uploaded an updated version which will not suppress error messages and
also outputs both the client machine host name and the host node WPKG
matches to it
regards
Simon
--
View this message in context:
http://www.nabble.com/Accessing-WPKG-parameters-tp25979851p26101332.html
Sent from the
Paul McGrath-2 wrote:
Hi,
I am trying to apply a number of profiles to the same host.
Hi
I can't see anything wrong with your code but you might want to try out my
latest offering which will make it easier to see what profiles/packages WPKG
thinks it should be trying to apply to a
I decided the best way was to modify wpkg.js by adding a few if statements to
just output the host/profile(s)/package(s) information.
I did this by adding an extra flag (/hppcheck) which invokes /synchronise,
/dryrun and /quiet and the mods just turn off /quiet at appropriate points.
Modifled
I recently made up a package to deploy Scratch 1.4.
It had a check condition in to make sure it wasn't deployed if it already
existed (some machines had been updated manually) and I deployed it to all
my workstations and after I'd done about half the school I noticed that I'd
forgotton to copy a
mangoo wrote:
Check the hostname, and then, check against the remote hosts.xml?
yes - that would work - I was just wondering if there was an easy way
already :)
regards
Simon
--
View this message in context:
http://www.nabble.com/Accessing-WPKG-parameters-tp25979851p25981627.html
Just wondered how others around here use WPKG.
I use it very simply :)
I just copy a shortcut to the all users startup folder and run a batch file
containing cscript %WPKGROOT%\wpkg.js /synchronise
(currently modifying this to put a batch file directly into the startup
folder that delays
Rainer Meier wrote:
Hi Simon,
Well this warning is justified I think because this is a profile/package
inconsistency where the administrator schould have a look at
...
Regarding the fact of profile inconsistency I prefer to send at least a
warning-level notification to the
Just a simple question as I've never used checks before :)
Are checks just used for the install command?
Are they ignored when a package revision is incremented and the upgrade
command is executed?
Or can you have separate check conditions for an upgrade?
regards
Simon
--
View this message
OK - lets see if I've got this :)
1st run of package with a simple does the uninstall exist check command.
If check command = false (which it would normally be) then install commands
invoked and assuming no errors, check is run again and if check=true then
wpkg assumes package installed.
On
Good so far then :)
So I now increase revision number.
wpkg sees the revision increase and jumps straight to the upgrade commands
(just ignores the check statement and assumes the upgrade is needed due to
the revision increase)
On completion of the upgrade commands(and assuming no errors
Chris Wilcox wrote:
I also use WPKG across 16 schools. One of the first things I did when
trialling and now using wpkg live was dredge out an old and unused PC
capable of running XP Pro and set this up as a test workstation for wpkg
packages before I roll things out to the live
I hadn't realised that WPKG removed an wpkg.xml entry before upgrading it -
(e.g line 614) so my initial modification request is no longer valid :(
I'll have to learn more and try again in the future :)
If this is not what you want to achieve please explain your use-case in
more detail.
I
Starting from the beginning again :)
I adminster several small school networks and use wpkg to deploy packages to
several machines if it is quicker to use wpkg than to go around all
computers and do a manual install.
I want to be able to test a new package out or a modified one on an existing
Rainer Meier wrote:
Could you explain this certain circumstances in a bit more detail
because it
might be a bug. I've checked the code and wpkg.xml entries are only
removed in
the removePackage function. And all of them are completely skipped if the
/noremove flag (or noremove config)
I don't know how you are viewing my message but when I view it on Nabble - it
shows the relavent part of the documentation in bold :)
Please just look at the documentation in wpkg.js about noremove especially
the last bit
regards
Simon
--
View this message in context:
Rainer Meier wrote:
Personally I prefer to specify that A is a dependency for B and then
either
assign A and B or just B to the profile which will assure that package A
is
installed first (since B depends on it).
Thats what I do (I add both packages but specify that B depends on A)
simplesi wrote:
Also - is there a history of changelogs on the wiki - if not I'll try and
make ones up from the release docs.
Sorry -didn't notice them as links - OK now :)
regards
Simon
--
View this message in context:
http://www.nabble.com/Package-Dependancy-tp25713729p25727515.html
Just as a matter of interest - when did the new dependancy functionality come
in (e.g new depends/chain/including) or has it been there for ages and I've
just missed it! :)
regards
Simon
--
View this message in context:
http://www.nabble.com/Package-Dependancy-tp25713729p25713729.html
Sent
:)
I know dependancy came in a few years ago:)
I meant when did the old method of dependancy (e.g a package must already be
installed for another package to be attempted to be installed) change to the
new model?
The new method seems to imply that packages will automatically be included
for
And looking at Wiki edits - a user called Talk edited it with the new
descriptions on Aug 18 2009
regards
Simon
--
View this message in context:
http://www.nabble.com/Package-Dependancy-tp25713729p25722545.html
Sent from the WPKG - Users mailing list archive at Nabble.com.
Rainer Meier wrote:
Sure, these days I would call it include but also the depends node
does the
same job - so apart from possible confusion there is no reason to change
it.
Changing it would mean to break compatibility with very little advantages.
Could I suggest that when you have
Hi - I've been on holiday but back now :)
Rainer Meier wrote:
A negative effect would be that after a while there might be pretty much
packages in wpkg.xml where no remove command is specified and where there
is no
corresponding package on server side...
All these points are true
I've been thinking about WPKGs default behaviour (following from earlier
discussions) and I'd like to start a genuine discussion on changing its
current behaviour.
Currently, WPKG will attempt to remove an existing package from the local
compuer wpkg.xml file if it decides that an existing
Could WPKG be modified to allow direct allocation of a package to a host.
The main use for this would be for testing to save a lot of editing when
testing out a package.
regards
Simon
--
View this message in context:
The two packages are read in correctly: the first one with a priority of
1000 and the second one has no priority attribute at all.
Ok - adding code to deal with no priority attribute.
do you have any suggestions as to how to deal with this.
Should the program display these packages
I've put at bit more work into a WPKG Priority Package Editor and v0.2 is
available via this link
http://www.euxton.lancs.sch.uk/index.php?option=com_contentview=articleid=269
It allows you to simply edit the priority attribute in your package files.
To use, enter the location of your wpkg root
Pendl Stefan wrote:
For Windows XP and newer, you can use the TASKKILL utility.
Ta - I've have to lookup how to use it
(any examples greatly received :) )
On the other hand, how about running the AutoIT script from the WPKG
launcher ???
This way you can make sure they are always
I've written a simple tool (in VB 2008) to edit package priorities.
I'm looking for some alpha testers who know NOT to use it on a live system.
It can easily be tested on a copy of a typical packages folder.
regards
Simon
--
View this message in context:
Hi
AFAIK the default behaviour of WPKG is designed to do an update before a
remove is attempted in order to give you a chance to alter the remove
command.
regards
Simon
--
View this message in context:
http://www.nabble.com/Using-bat-files-for-remove-procedure-tp24068296p24088078.html
Sent
Hi,
I was adding a new package (autopupillogonnull) to a profile and noticed
that WPKG was telling me the package was already installed on the first run
on wpkg.js after adding the package e.g
Console output using WPKG 1.1.0
Installing 'Set Pupil user to auto logon' (autologonpupilnull)...
You are the current maintainer of a multi-purpose tool that has been around
and used by a number of people for a long time.
I have used WPKG across about 10 primary schools (ages 5-11) where secure
locked down networks are not required or needed.
I believe that my suggestion of WPKG doing
Rainer Meier wrote:
Hi Simon,
If you allow me to make one more proposal...
Thank you very much for your proposal. :-)
I will try out your suggestion and get back to you as quickly as possible :)
regards
Simon
--
View this message in context:
Rainer Meier wrote:
You did not answer yet if your packages define some checks.
I believe I published my package in my last post - I think you missed it :)
It does not have any checks
The only difference (and that's what is irritating you I think) is that
WPKG is
going to verify the
When testing I removed a package from a profile but wpkg seemed to still run
it the next time i ran my logon script (which does cscript
%WPKGROOT%\wpkg.js /synchronize )
It them doesn't do run it on subsequent runs.
I'm assuming it looks in wpkg.xml and sees the entry there and decides to
run
Rainer Meier wrote:
However the issue you face with your packages might come from the fact
that you
did not specify appropriate checks for the packages. From your description
I
have to assume that you do not specify any checks. As a result the
WPKG-internal
isInstalled() check will
Pendl Stefan wrote:
The dependency needs to be placed in the package, not in the profile.
Ahh - thank you - I;ll try and update the wiki to make that a bit more
obvious :)
regards
Simon
--
View this message in context:
http://www.nabble.com/Package-Dependency-tp23635410p23636911.html
mangoo wrote:
If you have 2 minutes of your time, could you guys add your testimonials
to http://wpkg.org/Testimonials? ;)
I work in 9 small schools that mainly use Win98 machines as servers and
use it to deploy software installs in combination with Autoit scripts.
Approx 300
Rainer Meier wrote:
In any case I think Simon should take a bit more care about an integral
and
sensitive part of his software environment. In most cases re-installing an
application is not an issue and if it is then I suggest testing and
carefully
handling the package database.
Rainer Meier wrote:
...This way wpkg.js will never remove any settings node. But hey, I really
don't
see any legitimate use case for this.
Well the legitimate use is that I'd like to do it and I don't think anyone
or any computer dies as a result of doing this :)
If the settings
Hello - I've been away from the list for a while so apologies if this has
been answered recently.
When I'm changing my hosts/profiles files I sometimes end up not specfiying
a previously applied package and wpkg attempts to uninstall it.
I never have any uninstall commands in my packages and
Chris Wilcox wrote:
Without meaning to be offensive, the answer to this perhaps is not within
WPKG itself but more in your housekeeping of the xml files?
:lol:
Well - everyone makes mistooks :)
Take a look at the /noremove command line options resp. the noRemove
config.xml parameter.
50 matches
Mail list logo