I am not allowed to run powershell scripts at work because "security" even if I write them myself. But I can still run powershell and type commands into it. Same for .cmd or .bat files, I can still run a shell but I can't run a script. I wanted to do some text processing in powershell (as we are not allowed to install software of course, so I can't install anything actually good for the purpose like perl) and found that I wasn't allowed to. So, pathetically, the only thing I can actually script in is VBscript, and only from inside Word or Excel; I'm still allowed to write macros! I suppose the next frontier would be learning how to use Excel macros to import data from files into Excel and process it there. (I don't have Access either.)

So I think it's just great that you can one-line enough Powershell to infect a system, proving that these restrictions are worthless. I have a one-line cmd.exe shortcut to copy a certain document index file so that when it's updated I can just double-click it instead of having to go where it is to get it... It's not a script, so I can run that! Madness.