Forum Discussion
FEATURE REQUEST - Welcome to a new era of activation tooling - this is not an announcement
When promoting the idea within the community we came to a point that a PShell Module for activation management is really required for IT professionals esp. large scaled (Providers). Thank you Bronson Magnan for fueling this from your professional perspective.
In this case I would be even absolutely fine to drop the issue report of VAMT from the ADK and not fixing the WS 2019 / 2022 Key issue in VAMT, if we see this coming instead, just to save dev time. And even dropping VAMT altogether as it would no longer feasible, if the PSModule could also replace all Office VBS Activation setups.
fyi abbodi1406
on a sidenode:
With that said, I had one great success at a customer to convert an existing complex VBS script into PowerShell using BingGPT Enterprise. I was really amazed how it cleaned up the "Spaghetti code" of the past in seconds.
Now they are using this converted script in production.
This could also be helpful for the product groups that use VBS today. Such as slmgr, printmgr.vbs, office activation vbs (2010 (need a Win10 fix anyway) - 2021), and also MDT, while deprecated for Windows 11 and potentially vNext deployment, too, which I suspect rather to check and deal with the new HW requirements or whatever.
https://github.com/OfficeDev/Office-IT-Pro-Deployment-Scripts/blob/master/Office-ProPlus-Deployment/Remove-PreviousOfficeInstalls/OffScrubc2r.vbs
- Karl-WEJan 17, 2024MVP
Hey abbodi1406 do you mean I should try if GPT enterprise will convert the vbs into PowerShell? But then by what means? I wouldn't be able to code a module as proposed.
- abbodi1406Jan 19, 2024Iron ContributorI don't really how GPT enterprise (or any GPT) works
- Karl-WEJan 20, 2024MVPif you'd like to talk about it more, write me via DM Abbodi, I am looking forward to meeting with you.