I have cobbled together a PowerShell script that lists all alerts created since the previous run of the script and sends a summary of these off to the disinterested parties in the operations group. The script works perfectly when run in the SCOM shell but gets annoyed when run as a scheduled task using normal PowerShell. I have included the SCOM snap-ins via
 
Add-PSSnapin Microsoft.EnterpriseManagement.OperationsManager.Client

The problem I am currently having is that the Get-Alert cmdlet is complaining that the path is not set:
 
Get-Alert : The 'Path' parameter is empty or the required provider location is not set.

I have searched for clues about what should be entered in the path parameter as well as trying various semi-random text to no avail.

Any pointers and advice would be most welcomed.

It all depends on your environment. This may help:
http://technet.microsoft.com/en-ca/magazine/2008.08.scom.aspx

Doing the add-snapin you outlined is not sufficient to recreate the environment you need to do OpsMgr tasks, but that article should help.

Be sure to check out www.systemcentercentral.com and the forums and scripts there.

Thank you for your fast and very effective response, Marco.
 
Just in case someone else is looking for a similar issue here is what made me go away happy  In searching through the SystemCenterCentral.com site I found this blog titled How to use the Powershell to get access to the SDK that discusses how to set the entire Operations Manager environment in ‘regular’ PowerShell. All the best!