Ask the Community
Groups
Failed to save client: Registration for client failed. (Windows client) - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Registration for client connection failed when attempting to register a new Windows client to the Unitrends system.</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p><br>The purpose of this article is provide troubleshooting steps for client registration failures.<br> </p> <h3 data-id="cause"><b>Cause</b></h3> <br>The Unitrends system performs validations checks when a new client is added to the Unitrends system to be protected.<br> <h3 data-id="resolution"><b>Resolution</b></h3> <br>Follow these common troubleshooting steps to resolve client registration problems when a new client is added for protection.<br><br><b>For Windows clients:</b><br><br>First, for Windows systems, identify whether you are installing from the Unitrends system using Agent push or installing the agent software directly on the protected client. The Unitrends system uses agent push to allow you to install and update the Unitrends agent software on the protect client from the Unitrends system. Agent push has more prerequisites as the Unitrends system must have authorization to install the agent on the client. <div> <br><br><b>For Windows clients using agent push:</b><br> </div> <ol><li>Verify that the protected asset you desire to add meets the prerequisites for <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fguides.unitrends.com%2Fdocuments%2Frs-ueb-admin-guide%2F%3F_ga%3D2.15636147.485450628.1514459373-1539640114.1514459373%23satori%2Finstalling_the_windows_agent.htm">installing the windows agent</a> </li> <li>If all prerequisites are met, try installing the agent manually to determine whether there are problems with installing the agent outside of the agent push feature. This will help identify whether the problem is related to the agent installing or with the Unitrends system pushing the agent to the client.</li> </ol><div> <br><b>For Windows clients NOT using agent push:</b><br> </div> <ol><li>Verify that the client you desire to protect meets the <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fguides.unitrends.com%2Fdocuments%2Frs-ueb-admin-guide%2F%3F_ga%3D2.15636147.485450628.1514459373-1539640114.1514459373%23satori%2Finstalling_the_windows_agent.htm">requirements for installing the Windows agent.</a> </li> <li>Make sure to uncheck the "Install Agent (Windows Only)" option. *This is one of the most common reasons for the client registration process to fail once the agent software has been manually installed.</li> <li>Verify that ping request are allowed to the client.</li> <li>Disable any anti-virus or firewall software running on the client.</li> <li>Verify ports 1743 - 1749 are accessible and not in use by another application.</li> <li>You may also try to uninstall and reinstall the agent software to ensure the agent was successfully installed. See also <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Funitrends-support.zendesk.com%2Fhc%2Fen-us%2Farticles%2F360013266758">How to install a new Windows Agent</a> </li> <li>The Windows event logs may also present more details error messages indicating the point of failure.</li> <li>The Unitrends agent logs error to the "wbps" log where errors occur. The default location of the wbps log is on the protected client under c:\pcbp\logs.dir. Use the date modified to identify the log corresponding to the time of troubleshooting.</li> </ol> </article> </main>