Re: [wpkg-users] ERROR: is null or not an object

Thanks that has worked. On 1 July 2011 12:05, Malte Starostik wrote: > Am Freitag, 1. Juli 2011, 12:45:35 schrieb Charles Gargent: > > Hi > > > > I get an error in my log file like so: > > > > 2011-07-01 11:16:36, ERROR : Error evaluating package check for

[wpkg-users] ERROR: is null or not an object

Hi I get an error in my log file like so: 2011-07-01 11:16:36, ERROR : Error evaluating package check for package > 'Microsoft .NET Framework': 'null' is null or not an object The check for that package is like so: as suggested by this msdn site

Re: [wpkg-users] Chrome Enterprise

I am using the following, this isnt the problem though as the log file is generated so i know it is trying to install On 8 June 2011 14:09, John Danks wrote: > Can you post the package definition you're using? > > On Wed, Jun 8, 2011 at 3:

[wpkg-users] Chrome Enterprise

Hi, I am trying to deploy Google Chrome by following the instructions from here http://wpkg.org/Google_Chrome . Unfortunately it doesn't install and I keep getting an error 1722 I have added logging to the install command and below is the section of the log where the error lies. Has anyone had

Re: [wpkg-users] Windows 7 wpkg launch with AD startup script

Yes the network is connected because the GP is set to run a startup script, there is a logging in it which works so the script is being run, just not the wpkg.js command On 4 November 2010 20:02, Charles Gargent wrote: > Yes the network is connected because the GP is set to run a star

[wpkg-users] Windows 7 wpkg launch with AD startup script

Hi I am testing the wpkg script on Windows 7, it seems to run fine when logged in and executed from the command line but when I run the same command from a batch file as a start up script in a group policy the command doesnt run nor does it give any indication of what went wrong. I know the startu

Re: [wpkg-users] Registry Check failing

On 2 August 2010 16:45, Falko Trojahn wrote: > Hi, >> >> Neither the registry path >> >> 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UpgradeCodes\AA5D9C68C00F12943B2F6CA09FE28244' >> nor its expanded value of >> >> 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UpgradeCode

Re: [wpkg-users] Registry Check failing

On 2 August 2010 13:21, wrote: > > >> > path="HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer >> \UpgradeCodes\AA5D9C68C00F12943B2F6CA09FE28244" >> /> >> > >> Neither the registry path >> 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer >> \UpgradeCodes\AA5D9C68C00F12943B2F6CA09

[wpkg-users] Registry Check failing

Hi, I have a registry check as follows: The error message I get in the logs: Neither the registry path 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UpgradeCodes\AA5D9C68C00F12943B2F6CA09FE28244' nor its expanded value of 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Up

Re: [wpkg-users] Event Log format

2009/11/19 Rainer Meier : > Hi Charles, > > Charles Gargent wrote: >> Thanks for that, I never really looked at this setting. I have always >> left in on by default. I will have to test a bit further as to what is >> going on as it doesnt work. I dont fully understand wh

Re: [wpkg-users] Event Log format

2009/11/19 Rainer Meier : > Hi Charles, > > Charles Gargent wrote: >> Thanks for that, after I posted I think I did your last suggestion >> >> I add the following in line 5753 of v1.1.2 >> description = description.replace(new >> RegExp("(\\r\\n)|(\\n\

Re: [wpkg-users] Event Log format

2009/11/19 Rainer Meier : > Hi Charles, > > Charles Gargent wrote: >> I export the eventlogs from each client to a central log on the server >> so I can parse them latter. Unfortunately the line breaks in the >> message come through with the export. I have made a star

[wpkg-users] Event Log format

Hi, I export the eventlogs from each client to a central log on the server so I can parse them latter. Unfortunately the line breaks in the message come through with the export. I have made a start on changing the script and removing the line breaks, does anyone know where all the occurrences are

[wpkg-users] Package Problems

Hi, I have noticed a problem when uninstalling NSIS installer products. When you run the command csscript wpkjg,js /remove:Inkscape whilst a user is logged in the final command 'cmd /c rmdir /s /q "%programfiles%\Inkscape"' does remove the the folder. However if the command is run in a system

Re: [wpkg-users] Silent installs of MSI or exe files.

Works on my XP machine and my 7 RC1 machine 2009/8/12 Rainer Meier : > Hi Charles, > > Charles Gargent wrote: >> try %WINDIR% > > I think %windir% has been used in pre-Windows NT times while starting from > Windows NT %SystemRoot% has been introduced. > &

Re: [wpkg-users] Silent installs of MSI or exe files.

try %WINDIR% 2009/8/11 David Christensen : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Rainer Meier wrote: >> Hi David, >> >> David Christensen wrote: >>> Thanks for the help with this, looks like I got it working.  The file >>> needed to be installed under C:\Windows, I had to specify t

Re: [wpkg-users] Silent installs of MSI or exe files.

> Is anyone familiar with modifying msi files by way of mst to do silent > installs, is this even possible? If you run msiexec /i __PATHTOPACKAGE__ /qn The /qn will run the install with no user interface, ie it is silent, however if you want it unattended you may need to supply extra properties o

Re: [wpkg-users] load balancing

you could make up 5 different profiles and assign 300 clients to each of those profiles and then add them 1 day at a time, then by friday they will all be done 2009/7/27 Sergey Karapetyan : > hello again :) > i have 1500 wpkg-clients, all users start working at 9am and i need > install\reinstall

Re: [wpkg-users] xml Elements and attributes

2009/7/15 Charles Gargent : > 2009/7/15 Rainer Meier : >> Hi Charles, >> >> Charles Gargent wrote: >>> IMHO it makes more sense to have everything one way or t'other, I >>> appreciate that converting everything to elements would break >>>

Re: [wpkg-users] xml Elements and attributes

2009/7/15 Rainer Meier : > Hi Charles, > > Charles Gargent wrote: >> 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 e

Re: [wpkg-users] xml Elements and attributes

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 >> >> instead of >> >> >> Can you change all the data to b

[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 instead of Can you change all the data to be stored in an element rather than some attributes some elements? ie 7-Zip 7-Zip 4.57 uninstall etc..

[wpkg-users] Using bat files for remove procedure

If I specify a bat file as the remove command and then change the bat file before the package has removed on all hosts where it is installed, what happens when the hosts that havent yet run the remove command try and run the remove command that essentially contains a different bat file. Has anyone

[wpkg-users] Variable Dependencies

Hi I have a package for PowershellCX which is platform independant. How can I specify Powershell as a dependency when I have a package for Powershell XP and a package for Powershell 2K3. I could make 2 packages for PowershellCX the only difference between them being the dependancy node, but is the

Re: [wpkg-users] re the post: WPKG Server 1.1.0 breaks packages working in 1.0.4

well I think I have cobbled a solution together, it may not be technically correct but it works for me change line 5904 from cmd = "%COMSPEC% /c " + cmd; to cmd = "%COMSPEC% /c " + "\"" + cmd + "\""; 2009/5/28 Charles Gargent : > re the pos

[wpkg-users] re the post: WPKG Server 1.1.0 breaks packages working in 1.0.4

re the post: WPKG Server 1.1.0 breaks packages working in 1.0.4 I have experienced this error also. I have done some investigation, this command fails when it used to work in 1.0.4: however if you take the spaces out of the path names and remove the inner quotes it works here is the working com