{"id":196,"date":"2021-02-23T16:44:14","date_gmt":"2021-02-24T00:44:14","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/powershell-community\/?p=196"},"modified":"2021-02-27T09:33:11","modified_gmt":"2021-02-27T17:33:11","slug":"using-get-service-in-powershell-7-vs-windows-powershell-5-1","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell-community\/using-get-service-in-powershell-7-vs-windows-powershell-5-1\/","title":{"rendered":"Using Get-Service in PowerShell 7 vs. Windows PowerShell 5.1"},"content":{"rendered":"

Q<\/strong>: How can I get the Username, and StartType for a Windows Service?<\/p>\n

A<\/strong>: Quick answer is PowerShell 7.<\/p>\n

Microsoft is doing a great job on PowerShell with each version they release. The simple answer to this question is a command called Get-Service<\/code>. But there is a big update that makes getting the required information much easier with PowerShell 7. I will show the result of this command using both PowerShell 7<\/strong> and Windows PowerShell 5.1<\/strong>.<\/p>\n

Let’s start by typing the simple command Get-Service Workstation<\/code>. This command return basic details for a service called Workstation<\/strong>. The result is the same for both PowerShell 7 and Windows PowerShell 5.1.<\/p>\n

Status   Name               DisplayName\n------   ----               -----------\nRunning  LanmanWorkstation  Workstation\n<\/code><\/pre>\n
To drill-down and get a more detailed result, we need to see all the associated properties<\/em> and methods<\/em> for this service, which can be achieved using the following command.<\/p>\n
Getting Windows Services using Get-Service<\/h2>\n
Get-Service Workstation | Get-Member | Select-Object Name, MemberType\n<\/code><\/pre>\n
The output returns a list of members that can be invoked in the command line. Here is the output in PowerShell 7.<\/p>\n
Name                         MemberType\n----                         ----------\nName                      AliasProperty\nRequiredServices          AliasProperty\nDisposed                          Event\nClose                            Method\nContinue                         Method\nDispose                          Method\nEquals                           Method\nExecuteCommand                   Method\nGetHashCode                      Method\nGetLifetimeService               Method\nGetType                          Method\nInitializeLifetimeService        Method\nPause                            Method\nRefresh                          Method\nStart                            Method\nStop                             Method\nWaitForStatus                    Method\nBinaryPathName                 Property\nCanPauseAndContinue            Property\nCanShutdown                    Property\nCanStop                        Property\nContainer                      Property\nDelayedAutoStart               Property\nDependentServices              Property\nDescription                    Property\nDisplayName                    Property\nMachineName                    Property\nServiceHandle                  Property\nServiceName                    Property\nServicesDependedOn             Property\nServiceType                    Property\nSite                           Property\nStartType                      Property\nStartupType                    Property\nStatus                         Property\nUserName                       Property\nToString                   ScriptMethod\n<\/code><\/pre>\n
Here is the output in Windows PowerShell 5.1.<\/p>\n
Name                         MemberType\n----                         ----------\nName                      AliasProperty\nRequiredServices          AliasProperty\nDisposed                          Event\nClose                            Method\nContinue                         Method\nCreateObjRef                     Method\nDispose                          Method\nEquals                           Method\nExecuteCommand                   Method\nGetHashCode                      Method\nGetLifetimeService               Method\nGetType                          Method\nInitializeLifetimeService        Method\nPause                            Method\nRefresh                          Method\nStart                            Method\nStop                             Method\nWaitForStatus                    Method\nCanPauseAndContinue            Property\nCanShutdown                    Property\nCanStop                        Property\nContainer                      Property\nDependentServices              Property\nDisplayName                    Property\nMachineName                    Property\nServiceHandle                  Property\nServiceName                    Property\nServicesDependedOn             Property\nServiceType                    Property\nSite                           Property\nStartType                      Property\nStatus                         Property\nToString                   ScriptMethod\n<\/code><\/pre>\n
PowerShell 7<\/h2>\n
The big difference is in the Property<\/strong> members. Now, in PowerShell 7, it’s possible to read some additional properties that were not available in Windows PowerShell 5.1, such as UserName<\/strong>, BinaryPathName<\/strong>, StartType<\/strong>. So let’s see how to read these properties using PowerShell 7.<\/p>\n
PS 7> Get-Service workstation | select  Username,Starttype,BinaryPathName\n<\/code><\/pre>\n
The output is a clear, with all the required results using a native one-liner command.<\/p>\n
UserName                    StartType BinaryPathName\n--------                    --------- --------------\nNT AUTHORITY\\NetworkService Automatic C:\\WINDOWS\\System32\\svchost.exe -k NetworkService -p\n<\/code><\/pre>\n
Windows Powershell 5.1<\/h2>\n
For Windows PowerShell 5.1, the operation is not as simple as in PowerShell. We need to use the Get-CimInstance<\/code> and pass the required WQL query. So, in Windows PowerShell 5.1, run the following command:<\/p>\n
WPS 5.1> Get-CimInstance -Query 'select * from Win32_Service where caption like \"Workstation\"' | select StartName,StartMode,PathName\n<\/code><\/pre>\n
StartName                   StartMode PathName\n---------                   --------- --------\nNT AUTHORITY\\NetworkService Auto      C:WINDOWS\\System32\\svchost.exe -k NetworkService -p\n<\/code><\/pre>\n
In this example, we invoke Get-CimInstance<\/code> with a query to get the service name and then select the required properties, which is a long way and requires you to know extra information related to the original service name and some basic WMI query language.<\/p>\n
Summary<\/h2>\n
More and more to come with PowerShell 7, ease of use, backward compatibility much rich experience. This post shows a small portion of a small change in PowerShell which will help a lot of admin in their day-to-day tasks.<\/p>\n","protected":false},"excerpt":{"rendered":"
Q: How can I get the Username, and StartType for a Windows Service? A: Quick answer is PowerShell 7. Microsoft is doing a great job on PowerShell with each version they release. The simple answer to this question is a command called Get-Service. But there is a big update that makes getting the required information […]<\/p>\n","protected":false},"author":53227,"featured_media":77,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[13],"tags":[],"class_list":["post-196","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-powershell"],"acf":[],"blog_post_summary":"
Q: How can I get the Username, and StartType for a Windows Service? A: Quick answer is PowerShell 7. Microsoft is doing a great job on PowerShell with each version they release. The simple answer to this question is a command called Get-Service. But there is a big update that makes getting the required information […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/posts\/196","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/users\/53227"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/comments?post=196"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/posts\/196\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/media\/77"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/media?parent=196"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/categories?post=196"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell-community\/wp-json\/wp\/v2\/tags?post=196"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}