Windows PowerShell Web Access in Windows Server 2012

by [Published on 7 Aug. 2013 / Last Updated on 7 Aug. 2013]

This tip explains Windows PowerShell Web Access introduced in Windows Server 2012.

Windows PowerShell Web Access is a new feature introduced in Windows Server 2012. Web Access acts as a gateway to run the PowerShell cmdlets remotely on a computer. PowerShell Web Access does not require any remote management software to be installed on the remote computers. All is required to run PowerShell cmdlets remotely in a web browser is to configure the PowerShell Web Access Gateway on a Windows Server 2012 computer.

IT workers can use this new feature to run PowerShell commands remotely even from non-Windows computer.

PowerShell Web Access is a three-step process as mentioned below:

  1. Installing the PowerShell Web Access Gateway
  2. Configuring the Gateway
  3. Configuring Authorization rules and security

Requirements to setup Web Access (Server Component)

The following is the minimum requirement before you can setup the Gateway server and below components must be running on server where you want to setup the gateway

  • Windows Server 2012
  • Internet Information Server (IIS)
  • .NET Framework 4.5
  • PowerShell 3.0

Note: PowerShell Web Access Gateway is available as a role in the Server Manager.

Requirements for clients to access the Gateway (Client component)

For client to access PowerShell Web Access Gateway, clients must support the following:

  • Must be able to read HTML pages
  • Able to execute JavaScript
  • and enable cookies.

Note: A client can also be running a non-windows Operating System as long as it supports above client requirement.

 

Featured Links