Re: [wpkg-users] Problem with 64bit version of WPKG on WinXP 64
Am 19.09.2012 16:24, schrieb Kyle Conti: Stefan, I apologize for not responding. It has been very busy here at work. I have tried setting the service to manual - still has the same issue of needing to repair the wpkg application. I have not set the service to stop after execution in the wpkg client settings. WPKG_Force_Update.bat looks like: " :: Startup script for wpkg, for the first installation :: :: These are not (still) defined elsewhere, define it. :: @ECHO Updates Being Installed Please be Patient... set WPKGROOT=\\server\data\software\wpkg set SOFTWARE=\\server\data\software\Applications\Windows set ALLUSERS_STARTMENU="C:\Documents and Settings\All Users\Start Menu\Programs" set ALLUSERS_DESKTOP="C:\Documents and Settings\All Users\Desktop" :: Call directly wpkg.js, note the %* at the end, that permit to add custom parameters... :: assoc .js=JSFile cscript %WPKGROOT%\wpkg.js /synchronize %* " If you need to to send some of our past emails to catch you up, please let me knowits been since mid august since we last spoke (sorry again). I don't see anything obvious, so I am lost at how to further help you. I don't think you need to associate the .js extension on each run. I never had a software changing it and you use "cscript" directly and not "start" or "explorer". Does the Windows event log shed some light on this issue? -- Stefan P. Top-posting: A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? - 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] Problem with 64bit version of WPKG on WinXP 64
Stefan, I apologize for not responding. It has been very busy here at work. I have tried setting the service to manual - still has the same issue of needing to repair the wpkg application. I have not set the service to stop after execution in the wpkg client settings. WPKG_Force_Update.bat looks like: " :: Startup script for wpkg, for the first installation :: :: These are not (still) defined elsewhere, define it. :: @ECHO Updates Being Installed Please be Patient... set WPKGROOT=\\server\data\software\wpkg set SOFTWARE=\\server\data\software\Applications\Windows set ALLUSERS_STARTMENU="C:\Documents and Settings\All Users\Start Menu\Programs" set ALLUSERS_DESKTOP="C:\Documents and Settings\All Users\Desktop" :: Call directly wpkg.js, note the %* at the end, that permit to add custom parameters... :: assoc .js=JSFile cscript %WPKGROOT%\wpkg.js /synchronize %* " If you need to to send some of our past emails to catch you up, please let me knowits been since mid august since we last spoke (sorry again). Regards, Kyle Conti , IT Engineer Boston Engineering Corporation 300 Bear Hill Rd. | Waltham, MA 02451 | 781-314-0753 - Original Message - From: "Stefan Pendl" To: "Kyle Conti" Cc: wpkg-users@lists.wpkg.org Sent: Tuesday, August 14, 2012 4:01:31 PM Subject: Re: [wpkg-users] Problem with 64bit version of WPKG on WinXP 64 Am 14.08.2012 15:32, schrieb Kyle Conti: > Stefan, > > To answer your question on how we push out software to our users, I have > attached three scripts. So initially, I run the UpdateScript64.bat > script. I choose to input the IP for the computer I want to push the > updates to. If the computer does not currently have wpkg on it, it will > run the InstallWPKG_64.bat script, then follow up with the > updatescript64.bat. If the computer already has wpkg client already > installed, it only runs the updateworkstation.py script. > > I have gone ahead and removed/replaced things relating to my company in > these scripts. Please take a look through if you'd like. Once again, > the problem is that on 64 bit computers I HAVE to reinstall the wpkg > client before I can update a user again (after that user restarts > his/her machine). On 32 bit computers, I can just keep running the > update script and there are no issues. What would cause 64bit computers > to mess up the client after a restart? > > I had to rename the attachments to .txt to send. > Kyle, how about setting the WPKG service to manual instead of disabling it entirely? Have you set the service to stop after execution in the wpkg client settings? -- Stefan P. Top-posting: A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? - 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] Problem with 64bit version of WPKG on WinXP 64
Am 14.08.2012 15:32, schrieb Kyle Conti: Stefan, To answer your question on how we push out software to our users, I have attached three scripts. So initially, I run the UpdateScript64.bat script. I choose to input the IP for the computer I want to push the updates to. If the computer does not currently have wpkg on it, it will run the InstallWPKG_64.bat script, then follow up with the updatescript64.bat. If the computer already has wpkg client already installed, it only runs the updateworkstation.py script. I have gone ahead and removed/replaced things relating to my company in these scripts. Please take a look through if you'd like. Once again, the problem is that on 64 bit computers I HAVE to reinstall the wpkg client before I can update a user again (after that user restarts his/her machine). On 32 bit computers, I can just keep running the update script and there are no issues. What would cause 64bit computers to mess up the client after a restart? I had to rename the attachments to .txt to send. Kyle, how about setting the WPKG service to manual instead of disabling it entirely? Have you set the service to stop after execution in the wpkg client settings? -- Stefan P. Top-posting: A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? - 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] Problem with 64bit version of WPKG on WinXP 64
Am 14.08.2012 15:32, schrieb Kyle Conti: Stefan, To answer your question on how we push out software to our users, I have attached three scripts. So initially, I run the UpdateScript64.bat script. I choose to input the IP for the computer I want to push the updates to. If the computer does not currently have wpkg on it, it will run the InstallWPKG_64.bat script, then follow up with the updatescript64.bat. If the computer already has wpkg client already installed, it only runs the updateworkstation.py script. I have gone ahead and removed/replaced things relating to my company in these scripts. Please take a look through if you'd like. Once again, the problem is that on 64 bit computers I HAVE to reinstall the wpkg client before I can update a user again (after that user restarts his/her machine). On 32 bit computers, I can just keep running the update script and there are no issues. What would cause 64bit computers to mess up the client after a restart? I had to rename the attachments to .txt to send. Kyle, what is "WPKG_Force_Update.bat" looking like? -- Stefan P. Top-posting: A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? - 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] Problem with 64bit version of WPKG on WinXP 64
Stefan,
To answer your question on how we push out software to our users, I have
attached three scripts. So initially, I run the UpdateScript64.bat script. I
choose to input the IP for the computer I want to push the updates to. If the
computer does not currently have wpkg on it, it will run the InstallWPKG_64.bat
script, then follow up with the updatescript64.bat. If the computer already has
wpkg client already installed, it only runs the updateworkstation.py script.
I have gone ahead and removed/replaced things relating to my company in these
scripts. Please take a look through if you'd like. Once again, the problem is
that on 64 bit computers I HAVE to reinstall the wpkg client before I can
update a user again (after that user restarts his/her machine). On 32 bit
computers, I can just keep running the update script and there are no issues.
What would cause 64bit computers to mess up the client after a restart?
I had to rename the attachments to .txt to send.
Regards,
Kyle Conti , IT Engineer
Boston Engineering Corporation
300 Bear Hill Rd. | Waltham, MA 02451 | 781-314-0753
- Original Message -
From: "Stefan Pendl"
To: wpkg-users@lists.wpkg.org
Sent: Saturday, August 11, 2012 5:28:57 AM
Subject: Re: [wpkg-users] Problem with 64bit version of WPKG on WinXP 64
Am 10.08.2012 18:49, schrieb Kyle Conti:
> Stefan,
>
> I wasn't aware you can execute the wpkg.js and install programs without
> having the wpkg client installed. Anyway, I'd still like WPKG client to
> stay working without having to reinstall since our current scripts
> install the client remotely and then update the system that way. I do
> not have the time to rewrite our scripts. As i've said before, this
> works perfectly fine on 32-bit systems with no reinstalls needed. Very
> strange. Any ideas on why this would happen?
>
So we would need more information about how your environment is set up.
Currently I am not sure how you are using WPKG.
A detailed step-by-step description would be handy.
Any scripts and settings that aren't easy to describe would be handy too.
BTW, always use "reply to all" so you are also replying to the group not
just to the individual.
This makes sure that more people get involved, since it is likely that
someone uses a similar set up and can point out the cause of your
problems directly.
--
Stefan P.
Top-posting:
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
-
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
#!/usr/bin/python
###
#
###
#
# File: c:\scripts\updateWorkstations.py
# Description:
#
#
# Return Values:
# 0 = Success
#
# Changelog:
# * 2009/02/25
# - Initial file
###
##
# Imports
##
import sys
import ldap
import time
import re
import win32con
import logging, logging.config
from optparse import OptionParser
import subprocess
from threading import Thread
import threading
##
# Local Classes
##
class UpdateSystemThread(Thread):
import subprocess
logger = logging.getLogger()
def __init__ (self, computer, failurefile):
Thread.__init__(self)
self.computer = computer
self.failurefile = failurefile
self.status = -1
def run(self):
logger.debug("Running update on %s..." % (self.computer))
retval = subprocess.call('psexec %s -u DOMAIN\USER -p password
WPKG_Force_Update.bat' % (self.computer))
if retval <> 0:
logger.error("Update failed on %s. Return value of %s." %
(self.computer, retval))
self.failurefile.write("%s %s\n" % (self.computer, retval))
else:
logger.info("Updated %s. %s" % (self.computer, retval))
##
# Local Vars
##
ldapServer = "SERVERNAME"
baseDN = "ldap dn info"
runTypes = ('all', 'workstations', 'laptops', 'computer', 'file')
#***
Re: [wpkg-users] Problem with 64bit version of WPKG on WinXP 64
Am 10.08.2012 18:49, schrieb Kyle Conti: Stefan, I wasn't aware you can execute the wpkg.js and install programs without having the wpkg client installed. Anyway, I'd still like WPKG client to stay working without having to reinstall since our current scripts install the client remotely and then update the system that way. I do not have the time to rewrite our scripts. As i've said before, this works perfectly fine on 32-bit systems with no reinstalls needed. Very strange. Any ideas on why this would happen? So we would need more information about how your environment is set up. Currently I am not sure how you are using WPKG. A detailed step-by-step description would be handy. Any scripts and settings that aren't easy to describe would be handy too. BTW, always use "reply to all" so you are also replying to the group not just to the individual. This makes sure that more people get involved, since it is likely that someone uses a similar set up and can point out the cause of your problems directly. -- Stefan P. Top-posting: A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? - 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] Problem with 64bit version of WPKG on WinXP 64
Am 09.08.2012 23:07, schrieb Kyle Conti: Thanks for the reply! I am also using 1.3.14 on WinXP x64 SP2 and Win7 64. They seem to act identically. I do not use WPKG in the regular way...I have a script that remotely pushes updates to clients I designate by IP addresses. I do not run wpkg on startup or shutdown. For now, I am just manually running the forceupdate.bat script to install the packages I have created on WPKGexpress. Works great! but...for some reason it makes me have to reinstall it or else the script fails. Kyle, since you aren't using a poll configuration, why use the client at all? You can do this with a regular scheduled job too. The client is optional, so I don't have it installed on my Win7 machines at all, since I use a scheduled task that executes WPKG.js directly. -- Stefan P. Top-posting: A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? - 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] Problem with 64bit version of WPKG on WinXP 64
Am 09.08.2012 19:38, schrieb Kyle Conti: Hello WPKGUSERS, I have been running into this issue where I have to reconfigure/reinstall WPKG on a computer after a system (Windows XP 64bit) restart. This doesn't happen on Windows XP Professional SP3. We are going to be moving to Windows 7 64bit very soon, and I would really not like to have to repair WPKG everytime I want to do a forceupdate. When I do try to run forceupdate after a computer restart, the script kicks off and quickly ends. A repair pointing to our settings file fixes this and am able to do a forceupdate. Is this a known issue on 64bit machines? I am indeed using the 64-bit version of WPKG on the 64-bit machines. I'd really appreciate the help. Thanks! Which version of the client do you use? When do you run it (start up or shutdown)? BTW, using the client on Win7 is a bit tricky. I haven't had such problems when running the latest client v1.3.14 at shutdown on WinXP x64 Edition SP2. -- Stefan P. Top-posting: A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? - 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
