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

[LAPLAUD François]

After lots of testings, i think one of my problems is the fact i scheduled short period (2 minutes) for the scheduled task. Multiplied by about 100 testing computers, my server generate authentication error messages maybe because there are too many auth/deauth request during a short period....

I am now trying to increase to 15 minutes the execution interval of the task (I will increase it more later in production, but to see if all is working, a short interval is easier...).

I am logging on the fileserver to have a view of which computer are "responding" or not.

Now, I am getting another problem that I can't understand (maybe I should post in a new thread (if so please let me know)

Every computer which run the task will never end its execution.
When I look into the logfile with is on the fileserver, here is what I can see :


DEBUG   : Initialized temporary local log file: C:\WINDOWS\TEMP\wpkg-logInit.log
DEBUG   : Initializing new log file: \\srv-wds01.sdis72.fr\wpkg\Logs\degre067f.XP.log
DEBUG   : Reboot-Cmd is standard.
DEBUG   : WPKG 1.1.2 starting...
DEBUG   : Base directory is '\\srv-wds01.sdis72.fr\wpkg-xp'.
DEBUG   : Log level is 255
DEBUG   : Trying to read XML file: \\srv-wds01.sdis72.fr\wpkg-xp\profiles.xml
DEBUG   : Successfully loaded XML file: \\srv-wds01.sdis72.fr\wpkg-xp\profiles.xml
DEBUG   : Trying to read XML files from directory: \\srv-wds01.sdis72.fr\wpkg-xp\profiles
DEBUG   : Specified XML directory does not exist: \\srv-wds01.sdis72.fr\wpkg-xp\profiles
DEBUG   : Trying to read XML file: \\srv-wds01.sdis72.fr\wpkg-xp\hosts.xml
DEBUG   : Successfully loaded XML file: \\srv-wds01.sdis72.fr\wpkg-xp\hosts.xml
DEBUG   : Trying to read XML files from directory: \\srv-wds01.sdis72.fr\wpkg-xp\hosts
DEBUG   : Specified XML directory does not exist: \\srv-wds01.sdis72.fr\wpkg-xp\hosts
DEBUG   : Trying to read XML file: \\srv-wds01.sdis72.fr\wpkg-xp\packages.xml
DEBUG   : Successfully loaded XML file: \\srv-wds01.sdis72.fr\wpkg-xp\packages.xml
DEBUG   : Trying to read XML files from directory: \\srv-wds01.sdis72.fr\wpkg-xp\packages
DEBUG   : Found network service: {A97EF47F-A726-4BBC-8D01-723F006793FB}
DEBUG   : Reading DHCP address.
DEBUG   : Found DHCP address: 192.168.0.101
DEBUG   : Profiles applying to the current host:|defaut2|
DEBUG   : Reading settings file: C:\WINDOWS\system32\wpkg.xml
DEBUG   : Trying to read XML file: C:\WINDOWS\system32\wpkg.xml
DEBUG   : Successfully loaded XML file: C:\WINDOWS\system32\wpkg.xml
DEBUG   : Saving current environment

And nothing is written after this ...

Would one of you have any hints on what the script do after the last message and what could cause my troubles ?

Thanks by advance




Laplaud François


-----Message d'origine-----
De : LAPLAUD François 
Envoyé : vendredi 7 janvier 2011 13:32
À : 'Rainer Meier'
Cc : Falko Trojahn; wpkg-users at lists.wpkg.org
Objet : RE: [wpkg-users] Running wpkg.js as System Account

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}" /> 
  <EventID>4625</EventID> 
  <Version>0</Version> 
  <Level>0</Level> 
  <Task>12544</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8010000000000000</Keywords> 
  <TimeCreated SystemTime="2011-01-07T12:11:59.706889900Z" /> 
  <EventRecordID>776876</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="540" ThreadID="13936" /> 
  <Channel>Security</Channel> 
  <Computer>srv-wds01.sdis72.fr</Computer> 
  <Security /> 
  </System>
- <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">192.168.100.77</Data> 
  <Data Name="IpPort">51790</Data> 
  </EventData>
  </Event>

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

Cheers,


-----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

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 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
logging.

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.


br,
Rainer