[wpkg-users] Running wpkg.js as System Account

LAPLAUD François laplaud at sdis72.fr
Fri Jan 7 13:32:19 CET 2011

I have maybe a reason that i can't really explain : the more I make tests, the more i find strange behaviours, asif it was a server problem.

I am getting plenty of error messages like this one for many computers running wpkg.js 
Event ID 4625 (authentication failure)

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
+ <System>
  <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" /> 
  <TimeCreated SystemTime="2011-01-07T12:11:59.706889900Z" /> 
  <Correlation /> 
  <Execution ProcessID="540" ThreadID="13936" /> 
  <Security /> 
- <EventData>
  <Data Name="SubjectUserSid">S-1-0-0</Data> 
  <Data Name="SubjectUserName">-</Data> 
  <Data Name="SubjectDomainName">-</Data> 
  <Data Name="SubjectLogonId">0x0</Data> 
  <Data Name="TargetUserSid">S-1-0-0</Data> 
  <Data Name="TargetUserName">Administrateur</Data> 
  <Data Name="TargetDomainName">PC1007-061</Data> 
  <Data Name="Status">0xc000006d</Data> 
  <Data Name="FailureReason">%%2313</Data> 
  <Data Name="SubStatus">0xc000006a</Data> 
  <Data Name="LogonType">3</Data> 
  <Data Name="LogonProcessName">NtLmSsp</Data> 
  <Data Name="AuthenticationPackageName">NTLM</Data> 
  <Data Name="WorkstationName">PC1007-061</Data> 
  <Data Name="TransmittedServices">-</Data> 
  <Data Name="LmPackageName">-</Data> 
  <Data Name="KeyLength">0</Data> 
  <Data Name="ProcessId">0x0</Data> 
  <Data Name="ProcessName">-</Data> 
  <Data Name="IpAddress"></Data> 
  <Data Name="IpPort">51790</Data> 

P.S : The file server is running Windows Server 2008 R2


-----Message d'origine-----
De : Rainer Meier [mailto:r.meier at wpkg.org] 
Envoyé : jeudi 6 janvier 2011 17:25
À : LAPLAUD François
Cc : Falko Trojahn; wpkg-users at lists.wpkg.org
Objet : Re: [wpkg-users] Running wpkg.js as System Account


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 below :
> psexec \\pc1007-057 -s cscript \\srv-wds01.sdis72.fr\wpkg-w7\wpkg.js /synchronize /debug
> 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 DENIED; falling back to local logging: null

This line is interesting. There was a problem writing to the defined log
directory (defined in settings.xml) on your network share. So WPKG should fall
back to local logging (in %TEMP%). BUt it should not display "null" here. This
might cause the error. You might have encountered a bug in wpkg.js.

I will investigate. Work-around: Specify writeable location for your logs either
via command-line or via settings.xml so WPKG does not have to fall back to local

NOTE: THe initial local log file is always written in order to write log entries
about issues encountered before settings.xml is read (where the final log path
is specified). However the fallback seems to be faulty.


More information about the wpkg-users mailing list