Can anyone help with this problem - or has anyone else seen it.
We are migrating our Agents over from a 95 core and this is what we see.
A fresh machine and fresh install no problems.
I run a uninstallwinclient with forceclean and registry clean, directory clean so there is no trace of the agent.
When we install the 2016 agent we can scan it from the console, but if i scan it in a task i get this error.
We can run a repair job for patches however it will return this error - the part of the log file that is the issue is this.
Fri, 11 Aug 2017 20:31:48 Calling 'ApplyBehavior' in 'C:\Program Files\LANDesk\LDClient\InventorySettingsBehavior_Apply.dll'
Fri, 11 Aug 2017 20:31:48 SOFTWARE\LANDesk\ManagementSuite\WinClient\IncludeNET registry value is 1 so we need to check if .NET 4.0 is already on the client or not
Fri, 11 Aug 2017 20:31:48 Already have .NET installed so skip it
Fri, 11 Aug 2017 20:31:48 InventorySettings_Apply.dll Failed to load our behavior from 'C:\ProgramData\vulScan\InventorySettingsBehavior_VM841_v575_38F14.xml'. Returning failure
Fri, 11 Aug 2017 20:31:48 ERROR: failed to 'ApplyBehavior' for InventorySettingsBehavior, ID VM841_v575_38F14
Fri, 11 Aug 2017 20:31:48 Checking whether to unzip 'C:\ProgramData\vulScan\ClientConnectivityBehavior_Apply.zip'. Force: false
Fri, 11 Aug 2017 20:31:48 GetFileHash: could not find "C:\ProgramData\vulScan\ClientConnectivityBehavior_Apply.zip"
Fri, 11 Aug 2017 20:31:48 Calling 'PreApplyBehavior' in 'C:\Program Files\LANDesk\LDClient\ClientConnectivityBehavior_Apply.dll'
Fri, 11 Aug 2017 20:31:48 Client connectivity settings pre-apply dll
The settings file is downloading from the core - the XML file is on the client
I have tried replacing the inventorysettingsbehavior_apply.dll from a working machine. No joy.
I have resaved the agent settings - no joy -
the problem is this fail in the vulscan.log file will send a fail status back to the core.
out of 300 machines 135 of them behave like this. so from a status stand point it looks bad - these are the 300 first machines we are cutting over -
Landesk is saying to recreate the agent from scratch and all settings which i am reluctant to do as i have already tried brand new settings and the agent we have works on a fresh machine - we even see it working on machines that have been cut over but the majority are failing with this error.
if anyone can chime it would be greatly appreciated - the call is still open with landesk support also just seeing if the community can help.