I’ve had many instances where it was easier to maintain a collection of commonly used PowerShell scripts on a webserver that can be reached from multiple different servers or workstations. Let’s say your .ps1 is called “checkvpn.ps1” We would run the Powershell command “iex ((New-Object System.Net.WebClient).DownloadString(‘http://www.codeisda.com/checkvpn.ps1’))“ Post Views: 233
AUTHOR: Code Monkey
I am the original "CodeMonkey", founder, CISSP and a Sr. System Administrator with over 31 years experience. I specialize in PowerShell Scripting and Virtualization. I hope that everyone will enjoy the site and contribute to make this a great resource for everyone! Author of "PowerShell Studio - A Comprehensive Guide"