Patch Got initiated some other day after deadline reached

Poll

for example If the patching was scheduled for 25th May, but patching deployment got initiated some other day after deadline reached. let me know the reason…

for example If the patching was scheduled for 25th May, but patching deployment got initiated some other day after deadline reached. let me know the reason…

in progress 0
Rejin Sree 4 months 6 Answers 106 views Beginner 0

Answers ( 6 )

  1. So did we fulfil what you were looking for? Or any further support needed?

  2. First of all.. can you please provide an appropriate heading for the question.

    Don’t copy-paste content and heading as same

    There could be several reasons for that :

    How do we identify whether the patch is installed? Do you mean to say the restart time of the patch?

    There is always a grace period after the deadline to get installation and restart

    There are many things involved in the installation after deadline:

    1. Maintenance window
    2. Grace period before restart /force restart etc

    • thanks for your replay. In customer systems the patching was scheduled for 25th May, but after deadline reach also its not installed. after 3 days later it got installed. what is the reason behind this…

      • Why didn’t check the answers given above

        Can you please reply on that front and check the log files

        Updatedeployment.log – The following entries Deadline received for assignment, DetectJob completion received for assignment, Starting install for assignment, EnumerateUpdates for action (UpdateActionInstall) – Total visible updates = ?

        RebootCoordinator.log – Shutdown is already in progress

      • As Anoop Sir said.
        There could be several reasons for that :

        How do we identify whether the patch is installed? Do you mean to say the restart time of the patch?

        There is always a grace period after the deadline to get installation and restart

        1. Maintenance window
        2. Grace period before restart /force restart etc

        Adding to his questions which is not answered by you yet.

        1. Can you please check if any Maintenance Window applying to that collection?
        2. What was the deadline defined? I am assuming you defined it as 25th May . Time please? Also as you said it didn’t install at the deadline but installed after 3 days. If MW applied after 3 days then it’s suppose to behave this way.
        3. When did you staged these patches to these machines? Recommended is to expose 24 hours before deadline so it can download the patches in advance and trigger installation at deadline. What’s the setting used for option “Available After”.
        4. Can you check updatedeployment log to see what time evaluation started and you will see line something like downloading 0%.
        5. Can you check rebootcoordinator log to see if anything pending for reboot and you see “Waiting for MW”.
        6. Can you see “Checking Leaves and Bundles” in WUAHandler?
        7. What’s the status you see in contenttransfermanager?
        8. Can you see if anything was downloaded in C:Windowsccmcache? If yes what’s the date it downloaded the content.
        9.Is it for all the machines in that deployment or only few? Was this targeted to default collections or collection created by you?
        10. What was the status of client health?
        11. Are those clients always online and connected to LAN or they are in VPN?
        12. Is 4 hours of Handshake happening between these clients and SCCM Server?
        13. What do you see in update store? Do you see anything applicable?
        14. These machines are part of many collections and many deployments ?
        15. Please check all the above points and also explain the infra setup for further troubleshooting. SCOPE : We will consider it resolved if we deploy test patch and installs at the deadline without any issues.

Leave an answer

Sorry, you do not have a permission to answer to this question .