Re: [wpkg-users] Behaviour of WPKG

Hello Rainer, I agree to most of your arguments. But there are some circumstances which cause problems. Most of my users are road warriors. Although they have a VPN connection to our company network, a software update over VPN is impossible (takes too long, blocks the line). So, I added a

Re: [wpkg-users] Shutdowns with option -noreboot

Hello Rainer, sorry that I was not correct in the syntax but the reboot occures if I use /noreboot. So, any idea? br Johannes Rainer Meier r.me...@wpkg.org 14.07.2009 18:57 To: johannes.b...@evidian.com cc: wpkg-users@lists.wpkg.org Subject:Re:

Re: [wpkg-users] Shutdowns with option -noreboot

johannes.b...@evidian.com wrote: Hello Rainer, sorry that I was not correct in the syntax but the reboot occures if I use /noreboot. Could you provide a full debug log? PS. please fix your mailer, it doesn't seem to quote correctly. -- Tomasz Chmielewski http://wpkg.org

Re: [wpkg-users] msiexec 1619 error in Boot Camp but not in Parallels

Hi I'm in the middle of implementing WPKG to manage the Windows side on a bunch of Macs running Boot Camp. I've been doing my testing on an instance of Windows XP in Parallels on my own machine without a problem. However, when I install the WPKG client in Boot Camp and import the settings

Re: [wpkg-users] Shutdowns with option -noreboot

johannes.b...@evidian.com schrieb: Hello, some of my users reported shutdowns during softwareupdate, although wpkg is started with the parameter NOREBOOT. Any idea? Hello, WPKG relies on the individual installers to give a return code that indicates reboot required, but *do not*

[wpkg-users] xml Elements and attributes

Hi In the packages xml file the exit code data is stored in an element, can you change it to be stored in an attribute? ie remove cmd='msiexec /x {23170F69-40C1-2701-0457-0100} /qn /norestart' exitcode='any' / instead of remove cmd='msiexec /x {23170F69-40C1-2701-0457-0100} /qn

Re: [wpkg-users] msiexec 1619 error in Boot Camp but not in Parallels

On Jul 15, 2009, at 4:05 AM, Falko Trojahn wrote: Hi I'm in the middle of implementing WPKG to manage the Windows side on a bunch of Macs running Boot Camp. I've been doing my testing on an instance of Windows XP in Parallels on my own machine without a problem. However, when I install the

Re: [wpkg-users] xml Elements and attributes

Hi Charles, Charles Gargent wrote: Hi In the packages xml file the exit code data is stored in an element, can you change it to be stored in an attribute? ie remove cmd='msiexec /x {23170F69-40C1-2701-0457-0100} /qn /norestart' exitcode='any' / instead of remove cmd='msiexec /x

Re: [wpkg-users] msiexec 1619 error in Boot Camp but not in Parallels

Am Mittwoch, 15. Juli 2009 19:36:06 schrieb Patrick Lee: I've tried running the installer locally by having my package install from a local drive but I still get the same 1619 error. I've started working with a fresh install of XP and it seems to be working so I think that my current Windows

Re: [wpkg-users] xml Elements and attributes

Charles Gargent charlesgarg...@gmail.com writes: Hi Hello, In the packages xml file the exit code data is stored in an element, can you change it to be stored in an attribute? ie remove cmd='msiexec /x {23170F69-40C1-2701-0457-0100} /qn /norestart' exitcode='any' / instead of

Re: [wpkg-users] xml Elements and attributes

IMHO it makes more sense to have everything one way or t'other, I appreciate that converting everything to elements would break compatability, so would it be possible to convert the exitcode and reboot data to an attribute like so remove cmd=' some command' exitcode='any' reboot='delayed' /

Re: [wpkg-users] xml Elements and attributes

Hi Charles, Charles Gargent wrote: Can you point me in the right direction for exporting the xml files into a database. I would like a web interface/reporting feature. I have looked at wpkgexpress however I would rather have the xml files taken from a file share than a web connection.