o- recreate the GPO, but set it to uninstall after it is revoked? o- plunder the registry a machine with the icon to see how it's set up in there, then run a login script to kill it?
On Mon, Jun 13, 2016 at 5:41 PM, Richard Stovall <[email protected]> wrote: > Seeing that no one uses SEP for application whitelisting (and I'm beginning > to understand why...), let's move on to another topic. One more directly > related to this list's charter. > > I'm working with a client who has deployed software via GPO for a long time. > We have one package we're trying to work with that behaves for all the world > like it was deployed via assignment to users. Uninstall the beast and it > still has a start menu icon which, if you click it, it reaches out to the > network installation point and puts it back on. This is classic deployment > via GPO assignment to users, right? > > Trouble is, there is no GPO that currently assigns this software to users. > It may be that the offending GPO was deleted some time ago and did not have > the "Uninstall this application when it falls out of the scope of > management" flag set. Does this sound plausible? If so, how do we > eliminate the offending start menu shortcut? I can always remove the > network installation point, but I'd like to clean it up 100% properly. > > Any ideas? > > Thanks, > Richard S
