Based on the excellent Oh My Zsh, this repository is designed to provide some out-of-the box enhancements to running PowerShell.

Powershell very powerful for interacting with Windows devices.

Goo Goo Ka Choob. - Dylan

##Boot Strapping PowerShell Yes, getting started with PowerShel can be a real problem.

First off, the default path apparently does not include PowerShell. This can, of course, be an issue trying to run PowerShell scripts which are terminated using the extension .PS1.

The Wolf, provides a little help in his blogpost about how to use a CMD file to bootstrap powershell.

There are four instances of PowerShell on my 64-bit Windows 7 installation. 1 C:\Windows\System32\WindowsPowerShell\v1.0 2 C:\Windows\SysWOW64\WindowsPowerShell\v1.0 3 C:\Windows\Winsxs\AMD64... 4 C:\Windows\Winsxs\wow64...

I use the one in SysWOW64. And in spite of the version numbers in the path, they are both version 2.

• Check if powershell.exe is in the path.
• Check if the found powershell.exe is v2 or later
• Update the path to include the appropriate powershell.exe executable
• Check ExecutionPolicy and if it is defaulted to Restricted set it to RemoteSigned

Engage a new Profile

http://www.rlmueller.net/PSGotchas.htm

http://superuser.com/questions/82053/setting-home-in-powershell