I've been asked to write up some documentation for our on-call team regarding potential problems that could occur that would require their immediate attention. One of the scenarios I can foresee is a patch deployment going sideways and causing clients to be unable to start. I understand that testing and planning are the normal preventative steps that will keep this from happening, but I'm being asked to plan for worst case scenarios.
What would everyone say is the best method to stop the deployment from being delivered to further machines? Being that we are talking about a scheduled patch deployment, the machines would likely have cached the files and are most likely just waiting for the deadline to begin the installation, is there really even much of a chance for us to stop more damage from occurring? What about in the instance of an OSD TS going out of control? Would stopping the WDS services make a difference? Regards, Matt ________________________________ This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message.
