Random tidbit I figured I'd toss in here. Security under Powershell is, well, very locked down by default due to concerns over normal users being e-mailed a script and running it.

The big thing for me was just getting .ps1 scripts to run both locally and remotely. By default, they won't, and most sites talk about using "SetExecutionPolicy RemoteSigned" to be able to run local unsigned scripts. However, that only covers the surface, and the security applies to 5 different scopes. Running the scripts remotely is a bit different. What finally helped is looking at "Get-ExecutionPolicy -list", as it shows the 5 different scopes and each security level. Ultimately for development I've ended up changing 3 of the 5 scopes to just full bypass mode.