I was reading the Virtual Twits blog by Alan Renouf, and I thought I would download and run the Power Shell Script. I have never gotten the time to play with Power Shell, but hey, no time better than the present right? Here is what I had to do.
His blog Entry is as follows.
“
Following the list of Powershell users collated by @StevenMurawski over at Mind of Root I thought I would follow suite and try and maintain a list of the VMware related twitters who I have found very informative and useful over the last couple of months of using twitter.
If I have missed you or you would prefer not to be on this list please let me know via the comments or contacting me on twitter @alanrenouf
You can also download the below powershell script that will run through this list and automatically follow them for you.
“
So as I stated above, I wanted to walk you through what I had to do to install Power Shell, and use this Script.
First, I downloaded Power Shell for Windows XP 64 from Microsoft’s web site, below.
“
Download Windows PowerShell 1.0
Windows PowerShell 1.0 is available as a download or can be evaluated as part of Windows Server 2008 evaluation versions. Download Windows PowerShell 1.0 for Windows XP SP2, Windows Server 2003 or Windows Vista via our Windows PowerShell download page.
“
So I downloaded the Above script onto my desktop, and double clicked it, and boom, notepad opened it.
Not quite what I had in mind.
Therefore, I googled, Running Power Shell, and found the following web site.
http://www.microsoft.com/technet/scriptcenter/topics/winpsh/manual/run.mspx
I found that you need to run the commands from the Power Shell Console, but not before you do a few things first.
I had to get my execution policy, by typing
Get-ExecutionPolicy
Then, I had to set it to unrestricted, ( i am sure there are better way’s ).
Set-ExecutionPolicy Unrestricted
Then, I had to add my desktop to a path so I could run it ( i am sure there are better way’s ).
$env:path = $env:path + ";c:Documents and SettingsuserDesktop"
Then I could run the script!
Thanks to Microsoft and the Blog Author for his Power Shell Script.
