Re: [wpkg-users] deploy to a pilot group first?
Hello Kent, Kent Tong wrote: However, I'd like to deploy it to pilot group first. To avoid deploying to all users, I can't modify the existing package. It means I have to create a new package. If they have the same package id, then it will confuse wpkg, right? If they have different package ids, then wpkg will execute the install command instead of the upgrade command. Yes. You could do the following - replace the check, upgrade and remove commands from the existing package mypackage by e.g. check type=file condition=exists path=%SystemDrive%\netinst\logs\acrobat7.txt / upgrade cmd='cmd /c echo ok %SystemDrive%\netinst\logs\acrobat7.txt ' exit code=any / /upgrade remove cmd='cmd /c del /q %SystemDrive%\netinst\logs\acrobat7.txt ' exit code=any / /remove (so the software is not changed in any way when upgrading/removing the package) - increase the revision number, so nothing on the existing clients is changed, only the text file will be created/removed - create a new, at least identical package, say mypackage2; assign it to the test group, remove mypackage from the same group - up to this point, nothing has changed to the clients but the text file and the contents of wpkg.xml - change the check/install/upgrade/remove entries in mypackage2 and test that at the test group - when you are satisfied with your package, remove the assignment of mypackage and assign mypackage2 to the target group An approach to this problem is to let different groups see a different set of available packages, then the problem will be solved. Is there any way to do it? Yes. You can set base as parameter or in config.xml, see http://wpkg.org/WPKG_flags#Optional_parameters But IMHO you would need a copy of your software repository, then. 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
Re: [wpkg-users] deploy to a pilot group first?
Falko Trojahn-2 wrote: - increase the revision number, so nothing on the existing clients is changed, only the text file will be created/removed - create a new, at least identical package, say mypackage2; assign it to the test group, remove mypackage from the same group Hi Falko, Thanks for your reply! Take the mypackage2 as an example, will it use the same package id as mypackage? - -- Kent Tong Wicket tutorials freely available at http://www.agileskills2.org/EWDW Axis2 tutorials freely available at http://www.agileskills2.org/DWSAA -- View this message in context: http://www.nabble.com/deploy-to-a-pilot-group-first--tp19620583p19622617.html Sent from the WPKG - Users mailing list archive at Nabble.com. - 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] deploy to a pilot group first?
Why not just create a new profile (called pilot or something) that contains the package to test, and then in your hosts.xml add this new profile to selected hosts that are to pilot the new package. You would still have to create a separate package entry with a unique id of course, but that's the way I would go about it. On 9/23/08, Kent Tong [EMAIL PROTECTED] wrote: Falko Trojahn-2 wrote: - increase the revision number, so nothing on the existing clients is changed, only the text file will be created/removed - create a new, at least identical package, say mypackage2; assign it to the test group, remove mypackage from the same group Hi Falko, Thanks for your reply! Take the mypackage2 as an example, will it use the same package id as mypackage? - -- Kent Tong Wicket tutorials freely available at http://www.agileskills2.org/EWDW Axis2 tutorials freely available at http://www.agileskills2.org/DWSAA -- View this message in context: http://www.nabble.com/deploy-to-a-pilot-group-first--tp19620583p19622617.html Sent from the WPKG - Users mailing list archive at Nabble.com. - 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] deploy to a pilot group first?
Hi, first: please don't top post / full quote, thank you. mscdex wrote: Why not just create a new profile (called pilot or something) that contains the package to test, and then in your hosts.xml add this new profile to selected hosts that are to pilot the new package. You would still have to create a separate package entry with a unique id of course, but that's the way I would go about it. At least after installation of the new package the old package would fail it's check(s), reinstall the older software, even possible that after this the newer package would remove/upgrade the older software ... nice loop. 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
Re: [wpkg-users] deploy to a pilot group first?
Mandi! Kent Tong In chel di` si favelave... Is there any way to do it? Apart what yust sayed, no. If the 'testbed' are to little and phisically near you, normally i modify the package but not the revision of, then i: 1) test the upgrade editing C:\WINDOWS\SYSTEM32\WPKG.XML and subtracting 1 to the revision of that package, so an upgrade are forced. 2) test install/remove by adding/removing package from the profile (this is a bit easy) clearly using a 'scatch' profile. Some time ago i've asked for a feature, eg like in modern package management system, to 'pinpoint' a package with a specific revision to a profile, eg: profile id=ced depends profile-id=default / package package-id=whfc revision=124/ /profile I think this is a good solution for this problem. -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia''http://www.sv.lnf.it/ Polo FVG - Via della Bontà , 7 - 33078 - San Vito al Tagliamento (PN) marco.gaiarin(at)sv.lnf.it tel +39-0434-842711 fax +39-0434-842797 Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA! http://www.lanostrafamiglia.it/chi_siamo/5xmille.php (cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA) - 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] deploy to a pilot group first?
Hi all, Thanks for all the suggestions! I think pinpointing is the way to go while the rest can serve as effective workaround for the moment. Going to file an feature request... - -- Kent Tong Wicket tutorials freely available at http://www.agileskills2.org/EWDW Axis2 tutorials freely available at http://www.agileskills2.org/DWSAA -- View this message in context: http://www.nabble.com/deploy-to-a-pilot-group-first--tp19620583p19624852.html Sent from the WPKG - Users mailing list archive at Nabble.com. - 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] [Bug 131] New: pinpointing a package to a certain revision
http://bugzilla.wpkg.org/show_bug.cgi?id=131 Summary: pinpointing a package to a certain revision Product: WPKG Version: 0.9.10 Platform: PC OS/Version: Windows 2000 Status: NEW Severity: enhancement Priority: P2 Component: wpkg.js AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: wpkg-users@lists.wpkg.org Suppose that there is an existing package which now has a new version, assuming that it can perform an in-place upgrade, it is easy to deploy the new version with wpkg: just modify the revision attribute and the install and upgrade commands. However, I'd like to deploy it to pilot group first. To avoid deploying to all users, I can't modify the existing package. It means I have to create a new package. A solution is to allow pinpointing a certain revision, such as: profile id=p1 package package-id=whfc revision=123/ /profile profile id=p1-pilot package package-id=whfc/ /profile This way all normal computers will belong to profile p1 and will continue to use the existing revision (123), while those in the pilot group will use profile p1-pilot and will use the latest revision. This is not only useful for piloting and phased deployments, but also useful if a certain group of users can't or are unwilling to upgrade due to application conflicts or other reasons. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - 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] Trouble installing Registry entries
Well, getting closer on this one. After a week off due to a server changeover I've had a chance to play with this more in my test environment. Getting hits on the log file now, but the edits still aren't applying. I've tried as both SYSTEM and using Administrator Cridentials with the same results. 2008-09-23 14:05:50, DEBUG : Initialized temporary local log file: C:\WINDOWS\TEMP\wpkg-logInit.log 2008-09-23 14:05:50, DEBUG : Initializing new log file: C:\WINDOWS\TEMP\wpkg-chrisxpprovm.log 2008-09-23 14:05:50, DEBUG : Reboot-Cmd is standard. 2008-09-23 14:05:50, DEBUG : WPKG 1.0.2 starting... 2008-09-23 14:05:50, DEBUG : Base directory is '\\arabis-red\wpkg'. 2008-09-23 14:05:50, DEBUG : Log level is 255 2008-09-23 14:05:50, DEBUG : Trying to read XML file: \\arabis-red\wpkg\profiles.xml 2008-09-23 14:05:50, DEBUG : Successfully loaded XML file: \\arabis-red\wpkg\profiles.xml 2008-09-23 14:05:50, DEBUG : Trying to read XML files from directory: \\arabis-red\wpkg\profiles 2008-09-23 14:05:51, DEBUG : Reading XML file: //arabis-red/wpkg/profiles/standard.xml 2008-09-23 14:05:51, DEBUG : Reading XML file: //arabis-red/wpkg/profiles/test.xml 2008-09-23 14:05:51, DEBUG : Reading XML file: //arabis-red/wpkg/profiles/regedit.xml 2008-09-23 14:05:51, DEBUG : Trying to read XML file: \\arabis-red\wpkg\hosts.xml 2008-09-23 14:05:51, DEBUG : Successfully loaded XML file: \\arabis-red\wpkg\hosts.xml 2008-09-23 14:05:51, DEBUG : Trying to read XML files from directory: \\arabis-red\wpkg\hosts 2008-09-23 14:05:51, DEBUG : Reading XML file: //arabis-red/wpkg/hosts/chrixpprovm.xml 2008-09-23 14:05:51, DEBUG : Reading XML file: //arabis-red/wpkg/hosts/standard.xml 2008-09-23 14:05:51, DEBUG : Trying to read XML file: \\arabis-red\wpkg\packages.xml 2008-09-23 14:05:51, DEBUG : Successfully loaded XML file: \\arabis-red\wpkg\packages.xml 2008-09-23 14:05:51, DEBUG : Trying to read XML files from directory: \\arabis-red\wpkg\packages 2008-09-23 14:05:51, DEBUG : Reading XML file: //arabis-red/wpkg/packages/morrisoncert.xml 2008-09-23 14:05:51, DEBUG : Reading XML file: //arabis-red/wpkg/packages/windowsupdate.xml 2008-09-23 14:05:51, DEBUG : Reading XML file: //arabis-red/wpkg/packages/thunderbird.xml 2008-09-23 14:05:51, DEBUG : Reading XML file: //arabis-red/wpkg/packages/flashplayrfirefox.xml 2008-09-23 14:05:51, DEBUG : Reading XML file: //arabis-red/wpkg/packages/firefox.xml 2008-09-23 14:05:52, DEBUG : Reading XML file: //arabis-red/wpkg/packages/java.xml 2008-09-23 14:05:52, DEBUG : Reading XML file: //arabis-red/wpkg/packages/off2007fmtconv.xml 2008-09-23 14:05:52, DEBUG : Reading XML file: //arabis-red/wpkg/packages/bitdefender.xml 2008-09-23 14:05:52, DEBUG : Reading XML file: //arabis-red/wpkg/packages/flashplayerie.xml 2008-09-23 14:05:52, DEBUG : Reading XML file: //arabis-red/wpkg/packages/adobe-reader.xml 2008-09-23 14:05:52, DEBUG : Reading XML file: //arabis-red/wpkg/packages/dotnet1.xml 2008-09-23 14:05:52, DEBUG : Reading XML file: //arabis-red/wpkg/packages/dotnet20.xml 2008-09-23 14:05:52, DEBUG : Reading XML file: //arabis-red/wpkg/packages/officexp.xml 2008-09-23 14:05:52, DEBUG : Profiles applying to the current host:|test| 2008-09-23 14:05:52, DEBUG : Reading settings file: C:\WINDOWS\system32\wpkg.xml 2008-09-23 14:05:52, DEBUG : Trying to read XML file: C:\WINDOWS\system32\wpkg.xml 2008-09-23 14:05:52, DEBUG : Successfully loaded XML file: C:\WINDOWS\system32\wpkg.xml 2008-09-23 14:05:52, DEBUG : Getting profiles which apply to this node. 2008-09-23 14:05:52, DEBUG : Applying profile: test 2008-09-23 14:05:52, DEBUG : Adding package with ID 'windowsupdate' to profile packages. 2008-09-23 14:05:52, DEBUG : Found package node 'Auto Updates From WSUS Server (windowsupdate) in package database 2008-09-23 14:05:52, DEBUG : Adding package with ID 'morrisoncert' to profile packages. 2008-09-23 14:05:52, DEBUG : Found package node 'Security Cert for IV4 (morrisoncert) in package database 2008-09-23 14:05:52, DEBUG : Adding package with ID 'firefox' to profile packages. 2008-09-23 14:05:52, DEBUG : Found package node 'Mozilla Firefox 3 (firefox) in package database 2008-09-23 14:05:52, DEBUG : Adding package with ID 'thunderbird' to profile packages. 2008-09-23 14:05:52, DEBUG : Found package node 'Mozilla Thunderbird (thunderbird) in package database 2008-09-23 14:05:52, DEBUG : Adding package with ID 'adobe-reader' to profile packages. 2008-09-23 14:05:52, DEBUG : Found package node 'Adobe Reader 7.0.9 (adobe-reader) in package database 2008-09-23 14:05:52, DEBUG : Adding package with ID 'office' to profile packages. 2008-09-23 14:05:52, DEBUG : Found package node 'Microsoft Office XP (office) in package database 2008-09-23 14:05:52, DEBUG : Adding package with ID 'off2007fmtconv' to profile packages. 2008-09-23 14:05:52, DEBUG : Found package node 'Compatibility Pack for the 2007 Office System (off2007fmtconv) in package database 2008-09-23 14:05:52,
Re: [wpkg-users] Trouble installing Registry entries
Hi Christopher, Christopher Leslie wrote: Well, getting closer on this one. After a week off due to a server changeover I've had a chance to play with this more in my test environment. Getting hits on the log file now, but the edits still aren't applying. I've tried as both SYSTEM and using Administrator Cridentials with the same results. 2008-09-23 14:05:54, DEBUG : Executing command : regedit /s %SOFTWARE%\Software\morrisoncert.reg 2008-09-23 14:05:56, DEBUG : Command in installation of Security Cert for IV4 returned exit code [0]. Success. 2008-09-23 14:05:56, DEBUG : Checking existence of package: Security Cert for IV4 2008-09-23 14:05:56, DEBUG : The registry path 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\ROOT\Certificates\910C309AD02F637DE043158A04ADDBE468E0422A' does not exist: the check failed 2008-09-23 14:05:56, ERROR : Could not process (install) Security Cert for IV4.|Failed checking after installation. The message is actually quite clear here. The registry key does not seem to exist. Could you please post the content of morrisoncert.reg as well as the package definition (XML sniplet) of the 'morrisoncert' package? 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
