Am 28.12.2010 19:29, schrieb Mark Lintern:
Does WPKG have the capability to inventory product keys off of the
machines it's running on?
Sorry for the late reply. We do it the following way, since OCS is not
capable of reading all needed keys:
package
id=keyfinder
name=Find all
Hello,
I am trying to run wpkg.js from a scheduled task running as System Account.
I am getting an access denied error message on line 5351.
It seems to be because the script tries to init
var tempLogPath = new
ActiveXObject(WScript.Shell).ExpandEnvironmentStrings(%TEMP%\\wpkg-logInit.log);
Hi again,
In fact i was wrong sorry, the TEMP var is correctly initialized...
My problem is totally different from what I previously said :
I am making tests of remotely running the wpkg.js script using System Account
by using psexec like below :
psexec \\pc1007-057 -s cscript
Hi,
On 06.01.2011 16:45, LAPLAUD François wrote:
Hi again,
In fact i was wrong sorry, the TEMP var is correctly initialized...
My problem is totally different from what I previously said :
I am making tests of remotely running the wpkg.js script using System Account
by using psexec like
Am 06.01.2011 16:45, schrieb LAPLAUD François:
Hi again,
In fact i was wrong sorry, the TEMP var is correctly initialized...
My problem is totally different from what I previously said :
I am making tests of remotely running the wpkg.js script using System Account
by using psexec like below
Mandi! Malte Starostik
In chel di` si favelave...
There is one requirement that might get in the way: machine authentication
requires kerberos, so you need an AD domain, either with a Windows 2000+ DC
or
Samba 4. I haven't tried the latter yet, but I certainly will some day. A
Am Donnerstag, 6. Januar 2011, 23:45:41 schrieb Marco Gaiarin:
Yes, i know that in AD machine account work, but i can confirm that, at
least for samba 3.2, in nt-like domain not... ;(((
Right, and it cannot work, regardless of samba version. Windows clients will
only authenticate with their
http://bugzilla.wpkg.org/show_bug.cgi?id=176
--- Comment #13 from Matthias matthias.martetschlae...@at.fujitsu.com ---
I received the information, that everything works fine with version 1.3.14 and
this version also solves the problem for me.
The service does not crash anymore and logon delay
2011/1/6 LAPLAUD François lapl...@sdis72.fr
...
All is going well except that I get this error message :
[...]
Initialized temporary local log file: C:\Windows\TEMP\wpkg-logInit.log
Initializing new log file: \\srv-wds01.sdis72.fr\wpkg\Logs\pc1007-057.W7.log
Failed to open log file: ACCESS
Just a wild guess: did you use double \\ in your config.xml?
param name='log_file_path'
value='server.smi-softmark.de\\install\\logs' /
Salut,
Falko
Hi Falko, yes, here is the way it is written in my config.xml
param name='log_file_path' value='srv-wds01.sdis72.fr\\wpkg\\Logs' /
10 matches
Mail list logo