PowerShell for Windows Admins


January 17, 2014  1:25 PM

Win32_Process examples–running scripts

Richard Siddaway Richard Siddaway Profile: Richard Siddaway

Back in the day when all we had was VBScript you could run scripts through the command line (cscript) or you would get a more graphical interface (wscript).  One of the examples at http://msdn.microsoft.com/en-us/library/aa394599(v=vs.85).aspx shows how to detect running scripts.

I don’t imagine much call for that technique but if you need it – here it is:

Get-CimInstance -ClassName Win32_Process -Filter “Name = ‘cscript.exe’ OR Name = ‘wscript.exe’” | Format-Table Name, Commandline

You could use a variation to test the command line input to other processes if you need to

January 17, 2014  11:45 AM

Winter Scripting Games 2014–tips

Richard Siddaway Richard Siddaway Profile: Richard Siddaway

Event 1 is available for download in just over 6 hours

In the mean time head over to powershell.org and look at the fantastic set of tips that the coaches are putting out


January 17, 2014  8:38 AM

Kindle app for Windows 8

Richard Siddaway Richard Siddaway Profile: Richard Siddaway

I’ve written unfavourably on the Kindle app in the past but I stumbled on an piece of functionality in the app that makes me take a lot of my comments back – search.

If you are in the Kindle app and bring up the charms you can get into search. This means you can search for books within your cloud store – this is especially useful fro me when I have hundreds of books most of which aren’t downloaded onto my Windows device at any one time.


January 17, 2014  3:36 AM

Win32_Process examples

Richard Siddaway Richard Siddaway Profile: Richard Siddaway

In case you were wondering where the examples came that inspired the code in this series from its here – http://msdn.microsoft.com/en-us/library/aa394599(v=vs.85).aspx

I’m providing PowerShell examples

In some cases it would be easier to use the *Process cmdlets but I want to demonstrate how to use the WMI class


January 16, 2014  1:58 PM

Win32_Process examples–terminate process

Richard Siddaway Richard Siddaway Profile: Richard Siddaway

Terminating a running process is simply a case of calling the Terminate method:

function remove-proc{

[CmdletBinding()]

param (

[string]$computername = $env:COMPUTERNAME,

[string]$processname

)

Get-CimInstance -ClassName Win32_Process -ComputerName $computername -Filter “Name = ‘$processname’” |

Invoke-CimMethod -MethodName Terminate

}

This will terminate all instances of a given process.  If you want to be more selective then change the function to use the process id rather than the process name


January 16, 2014  1:41 PM

Win32_Process examples–set priority

Richard Siddaway Richard Siddaway Profile: Richard Siddaway

Changing the priority of a process can give a processing boost to an application – but its not always a safe option.

You can modify the process like this:

function set-procpriority {
[CmdletBinding()]
param (
[string]$computername = $env:COMPUTERNAME,
[string]$processname,

[ValidateSet("Idle", "BelowNormal", "Normal", "AboveNormal", "HighPriority", "RealTime")]
[string]$priority
)

switch ($priority){
“Idle”         {[uint32]$priorityin =    64; break}
“BelowNormal”  {[uint32]$priorityin = 16384; break}
“Normal”       {[uint32]$priorityin =    32; break}
“AboveNormal”  {[uint32]$priorityin = 32768; break}
“HighPriority” {[uint32]$priorityin =   128; break}
“RealTime”     {[uint32]$priorityin =   256; break}
}

Get-CimInstance -ClassName Win32_Process -ComputerName $computername -Filter “Name = ‘$processname’” |
Invoke-CimMethod -MethodName SetPriority -Arguments @{Priority = $priorityin}
}

The advanced takes three parameters – computername (defaults to local machine), a process name and the priority that process should have.

A switch statement converts the priority name to an unsigned integer value

The process objects are retrieved by Get-CimInstance and Invoke-CimMethod is used to call the SetPriority method.

You can use it like this:

£> notepad

£> get-process notepad | Format-List Name, PriorityClass

