Criteria for successful agent scanning
1. Ensure that the agent services are running in the client machine under services.msc
2. In the application, under Admin >> Security Settings >> Ensure Stop uploading scanned XMLs via non-login URL is unchecked.
3. If ICMP is blocked in the network and if the ping is not possible, then under Admin >> Scan Settings >> You can check the Disable Ping option
4. Ping the client machine from the server
5. Ping the server from the client machine.
6. Please check if you are able to telnet the agent port from the server and the client machine by following the below steps.
Please open the command prompt as admin in the application server and then:
telnet<space><workstationname><space><portnumber of the agent>
Next, go to the workstation open the command prompt as admin and then:
telnet<space><application server name><space><portnumber of the application>
New to ADSelfService Plus?
Related Articles
Remote AE (Asset Scanning) Behavior changes
You can download the compatible version of Remote AE from the installed version of ServiceDeskPlus-MSP. Please go to Admin > Distributed Asset Scan and make use of the below highlighted. If you already have Asset Explorer in older versions, please ...Uninstalling agent 1.0.28
There is a known issue with the uninstalling of agent version 1.0.28 The issue occurs if you try to uninstall the given version from Agent Installed list view post SDP 9420 and AE 6205. How to confirm the issue: 1. Go to Assets > Agent Installed. 2. ...How does Agent Scan work ?
When you install Agent for the first time, It will initiate the scan immediately and send the data via application port (8080 or 443 as you configured) to Server. But when you scan from the Application, It will first try to check whether the client ...Agent related to FAQ's
https://www.manageengine.com/products/service-desk/on-premises/faq/it-asset-management.html#AgentBasedScanAsset Scan Issues
1. Either access denied for the user or the remote DCOM option might be disabled in the workstation. 2. User does not have the access privileges to perform this operation. 3. One of the WMI components is not registered properly. 4. Execution failure ...