... if they still rely on the decades old vbscript based licensing tool and have not migrated to other solutions such as the equivalent PowerShell tool which is itself around a decade old. Despite Microsoft's previous warnings, and despite having to take manual effort to re-enable vbscript on modern Windows installs.

This would take multiple levels of mistake to effect anyone.

Important event for Enterprise sysadmins, but awfully clickbaity title.

My workplace still VB scripts things. They tell me I’m being alarmist about Microsoft killing VB script when I point out they were warned about this quite a while ago.

I hate our IT. Their problems always become our problems.

Ok??? So don't kill it??? You control the ecosystem so just don't do the thing???