[Endpoint details update frequency]

For everyones information, CPU memory, etc are all 12 hour averages.

[PSA support experience poor]

Matt, 

I highly suggest you contact your account rep. We have also had these issues on the RMM side. Your rep may be able to help.

[User accessible scripts via Tray Icon]

Some competitors (datto) offer the ability for users to access scripts/software installs directly from their tray icon. This feature would greatly decrease overhead for things like software installs and common tasks.

[Live powershell/cmd/bash]

Currently the interface allows us to run a script which is great, but it would be more useful to have an interactive interface that allowed us to operate as if we were on the system.

[8.4.0 Changelog]

Server is showing version 8.4.0, but we don't have a change log. What has changed in the newest version?

[Endpoint details update frequency]

In tying pulseway to our PSA we need to know the frequency at which the endpoint communicates with the pulseway server in order to update stats like CPU/Memory Usage/etc. Can this be customized or can they be force updated via script?

 

[Services or Process - is not sending alert]

@Jan C. Nielsen just making sure you were able to figure this out.

[Services or Process - is not sending alert]

Jan,

Is the service monitored on the system you are trying to get a notification from? Open pulseway manager on that system and click the system tab and then services and ensure the service is checked. There is a script that will monitor all automatic services, but that can be quit overwhelming to receive a notification for all of them.

[Workflows not running]

Thanks for that feedback. I was afraid that notifications were the solution. I can't think of any better way to train my technicians not to look at notifications than to overload them with useless ones. We are currently in process of fully integrating the API into our custom front end, so my guess is we will have to turn on all these notifications and then filter what we show our technicians.

Pulseway, if you are reading this, please fix this implementation. We don't need a notification every time someone logs in just to run a workflow that updates the system name with the name of the person logging in. There are countless use cases for workflows that should not be kicked off by a notification.

[Documentation for custom fields]

We have requested this from the support team with 0 response (seems to be a common issue). We need documentation for the custom data. How do we display it, set it, etc. We would like to be able to pull information from the system via script and output to the custom field, but cannot find any documentation on how to do it.

[Workflows not running]

We have workflows set up User log in and systems back online set up. 

If we set it up with no conditions, just a script to run, the workflow never runs. It is enabled, but nothing seems to trigger it. 

We have tried adding conditions, removing and recreating them, all no luck. 

Anyone else having this issue.

[Remote Desktop Multiple Screens]

+1

[Allow api\web post as a workflow step]

Adding the ability to make an API call\web post as a remediation step in workflows would allow for more 3rd party applications to be tied in with the solution. 

[Allow workflow from new ticket creation]

When users submit a ticket, it would be useful to be able to take action based of that ticket item. This would allow simple scripts to be run based on user request input if it matches criteria.

[Allow remote access before login prompt]

In trying to diagnose systems, often we need to be able to connect to a system before the user prompt for login. This allows us to see statuses of updates, rollback errors, etc.

[Remote Control / Compliance for mobile devices]

As part of our contracts, we often support users on their mobile phones\tablets. We have worked with a few remote solutions that offered support of these devices. Ideally we would have screen control, but even screen viewing would be useful.

[Allow chat from Pulseway Remote Control App]

Often, we like to initiate chat before we access a users system. It would be nice to be able to start this chat from the remote control app as it is closely tied with the remote control features.

[Allow users to belong to multiple groups]

Treating user groups more like AD user groups would allow more granularity of access and less duplication of security roles.

[Additional Scope Filtering]

It would be nice to be able to add negative keywords to scopes (i.e. Does not have tag).

We currently use a script to automatically update the system name to include the username, but there are some systems that we want to keep a static name so they are easier to identify. Currently we have to separate these into their own groups in order to keep them statically named. 

[Global software reporting]

After coming from another competitor, one of the major things we are missing is a site wide software list with the ability to list systems with software and remove it from multiple systems.

Ideally, initially it would show all software, but would allow you to filter software by name. At that point you would be able to click in and see installed systems with installed version.