Cool. Yeah once I learned and became proficient Applications, i pretty much never used Programs again except for rare instances where they make more sense. Also, MS has a tool that will 80% convert all your Programs to Application. I say 80% because typically you need to go in an setup detection rules after it converts the app if the installer isn't an MSI (I think). Been a long time since I used it.
On Sun, Oct 11, 2015 at 8:45 AM, David McSpadden <[email protected]> wrote: > After seeing your other comment about applications, I looked them up, > specifically for the IE11 issue. Going to test that come Monday. > > The command line of the Task Sequence is solid and works if I cut and > paste it into a dos window. It is just that the TS is still at 0% after 72 > hours. > > I like what you have stated about the Application method and I need to > learn it for all the other apps we will be pushing out once we have the > Software Updates under control. > > I will respond once I have tested the Application ForFiles method of > removing IE11. I only have 2 collections that have it and they are a > control group of PC’s in the org so I am good for testing and > > Learning. > > Thanks again. > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Conrad Jones > *Sent:* Sunday, October 11, 2015 2:35 AM > *To:* [email protected] > *Subject:* Re: [mssms] Ie11 uninstall > > > > Yes as previously stated the detection rules with applications provide a > robustness through the detection rule that you just don't get with a > program or run command line step in a task sequence. > > > > And yes a task sequence to un-install an application does not seem the > most sensible way to go about this. > > > > On Sun, Oct 11, 2015 at 5:49 AM, ccollins9 <[email protected]> wrote: > > I'm assuming you followed this article? > https://weikingteh.wordpress.com/2013/05/13/how-to-rollback-remove-a-patch-using-sccm-configmgr/ > > > > I have no idea why the writer would recommend a TS over an Application or > Program. He mentions that a Program would likely fail on a 64-bit > machine---no idea where he's pulling that opinion from. > > > > > > IMO, Applications are the best way to do 98% of software > installs/uninstalls in SCCM. This is mainly due to "detection methods". > With these you setup criteria for the app to check on the machine to detect > if the app is installed or not. It will keep running then checking until > the app is either successfully installed or uninstalled (depending on which > action you are deploying to your collection), so it's not a one shot deal > like a Program or Task Sequence. > > > > Also, did you test the command first? Did you open Add/Remove and make > sure that KB# is listed in there? How long have you been running it? It > may say 0% for a while until machines start sending their status updates. > > > > If you decide to build and deploy an application for IE11, make sure you > test to be sure it successfully installs and uninstalls. For the uninstall > portion, It may be as simple as putting that command you have into a bat > file with some other things like taskkill.exe /im iexplore.exe /f to close > out IE before you uninstall it. The log to see application > install/uninstall status is AppDiscovery.log and AppEnforce.log. There > are a lot of things you could do for criteria. I would start by pulling a > report in SCCM to see which versions IE11 are installed in your environment. > > > > It's more work to do an Application, but when done right, the success > rates are usually extremely high. > > > > > > > > On Sat, Oct 10, 2015 at 11:53 PM, David McSpadden <[email protected]> wrote: > > First thing to come up on Google with uninstalling IE11 with SCCM 2012? > > What is a better way? > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Jason Sandys > *Sent:* Saturday, October 10, 2015 5:12 PM > *To:* [email protected] > *Subject:* RE: [mssms] Ie11 uninstall > > > > Why would you use a task sequence to run a single task? A package and > program are much better suited for this an require much less overhead. > > > > If you insist on using a TS, then smsts.log is the primary log to review > on the clients where the TS executes. > > > > J > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *David McSpadden > *Sent:* Friday, October 9, 2015 5:04 PM > *To:* [email protected] > *Subject:* RE: [mssms] Ie11 uninstall > > > > Just a task sequence with the uninstall parms. > > > > · c:\windows\system32\wusa.exe /uninstall /kb:2841134 /quiet > /norestart > > > This e-mail and any files transmitted with it are property of Indiana > Members Credit Union, are confidential, and are intended solely for the use > of the individual or entity to whom this e-mail is addressed. If you are > not one of the named recipient(s) or otherwise have reason to believe that > you have received this message in error, please notify the sender and > delete this message immediately from your computer. Any other use, > retention, dissemination, forwarding, printing, or copying of this email is > strictly prohibited. > > > > Please consider the environment before printing this email. > > > > > > This e-mail and any files transmitted with it are property of Indiana > Members Credit Union, are confidential, and are intended solely for the use > of the individual or entity to whom this e-mail is addressed. If you are > not one of the named recipient(s) or otherwise have reason to believe that > you have received this message in error, please notify the sender and > delete this message immediately from your computer. Any other use, > retention, dissemination, forwarding, printing, or copying of this email is > strictly prohibited. > > > > Please consider the environment before printing this email. > > > > > > > > > > > > This e-mail and any files transmitted with it are property of Indiana > Members Credit Union, are confidential, and are intended solely for the use > of the individual or entity to whom this e-mail is addressed. If you are > not one of the named recipient(s) or otherwise have reason to believe that > you have received this message in error, please notify the sender and > delete this message immediately from your computer. Any other use, > retention, dissemination, forwarding, printing, or copying of this email is > strictly prohibited. > > Please consider the environment before printing this email. > >
