Platform: LDMS 6.9 SP2 with CP 2016-0419
We tired pushing out a "bundle" which resulted in the system wanting to reboot after each of it's 3 componenet packages ran:
- First, Batch package: kill_explore.cmd
- Second, Executable package: jre-8u74-windows-i586.exe /s
- Third, Batch package: update_group_policy.cmd
Note, the system we were deploying to is setup with reboot settings that allow for an automatic reboot once a week on Saturday around 8 PM.
What I don't understand is why was the task stuck on "task will continue after reboot" -- When I look at the task log, it seems as if the package is flipping the flag to signal that the system needs to reboot... after EACH step in the bundle. I looked in the task settings as well as the settings for the bundle and each package. The only thing that stands out to me, is the option of "reboot expected" but in this case, nothing in the bundle should require a reboot and it is undesired.
Here is a snippet from the task log:
Wed, 04 May 2016 12:24:41 Launched application 'C:\Program Files\LANDesk\LDClient\sdmcache\packages\Genapps\Java\jre-8u74-windows-i586.exe' ('/s') result 0
Wed, 04 May 2016 12:24:41 Installation result DB50000
Wed, 04 May 2016 12:24:41 Rebooting system if needed
Wed, 04 May 2016 12:24:53 processing of package is complete, result 229965824 (0x0db50000 - code 0)
What gives? I don't get this at all. Has anyone else seen this behavior? Is it normal? Please help.