Hi Donny, On 22.07.2010 18:34, Donny Brooks wrote: > Please disregard this as I think I got it with just removing the package entry > from the profiles.xml portion. Thanks anyways! Please also note that removing from profiles.xml will make wpkg removing the package on next synchronization. Assuming that all your remove commands listed in the package definition are correct then the packages should uninstall properly. In case some packages fail to remove WPKG will re-try to remove them on each synchronization. To fix package definition problems just fix the remove commands in packages.xml and increase the package revision. So WPKG will use its upgrade-before-remove feature and first upgrade to your updated package specification (well, make sure the upgrade runs fine too) and immediately after execute the new/fixed remove commands again. Alternatively you can also remove packages which fail to remove cleanly (e.g. wrong remove commands, remove does not work as expected...) from packages.xml. In this case WPKG will first try to remove them and in case removal fails it will still remove the package definition from the local wpkg.xml since the package is regarded as a "zombie". Please note that in this case the application might remain on the client (but WPKG just forgets about it). So usually you should try to just remove packages from profiles.xml. If uninstall fails then first try to fix up your packages. And as a last action just remove the package entirely from packages.xml so WPKG will not re-try over and over again to remove the package. br, Rainer |