Happy New Year! What better way to start the new year out than by setting some goals and what better goal to set than to learn PowerShell this year.
Let’s start out at ground zero by learning how to launch PowerShell. On Windows 8 or 8.1, simply start typing the word PowerShell on the Metro interface screen:
Maybe you’re still running Windows 7? If so, the shortcuts for PowerShell are located in the start menu under All Programs > Accessories > Windows PowerShell:
Notice in the previous example that there are four different shortcuts for Windows PowerShell. This is because the computer is running a 64bit operating system. The shortcuts with the (x86) suffix are for the 32bit versions of PowerShell. For now, forget that those exist and stick to the shortcuts without the (x86) suffix unless you have a specific reason for using the 32bit versions.
Windows PowerShell shortcut will launch the PowerShell console and that’s what I’ll be
demonstrating during my next few blog articles. The
Windows PowerShell ISE shortcut will launch
the PowerShell Integrated Scripting Environment.
Go ahead and launch PowerShell and you should have a PowerShell console window that looks similar to this one:
Note that the title bar in the previous example says
Windows PowerShell. This means that the
PowerShell console is not running as an administrator. This can create problems where you’ll receive
errors when attempting to run commands that need elevated privileges such as trying to stop a
service. Most programs prompt the user with a UAC (User Access Control) prompt but PowerShell is
unable to participate in UAC.
It’s because of this that I recommend running PowerShell as an administrator by right clicking on
the PowerShell shortcut and selecting
Run as Administrator when launching the PowerShell console:
Notice the title bar now says
Administrator: Windows PowerShell. Keep in mind that you should be
running PowerShell as a local admin that is a domain user if your computer is a member of an Active
Directory domain (definitely not as a domain admin and not as a user in your domain that has