[wpkg-users] wpkg for crapware removal?

[Rainer Meier]

Hi Jon,

On 14.12.2012 01:32, Jon Goldberg wrote:
> I just inherited a new client whose workstations have users logged in as
> local administrators; the net result is a ton of crapware.

Yes this is what usually happens.


> I considered creating wpkg packages for the crapware with only a
> "remove" section to a) simplify cleanup, and b) ensure that machines
> remain clean, since a handful of users will be retaining local admin
> privileges.
>
> So, my questions:
> * Has anyone else tried this?  Do they have any package definitions to
> share?

In fact this will likely not work as expected. WPKG "remove" commands are 
executed only when a package is installed by WPKG and later removed.
What you're looking for is rather a package which has execute="always" flag set 
and therefore runs the install commands on every WPKG run.
Then put your crapware removal scripts in install commands. Note that if a 
specific crapware is not installed you need to deal with it. For example by 
using use scripts which still return success exit code even if crapware was not 
found and not removed. You might also use conditional commands to execute 
install commands only if specific crapware is found.

Also note that removing crapware would require you to maintain a potentially big 
list of crapware you would like to remove. Moreover removing it might have 
impact on installed applications as some of them will not work properly if the 
crapware (might be ad-ware) component is removed.

As long as users still have admin privileges it might end in a fight between 
your WPKG crapware-remover and the user re-installing it - up to the extend the 
user is going to disable automatic WPKG run (since the user has admin privileges 
you can't really prevent this too).


> * Should I bother posting these package definitions to the wpkg wiki?  I
> don't want to load up the wiki with entries for software no one would
> ever use, but I know that other folks may also benefit from these
> definitions.

Well yes, I think it could be useful to have unattended scripts or command-line 
parameters for unattended crapware removal at least for common crapware. This 
might be useful for others as well.

br,
Rainer