Yes, if I were doing this, this would be how I would do it. If anyone knows a slicker way, they can chime in:
1. Setup an Application that INSTALLS IE11 2. In the UNINSTALL section of the App, put in the wusa command you have to uninstall by KB 3. In the detection rules, put in the svcVersion "begins with" 11. (use the dot) 4. Deploy the Application to the collection as an UNINSTALL job Application discovery will use that registry setting in step 3 to "discover" that IE 11 is on these machines. And because it is on the machines, it will run the uninstall deployment. Theoretically, the svcVersion registry value will go back to the previous version, thus the detection rules from step #3 will know that the app is not present any longer. I say theoretically because I've never done this before and before I wasted my time building out the App, I would use my test VM, put IE11 on it, check the registry value, then run the uninstall command you have, then check the registry value again. And of course, this is all assuming that the wusa uninstall command you have will work for all versions of IE11 you have there in your environment. On Tue, Oct 13, 2015 at 12:12 PM, David McSpadden <[email protected]> wrote: > So instead of ForFiles I would you wusa and it would be better to use HKLM > version instead of file explorer version. > > Then do I just monitor appdeploy and appenforce logs? > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *justin stradley > *Sent:* Tuesday, October 13, 2015 11:50 AM > *To:* [email protected] > *Subject:* Re: [mssms] Ie11 uninstall > > > > Forgot to mention that command line is for 64-bit. 32-bit would be: > C:\windows\system32\WUSA.exe /uninstall /kb:2841134 /quiet /norestart > /log:%temp%\IE11-uninstall-log.evtx > > > > Thanks, > > > > *Justin R. Stradley* > > Email <[email protected]> *|* Lync *|* LinkedIn > <https://www.linkedin.com/profile/view?id=22281599> > > > > > ------------------------------ > > *From:* [email protected] <[email protected]> > on behalf of justin stradley <[email protected]> > *Sent:* Tuesday, October 13, 2015 10:43 AM > *To:* [email protected] > *Subject:* Re: [mssms] Ie11 uninstall > > > > I don't have much experience in setting up applications that are not > .msi's. We use a package to uninstall IE11, here is the command line we > use: > > %systemroot%\sysnative\cmd.exe /c C:\windows\system32\WUSA.exe /uninstall > /kb:2841134 /quiet /norestart /log:%temp%\IE11-uninstall-log.evtx > > > > Thanks, > > > > *Justin R. Stradley* > > Email <[email protected]> *|* Lync *|* LinkedIn > <https://www.linkedin.com/profile/view?id=22281599> > > > > > ------------------------------ > > *From:* [email protected] <[email protected]> > on behalf of David McSpadden <[email protected]> > *Sent:* Tuesday, October 13, 2015 10:10 AM > *To:* [email protected] > *Subject:* RE: [mssms] Ie11 uninstall > > > > Ok, > > I am having a real issue with this. > > Can someone direct me to good reading on this or show me how to set up the > application and detection? > > This seems so simple but I have spent way too much time and I am no better > than last Thursday. > > > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *David McSpadden > *Sent:* Tuesday, October 13, 2015 8:49 AM > *To:* [email protected] > *Subject:* RE: [mssms] Ie11 uninstall > > > > If I am using the ForFiles method and I have like 8 versions of IE11, I > need to set up a detection method for each of the versions with an or > connector linking them all? > > FORFILES /P %WINDIR%\servicing\Packages /M > Microsoft-Windows-InternetExplorer-*11.*.mum /c "cmd /c echo Uninstalling > package @fname && start /w pkgmgr /up:@fname /quiet /norestart > /l:C:\Windows\temp\IE11_uninstall.txt" > > > > Clause > > Path: %ProgramFiles%\Internet Explorer > > File: iexplore.exe > > > > Setting: > > Version Not equal To: > > 11.00.9600.18015 > > Or > > 11.00.9600.16428 > > Or > > 11.00.9600.17126 > > Or > > 11.00.9600.17501 > > Or > > 11.00.9600.17691 > > Or > > 11.00.9600.17496 > > Or > > 11.00.9600.17037 > > Or > > 11.00.9600.17843 > > > > These are all the versions I find under by Windows 7 machines. > > > > I got an error on my first run of 0x87D00324 and the client of the pc said > it failed and would be retired but the IE version is now IE10? > > So I think I am ok but with errors? > > > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Daniel Ratliff > *Sent:* Sunday, October 11, 2015 3:56 PM > *To:* [email protected] > *Subject:* RE: [mssms] Ie11 uninstall > > > > We use an application for our IE11 Uninstall/Rollback when necessary. We > use wusa.exe as well. In our environment (not sure if it happens elsewhere) > a package/program would not work because wusa.exe didn’t like being ran as > 32-bit. It has to be ran as a 64-bit process. No content is necessary since > its just a cmd line. > > > > Cmd line is pretty much the same as yours, only with logging: wusa.exe > /uninstall /kb:2841134 /quiet /norestart /log:C:\Temp\IE11Uninstall.evtx > > > > *Daniel Ratliff* > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Jason Sandys > *Sent:* Sunday, October 11, 2015 11:23 AM > *To:* [email protected] > *Subject:* RE: [mssms] Ie11 uninstall > > > > Script Installer is a choice for the deployment type, not the application. > For the application type, if you are not going to be using one of the > pre-defined types like MSI, then you need to choose custom. > > > > J > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *David McSpadden > *Sent:* Sunday, October 11, 2015 10:19 AM > *To:* [email protected] > *Subject:* RE: [mssms] Ie11 uninstall > > > > What if Script Installer is not showing as a deployment type? Where do I > set that in SCCM 2012 to show as a deployment type of an application. > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *ccollins9 > *Sent:* Sunday, October 11, 2015 9:13 AM > *To:* mssms <[email protected]> > *Subject:* Re: [mssms] Ie11 uninstall > > > > 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. > > > > > > > > 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. > > > > > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information. > > > > 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. > >
