Right, Looks like the MSI was authored per user with advertised shortcuts. You can see this and all other properties which control this by opening it in Orca. Possibly you can generate a transform and alter it at GPO install time unless they have done something intentional.
Either way, Orca will more than likely shed the light on it… jlc From: [email protected] [mailto:[email protected]] On Behalf Of Richard Stovall Sent: Monday, June 13, 2016 6:42 PM To: [email protected] Subject: [NTSysADM] GPO software installation 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
