As a matter of fact, YES! I keep forgetting that the logs are all over the place in 9.5 SP2, something I understand they've worked to correct in 9.6.
Scrolling through it, the only CRITICALERROR that jumps out immediately is regarding the BrokerConfig.
10/13/2014 14:54:52.614 2888 2856 ntstacfgDlg.cpp 1480 INI: FILE1004=BrokerConfig.lng, %PROGRAMFILES(x86)%\LANDesk\Shared Files\cbaroot\broker\BrokerConfig.lng, NOCOPYERROR
10/13/2014 14:54:52.630 2888 2856 file.cpp 91 INFO: Reboot needed for (C:\Program Files (x86)\LANDesk\LDClient\%PROGRAMFILES(x86)%\LANDesk\Shared Files\cbaroot\broker\BrokerConfig.lng)
10/13/2014 14:54:52.630 2888 2856 tokens.cpp 427 SUCCEEDED: Copying file 'C:\Program Files (x86)\LANDesk\LDClient\%PROGRAMFILES(x86)%\LANDesk\Shared Files\cbaroot\broker\BrokerConfig.lng'
10/13/2014 14:54:52.630 2888 2856 ntstacfgDlg.cpp 1480 INI: EXEC1006=BrokerConfig.exe, /r, INSTALLONLY
10/13/2014 14:54:52.630 2888 2856 tokens.cpp 664 Starting process: BrokerConfig.exe /r
10/13/2014 14:59:54.169 2888 2856 tokens.cpp 688 Processes returned : -2146435027
10/13/2014 14:59:54.169 2888 2856 tokens.cpp 586 CheckProcessExitCode processed app name: BrokerConfig.exe
10/13/2014 14:59:54.169 2888 2856 tokens.cpp 713 FAILED: Running application: BrokerConfig.exe /r
10/13/2014 14:59:54.169 2888 2856 ntstacfgDlg.cpp 1610 FAILED: bCriticalError set to TRUE. Processing BrokerConfig.exe
It's not set to reboot after this task, so maybe that's the problem?