How can we help?

Mac Endpoint Agents Installed but Not Appearing in the Auvik Endpoints Tab

Follow

Overview

The Auvik Collector and the Auvik Endpoint Agent are separate components with different purposes. The Auvik Collector is not supported on macOS, while the Endpoint Agent is specifically designed for endpoint monitoring and inventory on supported operating systems, including macOS.

If macOS devices have the Endpoint Agent installed but are not appearing in the Endpoints tab, the issue is typically related to site association, registration, connectivity, or configuration.

This article outlines steps to identify and resolve the issue.


Symptoms

  • macOS devices have the Endpoint Agent installed but do not appear in the Endpoints tab
  • No endpoint data is visible after installation
  • Devices appear to install successfully but never register

Step 1: Confirm the Correct Software Was Installed

Ensure the correct installer was used:

  • Verify that the Auvik Endpoint Agent for macOS was installed (not the Auvik Collector)
  • Re-download the macOS agent from:
    • Admin → Endpoint → Deploy Agent in your Auvik tenant 

Installing the Auvik Endpoint Agent on MacOS workstations

If unsure, uninstall and reinstall using the latest agent package.


Step 2: Verify Site Association and Enrollment

Each endpoint is tied to a specific Auvik site using a Site Registration Key (SRK).

  • Confirm the installer or deployment command used the correct site key
  • Ensure you are viewing the same site in Auvik where the agent was deployed
  • If needed:
    • Regenerate the Site Registration Key
    • Reinstall the agent using the updated key 

 Endpoint Troubleshooting

Important: Agents deployed with an incorrect site key will not appear in the expected tenant/site.


Step 3: Validate Endpoint Feature Enablement and Licensing

Confirm that Endpoint Monitoring is enabled:

  • Check Settings → Feature Enablement
  • Ensure your subscription includes Endpoint Monitoring

Endpoint Agent Shows Network Monitoring and Inventory as Disabled After Installation

If the feature or licensing is not enabled, endpoints may not register or display.


Step 4: Allow Time for Registration

After installation:

  • Initial registration and synchronization can take several minutes
  • In some cases, feature initialization may take longer

Ensure the device remains online during this period.


Step 5: Verify Connectivity to Auvik Cloud

The endpoint agent must communicate with Auvik services:

  • Ensure outbound HTTPS (TCP 443) is allowed
  • Check for:
    • Firewall restrictions
    • Proxy configurations
    • DNS resolution issues

If connectivity is blocked, the agent cannot register or report data.


Step 6: Confirm the Agent Is Running

On the macOS device:

  • Verify the agent is installed and running
  • Restart the device to ensure services initialize correctly
  • Confirm no local security controls (e.g., endpoint protection) are blocking execution

Step 7: Additional Troubleshooting

If devices still do not appear:

  • Reinstall the agent using the latest installer
  • Redeploy via MDM with a validated configuration and correct site key
  • Confirm system time and date are accurate (clock skew can affect secure registration)
  • Test from a different network to rule out firewall or proxy issues

When to Contact Support

If the issue persists after completing the steps above, gather the following before opening a support ticket:

  • Device name and hostname
  • macOS version
  • Installation timestamp
  • Deployment method (manual or MDM)
  • Network details (firewall/proxy)
  • Installation or agent logs (if available)

Important Notes

  • The Auvik Collector cannot be installed on macOS
  • Use a supported platform (Windows, Linux, or virtual appliance) for network data collection
  • Use the Auvik Endpoint Agent for macOS endpoint visibility

Summary

If macOS endpoint agents are not appearing in Auvik, the most common causes are incorrect site association, invalid registration keys, lack of licensing, or blocked connectivity. Verifying installation source, site mapping, and network access will resolve most issues.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request