Using Windows PowerShell WEB access

Microsoft introduced the Windows PowerShell Web Access feature in Windows Server 2012, which allows administrators to remotely run PowerShell commands and scripts over the network console.

Setting up PowerShell access on Windows Server R2 or Windows Server 2012 requires Web server (IIS),. NET Framework 4.5, and Windows PowerShell 3.0 or Windows PowerShell 4.0. You can enable the PowerShell Web access component by using the Add Roles and Features Wizard in Server Manager.

However, Web access poses some security risks, so you should enable some security mechanisms ahead of time. Make sure that PowerShell Web Access contains the authorization rules based on the cmdlet and uses the security features of the Web server (IIS).

For example, if you know the exact IP address or range of a remote PowerShell connection, you can implement address restrictions that specify the IP address or range of addresses that are allowed to connect.

The default URL for PowerShell Web access is https://< server_name >/PSWA. Users must know the name or IP address of the remote computer to which they want to access or administer when they log on. These users must be authorized users of the remote computer and the computer must be configured to allow remote administration. If the user does not exit, the connection will be automatically disconnected after 20 minutes.

As you can see in the screenshot, PowerShell Web access has several buttons at the bottom: Commit, Cancel, arrow, and exit, and also display the name or IP of the remote computer you are currently connected to.

PowerShell Web Access screenshot

PowerShell Web Access shares the same restrictions as regular remote Windows PowerShell sessions, so there are some PowerShell features and features that are not supported.

PowerShell Web Access also has some specific web-based access restrictions. For example, a function key (keyboard shortcuts) does not work. The input/output color cannot be changed, although the output color and style can be changed by running a script.

In addition, you can only connect to one remote computer at a time, and you cannot open PowerShell Web Access on multiple tabs.

Finally, PowerShell Web Access does not require the use of PowerShell and any remote access software, and you do not need to install a browser plug-in on the network console computer or device you are using. Microsoft currently has only a list of officially supported desktop browsers (IE, Firefox, Chrome, and Safari), but it has also been tested successfully on mobile browsers (Windows Phone, Android, and iOS). Any computer or device that supports JavaScript, cookies, and browsers that can connect to a secure site via HTTPS/SSL supports the PowerShell Web access feature.