Detection methods are basically the desired state of the install program. If your install program is an uninstall command line, then your desired state is the program not existing.
On Fri, Sep 5, 2014 at 12:30 PM, Taxter, Latisha <ltax...@kh.org> wrote: > If the file does not exist, then there should be no need for the > uninstall. > > > > *From:* listsad...@lists.myitforum.com [mailto: > listsad...@lists.myitforum.com] *On Behalf Of *Ryan > *Sent:* Friday, September 5, 2014 10:24 AM > *To:* mssms@lists.myitforum.com > *Subject:* Re: [mssms] RE: Quick question - uninstall > > > > Are you deploying an application that runs an uninstall as the install? If > so, the detection rule should be the program not existing, which would have > to be done with a script. Detection methods don't support "does not exist". > > > > If the uninstall command line is listed in the "Uninstall Program" portion > of the deployment type, your detection method would need to be if the > program does exist. Then you'd deploy the app with a purpose of uninstall > instead of install. > > > > On Fri, Sep 5, 2014 at 12:07 PM, Murray, Mike <mmur...@csuchico.edu> > wrote: > > That's what I'm wondering. My detection rule is looking for > %ProgramFiles%\Microsoft Security Client\msseces.exe. This file exists, so > does that mean the uninstall won't run? > > Mike > > > > -----Original Message----- > From: listsad...@lists.myitforum.com [mailto: > listsad...@lists.myitforum.com] On Behalf Of Taxter, Latisha > Sent: Friday, September 5, 2014 10:01 AM > To: mssms@lists.myitforum.com > Subject: [mssms] RE: Quick question - uninstall > > I'm still new to some of this on SCCM 2012, so excuse some of the basic > questions. Have you tried running the uninstall without the detection > rule.. say try it in good old packages and see if the issue is with the > detection rule? Or Sccm just not understanding the variables in your script > file? > > -----Original Message----- > From: listsad...@lists.myitforum.com [mailto: > listsad...@lists.myitforum.com] On Behalf Of Murray, Mike > Sent: Friday, September 5, 2014 9:44 AM > To: mssms@lists.myitforum.com > Subject: [mssms] RE: Quick question - uninstall > > The uninstall command points to the CMD file. Nothing in AppEnforce.log, > this is what I see in AppDiscovery.log: > > Performing detection of app deployment type Microsoft Endpoint > Protection Silent > Install(ScopeId_F0040EF5-9F88-4791-B5B2-2A1982EE68B9/DeploymentType_bbca880f-307f-410d-b7d9-a6d2d26ab3a8, > revision 9) for system. AppDiscovery 9/4/2014 4:31:40 PM 13120 > (0x3340) > +++ Discovered application [AppDT Id: > ScopeId_F0040EF5-9F88-4791-B5B2-2A1982EE68B9/DeploymentType_bbca880f-307f-410d-b7d9-a6d2d26ab3a8, > Revision: 9] AppDiscovery 9/4/2014 4:31:40 PM 13120 (0x3340) > +++ Detected app deployment type Microsoft Endpoint Protection Silent > Install(ScopeId_F0040EF5-9F88-4791-B5B2-2A1982EE68B9/DeploymentType_bbca880f-307f-410d-b7d9-a6d2d26ab3a8, > revision 9) for system. AppDiscovery 9/4/2014 4:31:40 PM 13120 > (0x3340) > > > > -----Original Message----- > From: listsad...@lists.myitforum.com [mailto: > listsad...@lists.myitforum.com] On Behalf Of William Jackson > Sent: Friday, September 5, 2014 9:26 AM > To: mssms@lists.myitforum.com > Subject: [mssms] RE: Quick question - uninstall > > > I created an uninstall script, but the program never runs. > > What did you put in the Deployment Type properties for the uninstall > command? Do you see anything in AppDiscovery.log or AppEnforce.log? > > William > > > > > > > > > > > > > > > > > > >
