MicrosoftFor those of us who are infrastructure types who use things like logon scripts, macros etc, but aren't necessarily core developers who know what some of the terminology above means, can you answer these simple scenario-type questions.
Affected or not?
1) .vbs logon scripts for users logging on to Win 11 machines for things like updating description fields for logon tracking and so on. Easy to move to powershell i know but will it be affected
2) Macros in word or excel that don't call external vbs files, they just do formatting stuff like inserting headers / footers and so on, referencing png files etc but no external vbs dependencies.
3) We also use VBS scripts as a wrapper for powershell scripts when we need it to run in user context but run hidden e.g. for scheduled tasks run in the user context or whatever but triggered by group policy. Powershell is i believe referred to as a console application or something like that and as such doesn't have a "hidden" option - the windowstyle hidden option still flashes up an initial launch window and THEN the launched script runs hidden. using cscript or wscript on the other hand, lets you call the powershell script without it flashing up in the user's face at all. This for us is the biggest risk of all of this change.
