Have you already tried that?
I think that the folder must exist in order to make this work.
That works, ofc. Logs all go to a \\servername\wpkg\logs folder.
What i would like is the program to put machine logs in subfolders of the
log folder in
David Petterson wrote:
If you can pass me that script i will be more than happy to use it
instead
of wasting hours trying to make psexec work with wpkg client. :)
I use a two parted script for this, they are not very pretty, but they
work! I have plans to do a version check to be able
I will probably solve the issue not using psexec (nobody seems to know why
it's not working via psexec and i can't wait weeks hoping that someone makes
a test and find what's wrong with psexec) but using a startup script
deployed via gdp (global domain policy). The instructions are basically the
Am 12.12.2011 12:11, schrieb chiddie:
I have 3 questions:
1. Logging: is it possible to make WPKG automatically create a folder with
the machine name in order to put each machine log in a different folder?
Example: now i have edited the config.xml in order to
* log everything ()
* create a log
If you can pass me that script i will be more than happy to use it instead
of wasting hours trying to make psexec work with wpkg client. :)
I use a two parted script for this, they are not very pretty, but they
work! I have plans to do a version check to be able to upgrade the WPKG
client to
David Petterson wrote:
Try running psexec with the -s variable to run as SYSTEM.
Cant you run the installation with your startup script in your domain?
I run a script to check if WPKG is installed, and it also make sure
older versions are uninstalled and replaced by current client
Hi David,
David Petterson wrote:
Try running psexec with the -s variable to run as SYSTEM.
Cant you run the installation with your startup script in your domain?
I run a script to check if WPKG is installed, and it also make sure
older versions are uninstalled and replaced by current
On 12/8/2011 10:13 AM, David Petterson wrote:
On 2011-12-07 18:11, chiddie wrote:
Hello, it's me again -.-
As the subject says, i'm trying to deploy WPKG client to some
computers over
the network in order to widen my tests environment.
I follwed the instructions:
- created the
On 12/9/2011 10:54 AM, Falko Trojahn wrote:
Hello,
The server from which i ran the psexec command runs Windows 2003 R2
x64,
while the target PC runs Windows XP x64.
So, again, what am i doing wrong?
Did you copy the files to C:\Temp on all the computers you want to
install them to?
If not,
Hello again,
The server from which i ran the psexec command runs Windows 2003 R2
x64,
while the target PC runs Windows XP x64.
So, again, what am i doing wrong?
I really don't know what else to try, i follwed the instructions step by
step (apart from putting the .xml files on the root
Try using this format for the command for psexec
psexec \\machinename or @host.xml -u domainname\user -p yourpassword
msiexec /i \\servername\folder\WPKG Client 1.3.9-x32.msi /qb
SETTINGSFILE=\\servername\folder\settings.xml
Make sure that your psexec user is a member of the domain admins or
On 2011-12-07 18:11, chiddie wrote:
Hello, it's me again -.-
As the subject says, i'm trying to deploy WPKG client to some computers over
the network in order to widen my tests environment.
I follwed the instructions:
- created the getcomputers.vbs file
- ran it and obtained the hosts.xml
Hello, it's me again -.-
As the subject says, i'm trying to deploy WPKG client to some computers over
the network in order to widen my tests environment.
I follwed the instructions:
- created the getcomputers.vbs file
- ran it and obtained the hosts.xml file
- copied the file in a C:\Temp
13 matches
Mail list logo
