Traditionally administrators have used tools such as Windows Task Manager to determine the current
status of each active process. By default from Task Manager you can view the process name, the user
context under which it is running, the percentage of total CPU utilization, and the memory being used
by the process. This is all useful information to an administrator investigating certain issues like
performance or unexpected behavior.
Windows PowerShell makes it possible to investigate these issues through the Get-Process cmdlet.
Using Get-Process you can collect detailed information about any processes running on an Exchange
Server 2007 computer. For example, to see the current state for the store.exe process, the following
command is used:
[PS] C:\ > get-process store
Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName
------- ------ ----- ----- ----- ------ -- -----------
1098 207 101504 40132 371 6.02 1764 store
The default output for Get-Process displays the current number of Handles opened by the process, the
Non - Paged Memory (NPM(K)) used by the process in kilobytes, the Paged memory (PM(K)) used by
the process in kilobytes, the size of the Working Set (WS(K)) in kilobytes, the Virtual Memory (VM(M))
used by the process in megabytes, the CPU(s) time used by the process total in seconds, the Process
Identifier number (ID), and the Process Name.
Pages:
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106