locked
Server 2012 R2 gets superseded updates instead of superseding ones RRS feed

  • Question

  • Newly Server 2012 r2 installed on a vm gets superseded updates instead of superseding ones which are approved too.Even if I decline those superseded the client won't gets the superseding ones.
    Why this happens and how can I solve that?

    Do I need anything regarding superseded update expiration after declining it or not?


    Edit:I noticed updating windows from microsoft also contain superseded updates.If there is a newer update which supersedes old one why the old one should install? 


    • Edited by harsini Monday, July 23, 2018 8:50 AM
    Sunday, July 22, 2018 2:34 AM

All replies

  • Hello harsini,

      

    Glad to help.

       

    That a update is superseded does not means it is not needed by all clients. 

      

    Consider the following scenarios in which you might need to deploy a superseded update:

      

    • If a superseding software update supports only newer versions of an operating system, and some of your client computers run earlier versions of the operating system.
    • If a superseding software update has more restricted applicability than the software update it supersedes. This would make it inappropriate for some client computers.

       

    Refer to following link (search for Supersedence Rules):

    https://docs.microsoft.com/en-us/previous-versions/system-center/system-center-2012-R2/gg712696(v=technet.10)#BKMK_SupersedenceRules

      

    So, for the best practice, if you want to decline a superseded updates, make sure the superseding update is installed on the all clients and the superseded one is not needed any more. Or you should still install the superseded update if the superseding one is not applicable.

        

    Hope above answer could help you and look forward to your feedback.

        

    Best regards,

    Ray Jia


    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Monday, July 23, 2018 2:08 AM
  • Hi.Thanks for your response.

    So in an enterprise with thousand of virtual and physical windows and clients which will added to in future , we couldn't decline any update in wsus because we couldn't determine which update won't be needed and never an update will applicable and install on all of the clients.



    • Edited by harsini Monday, July 23, 2018 4:22 AM
    Monday, July 23, 2018 2:29 AM
  • Hello harsini,

     

    Well, the point is do not decline a update which is still needed by some clients currently. To ensure that, you should make sure that the superseding update is not applicable. Maybe you should test that by installing on the client manually.

     

    What's more, all updates and product have their life cycle, a update would not be needed forever because it would be replaced or expired. And your issue should be just small probability event.

       

    Best Regards,

    Ray Jia


    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, July 24, 2018 3:09 AM
  • I declined all updates which are "not needed" by any client and "not superseeding" any other updates.But  newly installed windows client finds only 2 new updates from that server whilst before declining the client was getting almost 20 new updates for installing.
    • Edited by harsini Tuesday, July 24, 2018 4:31 AM
    Tuesday, July 24, 2018 4:18 AM
  • Hello,

     

    Then you could approve those declined updates check if they are needed.

     

    Best Regards

    Ray Jia


    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, August 1, 2018 8:19 AM
  • They will needed again possibly but what is the point of being superseded if they will be needed again in existence of an superseding update?
    Sunday, August 5, 2018 2:16 AM