[gptalk] Re: GPO .msi installation wont uninstall..
- From: Thorbjörn Sjövold <thorbjorn.sjovold@xxxxxxxxxxxxxxx>
- To: "gptalk@xxxxxxxxxxxxx" <gptalk@xxxxxxxxxxxxx>
- Date: Thu, 24 Apr 2008 21:58:10 +0200
Hi Ray,
Yes, I hang around Darrens list, it is one of the best with some really good
contributors, including Darren who seems to be living in every time zone there
is, since he answers around the clock :)
I'll be more than happy to help you out and also explain how the security
context of Group Policy Software Installation (GPSI) works while at it.
GPSI does not use a special account, rather the context it runs in is the
context of the System, and when it executes user policies it has an additional
token that it can use to change context to the user that the GPOs are being
applied to. Actually the above is true for all Group Policy processing. So
there is no special account involved like some services use for example.
The property that the setting you refer to is ALLUSERS, a property that is used
to control if only the current user that runs the setup should have the package
(set to 0) or all users (then you set it to 1 or 2), but when installing the
CSEs that is redundant since it is installed with the Client Side Extensions
using the Computer part of the GPO. So this means the exact same credentials is
used as when for example a Startup script is used. When accidental orphaning
happens instead of an uninstall, using the startup script is a very efficient
way to remove software that has been pushed out with GPSI.
My theory is that the problem is related to that that you are running versions
3.5.7 and 3.6.0 since we actually just have released 3.2 :) Seriously, since
this cannot be due to the installation context I think the problem IS related
to versioning here, i.e. you could have two versions where one upgrade the
other and then you point to the wrong one with MSIEXEC and there will nothing
to uninstall. But send me an email at the address below my name and I'll make
sure you get the right help you need, I think in this case all we have to do is
figure out the installed version and make sure your script point to it.
Thanks,
Thorbjörn Sjövold
Special Operations Software
www.specopssoft.com
thorbjorn.sjovold a t specopssoft.com
Download our free tool for remote Gpupdate with graphical reporting,
http://www.specopssoft.com/products/specopsgpupdate/
-----Original Message-----
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On
Behalf Of Ray Lewis
Sent: den 24 april 2008 19:30
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: GPO .msi installation wont uninstall..
Apologies to those who couldn't read the original email - seems my webmail
text editor spat its dummy - see below:
Thomas, there are three software packages:
* Specops Inventory client side extension v.3.5.7
* Specops Inventory client side extension v.3.6.0
* Specops Deploy Client side extension
We trialled the software some time ago but my company decided not to go with
the packages at this time and will possibly refer back at a later date. I
have contacted the vendors and liaised with one of their tech guys to no
avail.. I understand Thorbjörn Sjövold visits this board and is the original
"builder" of these .msi' so his input would really be appreciated, but any
ideas from all you guys would be a massive bonus.
Thanks
___________________________________________________________________________
Hello all - Little dilemma...
Some time ago, I pushed an .msi installation via Computer Configuration >
Software Settings > Software Installation within one of my GPO' which
consequently worked fine...
However, the GPO was deleted and now I want to remove the software from my
client machines. I scripted an msiexec.exe command using the /x & /passive
switch pointing to the original .msi files which should take care of things
nicely (pushed using startup script). But, the un-installation script won't
work because the original .msi package must have been built with "install
for this user only" - which now consequently wont let you uninstall it
despite what permissions you have on the client!
Any ideas how this should be tackled - which account would GP have used to
install the original .msi?
Cheers
Ray
***********************
You can unsubscribe from gptalk by sending email to
gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by
logging into the freelists.org Web interface. Archives for the list are
available at //www.freelists.org/archives/gptalk/
************************
***********************
You can unsubscribe from gptalk by sending email to
gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by
logging into the freelists.org Web interface. Archives for the list are
available at //www.freelists.org/archives/gptalk/
************************
Other related posts:
