Powershell V2.0 is the current latest realease [Dec 2011], installed by default on Windows 7 and Windows Server 2008 R2; and also available for download for earlier versions of Windows both 32bit and 64bit platforms.

On Windows 7, click the Start icon, All Programs, Accessories, “Windows PowerShell” folder
or Winkey+R type Powershell and enter

Windows Powershell is basically a CLI [Command Line Interface] like cmd but much more advanced

So Powershell is a task automation framework, cosisting of a command-line shell and associated scripting language built on top of, and integrated with the .NET Framework. PowerShell provides full access to COM and WMI, enabling administrators to perform administrative tasks on both local and remote Windows systems.

In PowerShell, administrative tasks are generally performed by cmdlets (pronounced command-lets), specialized .NET classes implementing a particular operation. Sets of cmdlets may be combined together in scripts, executables (which are standalone applications), or by instantiating regular .NET classes (or WMI/COM Objects). These work by accessing data in different data stores, like the filesystem or registry, which are made available to the PowerShell runtime via Windows PowerShell providers.

Windows PowerShell also provides a hosting mechanism with which the Windows PowerShell runtime can be embedded inside other applications. These applications then leverage Windows PowerShell functionality to implement certain operations, including those exposed via the graphical interface. This capability has been utilized by Microsoft Exchange Server 2007 to expose its management functionality as PowerShell cmdlets and providers and implement the graphical management tools as PowerShell hosts which invoke the necessary cmdlets. Other Microsoft applications including Microsoft SQL Server 2008 also expose their management interface via PowerShell cmdlets. With PowerShell, graphical interface-based management applications on Windows are layered on top of Windows PowerShell. A PowerShell scripting interface for Windows products is mandated by the Common Engineering Criteria.

 

 

PowerTip of the Day, from PowerShell.com:

Try this one-liner if you need to print out all PDF documents you have stored in one folder:

Dirc:\myfolder\*.pdf|Foreach-Object { Start-Process-FilePath$_.FullName – VerbPrint }

PowerTip of the Day, from PowerShell.com:

When you query network adapters with WMI, it is not easy to find the active network card. To find the network card(s) that are currently connected to the network, you can filter based on NetConnectionStatus which needs to be “2″ for connected cards. Then you can take the MAC information from the Win32_NetworkAdapter class and the IP address from the Win32_NetworkAdapterConfiguration class and combine both into one custom return object:

PS> Get-WmiObjectWin32_NetworkAdapter-Filter‘NetConnectionStatus=2′

 

 

ServiceName              : NETw5s64

MACAddress                 : 00:22:FA:D9:E1:50

AdapterType               : Ethernet 802.3

DeviceID                       : 11

Name                                  : Intel(R) WiFiLink 5100 AGN

NetworkAddresses :

Speed                                : 54000000

This gets you the network hardware but not the network configuration. To get the configuration data for this network card (like its IP address), get the related Win32_NetworkAdapterConfiguration instance:

functionGet-NetworkConfig {

  Get-WmiObjectWin32_NetworkAdapter-Filter‘NetConnectionStatus=2′|

    ForEach-Object {

      $result= 1 |Select-ObjectName, IP, MAC

      $result.Name=$_.Name

      $result.MAC=$_.MacAddress

      $config=$_.GetRelated(‘Win32_NetworkAdapterConfiguration’)

      $result.IP=$config|Select-Object-expandIPAddress

      $result

    }

 

}

 

PS> Get-NetworkConfig

 

Name                                                              IP                                                                  Mac

—-                                                              –                                                                  —

Intel(R) WiFiLink 5100… {78.64.118.150, fe80::a… 00:22:FA:D9:E1:50