This issue can occur if the user name or password that you entered is incorrect. Enter the correct user name and password to resolve this issue.
Endpoint Protection Manager is not able to authenticate as Administrator
This issue can occur if the client has Simple File Sharing (or the Sharing Wizard) enabled. It can also happen if you have set the "Sharing and security model for local accounts" client policy to Guest Only.
The Administrator Account is not assigned the "Access this computer from network" User Rights Assignment
On the client, open gpedit.msc. Go to Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment. Confirm that the account, or the administrators group the account is under is added to "Access this computer from network". More Information here.
The Remote Registry Service is disabled on the client computer
If the Remote Registry Service on the client has stopped and the service disabled, Endpoint Protection Manager cannot scan the registry because the service is not running. To resolve this issue, set the Remote Registry Service on the client to either Manual or Automatic.
For more information, refer to the SEPM tomcat logs located at C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Tomcat\Logs\scm-server-0.log
Example of remote registry failure condition from scm-server-0.log
THREAD 91 WARNING: SearchUnagentedHost>> parseNstOutputLine: NST log line -> [WARNING: Failed to open a connection to the RemoteRegistry service on 192.168.1.230. because "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it."]
To check the Remote Registry Service
In the Windows Control Panel, go to Administrative Tools > Services > Remote Registry.
Set Startup Type to either Manual or Automatic.
Click Start to start the service.
The LAN Manager authentication levels on the Endpoint Protection Manager and clients are not compatible
If the LAN Manager Authentication Levels on the Endpoint Protection manager and clients are incompatible, they cannot communicate. Normally they are the same because Group Policy Management in Active Directory sets the policy.
When computers on the network are not using this and the connections fail, check the options on the computers involved.
To check the LAN Manager options on Windows 2003 Server or Windows XP and later versions
In the Windows Control Panel, go to Administrative Tools > Local Security Policy > Local Policies > Security Options.
Right-click Network Security: LAN Manager authentication level, and click Properties.
Ensure that the Endpoint Protection Manager and client have the same settings.
Note: Endpoint Protection for Mac 12.1.5 and later supports remote push installation.
User name does not have administrative privilege
If the Mac client computer is part of an Active Directory domain, use domain administrator account credentials for a remote push installation. Otherwise, have the administrator credentials available for each Mac to which you deploy.
Remote Login is disabled
Go to System Preferences > Sharing > Remote Login.
Allow access either for all users or only for specific users, such as Administrators.
Stealth mode is enabled
If you use the Mac firewall, disable stealth mode. With stealth mode enabled, the remote push installation cannot discover the client through Search Network.
See the appropriate Apple knowledge base article that applies to your version of macOS:
macOS Sierra (10.12): Prevent others from discovering your Mac
OS X El Capitan (10.11): Prevent others from discovering your Mac
OS X Yosemite (10.10): Prevent others from discovering your Mac
OS X Mavericks (10.9): Prevent others from discovering your Mac
OS X Mountain Lion (10.8): Prevent others from discovering your computer
TCP port 22 is blocked
Ensure that the firewall does not block TCP port 22, which Secure Shell (SSH) uses. This port allows the required communication for remote log in.
Known_hosts file is using public key formats other than SSH-RSA