[wpkg-users] Running at shutdown
I'm trying to change some of our computers to run WPKG during shutdown. I've used wpkgclient to change the setting, and saved it. I have a package (Adobe Reader) which should deploy to the computer. It installs using msiexec /i /qb, so there should be a progress bar. During shutdown (Windows 7) I see shutting down WPKG Service service, followed about ten seconds later by Windows is shutting down, which lasts for about 20 seconds. This is nothing like enough time for Adobe Reader to be installed. After restart, Adobe Reader is not present. Does WPKG put messages to the screen, for example do not shut down or power off, installing software? Do the msiexec progress bars get shown? The event log shows three WSH messages showing the installation starting, followed by an MSIEXEC message for the start of the installation. Then it creates a restore point. Then the user profile service stops. The next message is part of the restart sequence. These messages occur within a time span of 5 seconds. It looks as though the system is not waiting for the installation to complete before shutting down. Is this expected windows 7 behaviour? Alan - 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] Adobe reader package problem
I've been trying to create a package which will update Adobe Reader, removing any of several possible existing versions first. An added complication is that in the past I've installed two different MSIs which I now discover install the same version. I therefore have to try using both msis in turn to remove that version. This means that one of the msi's will return 1605 or the other 1638, i.e. one can't find the product, and the other says another version is installed. I tested this quite extensively on one computer, where it worked. However on another computer, where Adobe Reader has been uninstalled, it tries to uninstall both 10.1.0 and 10.1.1, returns 1605 (treated as success) then does not attempt to install 10.1.2. The file it is testing doesn't exist on this computer. Can anyone see why? The package is: package id=adobereader10-1-2 name=Adobe Reader 10.1.2 update revision=3 priority=1 check type=file condition=versiongreaterthan path=%programfiles%\Adobe\Reader 10.0\Reader\AcroRd32.exe value=10.1.2.0 / install cmd='msiexec /uninstall %software%\adobe acrobat reader\10.1.1\AdbeRdr1011_en_US\AcroRead.msi/qb /norestart' condition check type=file condition=versionequalto path=%programfiles%\Adobe\Reader 10.0\Reader\AcroRd32.exe value=10.1.0.534 / /condition exit code=1638/ exit code=1605/ /install install cmd='msiexec /uninstall %software%\adobe acrobat reader\10.1.0\AdbeRdr1010_en_US.msi/qb /norestart' condition check type=file condition=versionequalto path=%programfiles%\Adobe\Reader 10.0\Reader\AcroRd32.exe value=10.1.0.534 / /condition exit code=1638/ exit code=1605/ /install install cmd='msiexec /uninstall %software%\adobe acrobat reader\10.0\AdbeRdr1000_en_US.msi/qb /norestart' condition check type=file condition=versionequalto path=%programfiles%\Adobe\Reader 10.0\Reader\AcroRd32.exe value=10.0.0.396 / /condition /install install cmd='msiexec /i %software%\adobe acrobat reader\10.1.0\AdbeRdr1010_en_US.msi TRANSFORMS=%software%\adobe acrobat reader\10.1.0\LBJ-setup.mst /update %software%\adobe acrobat reader\10.1.2\AdbeRdrUpd1012.msp /qb /norestart' / upgrade cmd='msiexec /i %software%\adobe acrobat reader\10.1.0\AdbeRdr1010_en_US.msi TRANSFORMS=%software%\adobe acrobat reader\10.1.0\LBJ-setup.mst /update %software%\adobe acrobat reader\10.1.2\AdbeRdrUpd1012.msp /qb /norestart' / remove cmd='msiexec /x %software%\adobe acrobat reader\10.1.0\AdbeRdr1010_en_US.msi/qb /norestart' / /package - 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] Adobe reader package problem
Problem solved. I'd been testing in a folder with the 1.3 wpkg.js, then moved it to a folder with the 1.2 wpkg.js, which doesn't understand condition I've been trying to create a package which will update Adobe Reader, removing any of several possible existing versions first. An added complication is that in the past I've installed two different MSIs which I now discover install the same version. I therefore have to try using both msis in turn to remove that version. This means that one of the msi's will return 1605 or the other 1638, i.e. one can't find the product, and the other says another version is installed. I tested this quite extensively on one computer, where it worked. However on another computer, where Adobe Reader has been uninstalled, it tries to uninstall both 10.1.0 and 10.1.1, returns 1605 (treated as success) then does not attempt to install 10.1.2. The file it is testing doesn't exist on this computer. Can anyone see why? The package is: package id=adobereader10-1-2 name=Adobe Reader 10.1.2 update revision=3 priority=1 check type=file condition=versiongreaterthan path=%programfiles%\Adobe\Reader 10.0\Reader\AcroRd32.exe value=10.1.2.0 / install cmd='msiexec /uninstall %software%\adobe acrobat reader\10.1.1\AdbeRdr1011_en_US\AcroRead.msi/qb /norestart' condition check type=file condition=versionequalto path=%programfiles%\Adobe\Reader 10.0\Reader\AcroRd32.exe value=10.1.0.534 / /condition exit code=1638/ exit code=1605/ /install install cmd='msiexec /uninstall %software%\adobe acrobat reader\10.1.0\AdbeRdr1010_en_US.msi/qb /norestart' condition check type=file condition=versionequalto path=%programfiles%\Adobe\Reader 10.0\Reader\AcroRd32.exe value=10.1.0.534 / /condition exit code=1638/ exit code=1605/ /install install cmd='msiexec /uninstall %software%\adobe acrobat reader\10.0\AdbeRdr1000_en_US.msi/qb /norestart' condition check type=file condition=versionequalto path=%programfiles%\Adobe\Reader 10.0\Reader\AcroRd32.exe value=10.0.0.396 / /condition /install install cmd='msiexec /i %software%\adobe acrobat reader\10.1.0\AdbeRdr1010_en_US.msi TRANSFORMS=%software%\adobe acrobat reader\10.1.0\LBJ-setup.mst /update %software%\adobe acrobat reader\10.1.2\AdbeRdrUpd1012.msp /qb /norestart' / upgrade cmd='msiexec /i %software%\adobe acrobat reader\10.1.0\AdbeRdr1010_en_US.msi TRANSFORMS=%software%\adobe acrobat reader\10.1.0\LBJ-setup.mst /update %software%\adobe acrobat reader\10.1.2\AdbeRdrUpd1012.msp /qb /norestart' / remove cmd='msiexec /x %software%\adobe acrobat reader\10.1.0\AdbeRdr1010_en_US.msi/qb /norestart' / /package - 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] Big Problem with a deployment (LibO)
In message CALaMdAMPauszoetGbm9zV2w1ZeMd+EufN51BkQx_h_BhGfG6Tw@mail.g mail.com Cedric Frayssinet cedric.frayssi...@gmail.com wrote: Hi all ! I've a problem with deployment of LibreOffice. All was fine until i opened the msi with ORCA in order to find the names of langage packs not to install. My goal is to reduce the time to launch LibreOffice. ORCA is now closed, and i have made a copy of the MSI before... When i made a C:\cscript \\172.16.0.241\wpkg\wpkg.js /synchronise /debug /install:Libreoffice i have this message : Executing command: msiexec /qn /I %SOFTWARE%\libreoffice\libreoffice%version_sh ort%.msi Could not process (install) package 'LibreOffice : La suite bureautique Libre' ( Libreoffice): Exit code returned non-successful value (1619) on command 'msiexec /qn /I %SOFT WARE%\libreoffice\libreoffice%version_short%.msi'. Cleaning up temporary downloaded files Folder LibreOffice has the same ACL than others folders which works fine. WPKG is ok because i installed Firefox, 7-zip and more just before... If I run the MSI manually, it works... Do you have any idea ? If you google for msiexec exit code you'll find out what 1619 means. I keep a copy of that list in the wpkg folder. 1619 This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. It usually means there is a type in the path. Thanks a lot ! Cédric NB : %version_short% is defined. -- Alan Adams, from Northamptonshire a...@adamshome.org.uk http://www.nckc.org.uk/ - 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] Package to do an uninstall?
I have a situation where, due to a variety of attempts to get Adobe Reader up to date, some computers have 10.0.0, some 10.1.0, and some 10.1.1. Some were installed via wpkg, and others through Active Directory Group Policies. I now want to install 10.1.2 - but I want to turn off automatic updates. The management tool to customize it for this also turns off uninstall previous versions, and the new version refuses to install if an older one is present. My question - can I create a package, or set of packages, to test for the presence of any of the older versions and run the appropriate msi to uninstall them? check type=file condition=versionequalto ... would seem to identify the offending version - how do I negate the action so it only uninstalls if successful, rather than the usual action of only installing if unsuccessful? I don't want to blindly try uninstalling, because that copies each msi in turn, and due to the 45MB size and the limitations of wireless networks, would cause far too much network traffic and disruption. -- Alan Adams, from Northamptonshire a...@adamshome.org.uk http://www.nckc.org.uk/ - 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] WPKG + Wireless Laptops
In message 4f2bf516.7070...@pyther.net Matthew Gyurgyik pyt...@pyther.net wrote: On 02/02/2012 04:18 PM, Alan Adams wrote: You've picked up one of the biggest problems with respect to deploying software to laptops. In general they are only turned on and connected to the network when the users want to work on them, and pushing software out to them in the background can cause problems. It is a particular problem in schools. A typical scenario is that of 30 children collecting laptops, taking them to the classroom and switching them on. At this point there is a lot of network traffic associated with Group Policies being deployed. As soon as the login window appears they enter their credentials, and there is another burst of GPO traffic. Somewhere in the middle of this wpkg starts downloading the 45MB MSI of Adobe Reader. Not content with that, it uninstalls the previous version, so it downloads that MSI as well. You've now got 30 laptops downloading 100MB of data each across, in the best case, 2 33Mb/sec wireless shared links. 30,000 mbits, through 66mbit/sec is 500 seconds, about ten minutes, ADDED to the normal startup and login time. Add the contention and retransmission overhead when the wireless gets saturated, and it can, and does, take an hour before the last pupil is logged in and ready to work. Primary school lessons are typically 25 minutes. Now I can see a way in the long term to reduce that. The wpkg script will copy the msi to a location on the hard drive, then run the msiexec command referencing the copy. No improvement this time round, but when it comes time to uninstall, it doesn't need to copy the msi again. That should give a factor two improvement. It will also help in deploying patch versions. To deploy 10.1.2 you deploy the 10.1.0 msi accompanied by the 10.1.2 msp. Combined, 65M. However the msi for 10.1.0 would already be on the computer. It also avoids the problem I've got at the moment. I deleted the Adobe reader 9.4.0 msi, then discovered some computers needed it for the uninstall when I deployed 10.1.2. (I don't know why they didn't get 10.0.0, 10.1.0 etc...) This means that I now cannot deploy 10.1.2 to those computers, because the uninstall part of the process fails. Setting the flag in 10.1.2 not to uninstall doesn't help, because it simply refuses to install as another version is present. I had to deploy Number Shark 4 last week. The msi is 450MB. Using wired connections it took around 15 minutes. Those using wireless, only 4 at a time, took almost an hour. Fortunately that school only has 30 laptops, so I managed to finish in a day. I had to pre-arrange that there would be no laptops available for the whole day though. i have been hoping I could use wpkg, running as a service, to allow deployment during lessons. Using AD deployment simply prevents the lesson from starting. (I only have one day every 3 weeks in each school, so doing it out of normal hours is generally not possible.) However the issues described above are making me think it still isn't going to work. I appreciate your in-depth reply. It has brought up a lot a valid and helpful points. We are dealing, currently, with 4 laptop carts each containing 24 laptops. We have longer class periods (90 minutes). Just to deploy Firefox (10MB) to a set of laptops would take 45 seconds assuming ideal conditions (54Mbps). We have Wireless N access points, but realistically we likely wouldn't come close to that with all 24 clients connected. From boot to login, it takes about 2-3 minutes. To add much more time to the login process would be frowned upon. Maybe, the best solution in this case would be to manually run wpkg from each machine to fetch new updates/software. Alternatively, I might be able to create an AD user that has a login script to call wscript. This way I could give said username to a few staff to help with this process. The last is an interesting thought. Do you have staff who would be willing/able to help you out? Great if so. I'm heading down the run at shutdown route as the least-worst option. If I implement that I will be expecting lots of phone calls complaining that the computers won't shut down. Again the problem, as you no doubt find, is that 30+ computers do the same thing simultaneously, and wireless networks don't like that. -- Alan Adams, from Northamptonshire a...@adamshome.org.uk http://www.nckc.org.uk/ - 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] WPKG + Wireless Laptops
In message 4f2bf134.2060...@pyther.net Matthew Gyurgyik pyt...@pyther.net wrote: On 02/02/2012 04:10 AM, Malte Starostik wrote: Hi, now on topic :) Same here, our (admittedly few) laptops are configured for EAP-TLS auth with a machine specific certificate, not user specific. WPKG is run by WPKG-gp and this works nicely. Sure it takes somewhat longer than for the wired clients but that's just the price you pay for mobility IMHO. If the laptop is out of our WLAN's range, it obviously doesn't connect and WPKG-gp skips the whole process. Same if its associated with a different WLAN. Maybe a VPN could do in such cases. Cheers, Malte - 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 This helps a lot, Unfortunately we are using WPA with a PSK at the moment. I'm not sure if we get connected, before the login screen appears. I'm assuming WPKG-gp runs prior to system login, correct? I do know we have cases where users have to wait a bit (~15/~30 sec) before logging in for the wireless connection to be established. i don't think it depends on the wireless setting, but something within Windows. Running XP home edition, the wireless doesn't start until after the user has logged in. Running XP Pro as a domain member, the wireless starts first so the domain controller can be contacted. I would not be surprised if there is a registry setting to change this behaviour on the home/workgroup model. I just haven't found it yet. Incidentally, when using AD to manage computers there is a setting always wait for the network which is useful. It doesn't affect the wireless connection, but does ensure that changes to group policy are picked up at the first startup after they have been made, instead of (frequently) needing two or more restarts. It's in, if I remember correctly, computers-policies-system-login. I guess I'll just have try it and see. - 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 -- Alan Adams, from Northamptonshire a...@adamshome.org.uk http://www.nckc.org.uk/ - 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] Deploying Adobe Reader to be Default Web Viewer
In message 0ba0129d-2c44-4848-8681-49c9217a0...@om.org Urs Rau (UK) urs@om.org wrote: Mikhail, On 30 Jan 2012, at 03:28, Mikhail Joseph Salviejo wrote: Good day Guys, I having a little bit trouble with Adobe Reader 9 and X. After deploying them to our computers (Win XP for Adobe 9, and Win 7 for Adobe X) They can't seem to open pdf files via web that has no extension like this http://design.rldp.com/wiwi/543asdls1231adf (uploaded in mysql) Are you sure this issue is wpkg related? If you install Adobe Reader by hand , does it then open up the above mentioned files? If you have the same problem then this is not wpkg related. When a file has no extension, then trying to open it by double-clicking it will fail, as will using the menu and choosing open or run. However File - Open within Adobe Reader should work, if the file is indeed valid PDF. Are these files by any chance connected with RISC OS (Acorn and successors)? The filetype hex(adf) is used on RISC OS for pdf files. RISC OS systems do not require extensions. If you have control of the webserver config that serves those files you might be able to resolve it making sure the web server either serves them with the extension pdf or else make sure it sends the right http mime content headers so the browser knows to call on Adobe Reader to read them. Regards, -- Urs Rau Operation Mobilisation (OM) - a company limited by guarantee - The Quinta, Weston Rhyn, Oswestry, SY10 7LT, United Kingdom Company reg no: 2564320 (England Wales) - Charity reg. no: 1008196 (England Wales) - SC040988 (Scotland) Web: http://www.uk.om.org - 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 -- Alan Adams, from Northamptonshire a...@adamshome.org.uk http://www.nckc.org.uk/ - 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] [Bug 258] Windows 7 64 bit not correctly detected
In message 4edd1224.3060...@freakyacres.com Joe j...@freakyacres.com wrote: On 12/5/2011 1:03 PM, bugzilla-dae...@bugzilla.wpkg.org wrote: http://bugzilla.wpkg.org/show_bug.cgi?id=258 Rainer Meierr.me...@wpkg.org changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #3 from Rainer Meierr.me...@wpkg.org --- Oh, I did not even think about this. But sure this is a good explanation too :) Closing this issue. Is that the proper behavior? Should a 64bit machine be detected as 32bit because of the client software? I imagine it is. I would not expect to be able to run a 64-bit application on a 32-bit OS, which is what would happen if the hardware determined the architecture type. Alan - 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 -- Alan Adams, from Northamptonshire a...@adamshome.org.uk http://www.nckc.org.uk/ - 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] Delayed sevice start
In message 2023083018.gc3...@sv.lnf.it Marco Gaiarin g...@sv.lnf.it wrote: Mandi! John Danks In chel di` si favelave... WPKG Client has a few settings you might try. I haven't experimented with logon delay, but it's there under Logon Settings / Execution mode. Consider also: http://support.microsoft.com/default.aspx?scid=kb;en-us;305293 I am only too aware of that, and in the domain always ensure it is set in Group policy to wait for the network. However XP Home edition can't join a domain, and I haven't found an equivalent registry setting to make it start the wireless before logging in. The problem is not that the wireless is slow to start - you can leave the computer at the login window for an hour, and the wireless still hasn't started. It waits for someone to login before it tries to connect. -- Alan Adams, from Northamptonshire a...@adamshome.org.uk http://www.nckc.org.uk/ - 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] Empty remove command
In message 89c7d0b417b13d4cb5de0d2271d22d2c011025c...@ce2k8emb.ier.gr oup VERDEYEN Jonathan jverde...@automatic-systems.com wrote: snip I thought it all made sense but my problem is when I remove the package from the profile, it will try to uninstall the last update and fail as the install checks succeed and stop proceeding to any further uninstall as it couldn't uninstall the dependent package. In the end, I think there should be an option to remove a package without uninstalling the software, or is there already ? Thank you :) This is a problem for me as well. i had a massive problem after I made a typo in the script for Google Earth. I had to remove the package as it was failing to install, and rebooting each time. Now it tries to uninstall, then reboots, then tries to uninstall, then reboots ... I had to boot each computer in safe mode and remove wpkg.xml from c:\windows\system32 - that being the file which remembers the uninstall command. After this experience I generally create packages without uninstall commands - and have to live with the uninstall failed messages. I can see little advantage in caching the uninstall commands like this, and as you see above, major potential disadvantages. If instead the uninstall command is always read from the package on the server, then removing the package from a profile would cause an uninstall, while removing it from packages.xml would not. This would seem to give an additional useful flexibility. Or have I missed something which allows this anyway? snip -- Alan Adams, from Northamptonshire a...@adamshome.org.uk http://www.nckc.org.uk/ - 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
