For more information on Agent deployment failure, refer to:
To determine why Agent deployment failed, click Reports → Agent Deployment tasks 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 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/ESET PROTECT 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 the ESET Security Management Center Server service or ESET PROTECT Server service.
If a computer disappears from the Web Console or hangs at "In Progress" during Agent deployment, one of the following DNS troubleshooting processes could resolve the issue:
Enable Secure Shell on macOS to deploy the ESET Management Agent.
In the system tray, click the Apple icon → System Preferences → Sharing.
Select the check box next to Remote Login.
Close the Sharing window and attempt to Deploy the ESET Management Agent again.