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
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 i
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
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
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
s
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
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 c
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 o
Hi,
Ok, now i'm even more confused XD
- I went to the target machine
- I opened a dos prompt
- I went to the pstools directory (c:\pstools)
- I ran the command "psexec -h -u domain\useradmin -p password cmd.exe:
another command prompt opened
- at the NEW prompt i ran the command "net use x:
\\s
Hello Claudio,
On 12/9/2011 2:29 PM, Claudio Ghirardi wrote:
On 12/9/2011 1:47 PM, Falko Trojahn wrote:
I'd suggest to go to a target machine, run the psexec command locally
using cmd.exe instead of msiexec, and then within cmd.exe run msiexec
manually to get an idea what's wrong.
I don't un
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 direct
On 2011-12-09 12:30, Claudio Ghirardi wrote:
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 co
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,
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 fil
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, put them on a network share and install from t
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 getcomputers
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 fil
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 folde
18 matches
Mail list logo
