Re: [wpkg-users] Running wpkg.js as System Account
Hi again, My problems seems to be resolved. For Rainer, its not a bug... My permission denied messages were due to simultaneous file access... When the I was doing wrong deployment packages, sometimes wpkg was idling in background waiting for user interaction wich never happends. In this state, when the scheduled task was run again, it tried to access again the log file and was getting a permission denied error message. I had another problem : for my testing purposes, my scheduled task was running every 2 minutes on 200 computers. I encountered authentication problems from the fileserver (2043 error id in the security event log) After increasing the scheduled task interval (15 minutes) it has been fixed. Now all is working well. I only need another thing : add a random waiting time before the script tries to install packages. I will post my modifications of the script if someone ask for. Thanks for your help. This wpkg tool is really great. BTW I now also use the wpkg create report tool which is great too. Cheers, Laplaud François De : wpkg-users-boun...@lists.wpkg.org [mailto:wpkg-users-boun...@lists.wpkg.org] De la part de Troy Hamilton Envoyé : jeudi 6 janvier 2011 18:35 À : wpkg-users@lists.wpkg.org Objet : Re: [wpkg-users] Running wpkg.js as System Account 2011/1/6 LAPLAUD François ... 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 WPKG 1.1.2 starting... Base directory is '\\srv-wds01.sdis72.fr\wpkg-w7'. [...] I have checked shares and NTFS rights and they seems correct. I then types the following command : psexec \\pc1007-057 -s cmd /c echo test > \\srv-wds01.sdis72.fr\wpkg\Logs\pc1007-057.W7.log And this last command works perfectly (the log file is created... with the text "test" in it) Your echo test does seem to indicate that your rights on the server share are correct, which is kind of puzzling. You might try actually logging into a workstation and running your command: cscript \\srv-wds01.sdis72.fr\wpkg-w7\wpkg.js /synchronize /debug from within a SYSTEM user command prompt (http://wpkg.org/SYSTEM_user_Command_Prompt). I use the same method that you are attempting using beyondexec (http://www.beyondlogic.org/solutions/remoteprocess/BeyondExec.htm), but I don't remember encountering this error. Cheers, Troy - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Running wpkg.js as System Account
2011/1/7 LAPLAUD François > Yes indeed, > > Here are my needs : > - a working wpkg ( ;-) ) > - possibility to run wpkg periodically to be able to deploy packages in > background while users are working. > I use CRON (http://www.kalab.com/freeware/cron/cron.htm) to do this. I prefer these native versions to PyCron since they don't require a Python installation. For running WPKG, I use the crons.exe version which installs itself as a service. After copying crons.exe and a crontab file to C:\WINDOWS\SYSTEM32, I just run these two commands: c:\windows\system32\crons.exe /install c:\windows\system32\sc.exe start CRON And here is an example of the crontab that I use (look out for wrapped lines below): - # Basic crontab format: # # + minute (0 - 59) # | +- hour (0 - 23) # | | +-- day of month (1 - 31) # | | | +--- month (1 - 12) # | | | | + day of week (0 - 6) (Sunday=0) # | | | | | # * * * * * command to be executed # refresh the crontab file every 10 minutes 0,10,20,30,40,50 * * * * c:\windows\system32\xcopy.exe /y "\\myserver\myshare\APPS\cron\crontab" "c:\windows\system32" # run wpkg.bat at 10pm, midnight, and 2am each day 0 22,0,2 * * * c:\windows\system32\cmd.exe /c \\myserver\myshare\APPS \wpkg\wpkg.bat - Now this takes care of the scheduled after hours synchronization. And for ad-hoc installations during business hours, I can just add another line to the crontab file to run wpkg for installing a particular package: #55 9 * * * cmd.exe /c \\myserver\myshare\apps\wpkg\wpkg.bat urgent-package All of my workstations will pull down the new copy of the crontab file within 10 minutes, and then they will run wpkg at 9:55 AM in this case to install "urgent-package". After that time has passed, I can remove the line from the crontab file so that it doesn't run everyday after that. Of course, I also use beyondexe or psexec sometimes if I just have a few workstations to work with. By the way, I like CRON better than scheduled tasks because it's much easier to copy out a new crontab file than to modify the scheduled task(s). I also remember having some issues with the scheduled tasks not running reliably. If I need to use scheduled tasks, why would I run a service wich will in > return run a script whereas I can run that script directly ? At one point I installed a "custom" wpkg service, but I abandoned that when I implemented cron. The only advantage of the service is that I used setacl.exe to modify the permissions of the service so that limited users could start and stop it. - when the scheduled tasked is about to run wpkg, I would like it to wait > for some random time between 1 and 30 minutes for instance so that the > network is not overloaded. (I suppose this part will need little > modifications of the wpkg.js script itself but seems to be a quite easy one) > I've thought of that before, too, and I think I may modify my wpkg.bat file as follows (note the "set /a delay" line: wpkg.bat *-* @echo off set WPKGROOT=%~dp0 CALL "%~dp0setServer.bat" set SOFTWARE=\\%SERVER%\software IF NOT EXIST %SOFTWARE% EXIT /B 1 c:\windows\system32\msiexec.exe /unreg c:\windows\system32\msiexec.exe /regserver IF EXIST c:\windows\system32\wpkg.xml DEL /Q /F c:\windows\system32\wpkg.xml set PATH=c:\windows;c:\windows\system32;c:\windows\system32\wbem;%WPKGROOT%\tools;%PATH% :: random number of seconds between 1 and 1800 (30 minutes) set /a delay=%random%%1800+1 :: sleep.exe from gnuwin32 %WPKGROOT%\tools\sleep.exe %delay% IF [%1]==[] ( c:\windows\system32\cscript.exe //nologo /E:JScript %WPKGROOT%\wpkg.js /synchronize /noremove /quiet /nonotify /sendStatus /logLevel:23 /log_file_path:\\myserver\work\log\wpkg /logfilePattern:[HOSTNAME]-[][MM][DD]-[hh][mm].log ) ELSE ( IF [%2]==[force] ( c:\windows\system32\cscript.exe //nologo /E:JScript %WPKGROOT%\wpkg.js /forceinstall /install:%1 /noremove /quiet /nonotify /sendStatus /logLevel:23 /log_file_path:\\myserver\work\log\wpkg /logfilePattern:[HOSTNAME]-[][MM][DD]-[hh][mm].log ) ELSE ( c:\windows\system32\cscript.exe //nologo /E:JScript %WPKGROOT%\wpkg.js /install:%1 /noremove /quiet /nonotify /sendStatus /logLevel:23 /log_file_path:\\myserver\work\log\wpkg /logfilePattern:[HOSTNAME]-[][MM][DD]-[hh][mm].log ) ) set year=%date:~10,4% set month=%date:~4,2% set day=%date:~7,2% set tm=%time:~0,8% set tm=%tm::=-% set tm=%tm: =% IF EXIST c:\windows\system32\wpkg.xml RENAME c:\windows\system32\wpkg.xml wpkg-%year%-%month%-%day%-%tm%.xml - Hope this helps, Troy - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
Re: [wpkg-users] Running wpkg.js as System Account
- WPKG Client can run wpkg at shutdown. - Scheduled tasks even for the System account can be created remotely without the need for psexec. See the schtasks command. (But note that schtasks depends on system language and version.) This is how I trigger wpkg (client) deployment remotely. - Both scheduled tasks and wpkg client (the service) can be triggered remotely (by schtasks or by sc). Actually I use WPKG Client on the clients and a few CMD scripts on the management server. LAPLAUD François schrieb am 07.01.2011 15:50: It's not possible in my organization to have every computer running deployment script at startup : too many computers startup at almost the same time. Some packages will be quite big and, as said before, WAN (understand "slow" interco network) links must have a random waiting time because if there are only 4 or 10 computer booting during a 15 minutes delay on a 4Mbits and there are 10 MB or more package deployed to thoses machines, the best way would be for me to not deploy at boot, but later cause as you said, deploying software when users are working won't slow down their computers thanks to its perf. I think a service would be usefull if it could add features like "agents" usually do ie : - wake up / force package deployment remotely. - periodic "ping" to check alive computers - and best of all, be able to design a "master" computer per subnet storing the whole packages and sharing them with local neighboors to not overload the network. Anyway, it's just my opinion ;) -Message d'origine- De : Natxo Asenjo [mailto:natxo.ase...@gmail.com] Envoyé : vendredi 7 janvier 2011 15:30 À : LAPLAUD François Cc : wpkg-users@lists.wpkg.org Objet : Re: [wpkg-users] Running wpkg.js as System Account 2011/1/7 LAPLAUD François: Yes indeed, Here are my needs : - a working wpkg ( ;-) ) I would start with this. Just follow the wiki http://wpkg.org/WPKG_QUICK_INSTALL guide. - possibility to run wpkg periodically to be able to deploy packages in background while users are working. For my part, I won't force shutdown, but when I need it, I will add an install cmd in my packages using msg.exe telling the user to Reboot when he can to complete an update. (to run it periodically I thought about scheduled tasks. If I need to use scheduled tasks, why would I run a service wich will in return run a script whereas I can run that script directly ? in both cases I will have to create a scheduled task...) No, if you have a service you do not need to create a scheduled job. That's the point of running a service, it runs automatically after booting. You can create a job to run at boot time, but that is not a service. You can have both. While I can understand you do not want to have both, it will be easier for you to have both. Bootstrap the client installation so you know it's working, then install scheduled jobs with it to run it periodically. This is redundancy, it can never hurt. We run our wpkg and our cfengine frameworks like this. Besides, the wpkgservice is not a typical one. It does not reread its config continually. it just runs after boot and then sits there doing nothing. It will not consume any significant resources. - when the scheduled tasked is about to run wpkg, I would like it to wait for some random time between 1 and 30 minutes for instance so that the network is not overloaded. (I suppose this part will need little modifications of the wpkg.js script itself but seems to be a quite easy one) If you run it as a service you do not need to worry about this. Not everybody turns their pc on at the same time. In the time we have been running this, I have not seen significant problems even with large packages (well, we do have fast networks, that helps too). We are not deploying it to wan offices with slow links. If you have slow wan links, then this could indeed be a problem with large software packages. What I like about wpkg is that it runs quite fast, so usually everything is done while the user is getting some coffee after turning their pc on. With our new workstations you really need to know something is being installed because they are so fast that I usually have to check the event log to see any activity, it's done before I know it. - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Running wpkg.js as System Account
Am 07.01.2011 16:38, schrieb 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) > ... > 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 Could you please try the latest wpkg.js release if it does the same? http://wpkg.svn.sourceforge.net/viewvc/wpkg/wpkg/stable/1.1/wpkg.js?revision=124 Here is the revision log if you need it: http://wpkg.svn.sourceforge.net/viewvc/wpkg/wpkg/stable/1.1/wpkg.js?view=log Falko - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Running wpkg.js as System Account
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@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)
http://schemas.microsoft.com/win/2004/08/events/event";>
+
4625
0
0
12544
0
0x8010
776876
Security
srv-wds01.sdis72.fr
-
S-1-0-0
-
-
0x0
S-1-0-0
Administrateur
PC1007-061
0xc06d
%%2313
0xc06a
3
NtLmSsp
NTLM
PC1007-061
-
-
0
0x0
-
192.168.100.77
51790
P.S : The file server is running Windows Server 2008 R2
Cheers,
-Message d'origine-
De : Rainer Meier [mailto:r.me...@wpkg.org]
Envoyé : jeudi 6 janvier 2011 17:25
À : LAPLAUD François
Cc : Falko Trojahn; wpkg-users@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 ha
Re: [wpkg-users] Running wpkg.js as System Account
It's not possible in my organization to have every computer running deployment script at startup : too many computers startup at almost the same time. Some packages will be quite big and, as said before, WAN (understand "slow" interco network) links must have a random waiting time because if there are only 4 or 10 computer booting during a 15 minutes delay on a 4Mbits and there are 10 MB or more package deployed to thoses machines, the best way would be for me to not deploy at boot, but later cause as you said, deploying software when users are working won't slow down their computers thanks to its perf. I think a service would be usefull if it could add features like "agents" usually do ie : - wake up / force package deployment remotely. - periodic "ping" to check alive computers - and best of all, be able to design a "master" computer per subnet storing the whole packages and sharing them with local neighboors to not overload the network. Anyway, it's just my opinion ;) -Message d'origine- De : Natxo Asenjo [mailto:natxo.ase...@gmail.com] Envoyé : vendredi 7 janvier 2011 15:30 À : LAPLAUD François Cc : wpkg-users@lists.wpkg.org Objet : Re: [wpkg-users] Running wpkg.js as System Account 2011/1/7 LAPLAUD François : > Yes indeed, > Here are my needs : > - a working wpkg ( ;-) ) I would start with this. Just follow the wiki http://wpkg.org/WPKG_QUICK_INSTALL guide. > - possibility to run wpkg periodically to be able to deploy packages in > background while users are working. For my part, I won't force shutdown, but > when I need it, I will add an install cmd in my packages using msg.exe > telling the user to Reboot when he can to complete an update. (to run it > periodically I thought about scheduled tasks. If I need to use scheduled > tasks, why would I run a service wich will in return run a script whereas I > can run that script directly ? in both cases I will have to create a scheduled task...) No, if you have a service you do not need to create a scheduled job. That's the point of running a service, it runs automatically after booting. You can create a job to run at boot time, but that is not a service. You can have both. While I can understand you do not want to have both, it will be easier for you to have both. Bootstrap the client installation so you know it's working, then install scheduled jobs with it to run it periodically. This is redundancy, it can never hurt. We run our wpkg and our cfengine frameworks like this. Besides, the wpkgservice is not a typical one. It does not reread its config continually. it just runs after boot and then sits there doing nothing. It will not consume any significant resources. > - when the scheduled tasked is about to run wpkg, I would like it to wait for > some random time between 1 and 30 minutes for instance so that the network is > not overloaded. (I suppose this part will need little modifications of the > wpkg.js script itself but seems to be a quite easy one) If you run it as a service you do not need to worry about this. Not everybody turns their pc on at the same time. In the time we have been running this, I have not seen significant problems even with large packages (well, we do have fast networks, that helps too). We are not deploying it to wan offices with slow links. If you have slow wan links, then this could indeed be a problem with large software packages. What I like about wpkg is that it runs quite fast, so usually everything is done while the user is getting some coffee after turning their pc on. With our new workstations you really need to know something is being installed because they are so fast that I usually have to check the event log to see any activity, it's done before I know it. -- natxo - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Running wpkg.js as System Account
2011/1/7 LAPLAUD François : > Yes indeed, > Here are my needs : > - a working wpkg ( ;-) ) I would start with this. Just follow the wiki http://wpkg.org/WPKG_QUICK_INSTALL guide. > - possibility to run wpkg periodically to be able to deploy packages in > background while users are working. For my part, I won't force shutdown, but > when I need it, I will add an install cmd in my packages using msg.exe > telling the user to Reboot when he can to complete an update. (to run it > periodically I thought about scheduled tasks. If I need to use scheduled > tasks, why would I run a service wich will in return run a script whereas I > can run that script directly ? in both cases I will have to create a scheduled task...) No, if you have a service you do not need to create a scheduled job. That's the point of running a service, it runs automatically after booting. You can create a job to run at boot time, but that is not a service. You can have both. While I can understand you do not want to have both, it will be easier for you to have both. Bootstrap the client installation so you know it's working, then install scheduled jobs with it to run it periodically. This is redundancy, it can never hurt. We run our wpkg and our cfengine frameworks like this. Besides, the wpkgservice is not a typical one. It does not reread its config continually. it just runs after boot and then sits there doing nothing. It will not consume any significant resources. > - when the scheduled tasked is about to run wpkg, I would like it to wait for > some random time between 1 and 30 minutes for instance so that the network is > not overloaded. (I suppose this part will need little modifications of the > wpkg.js script itself but seems to be a quite easy one) If you run it as a service you do not need to worry about this. Not everybody turns their pc on at the same time. In the time we have been running this, I have not seen significant problems even with large packages (well, we do have fast networks, that helps too). We are not deploying it to wan offices with slow links. If you have slow wan links, then this could indeed be a problem with large software packages. What I like about wpkg is that it runs quite fast, so usually everything is done while the user is getting some coffee after turning their pc on. With our new workstations you really need to know something is being installed because they are so fast that I usually have to check the event log to see any activity, it's done before I know it. -- natxo - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Running wpkg.js as System Account
Yes indeed, Here are my needs : - a working wpkg ( ;-) ) - possibility to run wpkg periodically to be able to deploy packages in background while users are working. For my part, I won't force shutdown, but when I need it, I will add an install cmd in my packages using msg.exe telling the user to Reboot when he can to complete an update. (to run it periodically I thought about scheduled tasks. If I need to use scheduled tasks, why would I run a service wich will in return run a script whereas I can run that script directly ? in both cases I will have to create a scheduled task...) - when the scheduled tasked is about to run wpkg, I would like it to wait for some random time between 1 and 30 minutes for instance so that the network is not overloaded. (I suppose this part will need little modifications of the wpkg.js script itself but seems to be a quite easy one) If you have any other opinion to share please let me know, I am trying to deploy wpkg since 1 week so I don't have an enough global vision to decide wich is the best solution. François -Message d'origine- De : wpkg-users-boun...@lists.wpkg.org [mailto:wpkg-users-boun...@lists.wpkg.org] De la part de Natxo Asenjo Envoyé : vendredi 7 janvier 2011 13:43 À : wpkg-users@lists.wpkg.org Objet : Re: [wpkg-users] Running wpkg.js as System Account 2011/1/7 LAPLAUD François : > Yes, except that you have to install an MSI first I don't understand the need > to install specific software with problems which can be caused by this > specific software if Windows already handle all my needs : run a script > periodically and run it with system privileges. > But maybe I am missing something. well, maybe the fact that it is not working for you the way you are trying to do it :-). We are using the client with both xp as windows 7 workstations and 2003 and 2008r2 servers (bot x86 as x64) without any trouble. We also run it from scheduled tasks as well. And installing an msi is just as easy as it gets, specially if it's part of your unattended deployment. Besides, if you have a different setup than most people, it will be harder to find people to debug your problems (as you have found out). This is, of course, just my opinion. Interesting discussion, indeed. -- natxo - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Running wpkg.js as System Account
2011/1/7 LAPLAUD François : > Yes, except that you have to install an MSI first I don't understand the need > to install specific software with problems which can be caused by this > specific software if Windows already handle all my needs : run a script > periodically and run it with system privileges. > But maybe I am missing something. well, maybe the fact that it is not working for you the way you are trying to do it :-). We are using the client with both xp as windows 7 workstations and 2003 and 2008r2 servers (bot x86 as x64) without any trouble. We also run it from scheduled tasks as well. And installing an msi is just as easy as it gets, specially if it's part of your unattended deployment. Besides, if you have a different setup than most people, it will be harder to find people to debug your problems (as you have found out). This is, of course, just my opinion. Interesting discussion, indeed. -- natxo - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
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) http://schemas.microsoft.com/win/2004/08/events/event";> + 4625 0 0 12544 0 0x8010 776876 Security srv-wds01.sdis72.fr - S-1-0-0 - - 0x0 S-1-0-0 Administrateur PC1007-061 0xc06d %%2313 0xc06a 3 NtLmSsp NTLM PC1007-061 - - 0 0x0 - 192.168.100.77 51790 P.S : The file server is running Windows Server 2008 R2 Cheers, -Message d'origine- De : Rainer Meier [mailto:r.me...@wpkg.org] Envoyé : jeudi 6 janvier 2011 17:25 À : LAPLAUD François Cc : Falko Trojahn; wpkg-users@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 - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Running wpkg.js as System Account
Yes, except that you have to install an MSI first I don't understand the need to install specific software with problems which can be caused by this specific software if Windows already handle all my needs : run a script periodically and run it with system privileges. But maybe I am missing something. Cheers, Francois -Message d'origine- De : Falko Trojahn [mailto:nospam...@smi-softmark.de] Envoyé : vendredi 7 janvier 2011 12:35 À : LAPLAUD François Cc : wpkg-users@lists.wpkg.org Objet : Re: [wpkg-users] Running wpkg.js as System Account Hi, > Falko: > If I remember correctly, you use psexec. Could you make a test please, > using Wpkg Client? You could trigger Wpkg Client remotely, too, if you > just set the Wpkg Service to run "manual" and trigger the service start > via psexec. Wpkg client works flawlessly here on W7, just doesn't show > the messages on startup. That's why we are trying to get wpkg-gp running > on W7-64. > François: > In fact my problem is not related to Windows 7 exclusively. > I prefer not using wpkg-client because I don't want all my workstations to > deploy packages at system logon. That's why I recommended setting the wpkg client service to "manual" start. > I prefer using some scheduled task to be able to update machines during the > day without waiting for a reboot. > > I also don't want user notifications, except when needed (so I use the > notify=true parameters in packages definition when needed). My intention was not that you should install wpkg client on all machines - please test on one machine only, if the problem with the logfile is the same as with psexec. > And this way, I don't need to install anything more than a scheduled tasks. If the scheduled task does "net start wpkgservice" or runs wpkg.js itself - does this matter, isn't it the same? HTH Falko - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Running wpkg.js as System Account
Hi, > Falko: > If I remember correctly, you use psexec. Could you make a test please, > using Wpkg Client? You could trigger Wpkg Client remotely, too, if you > just set the Wpkg Service to run "manual" and trigger the service start > via psexec. Wpkg client works flawlessly here on W7, just doesn't show > the messages on startup. That's why we are trying to get wpkg-gp running > on W7-64. > François: > In fact my problem is not related to Windows 7 exclusively. > I prefer not using wpkg-client because I don't want all my workstations to > deploy packages at system logon. That's why I recommended setting the wpkg client service to "manual" start. > I prefer using some scheduled task to be able to update machines during the > day without waiting for a reboot. > > I also don't want user notifications, except when needed (so I use the > notify=true parameters in packages definition when needed). My intention was not that you should install wpkg client on all machines - please test on one machine only, if the problem with the logfile is the same as with psexec. > And this way, I don't need to install anything more than a scheduled tasks. If the scheduled task does "net start wpkgservice" or runs wpkg.js itself - does this matter, isn't it the same? HTH Falko - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Running wpkg.js as System Account
Hi, In fact my problem is not related to Windows 7 exclusively. I prefer not using wpkg-client because I don't want all my workstations to deploy packages at system logon. I prefer using some scheduled task to be able to update machines during the day without waiting for a reboot. I also don't want user notifications, except when needed (so I use the notify=true parameters in packages definition when needed). And this way, I don't need to install anything more than a scheduled tasks. Anyway, thanks -Message d'origine- De : Falko Trojahn [mailto:ftroj...@smi-softmark.de] Envoyé : vendredi 7 janvier 2011 09:57 À : LAPLAUD François Cc : Troy Hamilton; wpkg-users@lists.wpkg.org Objet : Re: [wpkg-users] Running wpkg.js as System Account Am 07.01.2011 08:50, schrieb LAPLAUD François: > 2011/1/6 LAPLAUD François >> ... >> 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 >> WPKG 1.1.2 starting... >> Base directory is '\\srv-wds01.sdis72.fr\wpkg-w7'. >> [...] >> >> I have checked shares and NTFS rights and they seems correct. >> I then types the following command : >> psexec \\pc1007-057 -s cmd /c echo test > >> \\srv-wds01.sdis72.fr\wpkg\Logs\pc1007-057.W7.log >> >> And this last command works perfectly (the log file is created... with the >> text "test" in it) >> >> Your echo test does seem to indicate that your rights on the server share >> are correct, which is kind of puzzling. > You might try actually logging >> into a workstation and running your command: >> >> cscript \\srv-wds01.sdis72.fr\wpkg-w7\wpkg.js /synchronize /debug >> >> from within a SYSTEM user command prompt >> (http://wpkg.org/SYSTEM_user_Command_Prompt). >> >> I use the same method that you are attempting using beyondexec >> (http://www.beyondlogic.org/solutions/remoteprocess/BeyondExec.htm), but I >> don't remember encountering this error. >> >> Cheers, >> >> Troy > I've tried to use the systemcmd.bat file to try running > \\srv-wds01.sdis72.fr\wpkg-w7\wpkg.js /synchronize /debug > And i am getting exactly the same behaviour. > > Could this Access Denied message be a Windows 7 restriction on wsh scripts > under System Account ? > Btw, I think I made a mistake by translating my error message the French > Error message I am getting is "Permission refusée" wich doesn't mean ACCESS > DENIED but maybe something more like PERMISSION DENIED. > If you have any clues ... > If I remember correctly, you use psexec. Could you make a test please, using Wpkg Client? You could trigger Wpkg Client remotely, too, if you just set the Wpkg Service to run "manual" and trigger the service start via psexec. Wpkg client works flawlessly here on W7, just doesn't show the messages on startup. That's why we are trying to get wpkg-gp running on W7-64. Salut, Falko -- Falko Trojahn fon +49-341-3581294 Dipl.-Ingenieur Netzwerke/Support fax +49-341-3581295 SMI Softmark Informationstechnologien GmbH Sitz: D-04416 Markkleeberg, Friedrich-Ebert-Str. 51 Registergericht: Amtsgericht Leipzig HRB 164 Geschäftsführer: Andreas Griesmann www.smi-softmark.de www.elektronisches-laborbuch.de - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Running wpkg.js as System Account
Am 07.01.2011 08:50, schrieb LAPLAUD François: > 2011/1/6 LAPLAUD François >> ... >> 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 >> WPKG 1.1.2 starting... >> Base directory is '\\srv-wds01.sdis72.fr\wpkg-w7'. >> [...] >> >> I have checked shares and NTFS rights and they seems correct. >> I then types the following command : >> psexec \\pc1007-057 -s cmd /c echo test > >> \\srv-wds01.sdis72.fr\wpkg\Logs\pc1007-057.W7.log >> >> And this last command works perfectly (the log file is created... with the >> text "test" in it) >> >> Your echo test does seem to indicate that your rights on the server share >> are correct, which is kind of puzzling. > You might try actually logging >> into a workstation and running your command: >> >> cscript \\srv-wds01.sdis72.fr\wpkg-w7\wpkg.js /synchronize /debug >> >> from within a SYSTEM user command prompt >> (http://wpkg.org/SYSTEM_user_Command_Prompt). >> >> I use the same method that you are attempting using beyondexec >> (http://www.beyondlogic.org/solutions/remoteprocess/BeyondExec.htm), but I >> don't remember encountering this error. >> >> Cheers, >> >> Troy > I've tried to use the systemcmd.bat file to try running > \\srv-wds01.sdis72.fr\wpkg-w7\wpkg.js /synchronize /debug > And i am getting exactly the same behaviour. > > Could this Access Denied message be a Windows 7 restriction on wsh scripts > under System Account ? > Btw, I think I made a mistake by translating my error message the French > Error message I am getting is "Permission refusée" wich doesn't mean ACCESS > DENIED but maybe something more like PERMISSION DENIED. > If you have any clues ... > If I remember correctly, you use psexec. Could you make a test please, using Wpkg Client? You could trigger Wpkg Client remotely, too, if you just set the Wpkg Service to run "manual" and trigger the service start via psexec. Wpkg client works flawlessly here on W7, just doesn't show the messages on startup. That's why we are trying to get wpkg-gp running on W7-64. Salut, Falko PS: Sorry for reposting - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Running wpkg.js as System Account
> Just a wild guess: did you use double "\\" in your config.xml? > > value='server.smi-softmark.de\\install\\logs' /> > > Salut, > Falko Hi Falko, yes, here is the way it is written in my config.xml - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Running wpkg.js as System Account
2011/1/6 LAPLAUD François > ... > 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 > WPKG 1.1.2 starting... > Base directory is '\\srv-wds01.sdis72.fr\wpkg-w7'. > [...] > > I have checked shares and NTFS rights and they seems correct. > I then types the following command : > psexec \\pc1007-057 -s cmd /c echo test > > \\srv-wds01.sdis72.fr\wpkg\Logs\pc1007-057.W7.log > > And this last command works perfectly (the log file is created... with the > text "test" in it) > > Your echo test does seem to indicate that your rights on the server share are > correct, which is kind of puzzling. > You might try actually logging into a > workstation and running your command: > > cscript \\srv-wds01.sdis72.fr\wpkg-w7\wpkg.js /synchronize /debug > > from within a SYSTEM user command prompt > (http://wpkg.org/SYSTEM_user_Command_Prompt). > > I use the same method that you are attempting using beyondexec > (http://www.beyondlogic.org/solutions/remoteprocess/BeyondExec.htm), but I > don't remember encountering this error. > > Cheers, > > Troy I've tried to use the systemcmd.bat file to try running \\srv-wds01.sdis72.fr\wpkg-w7\wpkg.js /synchronize /debug And i am getting exactly the same behaviour. Could this Access Denied message be a Windows 7 restriction on wsh scripts under System Account ? Btw, I think I made a mistake by translating my error message the French Error message I am getting is "Permission refusée" wich doesn't mean ACCESS DENIED but maybe something more like PERMISSION DENIED. If you have any clues ... Cheers, Francois - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Running wpkg.js as System Account
2011/1/6 LAPLAUD François > ... > 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 > WPKG 1.1.2 starting... > Base directory is '\\srv-wds01.sdis72.fr\wpkg-w7'. > [...] > > I have checked shares and NTFS rights and they seems correct. > I then types the following command : > psexec \\pc1007-057 -s cmd /c echo test > \\srv-wds01.sdis72.fr > \wpkg\Logs\pc1007-057.W7.log > > And this last command works perfectly (the log file is created... with the > text "test" in it) > > Your echo test does seem to indicate that your rights on the server share are correct, which is kind of puzzling. You might try actually logging into a workstation and running your command: cscript \\srv-wds01.sdis72.fr\wpkg-w7\wpkg.js /synchronize /debug from within a SYSTEM user command prompt ( http://wpkg.org/SYSTEM_user_Command_Prompt). I use the same method that you are attempting using beyondexec ( http://www.beyondlogic.org/solutions/remoteprocess/BeyondExec.htm), but I don't remember encountering this error. Cheers, Troy - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Running wpkg.js as System Account
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 : > 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 > WPKG 1.1.2 starting... > Base directory is '\\srv-wds01.sdis72.fr\wpkg-w7'. > [...] > > I have checked shares and NTFS rights and they seems correct. > I then types the following command : > psexec \\pc1007-057 -s cmd /c echo test > > \\srv-wds01.sdis72.fr\wpkg\Logs\pc1007-057.W7.log > > And this last command works perfectly (the log file is created... with the > text "test" in it) > > If I try again to run the first command, same error message appear. > > I am lost... > Just a wild guess: did you use double "\\" in your config.xml? Salut, Falko - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
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 - wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Running wpkg.js as System Account
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
WPKG 1.1.2 starting...
Base directory is '\\srv-wds01.sdis72.fr\wpkg-w7'.
[...]
I have checked shares and NTFS rights and they seems correct.
I then types the following command :
psexec \\pc1007-057 -s cmd /c echo test >
\\srv-wds01.sdis72.fr\wpkg\Logs\pc1007-057.W7.log
And this last command works perfectly (the log file is created... with the text
"test" in it)
If I try again to run the first command, same error message appear.
I am lost...
Thanks by advance and sorry about my previous erroneous message.
Laplaud François
>
>Bonjour!
>
>> 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");
>>
>> %TEMP% is not available for the System Account, so the resulting var is
>> >null.
>> I am wondering if I am doing something wrong and what could be the best >way
>> to modify the script to make a default log file for instance at the >root of
>> the C drive for instance.
>>
>> Hope to find some help quickly.
>>
>How do you start the scheduled task? Just define a TEMP variable in a
>batch file and start "cscript wpkg.js /synchronize" from within the
>batch file.
>
>Best regards
>Falko
>
>-
>wpkg-users mailing list archives >>
>http://lists.wpkg.org/pipermail/wpkg->users/
>___
>wpkg-users mailing list
>wpkg-users@lists.wpkg.org
>http://lists.wpkg.org/mailman/listinfo/wpkg-users
-
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Running wpkg.js as System Account
Bonjour!
> 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");
>
> %TEMP% is not available for the System Account, so the resulting var is null.
> I am wondering if I am doing something wrong and what could be the best way
> to modify the script to make a default log file for instance at the root of
> the C drive for instance.
>
> Hope to find some help quickly.
>
How do you start the scheduled task? Just define a TEMP variable in a
batch file and start "cscript wpkg.js /synchronize" from within the
batch file.
Best regards
Falko
-
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
