Is there a way to run the script manually?

[martywirenz]

Ist here a way to run the script manually when it's created?

When i look at my logs it doesn't show anything and the scheduled task isn't created

[qhajkasem]

I'm having the same issue(s) and it looks like Intune is tripping over all sorts of stuff in the script itself and it makes no sense at all. It first complained (from the agentexecutor en ime logging) that the use of the "&" is prohibited as it is reserved for future use. Even the & in a comment stopped it from running. Once I replaced these it started to complain about a missing quote on a line that only defines a variable (as a string with correct quoting) and I haven't found a way around this. I'm sure I'm missing something or whatever.

The weird thing is, that is absolutely nothing wrong with the script. If I execute it manually (use psexec with the -s and -i swithches to start a command prompt (or powershell) as SYSTEM) it works as expected and it has worked before as I only found about this after adding a new drive to it. None of our laptops get the updated script and I only see errors in intune (not helpfull at all but that's besides the point).

No clue why this behaviour changed but it is really annoying. I get that code should get checked in some way but this makes no sense at all. Maybe pack the script as a Win32App so it gets "installed" correctly?