Share via

SCCM - Patching

karthik palani 1,036 Reputation points
2020-12-03T09:28:48.863+00:00

Hi All,

I need some advice on the below

  • I have SCCM CB 1802 and trying to patch Windows Server 2016 (1607). I have some servers which was not patched from 2016 year so i download the active Wk2016 patches which was around 13 items

After deployment i can see one or two patches which is fine on few servers. But for some servers its not getting installed and it says compliant in SCCM server. I copied the said 2 patches on the affected server and installed manually without any issues.

Is there anything wrong on the WIndows server 2016 which is not getting updated. From Update store it says "Update status - already exist - modified existing instance"

Please advice

Microsoft Configuration Manager
0 comments
Accepted answer
  1. Youssef Saad 3,416 Reputation points
    2020-12-04T08:44:10.393+00:00

    Hi,

    To upgrade to the latest ConfigMgr CB version, you have first to upgrade to 1902 then 2002, follow the below step by step guides:

    Regards,

    Youssef Saad | New blog: https://youssef-saad.blogspot.com
    Please **remember to “Accept answer” ** for useful answers, thank you!

    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rahul Jindal [MVP] 10,196 Reputation points MVP
    2020-12-03T23:03:18.247+00:00

    Hi,

    It depends on the wsus scan. If a patch has a pre-req then the pre-req will get installed first, possibly require a reboot and then the dependent patch will get picked as applicable in subsequent scan. Also CB 1802 is quite old and there have been lot of bugs fixed since then with addition of tonnes of new features. You should probably look at upgrading to latest CB.

    0 comments
  2. AllenLiu-MSFT 45,611 Reputation points Microsoft Vendor
    2020-12-04T05:48:27.047+00:00

    @karthik palani
    Thank you for posting in Microsoft Q&A forum.

    But for some servers its not getting installed and it says compliant in SCCM server.

    Where did you see the compliant status in SCCM? How many clients show required or not required for the updates you have deployed?

    And like RahulJindal said, current branch 1802 was ended support on 22 September 2019, it's recommended to upgrade to the latest version as soon as possible.

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.