locked
Deploying IE 11 with SCCM 2012 R2 RRS feed

  • Question

  • Like many, we're looking to upgrade our environment to IE 11. We started doing some testing deploying the update rollup Internet Explorer 11 for Windows 7 for x64-based Systems through SCCM about month ago, and those tests were working fine. Now we're prepared to roll it out on a wider scale, but I'm finding the update is showing as expired under all software updates in the SCCM console. The associated KB number is 2841134, which as far as I can tell is still current.

    I really don't want to create a package deployment for this update. How do I re-enable the software update? And any ideas why the update would be listed as expired?

    Doug

    Wednesday, October 28, 2015 3:09 PM

Answers

  • Correct -- that's my theory because I can't say I've actually tested declining an update in WSUS. The fact that it is approved in WSUS means that someone has been messing with updates in WSUS which can dangerous as approving them is totally unnecessary.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, October 28, 2015 6:27 PM

All replies

  • Hi,

    There is no way to "-un-expire" it once it is expired. So I would go for a package instead. You can always check the reason why it is expired on Microsoft Update Catalog a great site.

    https://catalog.update.microsoft.com/v7/site/Home.aspx

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Wednesday, October 28, 2015 3:16 PM
  • My WSUS refreshed about 3 hours ago and I don't show that KB as expired.  Are you sure it is expired?


    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

    Wednesday, October 28, 2015 3:25 PM
  • The icon in the list of updates is the expired icon, and when selected the info below says, among other things, date released 5/13/2014, superseded no, and expired yes.
    Wednesday, October 28, 2015 3:46 PM
  • Sounds like someone has been going into WSUS and declining updates. You can open the WSUS console to confirm this. If so, I don't know of a supported way to go back. You can try approving it or setting it back to the default of not approved and then syncing the update catalog in ConfigMgr but I don't think that will trickle into ConfigMgr until ConfigMgr removes it completely (described at http://blogs.technet.com/b/configmgrteam/archive/2012/04/12/software-update-content-cleanup-in-system-center-2012-configuration-manager.aspx).


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, October 28, 2015 5:53 PM
  • The update is present in the WSUS console, and is set to approved there.

    Are you suggesting that after the expiration and tomb-stoning process described in your link above, there is the possibility the update might become available again?

    Wednesday, October 28, 2015 6:03 PM
  • Correct -- that's my theory because I can't say I've actually tested declining an update in WSUS. The fact that it is approved in WSUS means that someone has been messing with updates in WSUS which can dangerous as approving them is totally unnecessary.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, October 28, 2015 6:27 PM
  • This update is not expired, please check the setting in WSUS and find out why that is showing as expired, there must be declined

    Sharad Singh | My blogs: SharadTech | Twitter: @SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

    Wednesday, October 28, 2015 7:18 PM