PowerShell Web Access
summary
PowerShell Web Access on Windows Server 2012 installs as a web gateway (requires .NET 4.5), exposes a browser-based console and uses PS Remoting over WinRM to reach target servers; access is controlled by explicit authorization rules that map users or groups to specific servers and constrained session configurations (restricted language mode, visible commands only). Demonstrated features: install via Server Manager/PowerShell, test certificates, credSSP for second hop if needed, and impersonation via RunAs credentials. Limitations: no GUI/executable launches, no console APIs, three simultaneous sessions per user, configurable timeouts.
AI-written summary · about
chapters (8)
- 0:00Introduction to PWA
- 2:38Junior admin demo
- 7:36Senior admin demo
- 10:25Configuring PWA rules
- 14:01Session configurations
- 19:21Advanced security settings
- 22:14Final security demonstrations
- 31:36PWA limitations and FAQ
related talks
43mSecuring your Environment with Just Enough Administration
46mWebJEA: PowerShell driven Web Forms for Secure Self-Service
01h 34mPowerShell remoting - Installing and troubleshooting in a...
37mCreate a Secure RESTful API Gateway for PowerShell Scripts
45mKerberos Delegation, CredSSP, and Windows PowerShell
47mSecure PowerShell web tools with System Frontier
43mUsing PowerShell From a Browser to Manage Cloud Resources
01h 33mA hands-on lab working
