Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Powershell monitor for scheduled tasks that are not in default path

Hey all,

I'm stuck with trying to monitor the status of scheduled tasks that are not in either the root path or /microsoft - something that SAM's native Scheduled Tasks monitor can do, let's say that they are in Task Scheduler Library \fnord

Get-ScheduledTask | where {($_.taskpath -eq '\Fnord\')} works fine on the local server but returns a script error on the SAM component monitor targeted against that server.

A simple get-scheduledtask from the SAM component returns all values from the server, except those in the \fnord path.

Any ideas?

Thanks in advance

Find more posts tagged with

Accepted answers

allanseyberth

Figured it out, I think.

Need to specify -cimsession .

I guess I've been spoiled by how PDQ handles this.

All comments

sturdyerde

If you're using the Windows PowerShell script monitor, do you have it set to run the script locally (using PS Remoting within the script) or on the remote endpoint? What is the error that you are getting?

allanseyberth

No error message per se - but I did another look and found that I was essentially just pulling scheduled tasks from the SW server, not the server that the monitor was pointing too.

ie - the reason why I wasn't getting results is because there was not \fnord taskpath on the Solarwinds server.

I guess the question now is why is SW running the script against the SW server and not the server that the monitor has been assigned to.

Remote PS is enabled via trustedhosts.

allanseyberth

Figured it out, I think.

Need to specify -cimsession .

I guess I've been spoiled by how PDQ handles this.