Why does VAMT suck so much? We normally use ADBA and that works fine, but we've had to use VAMT to activate Win10 ESU licenses last year, and it was an absolute

Why does VAMT suck so much? We normally use ADBA and that works fine, but we've had to use VAMT to activate Win10 ESU licenses last year, and it was an absolute nightmare. Possibly the most poorly designed piece of Microsoft tool in my experience (maybe second only to MS cloud services). - There was no option to activate a specific set of machines sitting in a particular OU or AD group, which means you'd have to manually import machines that you want to activate - and you can't do a bulk import from a simple text/CSV file either. - VAMT does not automatically retry failed devices, or devices which were offline. Trying to find these devices and manually activate them via VAMT is also not feasible, especially if you have a large fleet. - Pretty much no useful reporting capability especially if you want to track failed/offline devices. I've had to end up hacking together a bunch of PowerShell scripts and scheduled tasks to make up for the lack of functionality - something I shouldn't have to do. And it wasn't nice that the VAMT module isn't compatible with PowerShell v5.1, which means I needed to run my scripts under PowerShell v2... And please don't tell me that the answer is "cloud". Cloud doesn't work for everyone, and I'm sure MS have plenty of Fortune 500 customers or critical organisations (like government agencies) that are still on-prem only.