In this video, Sebastian Perusat will walk you through the tasks needed to remove a license from the IGEL OS, including working with the IGEL UMS, License Portal, command-line, and IGEL OS itself. This is a frequently asked question within the IGEL Community, KB, and Support.
Présenté par Sebastian Perusat, IGEL Community FELLOW.
Dans cette vidéo, Sébastien vous apprendra à.. :
Animateur : Andy Whiteside
Coanimateur : Patrick Toner
Co-host: Seb Perusat
How IGEL OS Licensing Evolved
Licensing for IGEL OS has changed over the years. With IGEL OS 10, hardware devices were licensed perpetually and received updates for the life of the OS release. Third-party hardware could be converted with the Universal Desktop Converter, with a maintenance fee for updates. Several separate add-on licenses covered features such as the IGEL Cloud Gateway, which made quoting and managing them confusing.
IGEL OS 11 separated the license from the hardware. A perpetual Workspace Edition license carries yearly maintenance, and the premium features, including the Cloud Gateway and an asset inventory tracker, were bundled into the Enterprise Management Pack, a yearly subscription. That simplified the model to two licenses and meant a license could move to new hardware if a device failed. Further changes were planned toward a subscription-based model and the next major OS release.
Why Licenses Need Manual Removal
IGEL delivers licenses to endpoints as files. There is no API or communication channel for the licensing portal to talk to the device, so the portal and the endpoint can disagree. If a device is removed from a product pack in the licensing portal, the device keeps holding the license locally, and the UMS and the device’s About window can still show it.
Resetting a device to factory defaults does not remove the license either. Reimaging with the OS Creator asks whether to migrate licenses, but a device that is simply decommissioned still carries its feature set wherever it goes. Automatic removal is on the roadmap, but for now it takes a few manual steps.
When Removal Is Needed
There are several practical reasons to clean up licenses. A device might hold wrong license information or be many years old with leftovers from past deployments. Normally a device picks up new maintenance or a new license without trouble, but a small percentage stay stuck with older information.
Another example is the starter license, a limited version used for testing. If it remains on a device, a production license may not be picked up as expected. Moving from IGEL OS 10 to 11 can also leave several licenses on a device, and cleaning out the ones that are no longer used is sensible housekeeping.
The Removal Process
The process begins in the licensing portal. Find the device in the correct company’s product pack, remove it, and confirm the license agreement prompt. Refresh the product pack in the UMS, and then check the license status in the UMS asset information and in the About window on the device.
To remove the license from the device itself, open a local terminal as the root user. License files sit in a read-only partition, so the partition must first be remounted in read-write mode before the relevant license link file can be deleted. After deleting, check the remaining licenses to confirm only what is expected remains. For example, after removing the Enterprise Management Pack, only Workspace Edition and maintenance should be left. The partition returns to read-only after a reboot.
Using Profiles Instead
The command-line approach suits a single device or a test, but IGEL has published preconfigured profiles in its knowledge base that automate the same steps. They can be imported into the UMS and assigned to devices to delete a specific license type, such as only the Enterprise Management Pack, only the Workspace Edition, or all licenses.
The process is admittedly more involved than it should be. It is a frequently asked question in the IGEL community and from enterprise customers, and the move to a simpler subscription model and the next OS release are expected to make license management more automatic. As a security reminder, the default root login on a terminal should be disabled in production.