Today I had a chat with a customer about the Windows PowerShell Web Access. I told him, that the Web-based access could be very useful, at least sometimes, and not just a gimmick.
I told him to read this TechNet article: Install and Use Windows PowerShell Web Access.
The article is great, but instead of applying so many rules (most examples use single users and single computer) my approach is group based. I’m a big fan of groups, and that gives me the flexibility to manage everything via the existing Active Directory. And as a benefit, it could reduce the rules.
Please note the following:
UserGroupName – It must be the Format ‘DOMAIN\ACCESS-GROUP‘
ComputerGroupName – It must be the Format ‘DOMAIN\COMPUTER-GROUP‘. UPN will not work!
ConfigurationName – It must match with the provided name during the login, ‘Microsoft.PowerShell‘ is the default, it’s good idea to use another one.
RuleName – It Is for your information only
Certificate – I highly recommend using a trusted certificate
Security – I also recommend you to keep an eye on the Gateway, especially if it is published directly to the Internet (Please keep in mind, that this is a shell access to you systems)
Load Balancing – If you have multiple gateways, you can use a load Balancer. You must ensure, that the session is sticky. But I think it is not officially supported.
And here is why I find the Windows PowerShell Web Access so extremely useful: With the iPowerShell V.5 from SAPIEN Technologies, you can access it from you Mobile Device! Free from the AppStore!
I have some Scripts stored in my OneDrive and I execute them from my iPad. Mostly maintenance and reporting stuff that I need from time to time. And I don’t need to open or start my computer!