Can anyone confirm or deny if a client will ignore a new deadline date for patch installation if it is in a pending reboot state due to prior patches being installed from a previous date?
From: HELMS, DAVID C Sent: Thursday, June 15, 2017 7:09 PM To: '[email protected]' <[email protected]> Subject: RE: [mssms] SU deployment deadline issue So I'm able to use the 'Deployment Monitoring Tool' to identify the deadline date for this client, but what I need to know is when the client received the new policy that updated this deadline date. Anyone know if that info is able to be retrieved? [cid:[email protected]] From: HELMS, DAVID C Sent: Thursday, June 15, 2017 3:32 PM To: '[email protected]' <[email protected]> Subject: [mssms] SU deployment deadline issue Each month, I modify the installation deadline of all our deployments about a week prior to the new patch installation date. This has worked well for us and prevents me from having to recreate all new deployments each month. This month, I am seeing a handful of clients that are installing updates prior to the deadline time being reached. So out of 300+ servers, I see that 20ish machines installed the updates early. Is there a way for me to verify that clients receive the updated time and date for the deployment? My assumption here is that the dates were changed but the clients didn't receive the new time and once the new patches were added and clients ran a SU evaluation, the patches installed. [cid:[email protected]] Thanks, David
