1 of 1 people found this helpful
This KB article covers most of the scanning errors that occur with Protect:
Determining when you want to use agents is really up to you, but generally they are used when you have systems that are harder to manage with agentless scanning/deploying - laptops that might be off/on network, systems in remote locations, or if you just want the agent to manage the patching of the systems.
thanks for your prompt reply, but I have seen that docco - it explains the error code- not so much how to resolve the problem in a logical order.
for example - not very helpful for the 200 error ;
Error Code 200: System not found. Scan not performed. This indicates that the specified computer was not located and could not be scannedEven though I can ping and telnet to the machine that has this error from the Protect server, also the server is a VM that is selected from the Protect console-I wonder what process is used to scan the machines? Maybe this will help with trouble shooting- googleing now...Cheers,Jamie
Most of the errors are pretty straight forward, but the KB does give a little more description of the cause or what to do to fix it. There are a few that have links for full KBs (the errors that can get more complicated).
Other than that you just need to ensure you're meeting scan requirements which can be found in the following Help document within Protect:
If you still can't figure it out it might be best to contact support directly via email or phone.
OK thanks for your help.