Can you check the following registry entries on the client to see where the reboot is coming from and also check the task manager for the existence of ldreboot.exe :
- [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager]
- Vulscan Reboot Registry Key
- [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\landesk\managementsuite\WinClient\VulscanReboot ]
From the context of deploying some apps, this is a huge fail. Those keys are managed by LANDESK, is it not?
Tell me then, why do I have to factor in pending reboots from previous patching or other actions if I'm just trying to install Java? Of which, none of the install actions I'm taking require a reboot.
The PendingFileRenameOperations is a reboot regkey that many companies use, I used it to track SEP and SEP looked for this before installing its products. Usually if you first command in your batch has the removal of this regkey then things seem to work.
On your jre executable add REBOOT=0
In the situation you are describing, LANDESK is 'acting dumb'. Let me clarify.
LANDESK simply knows that 'something' is going to be updated following a reboot. It does not know what that is and as it doesn't know exactly what files the package/patch it is sending updates it also cannot make a decision about whether a reboot is needed or not for whatever it is sending now.
LANDESK is erring on the side of caution. If it simply went ahead and installed regardless of anything in that key (which is not owned by LANDESK) then there is the potential that something in there would overwrite/delete an important file in the current package. An example can be seen in the LANDESK agent (not tested this for a while so may not be accurate today). A machine with the agent can have the agent uninstall using uninstallwinclient. This 'should' force a reboot but it can be suppressed (assume we did this). If we install the agent again then everything looks good. If we then reboot the agent is broken. This is because some files were in use at the time of the agent being uninstalled so marked for deletion after the reboot. The agent install didn't know this so went ahead anyway. After the reboot those 'in use' files got deleted breaking the agent we just laid down.
With this in mind, LANDESK allows an option to ignore pending reboots in patching with the install/remove option of 'start repair even if reboot is already pending'. This is in your Distribution & Patch settings. Be careful using this. You therefore have the choice t take the risk, it is simply not the default of LANDESK to take that risk without you deciding to first.
MarXtar Ltd/MarXtar Corporation
LANDESK One Development Partner
Try MarXtar State Management for LANDESK to Better Understand and Manage your Assets