Discovery failure: invalid certificate when trying to update the Big3d

Currently we only support running the tasks from the computer they were installed on. The issue you were having before may have been caused by running discovery from the web console or a management server other than the RMS. Remote Desktop and Terminal Services should work just fine for discovery, however.

 

 

Do you have IPv6 installed? And if so, if you are not using it, try uninstalling it completely and trying discovery again. We've noticed some compatibility issues with IPv6 and certificates.

 

 

If that is not the issue, you can enable verbose logging by following the instructions here: Click here. Once you have this turned on, you should restart the "F5 Monitoring Service" and then try to discover again. If it is still failing at this point, if you can attach the trace.log file from C:\Program Files\F5 Networks\Management Pack\Logs we can read through it and figure out what is causing the invalid certificate error.

 

 

Thanks,

 

`Dave