4 ms·

PowerShell is disabled by default for security reasons. It's one command to enable it.

WorldWideWayne 11y ago
Yeah, one command - on every machine... Meanwhile on Linux, I don't need to do any special configuration to run scripts.
- dragonwriter 11y ago
  > Yeah, one command - on every machine... I think Microsoft envisions centrally-managed environments, rather than those with lots of Windows machines that aren't centrally managed.
- theg2 11y ago
  You do if those scripts can affect the system and need to run as root. Powershell is incredibly powerful (and dangerous) and some security isn't the worst thing.
  - swasheck 11y ago
    the irony of this is that if ms were to leave powershell open to run any scripts from anywhere at any time, they'd be ridiculed for lax security policies.
    - mmcru 11y ago
      why? .cmd and .bat can run any time, and can do just as much damage as powershell.
  - astrodust 11y ago
    It's no more powerful and dangerous than bash in the right hands.
- dragontamer 11y ago
  > on every machine... Or through one group policy pushed to every machine.
  - Someone1234 11y ago
    Plus, unlike what most people envision on here, Microsoft intends companies to push AllSigned or RemoteSigned, rather than Unrestricted. So the company can push their CA and new PS policy in a single GPO, and then all internal PS scripts are signed using an internal CA generated code signing certificate. This sounds complex but it is actually as simple as running Set-AuthenticodeSignature on each script using the code signing certificate.
useerup 11y ago
> PowerShell is disabled by default for security reasons. Small correction: PowerShell script files are disabled by default for security reasons. PowerShell is available with all Windows versions since Vista SP1. On the latest Windows versions, remote command (part of Remote Management) is enabled by default. I.e. you can connect (given proper credentials) to a Server 2012R2 through PowerShell remoting and execute commands. Indeed, the new "Server Nano" will not have any way to log in locally at all. There is no shell (as in operating system shell), and no local editor (like notepad). Only the remote command interface. PowerShell will be extended to allow remote file editing - i.e. use a local editor for a file residing on the remote computer (been missing that for the longest time now)

Yeah, one command - on every machine... Meanwhile on Linux, I don't need to do any special configuration to run scripts.

dragonwriter 11y ago
> Yeah, one command - on every machine... I think Microsoft envisions centrally-managed environments, rather than those with lots of Windows machines that aren't centrally managed.
theg2 11y ago
You do if those scripts can affect the system and need to run as root. Powershell is incredibly powerful (and dangerous) and some security isn't the worst thing.
- swasheck 11y ago
  the irony of this is that if ms were to leave powershell open to run any scripts from anywhere at any time, they'd be ridiculed for lax security policies.
  - mmcru 11y ago
    why? .cmd and .bat can run any time, and can do just as much damage as powershell.
- astrodust 11y ago
  It's no more powerful and dangerous than bash in the right hands.
dragontamer 11y ago
> on every machine... Or through one group policy pushed to every machine.
- Someone1234 11y ago
  Plus, unlike what most people envision on here, Microsoft intends companies to push AllSigned or RemoteSigned, rather than Unrestricted. So the company can push their CA and new PS policy in a single GPO, and then all internal PS scripts are signed using an internal CA generated code signing certificate. This sounds complex but it is actually as simple as running Set-AuthenticodeSignature on each script using the code signing certificate.

useerup 11y ago

> PowerShell is disabled by default for security reasons. Small correction: PowerShell script files are disabled by default for security reasons. PowerShell is available with all Windows versions since Vista SP1. On the latest Windows versions, remote command (part of Remote Management) is enabled by default. I.e. you can connect (given proper credentials) to a Server 2012R2 through PowerShell remoting and execute commands. Indeed, the new "Server Nano" will not have any way to log in locally at all. There is no shell (as in operating system shell), and no local editor (like notepad). Only the remote command interface. PowerShell will be extended to allow remote file editing - i.e. use a local editor for a file residing on the remote computer (been missing that for the longest time now)