Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Agreed! I'm sure Pulseway does some great development behind the scenes, but the current ways to let us know simply aren't working. You should consider regular updates along a predefined schedule, like publishing updates on day X once a month or on day X once every quarter, and then map a forum thread or webpage to it so we can get a better idea of what is coming and when.
  2. @Jamie Taylor - I can't see this change in our environment! We're using Pulseway OnPrem (8.7.3 build 709 release 307) and my experience is that OnPrem customers always have to wait several months (not weeks) for new updates. We still haven't benefitted from the 8.7.4 update that was published in july, and this is NOT a first time occurence. You guys need to improve the update workflow significantly, otherwise we'll have to move to another RMM provider. The development time frame for requested features in itself is extremely slow, and then having to wait even longer for the update to be applied is frankly ridiculous.
  3. I created a feature request on the featureupvote-page.. Hopefully it will get some traction and eventually an approval to start the development.. https://pulseway.featureupvote.com/suggestions/127787/send-messages-to-multiple-groups The issue with the idea Chris suggested is that the messages will be written ad-hoc and will not always be the same, so you'd have to modify the script and save it whenever you want to send a new message. That's why composing a message and then select which group/s to send it to inside the webGUI would be way easier. There's also no indication that the messages comes from Pulseway/IT-admin unless it's written explicitly within the message when using the msg method.
  4. Great stuff @Mark G38! I would've found the Client Portal a lot more useful if: 1 - The user was able to access it by right clicking the Pulseway-icon in the taskbar, rather than the current setup where we have to pre register accounts for that purpose and then give them permission to access the client portal through a browser. That's a lot of extra unnecessary steps and most certainly something that ordinary users doesn't want to get acquainted with. 2 - The newly added chat functionality is a great idea, but it does also require pre registration for those who want to use it. It's an administrative nightmare to add them separately, and as previously stated users will probably not see the benefits.
  5. I'm echoing Kyle's question, as I'm also curious about documentation for this..
  6. I just noticed this myself.. I assume they are listed as "others" in the pie chart at the top, but they are not shown in the list. EDIT: This applies to regular "Asset"-reports as well, and presumably others too.
  7. I have configured Email-notifications in our environment, and we receive notifications like these (see picture below) when we exceed the license limit. EDIT: Configured via Pulseway -> Server Admin -> Settings -> Email -> Server settings
  8. Hey guys! In case you're not already aware, I wanted to share a little trick that was recently added in Pulseway.. You can assign Site Key Codes to agent groups and let Pulseway automatically install Webroot on all clients that are added to that specific agent group. It has been working flawlessly for me and I don't have to copy/paste or worry about Webroot missing on any workstation or server. I also agree that fetching the key-codes from Webroot and show them (or at least show the webroot group name) in a drop down-menu would make it even easier to manage!
  9. I noticed last week that they recently added a "Request feature"-button on the What's new tab in Pulseway.. It seems to be a voting-system where customers can upvote features they want/need, add comments and the Pulseway staff can also add different tags depending on development status etc.
  10. I have installed a probe on a couple of computers+servers in our environment, and they only find clients within the same subnet. I'm able to ping devices in other subnets and access them with SMB-shares etc, but they are not found with a single probe.
  11. It's available in version 8.4.0 now! I had to open Pulseway preferences on the machine and go into System -> Remote Control and enable it first. It's also necessary give the PulsewayAgent three different permissions within the security and integrity section of the system settings. I've tried it a few times and it seems to be working fine. The screen updates seems a bit sluggish but that might be because the machine is on wifi, and it's also in beta which may explain things. I love the fact that we are also able to transfer files back and forth. @Paul - Do you have any news to share if the enable remote control process on Mac will become easier further down the road? I'm more specifically thinking about enabling remote control on the agent using policies from the webGUI. Thanks, and well done implementing this!
  12. This may not be entirely related, but I'd like the possibility to insert hostname in the email-notification that can be sent in an automation workflow.. Currently there is no easy way of knowing which computer the workflow was triggered on, except scrolling through the workflow history which might be a tedious task. I guess this could be achieved if we were able to insert custom fields like %pulseway.hostname% or whatever.
  13. If you expect an email- or push notification to be sent whenever the monitored process or service is stopped, then you also need to enable notifications on your Pulseway user account before they will be sent. Login to Pulseway and open Account -> Notifications and make sure that you have enabled the corresponding notification level on either the organization or it's sub sites / groups. Also make sure either/or Email and Push are enabled at the top of that screen.
  14. I don't know why they set it up this way, but you need to enable the corresponding notification in order for the workflows to be triggered. I had the same issue with a workflow that was supposed to trigger when a system is back online, and I had to enable the policy setting: "Send a notification when the computer is offline" in order for it to work. I would imagine that you also need to enable "Send a notification when a user logs in with priority x" in order for your second workflow to work properly. Honestly, I think this implementation is stupid.. I like the idea of having workflows, but I hate the fact that we need to enable notifications because it also means that they will be sent via email if you have that setup in your environment. In my particular case, you can't adjust the notification priority so an email will be sent each time the system goes offline or online (quite frankly, I don't care, but the workflow task does in order to function).
  15. I'm distributing all of our printers via GPO instead.. That's been working flawlessly, so I don't see the needs of using PowerShell.
  • Create New...