3 reputation
2
bio website
location
age
visits member for 2 years
seen Nov 24 at 14:56

Nov
15
awarded  Scholar
Nov
15
comment IIS script privileges with powershell
Ah, look, I tried upvoting it, but Accepting was the way to go.
Nov
15
accepted IIS script privileges with powershell
Nov
15
awarded  Editor
Nov
15
revised IIS script privileges with powershell
added 219 characters in body
Nov
15
comment IIS script privileges with powershell
Two things: First, thanks, your messages led me to realize what the terms I was actually looking for (handlers, accesspolicy read, script). Second, that led me to the following line: set-webconfigurationproperty -filter /system.webserver/handlers -name accesspolicy -value $flagsPermissions -PSPath $PS_PATH Which works wonderfully. Also, we switched to inherited script privileges as well. Thanks for the assistance!
Nov
15
comment IIS script privileges with powershell
Ah, thanks. The command partly works, however, only if I enter Read OR Script, otherwhise, the second option is ignored with an error message (In swedish unfortunately). Also, the thing I'm looking to do is in fact in web.config, just across 82 different sites.
Nov
15
comment IIS script privileges with powershell
Ah, then it seems that someone else have modified the defaults (I've also verified this with a local install), I'll have to check why that is before I make any changes to that. However, appcmd doesn't seem to exist on either of the systems I am working on. Also, yes, modifying web.config would work fine as well.
Nov
15
comment IIS script privileges with powershell
I might've been unclear. I want to turn scripts on, not off. It seperates between scripts and executables in the GUI, and I don't want normal programs executable, jsut scripts.
Nov
15
comment IIS script privileges with powershell
Ah, yes, sorry, 7.
Nov
15
asked IIS script privileges with powershell