Here's a fun one...
Client has 27 sockets for Availability Suite, and through consolidation has reduced their actual usage to 18 sockets. So far, so good.
They're in the process of updating hardware from older G6 & G7 to Gen9 gear, and doing so using side-by-side migration: add the new host to inventory, migrate VMs to the new host, remove the old host from inventory. With VBR, the license re-allocation is going just fine: old hosts aren't "keeping" sockets, and there are no complaints from the license manager.
But VeeamONE is having problems. Through these migrations, now the ONE license manager is showing 31 sockets deployed, and the automatic exclusion rule is grabbing new hosts as they're being added to inventory and NOT releasing the old hosts as they're removed.
All the hosts are in the environment by way of the single vCenter, so I'm not getting "double dipping" due to adding them individually as well as in aggregate.
And because the old hosts aren't in inventory anywhere in the Infrastructure View, I can't figure out how to exclude/remove these old buggers so that the new ones will instead be able to use the license.
Here's the question: is this something that I should be able to fix using the GUI, or is this going to require a support call & running TSQL scripts against the ONE database to remove old cruft?