![]() ![]() Test access to both HTTP on port 80 and HTTPS on port 443. If the target device can resolve the N-able N-central server's FQDN, verify that you can navigate to the N-able N-central server in a browser and sign in. ![]() If the agent or probe is configured to use the N-able N-central server's FQDN, use a PING command to verify that the server's address can be resolved properly. Installing agents or probes may fail if the installer can not communicate with the central server. ![]() Consult with your network administrator to see if there is a Group Policy that might restrict the installation.to start the installer as the domain administrator. If available, right-click on the name of the.Verify the account you are using has the appropriate administrative rights.To resolve this issue, grant "Logon as Service" privileges manually or use a different account to install the probe. Installation of a probe may fail due to "Logon as Service" privileges not being available. To revise you license limit, contact your applicable Service Organization or N-able sales representative. When the license limit for the number of Windows agents or probes permitted on the server has been reached, no additional Agents or Probes can be installed. If the installation has failed, verify that the information has been entered correctly with no errors.Ĭlick Administration > Customers and verify the name and customer ID are correct. The installation of agents or probes may fail if you provide incorrect activation information for the customer name, customer ID or activation key. If these options do not resolve your issues, contact N-able technical support. If the installation of a agent or probe software is not successful, review these areas where the install may be having issues.įor further troubleshooting and solution options, go to the N-central Troubleshooting Guide and search on agent and probe installation issues. Troubleshooting agent and probe install issues ![]()
0 Comments
Leave a Reply. |