Introduction
After installing the Auvik endpoint agent, you may notice that Network Monitoring and Inventory appear as disabled in the Auvik portal. This is typically a temporary condition related to initialization, policy application, or connectivity.
This article explains expected behaviour and provides troubleshooting steps if the issue persists.
Expected Behavior
The Auvik endpoint agent installs in multiple stages, where feature-specific modules are downloaded and enabled after the initial installation completes .
During this process:
- The agent registers with the platform
- Policies and feature entitlements are applied
- Monitoring modules initialize
It is normal for features to remain disabled for up to 1–2 hours after installation.
Troubleshooting Steps
1. Allow Time for Initialization
- Wait up to 1–2 hours after installation
- Ensure the endpoint remains online during this period
2. Verify Feature Enablement Settings
Check that features are enabled at the platform level:
- Navigate to Settings → Feature Enablement
- Confirm:
- Endpoint Monitoring is enabled
- Required features are not disabled at the site or global level
3. Confirm Licensing
Ensure the site:
- Has an active license that includes:
- Network Monitoring
- Inventory
Lack of licensing can prevent feature activation.
4. Verify Connectivity Requirements
The agent must communicate with Auvik services.
Check:
- Endpoint shows as online
- No firewall or proxy blocking outbound traffic
- Required ports and endpoints are allowed (see Endpoint Network Considerations)
5. Validate Agent Health
- Confirm the agent service is running
- Restart the agent service
- Ensure the agent is up to date (auto-updates typically apply automatically)
6. Reinstall the Agent
If the issue persists:
- Uninstall the existing agent
- Reinstall using admin privileges
- Allow time for re-initialization
When to Contact Support
If features remain disabled after completing all steps:
Provide:
- Endpoint logs
- Device ID
- Site name
- Timestamps of observed issue
Summary
This issue is most commonly caused by:
- Normal post-installation propagation delay
- Feature enablement or licensing configuration
- Connectivity issues
- Agent initialization failures
Following the steps above resolves most cases.