How you can automate Windows with PowerShell | Get to know Powershell

Get to know Powershell

Exploring the more advanced Windows tools is a great way to commence taking control of your PC. Learn about Taaskmgr, for example, and likely to soon have the ability to detect, and importantly, close down faltering processes that could be slowing down your computer.

Relying on the normal applets presents all types of problems, though. You have to personally launch them each and every time you want to do something. Then you're forced to work all the way through the interface, perhaps getting a same settings and options, over and over again. And even after all this, the applet might not do just what you need.

Fortunately, there is other ways. PowerShell is a powerful scripting vocabulary that permits one to take full control of every factor of your PC. Whether you need to look at running processes, keep an eye on the file system, modification the registry, download data files, analyse webpages, create studies or do just about anything else on the local PC or any other networked system, PowerShell can help you perform the job, as precisely as you need, and as quickly as possible.

Even greater, while it can sometimes be complicated, a person be a programmer to get started learning a few scripting basics. In simple fact, if you work at the Windows command series, even occasionally you can be having out useful tasks in PowerShell with simply a few minute's study.

Command Prompt

To launch PowerShell, type 'powershell' into the Search box, then right-click the Windows PowerShell entry and choose 'Run as administrator'.

As you will see, the PowerShell interface appears and feels almost similar to the standard control line. And in many ways, this is a good thing, because it means you may use all the commands you understand already.

Enter DIR to list the files in a folder, for instance, cls to clear the display, or IPCONFIG to list your network adapters; everything works as you'd expect.

What you are get, though, is innovative orders - or cmdlets (pronounced 'command-lets') in PowerShell-speak - and, fortunately, in which cmdlet to list all. Type get-command and press [Enter] for taking a look.

For now, dismiss the functions and look only at the cmdlets. As you'll see, cmdlets have a clear verb-noun naming structure: Start-Process, Clear-EventLog, Get- ComputerRestorePoint, Restart- Pc, etc. This makes them quite easy to understand however of course, you will often need to know more detail.

Enter Update-Help to download and set up the documentation, then use the Get-Help cmdlet, like this, to determine somewhat more about PowerShell:
Get-Help Start-Process
Get-Help service
Get-Help time

The first line exhibits specific help on Start-Process; the second lists cmdlets with 'service' in the name; and the third just searches the help system for any items containing the word 'clock' - great when you really know what you want to do, but just usually are sure which cmdlet to work with.

Quick inquiries

Enough of the theory; it's time to carry out some real work. Let's begin by using PowerShell to acquire some data on our bodies, like this: Get-Process.

As likely guess from the cmdlet name, this gets a couple of processes at the moment running on your system (just the same as you will see in Activity Manager), and displays their CPU and RAM use, along with some other statistics.

That's already useful, and not something you can do easily in Windows alone, but jooxie is just getting started. Subsequent, enter this:

Get-Process | Where-Object CPU -gt 5

As before, PowerShell is first checking your working processes. The pipeline figure tells PowerShell to that list to the Wherever cmdlet. And this tests through the process list, looking for anything that matches the condition coming from set - it should have used greater than five seconds of COMPUTER time (-gt is better than; -ge is increased than or corresponding to; -lt is less than; -le is no more than or equal to).

Coming from now filtered our original list a little, then, but there's still more to do. The next step is to get into this:

Get-Process | Where-Object CPU -gt 5 | Sort-Object handles -descending

Jooxie is still fetching your going processes and picking away the CPU hogs, but now PowerShell is also sorting the remaining techniques by their number of handles (a measure of how many files, recollection blocks and other items a process has open).

Again, this is merely a good example, so tweak it; form by CPU, say, or ProcessName (the column headers at the top of the Get-Process list will give you an idea of what they are called you can use).

Effective reports

As you may see, there are a lot of ways to customise and filter whatever PowerShell comes back, but there's a trouble: we're still only receiving plain text results. Therefore try this:

Get-Process | Where-Object CPU -gt five | Sort-Object handles -descending | Out-GridView

Now PowerShell doesn't only filter and sort the list; in addition, it displays the results in an interactive grid. You can hide, re-order or perhaps sort columns, and filtering your data in a variety of techniques. And once you're completely happy, any selected rows could be copied to the clip-board, looking forward to employing anywhere else.

This just isn't detrimental to a single range of code and, of course, you can possess as many lines while you need, but discover more. Because PowerShell cmdlets work in such a regular way, you can have this example and recycle it almost immediately. Check out these examples:

Get-Winevent Program | Where-Object LevelDisplayName -eq "Critical" | Out-GridView
Get-Service | Where-Object status -eq "running" | Sort-Object displayname | Out-GridView

The initial gets the contents of the Windows System journal, looks for critical mistakes and displays these inquiries table. The second brings our running services, once again sorting them to fit our needs. And both equally examples could be further modified and customised in various different ways.

Read More: Take Control With Powershell

Tweet