We will fairly regularly find assets that have stale data, such as showing an older build of Windows 10 than what is currently installed. Upon checking the Activity Log, we always are greeted by a slew of entries stating:



Error Description Unexpected exception occurred, Type: System.BadImageFormatException Exception description: Could not load file or assembly 'ZipCs, Version=0.86.0.518, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The module was expected to contain an assembly manifest. at SysAid.AgentObjectsManager.SysAidHandlers.ZipHelper.UnzipFile(String a_ZipFilePath, String a_ZipPassword) at SysAid.AgentObjectsManager.SysAidHandlers.ZipHelper.UnzipFile(String a_ZipFilePath) at SysAid.AgentObjectsManager.SysAidHandlers.Upgrade.UpgradeSynchronizationEngine.HandleUpgradeTaskProcess() Stack Trace ExecutionContext::RunInternal ExecutionContext::Run ExecutionContext::Run ThreadHelper::ThreadStart



While this is resolved by an undeploy and redeploy, it impedes our ability to manage the assets and assist our users; we need this information to be accurate.



This feature request is three-fold:

• The agent itself should have some manner of integrity check, and repair or reinstall itself if a component is corrupted or missing.

• If an agent does not catch such an issue and returns an error message, the server side should have an option to attempt a full redeploy; this will need to be configurable, as not all assets will be on an internal network at all times.

• The server side should have a report for agents that are returning error messages, preferably with a notification so that they can be manually remediated.