How to Start a Windows Service via Alert Action ONLY if the Startup Type is Automatic

It's getting late in the day here, so this will be a quick post....

To get the service start up type try:

$result = Get-Service <Name>

Write-Host $result.StartType

FYI:

$result | Get-Member      --- will show you all the other options available

If I get time tomorrow, I will try wrapping this into a PowerShell SWIS script.

Well yeah, I know how to use all that stuff.  My question isn't about that.  My question is if there is a way to use the Credential object for that component to pass to the Get-Service cmdlet, or, if not, then is there a way to call their program that drives the Service Control Manager feature in the Orion Web Console and get the Startup Type value from it, since that program gets the Startup Type.  How to actually write the script as it relates to using Get-Service and starting/stopping services I'm completely fine with, it's just the credential issue I'm trying to overcome.

Yup you're right, identifying the IDs isn't too hard, but I cannot see any way extracting the credentials and re-using them.

Possibly there is some way to extract to the password to New-Object System.Security.SecureString, tdanner is the man, if anyone knows.

Though I am scratching my head about a local script (on the managed device), invoked remotely from the Orion alert action, if you can send the Service Name sent as a parameter.

The script could check the startup configuration with ease.

Invoke-Command -ComputerName ${N=SwisEntity;M=Caption} -ArgumentList <Service Name> -FilePath C:\Scripts\RestartService.ps1

The script can check for start up type and would then inherit the node's credentials.

But at this hour of the evening, I can't work out how to pass the Service Name back as a variable...

Invoke-Command relies on PS Remoting though, doesn't it?  We don't have that setup on any of our Windows servers (except for the AppInsight for IIS/Exchange boxes of course).  It looks like the Password in the SQL table CredentialSettings uses RSA encryption via their Self-Signed certificate, so I'm wondering if I can use the certificate and the Convert SecureString cmdlets to decrypt it and create a Credential object out of it.  If not then I'll just have to break down and setup a little credential library of my own and call it based on what cred the node uses. 

I don't think SAM will be able to help you here other than through component monitors. The monitoring credentials are encrypted in the database and not exposed through the API. SAM's Service Control Manager feature lacks an API.

So my idea of using the certificate to decrypt the password won't work you think?

You are welcome to try it, but I can't really endorse that.

Oh, yeah, good point...   Sorry about that.

I'm thinking that it probably won't work anyways, but I figured I'd give it a shot.  I guess I'll not reply whether it worked or not as either confirming or denying that isn't a good idea.

Thanks for replying anyways.

I know a few feature requests already exist for Credential management support in the API, so I hope that becomes a thing.  I see that there is Service Control support in the API, I think it would be nice though if we could also tap into the Service Info that the real time service manager gets as well.  Or, even better, if the Windows Service Monitor component just gathered some additional data like the Startup Type as well as the extended Service State info that WMI gets.