Name          : notepad
PriorityClass : Normal

£> set-procpriority -processname ‘notepad.exe’ -priority HighPriority

ReturnValue PSComputerName
———– ————–
0 RSSURFACEPRO2

£> get-process notepad | Format-List Name, PriorityClass

Name          : notepad
PriorityClass : High

The function will modify the priority of all instances of the process. If you want to modify just one instance then you need to remove the process name parameter and add a process id parameter


January 15, 2014  4:31 PM

Winter Scripting Games 2014 –Event 1

Richard Siddaway Richard Siddaway Profile: Richard Siddaway

The first event in the 2014 Winter Scripting Games kicks off in just over 2 days time.

The practice event is finished and we’re testing the judging system

Good luck to all participants


January 15, 2014  2:02 PM

Win32_Process examples: get process owner

Richard Siddaway Richard Siddaway Profile: Richard Siddaway

Moving on with examples of using Win32_Process you can find the process owner:

function get-procowner {
[CmdletBinding()]
param (
[string]$computername = $env:COMPUTERNAME
)

Get-CimInstance -ClassName Win32_Process -ComputerName $computername |
foreach {
$owner = Invoke-CimMethod -InputObject $psitem -MethodName GetOwner

$props = [ordered]@{
Name = $psitem.Name
Domain = $owner.Domain
User = $owner.User
ComputerName = $psitem.PSComputerName

}
New-Object -TypeName PSObject -Property $props
}
}

Use the same param block as before to pass a computername – defaulted to local machine.

For each of the Win32_Process objects get the corresponding owner using the GetOwner method.

Create an ordered hash table for the properties and output a PSObject using those properties


January 14, 2014  12:50 PM

Win32_Process examples–processor time and memory usage

Richard Siddaway Richard Siddaway Profile: Richard Siddaway

I saw some example code for using Win32_Process and didn’t like it so decided to create my own versions.  In this case the objective is to display the processor time and memory usage:

function get-proctimeandRAM {
[CmdletBinding()]
param (
[string]$computername = $env:COMPUTERNAME
)

Get-CimInstance -ClassName Win32_Process -ComputerName $computername |
foreach {
$props = [ordered]@{
Name =  $psitem.Name
ProcessId = $psitem.ProcessId
WorkingSetSize = $psitem.WorkingSetSize
PageFileUsage = $psitem.PageFileUsage
PageFaults = $psitem.PageFaults
ProcessorTime = ($psitem.KernalModeTime + $psitem.UserModeTime) / 10000000
}

New-Object -TypeName PSObject -Property $props
}
}

Start by creating an advanced function that takes a computername as a parameter.  This is used to call Get-CimInstance to access the Win32_Process class on the machine.

I’m switching to the CIM cmdlets for everything as my test environment is, or soon will be, Windows 2012 R2 or Windows 8.1.

For each if the Win32_Process objects create a New-Object. I’ve chosen to use an ordered hash table (PS 3 and above) so that my properties remain in the order I want

The function produces a list by default as there 6 properties on the object. If you want  table output use Format-Table.

Examples of use:

get-proctimeandRAM
get-proctimeandRAM | ft -AutoSize


January 14, 2014  12:24 PM

VM disk info

Richard Siddaway Richard Siddaway Profile: Richard Siddaway

A question came into the forum about getting information on the virtual disks associated with particular Hyper-V virtual machines. Is a bit of a digging exercise but this gets the results:

Get-VM |
foreach {
$VMname = $psitem.Name
Get-VMHardDiskDrive -VMName $VMname  |
foreach {
Get-VHD -Path $_.Path |
select @{N=’VMname’; e={$VMName}}, Path, Size, FileSize
}
}

Get the set of VMs and for each of them get the VMHardDisks associated with the machine. For each VMHardDisk get the VHD – this is where you find the data you need.

 

The size and file size are in bytes – its a simple matter to create calculated fields that divide by 1GB or percentages if you require


Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: