How to troubleshoot errors when installing AgentP

Logs: Invalid class

Example:

System.Management.ManagementException: Invalid class
  at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
  at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
  at AgentP.Server.DataCollection.ComputerInformationCollector.DetectOperatingSystemVersion()
  at AgentP.Server.AgentServer.MakeEnrollmentRequest()

Reason:

The WMI repository on the endpoint is probably corrupted.

Verify if you have an issue with the WMI repository by executing the following command in the command line:

wmic os

Solution:

To fix the WMI repository, follow this article: WMI: Missing or Failing WMI Providers or Invalid WMI Class

Logs: There was no endpoint listening

Example:

Method https://mobilecentraal.portnox.com/AgentpBackEndEnrollment/Enrollment
- There was no endpoint listening at
https://mobilecentraal.portnox.com/AgentpBackEndEnrollment/Enrollment
that could accept the message. This is often caused by an incorrect 
address or SOAP action. See InnerException, if present, for more details.

Reason:

The communication with Portnox Cloud is blocked.

Solution:

Type the following URLs in the browser on the same computer and check if you receive the Method not allowed message in the browser:

• https://mobilecentraal.portnox.com/AgentpBackEndEnrollment/Enrollment
• https://mobilecentraal.portnox.com/AgentpBackEndEnrollment/CheckForUpdates

Logs: Organization not found

Example:

Method https://mobilecentraal.portnox.com/AgentpBackEndEnrollment/Enrollment
- Response BadRequest, Internal error 15074: Organization not found for device
'Laptop' with login 'VORLON\kosh.naranek'

Reason:

Portnox Cloud was not able correlate between the domain name collected from the machine and the domain name configured in Portnox Cloud for the specific domain and AD broker. For example, you may have configured vorlon.com as a domain name, but you didn’t configure vorlon, which is the name collected by AgentP.

Solution:

Add all relevant domain names to the broker configuration in Portnox Cloud: Settings > AUTHENTICATION REPOSITORIES > DIRECTORY INTEGRATION SERVICE > Edit > Add new domain name.

Events: Installation failed

Example:

Product: Portnox AgentP -- Installation failed.
Product: Portnox AgentP -- Error 1920.
Service 'Portnox AgentP Client Service' (PortnoxAgentP) failed to start.
Verify that you have sufficient privileges to start system services.

Reason:

.NET 4.5 is not installed on the endpoint.

Solution:

Install .NET 4.5 on the endpoint and reinstall AgentP.

GPO: Installation fails

Solutions:

1. Add the shared folder as a shared path.

2. Configure the AgentP GPO processing wait time:

   Computer Configuration > Administrative Templates > System > Group Policy > Specify startup policy processing wait time > Enabled > Amount of time to wait (in seconds) > 30

macOS: No profile downloaded

When you enroll AgentP, no profile is downloaded or installed. Enrollment works correctly and no errors are reported in Cloud or in the operating system.

Solution:

Check if the following file exists: /var/agentp/unattended.cfg. If it exists, delete this file. Then, unenroll AgentP and enroll again. AgentP should then download the profile.