Products in Nebula adhere to the licenses assigned in the console. Each product is allocated a select amount of seats which can vary based on the subscription, unless a bundle is purchased. For example, an account without a bundle may have 500 seats for Endpoint Detection and Response and 25 seats for DNS Filtering. An account with a bundle would have the same number of seats available for each subscription.
By having different seat counts across subscriptions, administrators can select features on a set number of endpoints instead of on every endpoint, while still having access to all subscribed products. While this can be useful, it can also cause the license t65o show it's overused on its seat amount in Nebula. This happens due to a misconfiguration of the policy and group settings for endpoints deployed in the console.
Click on your display name > Account in the top right of Nebula to view current number of used and available seats. For more information, see Manage subscriptions and billing in Nebula.
Note: The license key has moved to the bottom of the Download Center > Advanced tools page. If you are unable to locate your license key, contact Support.
Recommendations
If you encounter an alert in the console regarding an over-deployment of endpoints, choose one of the recommended options.
Remove inactive devices
Identify inactive endpoints on the Manage > Endpoints page by filtering the Last Sync column to Last Sync 30+ Days Ago. Select and remove them by clicking Actions > Delete. This frees up licenses by removing the device from the console and sending an uninstall command to the device. For more information, see Uninstall endpoints in Nebula.
You can automate this process by enabling the inactive endpoints policy setting. For more information, see Endpoint agent policy settings in Nebula.
Verify policy and group configuration
Verify your policies and groups are configured to accommodate the assigned endpoints and features they should be using. For example, if you are overallocated on Endpoint Detection and Response for Servers, ensure that the Endpoint Detection and Response policy settings are only enabled for your server policies and not all policies.
You can do this by creating separate groups and policies for endpoints and configuring the policy for the desired products. For information on creating groups and policies, see Overview of policies and groups in Nebula.
Also, review the ThreatDown recommended policy to see which policy settings apply to the different available features and set them accordingly for your endpoints.
Purchase more licenses
If you've verified all of the above and still require additional licenses, contact Sales. For more information, see Contact Sales.