The easiest way would probably be to use DNS to provide different IPs
depending on the network, it's fairly easy to setup with BIND, see:
http://www.oreillynet.com/pub/a/oreilly/networking/news/views_0501.html
(on a side note, if you have multiple locations I would highly recommend
setting up mu
Hello all
Iam running wpkg on our company network, really great tool thanks alot for
it :-). We have multiple locations connected by a VPN. The problem is that
we have 1 server with all the packages. Now if we put a "big" new software
to the profiles we get some traffic problems ofc ;-). Bad thing
sbotsford wrote:
At present when debugging, you get:
A window saying which xml file it was working on.
OK
A window saying what the problem was
OK
A window saying what line number it occured on
OK
A window saying the offset in the line
OK
A windows saying the file offset (a number I don't believ
sbotsford wrote:
Perhaps we need a 4th xml file for this.
After writing just a couple packages, I can see merit in being able to
define global environment variables for wpkg.
Example: suppose that my installation share point is
\\conan\installers\wpkg. I would much rather have $WPKG.
and
At present when debugging, you get:
A window saying which xml file it was working on.
OK
A window saying what the problem was
OK
A window saying what line number it occured on
OK
A window saying the offset in the line
OK
A windows saying the file offset (a number I don't believe...)
OK
Can thes
Perhaps we need a 4th xml file for this.
After writing just a couple packages, I can see merit in being able to
define global environment variables for wpkg.
Example: suppose that my installation share point is
\\conan\installers\wpkg. I would much rather have $WPKG.
and later, as I accumu
Yeah, figured that out once I looked over the code - looks like it will wonk out if it gets an unexpected error code or if the post-check fails. I ended up changing the type of package to an execute="once" package and then versioning it. Once the change was propagated I removed the package from
> OK, so I tried this - created a vbs file that essentially does nothing and
> changed the install, upgrade, and remove commands to that vbs. I versioned
> the package and then ran WPKG which changed the WPKG.xml file to reflect the
> changes to the package.
>
> However, when I removed the package
Hi, OK, so I tried this - created a vbs file that essentially does nothing and changed the install, upgrade, and remove commands to that vbs. I versioned the package and then ran WPKG which changed the WPKG.xml file to reflect the changes to the package. However, when I removed the package
Thought about that - was hoping for a more streamlined approach but that will do it. ThanksKristofer Kiik <[EMAIL PROTECTED]> wrote: On 2/3/06, Ed Wallig <[EMAIL PROTECTED]>wrote:> Hi again,>> Feature request - can the capability be added (or does it already exist) to> remove a package
On 2/3/06, Ed Wallig <[EMAIL PROTECTED]> wrote:
> Hi again,
>
> Feature request - can the capability be added (or does it already exist) to
> remove a package from WPKG without it being removed from the clients?
>
> Basically, I'd like to be able to switch a "managed" application to an
> "unmanaged
Hi again, Feature request - can the capability be added (or does it already exist) to remove a package from WPKG without it being removed from the clients? Basically, I'd like to be able to switch a "managed" application to an "unmanaged" one where there is no reference to the package in p
On 1/7/06, Antonio Calvo Rodriguez <[EMAIL PROTECTED]> wrote:
> ¿Can post the modified exit procedure? Will be very useful
umm, let me see...
// call the main function with arguments.
try {
main(WScript.Arguments);
} catch (e) {
error(e.description);
notifyUserFail();
// exit(2);
}
ch
Saturday, January 07, 2006 6:32 AM
Subject: Re: [wpkg-users] Feature request
I'm guessing that this has been asked before, but I figured that I'd ask
again - is there any way to add a "skip on error" feature to a future
build
of WPKG? It would be nice if the synch would j
> I'm guessing that this has been asked before, but I figured that I'd ask
> again - is there any way to add a "skip on error" feature to a future build
> of WPKG? It would be nice if the synch would jump to the next package if the
> package that it was trying to install failed for some reason, rat
Hi, I'm guessing that this has been asked before, but I figured that I'd ask again - is there any way to add a "skip on error" feature to a future build of WPKG? It would be nice if the synch would jump to the next package if the package that it was trying to install failed for some reason, rat
Ed Wallig schrieb:
Duh! Good pointsometimes the simple fix is the best.
Question on this though - when in an AD domain, what permissions are
applied to the computer during logoff or shutdown?
hmm? those that you applied (in AD)?
When running WPKG
during startup, system permissions app
Duh! Good pointsometimes the simple fix is the best. Question on this though - when in an AD domain, what permissions are applied to the computer during logoff or shutdown? When running WPKG during startup, system permissions apply to the computer so software installs without any permissio
Ed Wallig schrieb:
Neat idea - another option would be to have a feature that delayed
installation until the user logged off / shut down - sort of like what
Windows Updates does now w/ XP SP2 ("Install Updates and shut down").
My 2 cents...
just run WPKG when system shuts down?
--
Tomek
htt
Andrew Z schrieb:
Hello,
I am trying out wpkg, and I have a suggestion: on our network I would
like users to be able to delay software installations. Imagine a
scenario where the software change is not critical, but the person may
be in a hurry and unnecessarily inconvenienced by waiting. T
On Wednesday 14 December 2005 14:08, Ed Wallig wrote:
> Neat idea - another option would be to have a feature that delayed
> installation until the user logged off / shut down - sort of like what
> Windows Updates does now w/ XP SP2 ("Install Updates and shut down").
>
> My 2 cents...
I second t
Neat idea - another option would be to have a feature that delayed installation until the user logged off / shut down - sort of like what Windows Updates does now w/ XP SP2 ("Install Updates and shut down"). My 2 cents...Andrew Z <[EMAIL PROTECTED]> wrote: Hello,I am trying out wpkg, and I hav
Hello,
I am trying out wpkg, and I have a suggestion: on our network I would
like users to be able to delay software installations. Imagine a
scenario where the software change is not critical, but the person may
be in a hurry and unnecessarily inconvenienced by waiting. Therefore, I
propos
Jean-Jacques Moulis schrieb:
On Wed, 16 Nov 2005 10:38:42 +0100 Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
TC> If you want to achieve what you want, just use a tool from UNIX like "less":
TC>
TC>
TC> cscript wpkg.js /query:a | less
What about:
cscript wpkg.js /query:a | more
more is
On Wed, 16 Nov 2005 10:38:42 +0100 Tomasz Chmielewski <[EMAIL PROTECTED]> wrote:
TC> If you want to achieve what you want, just use a tool from UNIX like "less":
TC>
TC>
TC> cscript wpkg.js /query:a | less
What about:
cscript wpkg.js /query:a | more
more is already present in Windows
--
Allan Stones schrieb:
Could you make it so when we do /query that you dont display ALL
packages on one dialog box. I have 40 applications so fat and its a bit
hard to read more then 10 without the dialog going off the screen.
Just split the dialog up so say it displays 10 packages then you cli
Could you make it so when we do /query that you dont display ALL
packages on one dialog box. I have 40 applications so fat and its a bit
hard to read more then 10 without the dialog going off the screen.
Just split the dialog up so say it displays 10 packages then you click
ok and it displays
oh ok, i will do that then, i wasnt aware that was the case :)
Tomasz Chmielewski wrote:
Allan Stones schrieb:
Could you code up /remove to be like query. So i could remove all
packages with /remove:a or all and /remove:package name would work also.
It would be very handy during package testi
Allan Stones schrieb:
Could you code up /remove to be like query. So i could remove all
packages with /remove:a or all and /remove:package name would work also.
It would be very handy during package testing and cleaning up a system
ready for another profile
if you do /synchronize, and the ho
Sorry for the previous sarcasm, bad mood.
On 11/10/05, Allan Stones <[EMAIL PROTECTED]> wrote:
> Could you code up /remove to be like query. So i could remove all
> packages with /remove:a or all and /remove:package name would work also.
>
> It would be very handy during package testing and cleani
On 11/10/05, Allan Stones <[EMAIL PROTECTED]> wrote:
> Could you code up /remove to be like query. So i could remove all
> packages with /remove:a or all and /remove:package name would work also.
erm... have you tried, like: wpkg.js /remove:package
that should probably do it...
i think...
i'm n
Could you code up /remove to be like query. So i could remove all
packages with /remove:a or all and /remove:package name would work also.
It would be very handy during package testing and cleaning up a system
ready for another profile
--
Nam: Allan Stones
Com: Optiver Australia PTY LTD
Pos: F
Jens Geile wrote:
Any suggestions? Objections?
IMHO too complicated, and it doesn't differ much from separate files for each
update (but read my other replies to see more reasoning and perhaps a solution).
The big advantage is that we can just add new updates under the last one. When
using
> > Any suggestions? Objections?
> IMHO too complicated, and it doesn't differ much from separate files for each
> update (but read my other replies to see more reasoning and perhaps a
> solution).
The big advantage is that we can just add new updates under the last one. When
using separate pack
Jens Geile wrote:
(...)
Any suggestions? Objections?
IMHO too complicated, and it doesn't differ much from separate files for
each update (but read my other replies to see more reasoning and perhaps
a solution).
--
Tomek
---
SF.Net em
Tim Fournet wrote:
So... What you're asking for is WSUS ;)
It would be interesting to see wpkg modified to do the same thing, but
I'm not sure if it will work smoothly. You'd need someone to manually
edit the packages.xml with each update and place the KB files into the
right share. Could be d
Jens Geile wrote:
So... What you're asking for is WSUS ;)
More or less, yes. But I unattended+wpkg is going to run off of a Linux server
and there wont be a Windows server in the network. So WSUS isnt an option.
I've read somewhere, that if you go to update.microsoft.com and install
a new v
> So... What you're asking for is WSUS ;)
More or less, yes. But I unattended+wpkg is going to run off of a Linux server
and there wont be a Windows server in the network. So WSUS isnt an option.
> It would be interesting to see wpkg modified to do the same thing, but I'm
> not sure if it will w
but it would be a lot better with a tool to
automate it all, which is what WSUS does.
-Tim
-Original Message-
From: Jens Geile [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 04, 2005 9:39 AM
To: wpkg; Tim Fournet
Subject: RE: [wpkg-users] Feature Request
> One alternative would be
> One alternative would be to slipstream all of your Office updates into your
> office install point. Not sure if that would be more work or not, but it
> should go faster.
Speed isnt an issue here. The problem is that i want to be able to install
updates _after_ Office was already installed. S
@lists.sourceforge.net
Subject: [wpkg-users] Feature Request
Hi,
been some time since I last had the chance to do some work on my
unattended+wpkg setup but this thing here is really bugging me and I
would _really_ like it to be implemented since it would make things _a
lot_ easier for all of us.
A
Hi,
been some time since I last had the chance to do some work on my
unattended+wpkg setup but this thing here is really bugging me and I would
_really_ like it to be implemented since it would make things _a lot_ easier
for all of us.
A current package entry would look something like this:
Sebastiaan Troost schrieb:
Dear Tomek,
After playing some more I still didn't resolve my problem with msoffice2003
sp1. The reg check doesn't seem to work... probably doing something wrong...
Anyway, the SP1 update for office can be found in the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Mic
ED] On Behalf Of Tomasz
Chmielewski
Sent: dinsdag 12 juli 2005 18:41
Cc: wpkg-users@lists.sourceforge.net
Subject: Re: [wpkg-users] Feature request: uninstall check for updates
[EMAIL PROTECTED] wrote:
> Hi there,
>
> Im trying to get all my software to work with wpkg and found a problem...
insdag 12 juli 2005 18:41
Cc: wpkg-users@lists.sourceforge.net
Subject: Re: [wpkg-users] Feature request: uninstall check for updates
[EMAIL PROTECTED] wrote:
> Hi there,
>
> Im trying to get all my software to work with wpkg and found a problem...
>
> I would like to see it possi
[EMAIL PROTECTED] wrote:
Hi there,
Im trying to get all my software to work with wpkg and found a problem...
I would like to see it possible to check for updates with the uninstall check.
It right now isnt possible to do so. (For example the MS office sp1).
"uninstall" check is checked before
Hi there,
Im trying to get all my software to work with wpkg and found a problem...
I would like to see it possible to check for updates with the uninstall check.
It right now isnt possible to do so. (For example the MS office sp1).
Thanks in advance,
Sebastiaan Troost
--
47 matches
Mail list logo
