App-V (5) may be the smartest one. With grouping I see more App-v coming for apps not suitable before and with CM12 it is easy to link.
From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Mittwoch, 28. August 2013 18:01 To: [email protected] Subject: RE: [mssms] RE: Application Uninstall Issue Yep. Lots of different permutations to this one - no one good solution except to yell at the vendors you created the stupid uninstaller in the first place. J From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: Wednesday, August 28, 2013 10:40 AM To: [email protected] Subject: RE: [mssms] RE: Application Uninstall Issue Unless you know how long to pause for and not make it way to long just to be "safe" They may run faster or slower in different scenarios. Also not a good solution. From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Mittwoch, 28. August 2013 17:15 To: [email protected] Subject: RE: [mssms] RE: Application Uninstall Issue And that of course assumes you actually know the "image" name of the process; many bootstrappers use random names. That's why automating this is not necessarily easy or straight-forward but a simple pause is typically sufficient. J From: [email protected] [mailto:[email protected]] On Behalf Of CESAR.ABREG0 . Sent: Wednesday, August 28, 2013 10:01 AM To: [email protected] Subject: Re: [mssms] RE: Application Uninstall Issue That is correct, spawned processes are a pain; ORA client comes to mind or even SCCM client. I've used 'tasklist' with 'find' to check for open process or excutable, loop if error level is '0' (found the process running) - works for me at times. Inline image 1 On Wed, Aug 28, 2013 at 7:35 AM, Jason Sandys <[email protected]> wrote: That doesn't change anything and is redundant. Batch files already wait on a command to exit before executing the next line. The issue is not about waiting on <yourexe>, it's about the processes/exes that <yourexe> spawns to perform the actual uninstallation -- <yourexe> exits immediately leaving the spawned processes to do the work but there is no good or easy way to track these spawned processes. J From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: Wednesday, August 28, 2013 2:58 AM To: [email protected] Subject: RE: [mssms] RE: Application Uninstall Issue Try using "start /wait <yourexe>" in a batch -Roland From: [email protected] [mailto:[email protected]] On Behalf Of Johns, Damon (DoJ) Sent: Mittwoch, 28. August 2013 04:13 To: [email protected] Subject: [mssms] RE: Application Uninstall Issue Thanks Jason, I will go ahead and alter my install action to use a script, it's good to also confirm that others have seen this. Cheers Damon From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Wednesday, 28 August 2013 11:40 AM To: [email protected] Subject: [mssms] RE: Application Uninstall Issue This is fairly typical with exe uninstallers. Essentially, the exe is just a bootstrapper that launches another process to perform the actual uninstallation and then exits right away. ConfigMgr does not know (or really have any way to know) that this is what is happening so when the bootstrapper exits, it thinks the uninstallation is done and it performs the detection. Of course the actual uninstallation is still going on so your detection method will probably still show the app as installed meaning that the uninstallation failed. The best way to handle this is to add a script to your package that first calls the uninstaller and then pauses for a handful of seconds to account for the spawned process that actually performs the uninstallation (the uninstallation is usually pretty quick so 5 seconds should suffice but ymmv so test). Then, run this script as your uninstaller. You could potentially get fancy and try to detect the process and wait for it to exit in your script but that's a lot of work for no real gain in functionality and where a simple pause works well enough (ConfigMgr could try to do this also for that matter but they never will as it's a lot of work for a minority use case). J From: [email protected] [mailto:[email protected]] On Behalf Of Johns, Damon (DoJ) Sent: Tuesday, August 27, 2013 7:16 PM To: [email protected] Subject: [mssms] Application Uninstall Issue Hi Everyone, Hoping someone has come across a solution to this. I have an application that is installing correctly however when I go to uninstall it using the Software Center it uninstalls correctly but the Software Center reports that it has failed. It's using its own uninstall .exe to remove the software and my detection rule is using the presence of the applications .exe to determine if its installed. (It doesn't use MSI technology, looks like install shield or something similar) When the uninstall.exe runs it kicks off the uninstall process however it returns an exit code 0 (success) straight away in the AppEnforce.log. Then App deployment detection runs immediately after this exit code is registered and because the application's exe is still present it thinks it hasn't uninstalled. It eventually fixes itself up after an Application Deployment Evaluation cycle is run which then picks up that the exe is no longer present. The problem really lies in my detection rule however I'm not sure what options I have. If anyone has encountered this sort of issue before and has a possible solution I would be interested in their thoughts. I'm thinking I need a script maybe that will loop until the uninstall.exe has finished removing the application?? Cheers Damon _____ CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission. _____ CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission.
<<image001.png>>
