This project has been moved. Please see the new location on GitHub.

Allowing PowerShell to run scripts

To use either the Module or Script flavor, your PowerShell execution policy must be set to "RemoteSigned" or "Unrestricted", as by default, PowerShell will not run unsigned scripts.

To change your execution policy start PowerShell as an elevated user and run one of the following commands

Set-ExecutionPolicy "Unsigned"


Set-ExecutionPolicy "RemoteSigned"

I normally prefer the latter. For more information about setting the execution policy, check this link:

If you choose the "RemoteSigned" option, you'll have to "unblock" the zip file. There is a great article on the "Hey Scripting Guy!" blog about just that:


The star of the show is the "Send-ProwlNotification" function (or script if using the standalone version).

Here is a simple example:
Send-ProwlNotification -ApiKey <40 digit api key> -Description "This is my notification"

This example would send a notification to the device linked to the 40 digit api key specified in the command line above. Many more options are available. For full help, from a PowerShell prompt run:
help Send-ProwlNotification -Full

PowerProwl will look for a $ProwlApkiKey variable defined in the global scope. I set this in my powershell profile, so I can send myself quick alerts like this:

Send-ProwlNotification "This is the notification text"

Starting with PowerProwl v1.2, there are three additional functions, which would be primarily used by service providers:
Test-ProwlApikey - Tests the validity of an API key.
Get-ProwlRegistration - Used by a service provider to get an registration token and URL, used to register users for push notifications.
Get-ProwlApiKey - Retrieves the API key of an end user once they have validated the URL returned by Get-ProwlRegistration.

Last edited Sep 6, 2016 at 1:48 AM by amcfarland, version 7


No comments yet.