Download PowerShell - Microsoft's New Command Shell
Get your copy of PowerShell
One of my themes with Windows PowerShell is that nothing is too simple. Therefore, let me start by checking that you have downloaded and installed the correct
PowerShell files. If indeed, you have PowerShell installed and functioning correctly then go to my 'Execute Commands' page.
PowerShell Downloads
It breaks my heart to send
you away from my site, but it is essential that you get a copy of PowerShell and .NET Framework from Microsoft's own site.
PowerShell itself Key point, you need to download an operating specific version of PowerShell. In
the winter of 2008, look out for version 2.0 of PowerShell. For now, Microsoft will provide you with slightly different version of PowerShell 1.0 RTW (Release to Web) for:
Vista
Windows Server 2003
XP
For Windows Server 2008, there is an easier technique: install PowerShell by launching the 'Add a Feature' option in Server Manager.
.NET Framework PowerShell is an
object based scripting language, consequently, it needs .NET Framework for the definitions of the Windows objects. PowerShell works fine with either .Net Framework v 2.0, or v 3.0.
Here are the three stages before you get up and running with PowerShell:
Obtain, then install .Net Framework 2.0
Get a copy of PowerShell, for example v1.0 (2.0 in 2008)
Start, Run, PowerShell.
Once you have installed PowerShell (and .Net), try this simple command: $Host
Here opposite is a screen shot of what you should see: Version 1.x.x.x
As usual, there are two ways of doing
everything, you could try. get-Host
Guy Recommends: SolarWinds Engineer's Toolset v10
The Engineer's Toolset v10 provides a
comprehensive console of utilities for troubleshooting computer problems. Guy says
it helps me monitor what's occurring on the network, and the tools
teaches me more about how the system literally operates.
There are so many good gadgets, it's like having free rein of a
sweetshop. Thankfully the utilities are displayed logically: monitoring, discovery, diagnostic, and Cisco tools.
Download your copy of the Engineer's Toolset v 10
The Situation with PowerShell and the Operating System
Previous scripting programs came 'built-in' to the operating system. DOS
has its cmd.exe, while VBScript has cscript.exe as its
scripting engine. As of 2007, no commercial operating system, not even Vista, has PowerShell 'built-in'. Fortunately, installation is one of Microsoft's strengths, thus obtaining both
PowerShell and .Net Framework is an uncomplicated one-off task.
PowerShell Runs on these systems: Windows Server 2003, Windows XP and even Windows Vista, however each has their own version of PowerShell.
Getting Started - PowerShell's Structure
The basic PowerShell command consists of a two-word sentence. Start with a verb follow with a dash and end with a noun. Naturally,
you press carriage return when you have finished the command.
get-Process (Correct).
get - process (Wrong. The dash needs no space).
With time and practice, you will soon increase your
vocabulary. Experiment with nouns such as Eventlog. For example: get-Eventlog -list.
From this example we learn that the dash or minus sign has another role, namely as a modifier or switch, thus
the role of a space, or a lack of a space, becomes more obvious, for example -list tells the command to display all the event logs.
Perhaps the most useful command for beginners is: get-help
followed by the command.
For example:
get-help process or get-help get-Process or better: get-help get-Process -full
Alternatively, you could try plain: help. From this we deduce that the default verb is 'get'. Test this theory by typing just a noun that PowerShell understands:
If you see an error of any kind, do let me know. Please report any factual mistakes, grammatical errors or broken links, I will be happy to not only to correct the fault, but also to give you credit.
*
Guy
Recommends: Orion's NPM - Network Performance Monitor
Orion's performance monitor is designed for detecting network outages.
A network-centric
view make it easy to see what's working, and what needs your attention.
This utility guides you through troubleshooting by indicating whether the
root cause is faulty equipment or resource overload.