{"id":682,"date":"2008-09-29T02:00:55","date_gmt":"2008-09-29T10:00:55","guid":{"rendered":"http:\/\/www.sapien.com\/blog\/2008\/09\/29\/managing-services-with-powershell-and-adsi\/"},"modified":"2008-09-29T02:00:55","modified_gmt":"2008-09-29T10:00:55","slug":"managing-services-with-powershell-and-adsi","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2008\/09\/29\/managing-services-with-powershell-and-adsi\/","title":{"rendered":"Managing Services with PowerShell and ADSI"},"content":{"rendered":"

In PowerShell v1.0, if you want to manage services on a remote computer, you likely used WMI and the Get-WMIObject<\/strong> cmdlet. But there is another solution using ADSI. If you use the WinNT provider, you can access all of the services on a remote machine in much the same way you would manage local users and groups. Let me show you.<\/p>\n

First, connect to the remote computer and specify the service:<\/p>\n

PS C:\\> [ADSI]$svc=”WinNT:\/\/godot\/spooler,service”<\/font><\/p>\n

The $svc object now represents the spooler service on the computer GODOT. There isn’t really valid way to specify alternate credentials. However, if you have an existing secure channel to the remote computer ADSI will use it. In this situation GODOT is a stand alone machine. I mapped a drive to the C$ share using GODOT credentials. My ADSI object will use this connection. <\/p>\n

Pipe the object to Select-Object<\/strong> to see all of its properties:<\/p>\n

PS C:\\> $svc | select *
<\/font> <\/p>\n

Path               : {C:\\WINDOWS\\system32\\spoolsv.exe}
LoadOrderGroup     : {SpoolerGroup}
Dependencies       : {RPCSS}
ServiceAccountName : {LocalSystem}
DisplayName        : {Print Spooler}
ServiceType        : {272}
StartType          : {2}
ErrorControl       : {1}
Name               : {spooler}
AuthenticationType : Secure
Children           : {}
Guid               : {C3968E50-4C66-11CF-A995-00AA006BC149}
ObjectSecurity     :
NativeGuid         : {C3968E50-4C66-11CF-A995-00AA006BC149}
NativeObject       : System.__ComObject
Parent             : WinNT:\/\/WORKGROUP\/godot
Password           :
Properties         : {Path, LoadOrderGroup, Dependencies, ServiceAccountName…}
SchemaClassName    : Service
SchemaEntry        : System.DirectoryServices.DirectoryEntry
UsePropertyCache   : True
Username           :
Options            :
Site               :
Container          :<\/font> <\/p>\n

You might get some error messages about reading object security and the password but that’s ok. Unfortunately one thing you don’t see is the Status property, but its there if you know it exists:<\/p>\n

PS C:\\> $svc.status
4<\/font><\/p>\n

A value of 4 indicates the service is running. A value of 1 indicates stopped. You also won’t see this property if you pipe the object to Get-Member<\/strong>. In fact you won’t see much. But there are methods you can use to stop and start the service.<\/p>\n

PS C:\\> $svc.stop()
PS C:\\> $svc.status
1
PS C:\\> $svc.start()
PS C:\\> $svc.status
4
PS C:\\><\/font> <\/p>\n

Pretty easy if you ask me.
There are a few other values you may want help in decoding. First is the StartType. The integer value can be decoded with a function like this:<\/p>\n

function Decode-StartType {
    Param([int]$startType) <\/font> <\/p>\n

    Switch ($startType) {
        0    {“Boot”}
        1    {“System”}
        2    {“Automatic”}
        3    {“Manual”}
        4    {“Disabled”}
       default    {“Unknown”}
    }
}<\/font> <\/p>\n

You can do something similar with the ServiceType:<\/p>\n

Function Decode-ServiceType {
    Param([int]$ServiceType)
    Switch ($ServiceType ) {
      1     {“Kernel-Mode Driver”}
      2     {“File System Driver”}
      4     {“Adapter Arguments”}
      8     {“File System Driver Service”}
      16    {“Own Process”}
      32    {“Shared Process”}
      272   {“Own Process – Interactive”}
      288   {“Shared Process – Interactive”}
      default   {“Unknown”}
     }
}<\/font> <\/p>\n

Thus you might do something along these lines: <\/p>\n

$svc | select @{name=”Service”;Expression={$_.name.value}},`
@{name=”DisplayName”;Expression={$_.displayname.value}},`
@{name=”Status”;Expression={
    if ($_.status -eq 4) {“Running”}
    elseif ($_.status -eq 1) {“Stopped”}
    else {“Unknown”}
}},`
@{name=”StartType”;Expression={Decode-StartType $_.startType.value}},`
@{name=”ServiceType”;Expression={Decode-ServiceType $_.servicetype.value}},
@{name=”ServiceAccount”;Expression={$_.serviceaccountname.value }}<\/font> <\/p>\n

When executed I get:<\/p>\n

Service        : spooler
DisplayName    : Print Spooler
Status         : Running
StartType      : Automatic
ServiceType    : Own Process – Interactive
ServiceAccount : LocalSystem<\/font> <\/p>\n

I’ll be back tomorrow with more fun on this topic.<\/p>\n","protected":false},"excerpt":{"rendered":"

In PowerShell v1.0, if you want to manage services on a remote computer, you likely used WMI and the Get-WMIObject cmdlet. But there is another solution using ADSI. If you use the WinNT provider, you can access all of the services on a remote machine in much the same way you would manage local users and groups. Let me show you.<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[283,25],"tags":[280,28,57,301,300],"class_list":["post-682","post","type-post","status-publish","format-standard","hentry","category-howto","category-windows-powershell","tag-adsi","tag-powershell","tag-scripting","tag-select-object","tag-service"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/682","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/comments?post=682"}],"version-history":[{"count":0,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/682\/revisions"}],"wp:attachment":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/media?parent=682"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/categories?post=682"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/tags?post=682"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}