For more information on Agent deployment failure, refer to the Troubleshooting - Agent deployment.
To determine why Agent deployment failed, click Reports → Agent Deployment task information in last 30 days and click Generate now. Deployment information is displayed in a table. The Progress column displays error messages about why agent deployment failed.
For more information, change the verbosity of the ESMC Server trace log. Click More → Server Settings → Advanced Settings → Logging. In the Trace log verbosity drop-down menu, select Error and click Save. Run Agent deployment. When Agent deployment fails, check the bottom of the ESMC Server trace log file for the latest log entries. View log files in the following file locations:
C:\Documents and Settings\All Users\Application Data\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs
To enable full logging, create a dummy file named
traceAll without extension in the same folder as a trace.log and restart the ESMC Server service.
If a computer disappears from ESET Security Management Center (ESMC), or hangs at "In Progress" during deployment, one of the following DNS troubleshooting processes could resolve the issue: