Get-Service

Gets the services running on the specified computers. The default is the local computer.

Type the NetBIOS name, an IP address, or a fully qualified domain name of a remote computer. To specify the local computer, type the computer name, a dot (.), or "localhost".

This parameter does not rely on Windows PowerShell remoting. You can use the ComputerName parameter of Get-Service even if your computer is not configured to run remote commands.

Gets only the services that depend upon the specified service.

By default, Get-Service gets all services.

Specifies the display names of services to be retrieved. Wildcards are permitted. By default, Get-Service gets all services on the computer.

Omits the specified services. The value of this parameter qualifies the Name parameter. Enter a name element or pattern, such as "s*". Wildcards are permitted.

Retrieves only the specified services. The value of this parameter qualifies the Name parameter. Enter a name element or pattern, such as "s*". Wildcards are permitted.

Specifies ServiceController objects representing the services to be retrieved. Enter a variable that contains the objects, or type a command or expression that gets the objects. You can also pipe a service object to Get-Service.

Specifies the service names of services to be retrieved. Wildcards are permitted. By default, Get-Service gets all of the services on the computer.

Gets only the services that this service requires.

This parameter gets the value of the ServicesDependedOn property of the service. By default, Get-Service gets all services.

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see  about_CommonParameters (http://go.microsoft.com/fwlink/p/?LinkID=113216).

This command retrieves all of the services on the system. It behaves as though you typed "get-service *". The default display shows the status, service name, and display name of each service.

PS C:\> get-service

This command retrieves services with service names that begin with "WMI" (the acronym for Windows Management Instrumentation).

PS C:\> get-service wmi*

This command displays services with a display name that includes the word

"network". Searching the display name finds network-related services even when the service name does not include "Net", such as xmlprov, the Network Provisioning Service.

PS C:\> get-service -displayname *network*

These commands get only the services with service names that begin with "win", except for the WinRM service.

PS C:\> get-service -name win* -exclude winrm

This command displays only the services that are currently running. It uses the Get-Service cmdlet to get all of the services on the computer. The pipeline operator (|) passes the results to the Where-Object cmdlet, which selects only the services with a Status property that equals "Running".

Status is only one property of service objects. To see all of the properties, type "get-service | get-member".

PS C:\> get-service | where-object {$_.Status -eq "Running"}

This command gets the services on the Server02 remote computer.

Because the ComputerName parameter of Get-Service does not use Windows PowerShell remoting, you can use this parameter even if the computer is not configured for remoting in Windows PowerShell.

PS C:\> get-service -computername Server02

These commands list the services on the computer that have dependent services.

The first command uses the Get-Service cmdlet to get the services on the computer. A pipeline operator (|) sends the services to the Where-Object cmdlet, which selects the services whose DependentServices property is not null.

Another pipeline operator sends the results to the Format-List cmdlet. The command uses its Property parameter to display the name of the service, the name of the dependent services, and a calculated property that displays the number of dependent services that each service has.

PS C:\> get-service | where-object {$_.DependentServices} | format-list -property Name, DependentServices, @{Label="NoOfDependentServices"; Expression={$_.dependentservices.count}}Name                  : AudioEndpointBuilderDependentServices     : {AudioSrv}NoOfDependentServices : 1Name                  : DhcpDependentServices     : {WinHttpAutoProxySvc}NoOfDependentServices : 1...

This command shows that when you sort services in ascending order by the value of their Status property, stopped services appear before running services. This happens because the value of Status is an enumeration, in which "Stopped" has a value of "1", and "Running" has a value of 4.

To list running services first, use the Descending parameter of the Sort-Object cmdlet.

PS C:\>get-service s* | sort-object statusStatus   Name               DisplayName------   ----               -----------Stopped  stisvc             Windows Image Acquisition (WIA)Stopped  SwPrv              MS Software Shadow Copy ProviderStopped  SysmonLog          Performance Logs and AlertsRunning  Spooler            Print SpoolerRunning  srservice          System Restore ServiceRunning  SSDPSRV            SSDP Discovery ServiceRunning  ShellHWDetection   Shell Hardware DetectionRunning  Schedule           Task SchedulerRunning  SCardSvr           Smart CardRunning  SamSs              Security Accounts ManagerRunning  SharedAccess       Windows Firewall/Internet Connectio...Running  SENS               System Event NotificationRunning  seclogon           Secondary LogonPS C:\>get-service s* | sort-object status -descendingStatus   Name               DisplayName------   ----               -----------Running  ShellHWDetection   Shell Hardware DetectionRunning  SharedAccess       Windows Firewall/Internet Connectio...Running  Spooler            Print SpoolerRunning  SSDPSRV            SSDP Discovery ServiceRunning  srservice          System Restore ServiceRunning  SCardSvr           Smart CardRunning  SamSs              Security Accounts ManagerRunning  Schedule           Task SchedulerRunning  SENS               System Event NotificationRunning  seclogon           Secondary LogonStopped  SysmonLog          Performance Logs and AlertsStopped  SwPrv              MS Software Shadow Copy ProviderStopped  stisvc             Windows Image Acquisition (WIA)

This command uses the Get-Service cmdlet to run a "Get-Service Winrm" command on two remote computers and the local computer ("localhost").

The Get-Service command runs on the remote computers, and the results are returned to the local computer. A pipeline operator (|) sends the results to the Format-Table cmdlet, which formats the services as a table. The Format-Table command uses the Property parameter to specify the properties displayed in the table, including the MachineName property.

PS C:\> get-service -name winrm -computername localhost, Server01, Server02  | format-table -property MachineName, Status, Name, DisplayName -autoMachineName    Status  Name  DisplayName------------   ------  ----  -----------localhost      Running WinRM Windows Remote Management (WS-Management)Server01       Running WinRM Windows Remote Management (WS-Management)Server02       Running WinRM Windows Remote Management (WS-Management)

This command gets the services that the WinRM service requires.

The command returns the value of the ServicesDependedOn property of the service.

PS C:\> get-service winrm -requiredServices

This command gets the WinRM service on the local computer. This example shows that you can pipe a service name string (enclosed in quotation marks) to Get-Service.

PS C:\> "winrm" | get-service