Allow me to explain. Is it possible to run a scan (for lack of a better term) that would look at the machine this patch is to be installed on and tell me if the machine will indeed reboot? This need for me comes from the couple of times that a patch may not reboot any of my test machines, but of course reboot some others. It is an embarrassing situation that I would like to avoid. My understanding of why a system needs to reboot is that a file is in use at the moment that needs to be patched or deleted, or the installer needs to clean up. There is a tool that can be run that looked for this, named WhyReboot http://exodusdev.com/products/WhyReboot . My question though is can this or is tyoe type of test built into LANDesk?
1 of 1 people found this helpful
It would be virtually impossible to determine the operational conditions that would dictate whether a machine needs to be rebooted based on a locked file. LANDesk would have to track each file in a patch, determine if it is locked, then take some action. It is much easier to determine whether a machine needs to be rebooted based on the PendingFileRenameOperations key.
So, it is luck of the draw then? I understand there are millions of variables that could cause the need for a reboot, however I had hoped staging and testing on a wide sample of systems would help me know better if a reboot would happen or not. (Reason being that some systems are only here for a short period of time, and I would like to push or auto fix while they work and go unnoticed and be able to apply more. A reboot gets me 1. Trouble with the user and 2. Unable to "spot fix" these systems that otherwise do not connect with my network often)
Not just patches write to that key - printer drivers, other software, etc.... write to the key for locked files. We create a policy that users run that displays whether a reboot is pending or not.