The license consumption count is based on the number of endpoints managed. When the Endpoint Central agent/MDM profile is installed on an endpoint, it automatically detects the MAC address, and is accounted as a license consumed. A UEM license is consumed when the endpoint is managed in any or all of the following modules:
To understand how the licensing works when devices are managed in the different license consuming modules, let us consider a scenario with 5 devices.
The below table illustrates how a license is consumed when devices are managed in the different modules of the product.
| Product Modules | ||||
|---|---|---|---|---|
| Device | SoM | OSD | MDM | License consumed |
| A | - | ✔ | - | 1 |
| B | ✔ | - | - | 1 |
| C | ✔ | ✔ | - | 1 |
| D | - | - | ✔ | 1 |
| E | ✔ | ✔ | ✔ | 1 |
✔ - Indicates device is managed in the respective product module
So with 100 UEM licenses, an organization can
Yes, this can be done! Let's imagine an organization with 600 Endpoint Central UEM licenses, used to manage,
Here, only one license will be consumed if you've deployed OS and installed the Endpoint Central agent on a computer. Now, you will have 350 computers installed with Endpoint Central agents. Under OS Deployment license details, you can see 250 MAC addresses listed as you have deployed operating systems in 250 computers. Out of these 250 computers, you can see 150 MAC addresses greyed out as these computers also have Endpoint Central agents installed in them.
If the org decides to retire, say 100 devices, 25 devices in each category. They can uninstall the agent and remove those machines from the Endpoint Central server. However, to reuse the licenses used to deploy operating systems, the machines need to be retired from the OSD module by navigating to Admin -> OS Deployment -> License Details. Kindly note that OS deployment cannot be performed again on these machines using the same license. Now that org has,
