Few PowerShell One-Liners To Check WinRM Settings on Remote Machines

To Check if WinRM has been enabled on a Remote machine: To Check the Default HTTP listener port on a remote machine: To Check the Default HTTPS listener port on a remote machine:

My First Impression on PowerShell Web Access

I ran up an instance of Windows Server 2012 in my test lab last night so I can play with various new features such as IPAM and PowerShell Web Access, etc. Today I configured this box as the PowerShell Web Access (PSWA) gateway. I have to say, I am very very impressed! The implementation is easy, took me less than an hour (including time spent reading TechNet articles) and having ability to access PowerShell console on virtually any web browser for all Windows machines in my lab is just fantastic! Now I can probably get away from using RDP most

Using PowerShell Remote Sessions in a large SCOM environment

I have previously blogged using SCOM PowerShell snap-in and SDK client in a PowerShell remote session to avoid maintain a consistent SDK connection to RMS server. I just found out there might be a potential issue when using this technique to run scripts against a reasonably large SCOM management group. By default, the maximum amount of memory a PowerShell remote session can use is limited to 150MB. You can check this setting on your computer by using Depending on how much data the remote session has to process, you might running into problems. For example, compare these 2 scripts: Sample

%d bloggers like this: