Re: [wpkg-users] Package Renaming [SEC=UNCLASSIFIED]
Michael Chinn schrieb: I was planning a mass rename of existing packages to conform with a new naming priority convention and just wondered if anyone else has attempted this? Would it be best to remove the local wpkg.xml prior to wpkg.js execution so that all the packages reperforms their checks? I can for see some issues with 'execute once' pkgs running again Yeah, removing wpkg.xml seems to be the easiest way if you renamed your packages. As you said, you will have problems with packages with no checks (execute once) - they will be started once again. If there are no big installers there, it shouldn't be a problem, though. Another thing you could do is to do the changes in wpkg.xml. The easiest would be if you kept this in one place (on a remote server - settable in config.xml). If this file is stored locally, you may use WPKG Client and execute before / after to rename entries in wpkg.xml. -- Tomasz Chmielewski http://wpkg.org - Reporting bugs, all WPKG mailing lists http://wpkg.org/Support ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Package Renaming [SEC=UNCLASSIFIED]
Hi Michael, Michael Chinn wrote: I was planning a mass rename of existing packages to conform with a new naming priority convention and just wondered if anyone else has attempted this? Would it be best to remove the local wpkg.xml prior to wpkg.js execution so that all the packages reperforms their checks? I can for see some issues with 'execute once' pkgs running again Well, I never did it but I would like to share some thoughts of course. When renaming the package ID then WPKG cannot know if the package is actually the same but just renamed. So it will regard it as a new package. This also means that the original package (old name) will not appear any more within the profile - so WPKG is going to remove them first before starting to re-install it using the new package ID. So if you keep your local settings (wpkg.xml) then WPKG will do the following (assuming all packages are renamed): - remove all packages which are listed in wpkg.xml - install all packages currently in the profile If you're going to remove wpkg.xml before the following will happen: - WPKG assumes no software intalled yet and will install all packages During installation WPKG will execute the checks and eventually skip the installation where it finds that the checks already succeed. So if all your packages supply appropriate checks then WPKG will do nothing but just re-fill wpkg.xml This also applies for execute=once packages. They will not be re-installed if checks succeed. However execute=once packages typically do not have checks and are used just to apply it once and then forget about it (unless it's upgraded). In such case the package will be re-applied (since WPKG cannot determine by checks that the package is already installed). I strongly recommend to test this migration on a testbed because it heavily depends on the quality of your packages. In best case (all checks appropriate) I would recommend deleting the local wpkg.xml as you already mentioned and then re-synchronize. br, Rainer - Reporting bugs, all WPKG mailing lists http://wpkg.org/Support ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] Profile inconsitency: Package with ID 'imageresize' is listed in profile but ...
Hi, firstly congratulations for this amazing system. In my job, we have Landesk and it is really messy. this system, seems easy and reliable! But I couldnt make it work! :( I need to install Image Resize from PowerToys in 100 computers. After reading the installations notes I decide not to use the service option. I create an OU and one policy that executes on start script launching the script. So I can easy move computers to that OU to test if the system is running properly. But before I tried to run it in my own computer from cmd. I get an error the wpkg database is empty It should be empty as far I didnt install any softwarre yet. I create the variable SOFTWARE with the value path to software folder in the server and run manually the script. coudl you give me any suggestion?? Many thanks in advance. Jose The output was C:\Documents and Settings\cortijoset SOFTWARE=\\delchnpek-fs002\WPKG-1.0.2\sof tware C:\Documents and Settings\cortijoecho %SOFTWARE% \\delchnpek-fs002\WPKG-1.0.2\software C:\Documents and Settings\cortijocscript \\DELCHNPEK-FS002\WPKG-1.0.2\wpkg.js / synchronize /verbose Microsoft (R) Windows Script Host Version 5.6 Copyright (C) Microsoft Corporation 1996-2001. All rights reserved. Reboot-Cmd is standard. Initialized temporary local log file: d:\temp\wpkg-logInit.log Initializing new log file: d:\temp\wpkg-delchnpek-wit01.log WPKG 1.0.2 starting... Base directory is '\\DELCHNPEK-FS002\WPKG-1.0.2'. Log level is 255 Trying to read XML file: \\DELCHNPEK-FS002\WPKG-1.0.2\profiles.xml Successfully loaded XML file: \\DELCHNPEK-FS002\WPKG-1.0.2\profiles.xml Trying to read XML files from directory: \\DELCHNPEK-FS002\WPKG-1.0.2\profiles Reading XML file: //DELCHNPEK-FS002/WPKG-1.0.2/profiles/default.xml Trying to read XML file: \\DELCHNPEK-FS002\WPKG-1.0.2\hosts.xml Successfully loaded XML file: \\DELCHNPEK-FS002\WPKG-1.0.2\hosts.xml Trying to read XML files from directory: \\DELCHNPEK-FS002\WPKG-1.0.2\hosts Trying to read XML file: \\DELCHNPEK-FS002\WPKG-1.0.2\packages.xml Successfully loaded XML file: \\DELCHNPEK-FS002\WPKG-1.0.2\packages.xml Trying to read XML files from directory: \\DELCHNPEK-FS002\WPKG-1.0.2\packages Reading XML file: //DELCHNPEK-FS002/WPKG-1.0.2/packages/imageresize.xml Profiles applying to the current host: default Reading settings file: C:\WINDOWS\system32\wpkg.xml Trying to read XML file: C:\WINDOWS\system32\wpkg.xml Successfully loaded XML file: C:\WINDOWS\system32\wpkg.xml Hosts file contains 1 hosts: DELCHNPEK-WIT01 Settings file contains 0 packages: Packages file contains 4 packages: wpkg1 wpkg2 wpkg3 time Profile file contains 4 profiles: default custom administration other Using profile(s): default Getting profiles which apply to this node. Applying profile: default Adding package with ID 'imageresize' to profile packages. Profile inconsitency: Package with ID 'imageresize' is listed in profile but doe s not exist within the package database or the local settings file. Please cont act your system administrator! Synchronizing: Number of packages referenced by profile: 0 Number of packages to remove: 0 Saving sorted settings to 'C:\WINDOWS\system32\wpkg.xml'. Saving XML : C:\WINDOWS\system32\wpkg.xml - Reporting bugs, all WPKG mailing lists http://wpkg.org/Support ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Profile inconsitency: Package with ID 'imageresize' is listed in profile but ...
Hi Jose, Jose Cortijo wrote: But before I tried to run it in my own computer from cmd. I get an error the wpkg database is empty It should be empty as far I didnt install any softwarre yet. I create the variable SOFTWARE with the value path to software folder in the server and run manually the script. coudl you give me any suggestion?? Sure, let's try to sort it out. Successfully loaded XML file: \\DELCHNPEK-FS002\WPKG-1.0.2\profiles.xml Reading XML file: //DELCHNPEK-FS002/WPKG-1.0.2/profiles/default.xml So two profile definition files have been read. Probably profiles.xml is just the sample one included. You might remove it. Successfully loaded XML file: \\DELCHNPEK-FS002\WPKG-1.0.2\hosts.xml OK, it seems to use host.xml. No host definitions stored within the hosts/ subdirectory. Successfully loaded XML file: \\DELCHNPEK-FS002\WPKG-1.0.2\packages.xml Reading XML file: //DELCHNPEK-FS002/WPKG-1.0.2/packages/imageresize.xml Good, here it read pacakges.xml (probably just the sample file included). You might remove it if you don't need the packages defined there. Reading imageresize.xml seems to be fine too. Profiles applying to the current host: default OK; the profile assigned (look at hosts.xml) ist default. Hosts file contains 1 hosts: DELCHNPEK-WIT01 Just one host? Hmm, you might consider to use a regular expression for productive use. Something like .+ will match all hosts. Settings file contains 0 packages: This is correct - your local wpkg.xml has not been written yet. Packages file contains 4 packages: wpkg1 wpkg2 wpkg3 time Looks a bit like the default list of packages. And here the problem seems to be actually. The default packages.xml includes exactly these 4 sample packages. It seems that either your imageresize.xml does not contain any package - or you just copied an entry and forgot to change the ID to imageresize. Your package definition within imageresize.xml should looks something like: packages package id=imageresize name=Image Resize revision=1 reboot=false priority=100 ... /package /packages Profile file contains 4 profiles: default custom administration other Correct - and as seen above default is applied to the host. Using profile(s): default Seems to be correct most probably. Adding package with ID 'imageresize' to profile packages. Profile inconsitency: Package with ID 'imageresize' is listed in profile but doe s not exist within the package database or the local settings file. Please cont act your system administrator! As named above - WPKG did not find any package definition with id=imageresize in its header. Please verify your imageresize.xml definition file. Hope this helps and gives you some more background about how WPKG works. br, Rainer - Reporting bugs, all WPKG mailing lists http://wpkg.org/Support ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Package Renaming [SEC=UNCLASSIFIED]
Hi Leon, Leon Hedding (ICT) wrote: I have seen a number of other solutions that use a GUID as part of the package. Is this something that we could somehow include in WPKG? I don't know how we would be able to create the GUID to put into the packages.xml file, but that would certainly assist with package renames which do occur in the real world more often than we would like. Gaim goes to Pigdin was one recent occurrence. How exactly do you intend to use the GUID? As an identification for the package? I also see numerous problems when using the GUID. In fact somebody could already use the GUID within the package ID attribute. Unfortunately some (lots) of package maintainers seem to change GUIDs more often than others change their underwear. For example it seems that each Acrobat release uses another ID. In addition appropriate checks are much more reliable from my point of view. If your packages use appropriate checks even renaming should not be so much of a problem. The example of product renaming (Gaim = Pidgin) is not an issue at all in my eyes. The first Pidgin package is anyway a fresh installation (I even don't know if an upgrade from Gaim to Pidgin was possible or if they installed in parallel). In any case there is not much difference in the upgrade path. In one case Pidgin would be upgraded (full Pidgin installer executed) and probably even the old version of Gaim would have to be removed manually. In the second case the Gaim package is simply deleted and a new Pidgin package is created. WPKG will uninstall Gaim and install Pidgin. I don't see a problem here - this is actually the way I did it. br, Rainer - Reporting bugs, all WPKG mailing lists http://wpkg.org/Support ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Profile inconsitency: Package with ID 'imageresize' is listed in profile but ...
Hi Rainer, thanks a lot man. You were absolutely right. It is working right now. I create an imageresize.xml in the packages folder with that lines but I didnt know I should modify the packages.xml . So, the first file is not needed?? Thanks a lot 2008/5/20 Rainer Meier [EMAIL PROTECTED]: Hi Jose, Jose Cortijo wrote: But before I tried to run it in my own computer from cmd. I get an error the wpkg database is empty It should be empty as far I didnt install any softwarre yet. I create the variable SOFTWARE with the value path to software folder in the server and run manually the script. coudl you give me any suggestion?? Sure, let's try to sort it out. Successfully loaded XML file: \\DELCHNPEK-FS002\WPKG-1.0.2\profiles.xml Reading XML file: //DELCHNPEK-FS002/WPKG-1.0.2/profiles/default.xml So two profile definition files have been read. Probably profiles.xml is just the sample one included. You might remove it. Successfully loaded XML file: \\DELCHNPEK-FS002\WPKG-1.0.2\hosts.xml OK, it seems to use host.xml. No host definitions stored within the hosts/ subdirectory. Successfully loaded XML file: \\DELCHNPEK-FS002\WPKG-1.0.2\packages.xml Reading XML file: //DELCHNPEK-FS002/WPKG-1.0.2/packages/imageresize.xml Good, here it read pacakges.xml (probably just the sample file included). You might remove it if you don't need the packages defined there. Reading imageresize.xml seems to be fine too. Profiles applying to the current host: default OK; the profile assigned (look at hosts.xml) ist default. Hosts file contains 1 hosts: DELCHNPEK-WIT01 Just one host? Hmm, you might consider to use a regular expression for productive use. Something like .+ will match all hosts. Settings file contains 0 packages: This is correct - your local wpkg.xml has not been written yet. Packages file contains 4 packages: wpkg1 wpkg2 wpkg3 time Looks a bit like the default list of packages. And here the problem seems to be actually. The default packages.xml includes exactly these 4 sample packages. It seems that either your imageresize.xml does not contain any package - or you just copied an entry and forgot to change the ID to imageresize. Your package definition within imageresize.xml should looks something like: packages package id=imageresize name=Image Resize revision=1 reboot=false priority=100 ... /package /packages Profile file contains 4 profiles: default custom administration other Correct - and as seen above default is applied to the host. Using profile(s): default Seems to be correct most probably. Adding package with ID 'imageresize' to profile packages. Profile inconsitency: Package with ID 'imageresize' is listed in profile but doe s not exist within the package database or the local settings file. Please cont act your system administrator! As named above - WPKG did not find any package definition with id=imageresize in its header. Please verify your imageresize.xml definition file. Hope this helps and gives you some more background about how WPKG works. br, Rainer - Reporting bugs, all WPKG mailing lists http://wpkg.org/Support ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Profile inconsitency: Package with ID 'imageresize' is listed in profile but ...
Hi Jose, Jose Cortijo wrote: thanks a lot man. You were absolutely right. It is working right now. I create an imageresize.xml in the packages folder with that lines but I didnt know I should modify the packages.xml . So, the first file is not needed?? Right. Strictly speaking it is not needed. It is just an example. By historical reasons packages.xml within the same directory as wpkg.js is a collection of all packages in one file. Some people do not like to maintain a huge XML file with all package definitions in a single file. So WPKG also scans every XML file from the packages/ subfolder an concatenates them. So yes, you might get rid of packages.xml if you like (or move it to packages/) - whatever you prefer. In any case you should remove the sample entries you don't need; which are there only for demo purposes. Hope that clarifies it. br, Rainer - Reporting bugs, all WPKG mailing lists http://wpkg.org/Support ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Profile inconsitency: Package with ID 'imageresize' is listed in profile but ...
Hi again,
this is what I have in packages.xml
package
id=imageresize
name=Image Resize
revision=1
reboot=false
priority=100
notify=false
execute=always
!--
notify=false - does not notify the user (with true user would be
notified)
execute=always - always executes install cmd - sets time in this
example
execute=once - executes only once, and never again
--
check type=uninstall condition=exists path=Image Resizer Powertoy
for Windows XP /
install
cmd=\\delchnpek-fs002\wpkg-1.0.2\software\powertoys\ImageResizerPowertoySetup.exe
/S /v/qn /
remove cmd='msiexec /qb /l* c:\netinst\logs\powertoy.log
x{1CB92574-96F2-467B-B793-5CEB35C40C29}' /
/package
and this is what I have in imageresize.xml
package
id=imageresize
name=Image Resize
revision=1
reboot=false
priority=100
notify=false
execute=always
!--
notify=false - does not notify the user (with true user would be
notified)
execute=always - always executes install cmd - sets time in this
example
execute=once - executes only once, and never again
--
check type=uninstall condition=exists path=Image Resizer Powertoy
for Windows XP /
install
cmd=\\delchnpek-fs002\wpkg-1.0.2\software\powertoys\ImageResizerPowertoySetup.exe
/S /v/qn /
remove cmd='msiexec /qb /l* c:\netinst\logs\powertoy.log
x{1CB92574-96F2-467B-B793-5CEB35C40C29}' /
/package
The installation works fine, now I am trying uninstall the software. I
remove the entry in profile.xml and profiles\default.xml but the software
doesnt get uninstalled
some help?
thanks a lot man.
jose
2008/5/20 Jose Cortijo [EMAIL PROTECTED]:
Hi Rainer,
thanks a lot man. You were absolutely right. It is working right now. I
create an imageresize.xml in the packages folder with that lines but I didnt
know I should modify the packages.xml .
So, the first file is not needed??
Thanks a lot
2008/5/20 Rainer Meier [EMAIL PROTECTED]:
Hi Jose,
Jose Cortijo wrote:
But before I tried to run it in my own computer from cmd.
I get an error the wpkg database is empty It should be empty as far I
didnt install any softwarre yet.
I create the variable SOFTWARE with the value path to software folder in
the server and run manually the script.
coudl you give me any suggestion??
Sure, let's try to sort it out.
Successfully loaded XML file: \\DELCHNPEK-FS002\WPKG-1.0.2\profiles.xml
Reading XML file: //DELCHNPEK-FS002/WPKG-1.0.2/profiles/default.xml
So two profile definition files have been read. Probably profiles.xml is
just the sample one included. You might remove it.
Successfully loaded XML file: \\DELCHNPEK-FS002\WPKG-1.0.2\hosts.xml
OK, it seems to use host.xml. No host definitions stored within the hosts/
subdirectory.
Successfully loaded XML file: \\DELCHNPEK-FS002\WPKG-1.0.2\packages.xml
Reading XML file: //DELCHNPEK-FS002/WPKG-1.0.2/packages/imageresize.xml
Good, here it read pacakges.xml (probably just the sample file included).
You might remove it if you don't need the packages defined there. Reading
imageresize.xml seems to be fine too.
Profiles applying to the current host:
default
OK; the profile assigned (look at hosts.xml) ist default.
Hosts file contains 1 hosts:
DELCHNPEK-WIT01
Just one host? Hmm, you might consider to use a regular expression for
productive use. Something like .+ will match all hosts.
Settings file contains 0 packages:
This is correct - your local wpkg.xml has not been written yet.
Packages file contains 4 packages:
wpkg1
wpkg2
wpkg3
time
Looks a bit like the default list of packages. And here the problem seems
to be actually. The default packages.xml includes exactly these 4 sample
packages. It seems that either your imageresize.xml does not contain any
package - or you just copied an entry and forgot to change the ID to
imageresize. Your package definition within imageresize.xml should looks
something like:
packages
package
id=imageresize
name=Image Resize
revision=1
reboot=false
priority=100
...
/package
/packages
Profile file contains 4 profiles:
default
custom
administration
other
Correct - and as seen above default is applied to the host.
Using profile(s):
default
Seems to be correct most probably.
Adding package with ID 'imageresize' to profile packages.
Profile inconsitency: Package with ID 'imageresize' is listed in profile
but doe
s not exist within the package database or the local settings file.
Please cont
act your system administrator!
As named above - WPKG did not find any package definition with
id=imageresize in its header. Please verify your imageresize.xml
definition file.
Hope this helps and gives you some more background about how WPKG works.
br,
Rainer
-
Reporting bugs, all WPKG mailing
Re: [wpkg-users] Package Renaming [SEC=UNCLASSIFIED]
So possibly using a GUID as the package could already be done. The main difficulty with that is that it is not easy to remember and type in. The advantage is that once a package has been installed you don't ever have to worry when renaming a package for any reason. It would be an optional header in the XML that is only checked for upgrades and uninstalls and only if it did not already meet the requirement of the package ID. The upgrade from Gaim to Pidgin was possible, but required two packages. I bring this point up because I have had difficulties with case sensitivity in the past and had to perform a rename of all my packages. I know that wpkg now support non-case sensitive checks so that is a big bonus. There are places that have run once cmd's which do not create a residual file that is used for checking. In those instances as well it would be helpful to have a GUID option as well. Cheers, Leon Hedding - Reporting bugs, all WPKG mailing lists http://wpkg.org/Support ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Profile inconsistency: Package with ID'imageresize' is listed in profile but ...
Remove command is incorrect. Should be:
msiexec /qb /l* c:\netinst\logs\powertoy.log
/x{1CB92574-96F2-467B-B793-5CEB35C40C29}
You missed the /x. Review of the eventvwr usually helps with MSI
packages to see why they failed to install or uninstall.
Cheers,
Leon Hedding
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jose Cortijo
Sent: 20 May 2008 09:27
To: Rainer Meier
Cc: wpkg-users@lists.wpkg.org
Subject: Re: [wpkg-users] Profile inconsitency: Package with
ID'imageresize' is listed in profile but ...
Hi again,
this is what I have in packages.xml
package
id=imageresize
name=Image Resize
revision=1
reboot=false
priority=100
notify=false
execute=always
!--
notify=false - does not notify the user (with true user would be
notified)
execute=always - always executes install cmd - sets time in this
example
execute=once - executes only once, and never again
--
check type=uninstall condition=exists path=Image Resizer
Powertoy for Windows XP /
install
cmd=\\delchnpek-fs002\wpkg-1.0.2\software\powertoys\ImageResizerPowerto
ySetup.exe /S /v/qn /
remove cmd='msiexec /qb /l* c:\netinst\logs\powertoy.log
x{1CB92574-96F2-467B-B793-5CEB35C40C29}' /
/package
and this is what I have in imageresize.xml
package
id=imageresize
name=Image Resize
revision=1
reboot=false
priority=100
notify=false
execute=always
!--
notify=false - does not notify the user (with true user would be
notified)
execute=always - always executes install cmd - sets time in this
example
execute=once - executes only once, and never again
--
check type=uninstall condition=exists path=Image Resizer
Powertoy for Windows XP /
install
cmd=\\delchnpek-fs002\wpkg-1.0.2\software\powertoys\ImageResizerPowerto
ySetup.exe /S /v/qn /
remove cmd='msiexec /qb /l* c:\netinst\logs\powertoy.log
x{1CB92574-96F2-467B-B793-5CEB35C40C29}' /
/package
The installation works fine, now I am trying uninstall the software. I
remove the entry in profile.xml and profiles\default.xml but the
software doesnt get uninstalled
some help?
thanks a lot man.
jose
2008/5/20 Jose Cortijo [EMAIL PROTECTED]:
Hi Rainer,
thanks a lot man. You were absolutely right. It is working right now. I
create an imageresize.xml in the packages folder with that lines but I
didnt know I should modify the packages.xml .
So, the first file is not needed??
Thanks a lot
2008/5/20 Rainer Meier [EMAIL PROTECTED]:
Hi Jose,
Jose Cortijo wrote:
But before I tried to run it in my own computer from cmd.
I get an error the wpkg database is empty It should be empty as
far I didnt install any softwarre yet.
I create the variable SOFTWARE with the value path to software
folder in the server and run manually the script.
coudl you give me any suggestion??
Sure, let's try to sort it out.
Successfully loaded XML file:
\\DELCHNPEK-FS002\WPKG-1.0.2\profiles.xml
Reading XML file:
//DELCHNPEK-FS002/WPKG-1.0.2/profiles/default.xml
So two profile definition files have been read. Probably
profiles.xml is just the sample one included. You might remove it.
Successfully loaded XML file:
\\DELCHNPEK-FS002\WPKG-1.0.2\hosts.xml
OK, it seems to use host.xml. No host definitions stored within
the hosts/ subdirectory.
Successfully loaded XML file:
\\DELCHNPEK-FS002\WPKG-1.0.2\packages.xml
Reading XML file:
//DELCHNPEK-FS002/WPKG-1.0.2/packages/imageresize.xml
Good, here it read pacakges.xml (probably just the sample file
included). You might remove it if you don't need the packages defined
there. Reading imageresize.xml seems to be fine too.
Profiles applying to the current host:
default
OK; the profile assigned (look at hosts.xml) ist default.
Hosts file contains 1 hosts:
DELCHNPEK-WIT01
Just one host? Hmm, you might consider to use a regular
expression for productive use. Something like .+ will match all hosts.
Settings file contains 0 packages:
This is correct - your local wpkg.xml has not been written yet.
Packages file contains 4 packages:
wpkg1
wpkg2
wpkg3
time
Looks a bit like the default list of packages. And here the
problem seems to be actually. The default packages.xml includes
exactly these 4 sample packages. It seems that either your
imageresize.xml does not contain any package - or you just copied an
entry and forgot to change the ID to imageresize. Your package
definition within imageresize.xml
Re: [wpkg-users] Package Renaming [SEC=UNCLASSIFIED]
What you describe is exactly what I am thinking. The other bit is as you
say, it is quite difficult to read logs since the GUID would be in the
logs then. That is why I am wondering if having an actual (optional)
GUID value would be of benefit. It might be over kill, but would
certainly help in at least the run once instance.
Cheers,
Leon Hedding
-Original Message-
From: Rainer Meier [mailto:[EMAIL PROTECTED]
Sent: 20 May 2008 09:37
To: Leon Hedding (ICT)
Cc: wpkg
Subject: Re: [wpkg-users] Package Renaming [SEC=UNCLASSIFIED]
To make it clear again. WPKG uses two attributes within the package
which can be used:
id:
This attribute is the unique identifier of each package. It cannot be
changed/renamed without making WPKG think it is a different package. So
if you put the GUID there it's fine - as long as you don't change the
GUID.
name:
More descriptive name - you can put any string in here. You might also
change this name later on without affecting WPKG at all.
So to take our Pidgin example again you could create a package like
packages
package
id={unique-GUID}
name=Gaim
revision=1
reboot=false
priority=100
...
/package
/packages
After the release of Pidgin you can do the following:
packages
package
id={unique-GUID}
name=Pidgin
revision=2
reboot=false
priority=100
...
/package
/packages
This would upgrade the Gaim Package to Pidgin. As long as you do not
change the GUID within the id field.
I am not fully sure if this is what you meant. So please don't shoot me
if not. I am sure you could explain it to me if this did not match your
expectations.
br,
Rainer
-
Reporting bugs, all WPKG mailing lists http://wpkg.org/Support
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] Vista and WPKG
Hi All, I've got a few Vista machines to support now, alas, so I've been giving some thought to how to get some information about what WPKG is doing to the users. This mail is me thinking aloud so that people get a chance to direct my efforts - or maybe offer assistance! The current WPKG client uses winlogon hooks to display its user message. These hooks have been removed from Vista so we need to use a different method. So far I've coded up a proof-of-concept executable which uses the WTSSendMessage API to put a message on the session attached to the physical console of the system (works under Vista Enterprise and XP Pro). I'm using named pipes to communicate - the intention is that wpkg.js will be able to send information down the named pipe to communicate to the user. WTSSendMessage just displays a message box to the user with at least an OK button, so what I think I need to do is have a thread monitoring whether the user has dismissed the message box or whether the message box has timed-out, and immediately produce another one with the latest message. Another thread will monitor the named pipe and put the latest message into a buffer for display. (That's today's job!) I think this means that there's no guarantee that the message from WPKG will actually get seen by the user (message A might get displayed, message B might be over-written by message C while message A is displayed, then message C is displayed) but perhaps offers some information about what is going on. Any comments? Yours, Frank - Reporting bugs, all WPKG mailing lists http://wpkg.org/Support ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Package Renaming [SEC=UNCLASSIFIED]
Hi Leon,
Leon Hedding (ICT) wrote:
What you describe is exactly what I am thinking. The other bit is as you
say, it is quite difficult to read logs since the GUID would be in the
logs then. That is why I am wondering if having an actual (optional)
GUID value would be of benefit. It might be over kill, but would
certainly help in at least the run once instance.
Did you read the rules at http://wpkg.org/Support? :-)
In general reading the logs should not be so much of a problem as
usually the output within the logfiles, event log and on the console is
as follows:
... package package-name (package-id) installed...
So this means you would see something like
... package Pidgin ({0EFDF2F9-836D-4EB7-A32D-038BD3F1FB2A}) installed...
Which is not really unreadable as the ID is mainly for administrators
anyway. I think introducing another guid attribute would be redundant
as the id was exactly mentioned to be used for this - identifying the
package. Describing the package in a readable form is the purpose of the
name attribute.
br,
Rainer
-
Reporting bugs, all WPKG mailing lists http://wpkg.org/Support
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Vista and WPKG
Hi Frank, Dr. Frank Lee wrote: I've got a few Vista machines to support now, alas, so I've been giving some thought to how to get some information about what WPKG is doing to the users. This mail is me thinking aloud so that people get a chance to direct my efforts - or maybe offer assistance! I am maintaining XP and Vista clients too. That's why I made some enhancements for full Vista and also 64-bit support in wpkg.js. The current WPKG client uses winlogon hooks to display its user message. These hooks have been removed from Vista so we need to use a different method. So far I've coded up a proof-of-concept executable which uses the WTSSendMessage API to put a message on the session attached to the physical console of the system (works under Vista Enterprise and XP Pro). You're right - I never tried the logon delay feature on Vista. So you say I don't have to try ;-) In fact I don't like the logon delay feature so much as I do not want to keep users waiting. I am installing the package in background while the user logs on. My experience is that WPKG finishes its work (even when some smaller packages are installed) before the user actually gets the chance to run some applications. And even if the user already started applications - in worst case installation fails and it will be re-tried on next start until it succeeds. Some (most?) installers can also handler the case when the application is currently running. Either by closing it or by scheduling file replacements for next windows start. I'm using named pipes to communicate - the intention is that wpkg.js will be able to send information down the named pipe to communicate to the user. WTSSendMessage just displays a message box to the user with at least an OK button, so what I think I need to do is have a thread monitoring whether the user has dismissed the message box or whether the message box has timed-out, and immediately produce another one with the latest message. Another thread will monitor the named pipe and put the latest message into a buffer for display. (That's today's job!) As already outlined when we discussed about displaying some progress information when using logon delay: I did not find a way to use named pipes by JScript. There seems to be no way as it is impossible to open a named pipe by JScript. That's why WPKG 1.1 is writing status information to STDOUT in order to allow re-directing of STDOUT and parsing its output. That's currently the most reliable way I was able to figure out. Well if we find a better way it might be quite simple to implement. Current WPKG architecture would allow to exchange the STDOUT printing with any output module. But remember, it needs to be very reliable and stable - I will not accept proposals which require hacks or external programs or other unreliable and complicated work-arounds as I consider this feature to be much less important than stability. I think this means that there's no guarantee that the message from WPKG will actually get seen by the user (message A might get displayed, message B might be over-written by message C while message A is displayed, then message C is displayed) but perhaps offers some information about what is going on. I am quite sure a thread could pick up the messages fast enough. However named pipes might not work - see above. Capturing WPKG STDOUT to a buffer might work better. br, Rainer - Reporting bugs, all WPKG mailing lists http://wpkg.org/Support ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Profile inconsitency: Package with ID 'imageresize' is listed in profile but ...
ok, it works perfect now.
Now just appear before all the process a message saying that the file is
already in c:\windows\download installation, if I want to replace or not
that file? any way to overwrite always??
but if I say yes, the package gets removed.
perfect , thanks a lot!!
2008/5/20 Rainer Meier [EMAIL PROTECTED]:
Hi Jose,
Jose Cortijo wrote:
this is what I have in packages.xml
package
id=imageresize
name=Image Resize
revision=1
reboot=false
priority=100
notify=false
execute=always
!--
notify=false - does not notify the user (with true user would be
notified)
execute=always - always executes install cmd - sets time in this
example
execute=once - executes only once, and never again
--
check type=uninstall condition=exists path=Image Resizer Powertoy
for Windows XP /
install
cmd=\\delchnpek-fs002\wpkg-1.0.2\software\powertoys\ImageResizerPowertoySetup.exe
/S /v/qn /
remove cmd='msiexec /qb /l* c:\netinst\logs\powertoy.log
x{1CB92574-96F2-467B-B793-5CEB35C40C29}' /
/package
This is fine - except the wrong remove command as outlined by Leon.
and this is what I have in imageresize.xml
package
id=imageresize
name=Image Resize
revision=1
reboot=false
priority=100
notify=false
execute=always
!--
notify=false - does not notify the user (with true user would be
notified)
execute=always - always executes install cmd - sets time in this
example
execute=once - executes only once, and never again
--
check type=uninstall condition=exists path=Image Resizer Powertoy
for Windows XP /
install
cmd=\\delchnpek-fs002\wpkg-1.0.2\software\powertoys\ImageResizerPowertoySetup.exe
/S /v/qn /
remove cmd='msiexec /qb /l* c:\netinst\logs\powertoy.log
x{1CB92574-96F2-467B-B793-5CEB35C40C29}' /
/package
So this means you have the package in both files:
- packages.xml
- packages/imageresize.xml
This is not needed. Either remove it from packages.xml or remove
imageresize.xml. WPKG will read both files - but the latter one will
overwrite the previous one as the packages need to be unique (by id).
The installation works fine, now I am trying uninstall the software. I
remove the entry in profile.xml and profiles\default.xml but the software
doesnt get uninstalled
As outlined by Leaon your remove command seems to be broken. I guess you
would see some errors in your logs about failed msiexec. WPKG will continue
to try uninstalling the package. To fix that you might fix your remove
command definition and increase the package version. Then WPKG will first do
an upgrade (including also the new remove command) and then correctly
uninstall it.
br,
Rainer
-
Reporting bugs, all WPKG mailing lists http://wpkg.org/Support
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Vista and WPKG
Hi Rainer,
I am maintaining XP and Vista clients too. That's why I made some
enhancements for full Vista and also 64-bit support in wpkg.js.
Any jolly good they are, too! The Vista machines are working well with
WPKG.
You're right - I never tried the logon delay feature on Vista. So you say I
don't have to try ;-)
No errors or anything - just no display!
In fact I don't like the logon delay feature so much as I do not want to keep
users waiting. I am installing the package in background while the user logs
on. My experience is that WPKG finishes its work (even when some smaller
packages are installed) before the user actually gets the chance to run some
applications.
And even if the user already started applications - in worst case
installation fails and it will be re-tried on next start until it succeeds.
Some (most?) installers can also handler the case when the application is
currently running. Either by closing it or by scheduling file replacements
for next windows start.
I've found some problem with that approach when updating virus scanners,
for example, which require reboots. Our users get a bit upset when the
machine starts to reboot while they're working! I think I'd prefer to
inconvenience the users by delaying them starting work than interrupting
them when they've started - but that's just my view.
As already outlined when we discussed about displaying some progress
information when using logon delay: I did not find a way to use named pipes
by JScript. There seems to be no way as it is impossible to open a named pipe
by JScript. That's why WPKG 1.1 is writing status information to STDOUT in
order to allow re-directing of STDOUT and parsing its output. That's
currently the most reliable way I was able to figure out.
That method would be possible too. There's a page
http://www.codesegment.com/sms_studio_help/Help/Tutorial/Samples/How%20to%20Send%20a%20Message%20through%20Named%20Pipe.htm
on using Named Pipes through VBScript, so I'd imagine the same approach
would work through JScript since they both use WSH.
Well if we find a better way it might be quite simple to implement. Current
WPKG architecture would allow to exchange the STDOUT printing with any output
module. But remember, it needs to be very reliable and stable - I will not
accept proposals which require hacks or external programs or other
unreliable and complicated work-arounds as I consider this feature to be much
less important than stability.
I'm hoping that using named pipes would be quite easy:
try {
writeToNamedPipe(msg);
} catch (e) {
// Oh well, it didn't work.
}
We might need an equivalent of dinfo() to indicate messages for the user
and perhaps some configuration about what messages ought to be sent. (I'd
like lots of detail but I suspect others wouldn't!)
At the moment, though, I'm concentrating on the code to display the
message box and assuming that we can get the information into the named
pipe easily enough, either through wpkg.js itself or by having something
parsing STDOUT.
I am quite sure a thread could pick up the messages fast enough. However
named pipes might not work - see above. Capturing WPKG STDOUT to a buffer
might work better.
It's more that there's no way of removing the message box once it's been
sent to the screen (I think - corrections welcome if I'm wrong about
that), so it's possible that the message box thread would pick up a
message which cannot be displayed while a previous message is being
displayed and then gets a third message which over-writes the second.
I think ideally we might try to use the CreateProcessAsUser API and get a
window where we can update things in real time, but that would be a job
for later / someone who knows more than I do about this sort of coding!
Yours,
Frank
-
Reporting bugs, all WPKG mailing lists http://wpkg.org/Support
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Vista and WPKG
Hi Frank,
Dr. Frank Lee wrote:
That method would be possible too. There's a page
http://www.codesegment.com/sms_studio_help/Help/Tutorial/Samples/How%20to%20Send%20a%20Message%20through%20Named%20Pipe.htm
on using Named Pipes through VBScript, so I'd imagine the same approach
would work through JScript since they both use WSH.
Unfortunately this is not true. I tried and lost about 2 days searching
for a solution but it seems to be impossible. I know it works with
VBScript, but not with JSCript.
I'm hoping that using named pipes would be quite easy:
try {
writeToNamedPipe(msg);
} catch (e) {
// Oh well, it didn't work.
}
This is what I thought as well. But implementing writeToNamedPipe(msg)
is actually the problem.
We might need an equivalent of dinfo() to indicate messages for the user
and perhaps some configuration about what messages ought to be sent.
(I'd like lots of detail but I suspect others wouldn't!)
This is addressed by the status print feature of WPKG 1.1 already. WPKG
already supports it, WPKG client is under investigation to be enhanced
to read the output of WPKG.
At the moment, though, I'm concentrating on the code to display the
message box and assuming that we can get the information into the named
pipe easily enough, either through wpkg.js itself or by having something
parsing STDOUT.
Since the first proposal seems not to be possible I did the necessary
changes already some time ago but currently printing to STDOUT.
Of course this might be changed if somebody knows how to do it in JScript.
It's more that there's no way of removing the message box once it's been
sent to the screen (I think - corrections welcome if I'm wrong about
that), so it's possible that the message box thread would pick up a
message which cannot be displayed while a previous message is being
displayed and then gets a third message which over-writes the second.
Why not using a thread which picks up messages and puts it to a local queue?
I think ideally we might try to use the CreateProcessAsUser API and get
a window where we can update things in real time, but that would be a
job for later / someone who knows more than I do about this sort of coding!
Also here, not much experience yet on this topic. Sorry.
br,
Rainer
-
Reporting bugs, all WPKG mailing lists http://wpkg.org/Support
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Profile inconsitency: Package with ID 'imageresize' is listed in profile but ...
Hi Jose,
Jose Cortijo wrote:
ok, it works perfect now.
Now just appear before all the process a message saying that the file is
already in c:\windows\download installation, if I want to replace or not
that file? any way to overwrite always??
but if I say yes, the package gets removed.
I don't know exactly why you get this message. Let's have a look at the
package definition once again:
package
id=imageresize
name=Image Resize
revision=1
reboot=false
priority=100
notify=false
execute=always
!--
notify=false - does not notify the user (with true user
would be notified)
execute=always - always executes install cmd - sets time
in this example
execute=once - executes only once, and never again
--
check type=uninstall condition=exists path=Image
Resizer Powertoy for Windows XP /
install
cmd=\\delchnpek-fs002\wpkg-1.0.2\software\powertoys\ImageResizerPowertoySetup.exe
/S /v/qn /
remove cmd='msiexec /qb /l* c:\netinst\logs\powertoy.log
x{1CB92574-96F2-467B-B793-5CEB35C40C29}' /
/package
I see some glitches here:
1. execute=always
This attribute within the package definition should be set only if you
wish that the package is re-installed on each WPGK run. I recommend to
remove it in this case
2. remove command
You use msiexec /qb /l* c:\netinst\logs\powertoy.log
/x{1CB92574-96F2-467B-B793-5CEB35C40C29}
Probably it would be a good idea to replace /qb by /qn parameter.
package
id=imageresize
name=Image Resize
revision=1
reboot=false
priority=100
notify=false
check type=uninstall condition=exists path=Image
Resizer Powertoy for Windows XP /
install
cmd=\\delchnpek-fs002\wpkg-1.0.2\software\powertoys\ImageResizerPowertoySetup.exe
/S /v/qn /
remove cmd='msiexec /qn /l* c:\netinst\logs\powertoy.log
/x{1CB92574-96F2-467B-B793-5CEB35C40C29}' /
/package
NOTE: Just pasted this one - not tested.
br,
Rainer
-
Reporting bugs, all WPKG mailing lists http://wpkg.org/Support
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] unexpected installation of already installed package
I was beginning to edit a package definition in packages.xml with the intention of gradually fixing and testing it. The package was already installed on a number of workstations, but I did not change the revision number, which was zero. I revised some of the install and upgrade commands and I changed the check condition. I was surprised to find that workstations were trying to install the package when they booted. As I said, the package was already installed on the workstations and there was no change in the revisions number. I'm guessing the workstations noticed the change in the check condition (which they did not meet) and decided an installation (not an upgrade) was needed. Expected behavior or a little bug? Mark - Reporting bugs, all WPKG mailing lists http://wpkg.org/Support ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] unexpected installation of already installed package
Hi Mark,
Mark Nienberg wrote:
I was beginning to edit a package definition in packages.xml with the
intention of
gradually fixing and testing it. The package was already installed on a
number of
workstations, but I did not change the revision number, which was zero. I
revised
some of the install and upgrade commands and I changed the check condition.
I was surprised to find that workstations were trying to install the package
when
they booted. As I said, the package was already installed on the
workstations and
there was no change in the revisions number. I'm guessing the workstations
noticed
the change in the check condition (which they did not meet) and decided an
installation (not an upgrade) was needed.
Expected behavior or a little bug?
You could be right. The install function took the server side definition
to check if a package is installed. In your case you probably got a log
entry like
Installed but checks failed. Re-Installing.
I will verify this. I think WPKG should use the checks defined in local
wpkg.xml to check if a package is still installed.
The change should be simple. Just change
if (isInstalled(packageNode)) {
to
if (isInstalled(installedPackage)) {
somewhere at line 2450. As a result WPKG will execute the checks if a
package is installed by using the locally defined checks.
After tests (and probably your feedback too) I will include it within
the next patch release.
br,
Rainer
-
Reporting bugs, all WPKG mailing lists http://wpkg.org/Support
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] unexpected installation of already installed package
Rainer Meier wrote: Hi Mark, Mark Nienberg wrote: I was beginning to edit a package definition in packages.xml with the intention of gradually fixing and testing it. The package was already installed on a number of workstations, but I did not change the revision number, which was zero. I revised some of the install and upgrade commands and I changed the check condition. I was surprised to find that workstations were trying to install the package when they booted. As I said, the package was already installed on the workstations and there was no change in the revisions number. I'm guessing the workstations noticed the change in the check condition (which they did not meet) and decided an installation (not an upgrade) was needed. Expected behavior or a little bug? You could be right. The install function took the server side definition to check if a package is installed. In your case you probably got a log entry like Installed but checks failed. Re-Installing. There was never a log entry for whether the package was installed or not. The first mention of the package is Installing dependencies for..., following by Installing, etc. Mark - Reporting bugs, all WPKG mailing lists http://wpkg.org/Support ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
