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
-
From: wpkg-users-boun...@lists.wpkg.org [mailto:wpkg-users-
boun...@lists.wpkg.org] On Behalf Of simplesi
Sent: Wednesday, November 11, 2009 11:00 PM
To: wpkg-users@lists.wpkg.org
Subject: Re: [wpkg-users] Just running one package at each run
Kevin Keane-2 wrote:
The first request should
From: subscript...@kkeane.com
To: wpkg-users@lists.wpkg.org
Date: Thu, 12 Nov 2009 03:50:11 -0800
Subject: Re: [wpkg-users] Just running one package at each run
First, one more pitfall warning: regardless of what you do, remember that
WPKG will also *UNINSTALL* software if it has
From: wpkg-users-boun...@lists.wpkg.org
[mailto:wpkg-users-boun...@lists.wpkg.org] On Behalf Of Chris Wilcox
Sent: Thursday, November 12, 2009 4:12 AM
To: wpkg
Subject: Re: [wpkg-users] Just running one package at each run
First, one more pitfall warning: regardless of what you do, remember
From: wpkg-users-boun...@lists.wpkg.org
[mailto:wpkg-users-boun...@lists.wpkg.org] On Behalf Of Chris Wilcox
Sent: Thursday, November 12, 2009 4:12 AM
To: wpkg
Subject: Re: [wpkg-users] Just running one package at each run
First, one more pitfall warning: regardless of what you
do
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
From: wpkg-users-boun...@lists.wpkg.org
[mailto:wpkg-users-boun...@lists.wpkg.org] On Behalf Of Chris Wilcox
Sent: Thursday, November 12, 2009 4:12 AM
To: wpkg
Subject: Re: [wpkg-users] Just running one package at each run
First, one more pitfall warning: regardless of what you
Hi Stefan,
Pendl Stefan wrote:
This is not true, WPKG removes only packages listed in the local wpkg.xml
file, which are not assigned to the host via profiles.
If the user installs any application without using WPKG, then it is not
managed.
Confirmed (see my other post in this thread
Hi Kevin,
Kevin Keane wrote:
I was under the impression that wpgk.js /synchronize would add all matching
Packages to wpkg.xml as well? Is that not the case?
No, WPKG does add only the packages you assign to the host via the assigned
profile.
WPKG cannot find matching packages. Going through
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
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
-
boun...@lists.wpkg.org] On Behalf Of simplesi
Sent: Wednesday, November 11, 2009 10:20 AM
To: wpkg-users@lists.wpkg.org
Subject: [wpkg-users] Just running one package at each run
I've a need for some sort of mechanism to just deploy one package at a
time
at each run of wpkg.js.
Some
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
13 matches
Mail list logo
