Search the Community

I would really like to see an outlook add-in that can be pushed through office 365 to all users that would allow them to submit tickets with drop down menus for ticket type, sub-type, priority and description.

TL;DR: Align timezones across reporting and web interface. Request: When raised during our trial to engineering, the feedback is that browser displays local time, and reports are generated using UTC. The misalignment is visible in my example shown where a report shows a system was back online at 05:32:07, but it actually and factually came back online at 06:32:07. Suggest either including "UTC" in the report, or allowing time zones to be configured globally or per site. Also noticed, that the "Generated at 04 Sep 2020 01:20" footer on the report is 6 hours behind GMT (report generated 07:20am GMT), so this could also do with being aligned accordingly.

I like automation and workflows but it has one big drawback. It can only run PW scrips or linux bash scripts. we cannot fire off any pulseway RMM internal functions. for example. Lets say when a computer checks in i want to launch a 3rd party Patch Management policy. Right now i can only do this on a timer or manually or set the policy for if missed, i can not make this part of a workflow. another thing i can't seem to do is have a workflow repeat. For example. i have a workflow that says when a computer registers it checkes and installs updates. Oviously for windows this needs to be done more than 1 time. I cannot find a way to have it check and then recheck until all windows updates are installed (maybe this is possible and i just dont know how)

Not that I am opposed to blue, but it would be nice feature to change the theme colors on the webapp. This may also help those that need a more high contrast display as well.

We use Puleway Webapp (RMM) and PSA. I have to setup to different logins (PSA is on SAML) for access. Is there any plans to allow us to link and integrate these two logins?

The ability to just pull your phone out and run a Ansible playbook would be amazing. Maybe even get run status or just the output of whatever playbook was run. This would add a crazy amount of flexibility to Pulseway.

Hi there, This might be a bit of a long shot - but I have an end client who's interested in deploying custom Teams issues with Pulseway (as there aren't many users in-office for obvious reasons). I've attempted to deploy this by pushing a batch script, to copy the backgrounds from a shared location. The backgrounds folder in question is located in the user's roaming appdata (%appdata%\Microsoft\Teams\Backgrounds\Uploads). For this reason I wasn't able to use %username% correctly in my batch script, as the script is being run by some Pulseway service, rather than as the local user account. Please let me know if you've any ideas and have a great day. Cheers, Joe

Would it be possible to add the current logged in user for each pc to the header info that shows in the middle panel. We manage several hundred pcs and the computer name of ASSET-1234 does not tell us whos using it at that time. Most end users do not know their computer names. So trying to find the computer a user is on is sometimes difficult. Having this info at hand in the search list would help that a lot. i am only thinking this information for workstations, servers could potentially have multiple users logged in at the same time and this information would not be as useful (not to mention not enough space) I have included a mockup of one way this could be done. Also adding the ability to search for a current logged in user would be helpful.

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.

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

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.

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.

Hi. If it is possible I would like to exclude full automation scripts from the diagnostics log "trace.log". In normal situations it is fine with just an indication of the execution with the script name. I guess you could add one more checkbox like "Include full Automation Scripts" in settings, and let it be disabled as default. Best Regards, Martin.

I was getting the policies configured for my new setup and I noticed that Patch Management only allows you to select categories of patches and just decide to install them as a whole or not. Unless I'm missing something, there's no ability to approve or deny patches on an individual level. This is a somewhat vital part of any RMM suite as we may often need to decline individual patches that are known to be causing issues (a common problem with Windows 10 these days.) I'd say this is something vital for Pulseway to get implemented as I've worked with a number of RMMs over the years and it's the first one I've seen that doesn't offer this.

Remote Control really needs the ability to both trigger a reboot and to automatically reconnect when the system you're connected to completes the restart. Having it immediately disconnect when a reboot is triggered (usually if it's running as a service, it should be able to hold the session open for things like the first phase of installing Windows updates) and having to manually try over and over again to see if the machine has completed its reboot is really frustrating when you're trying to solve an issue remotely that requires a lot of reboots or even when you're just trying to do a number of updates to a system.

I just signed up for Pulseway to monitor a small client of my side business. I am in the process of setting up patch management for workstations. I would like the systems to prompt the end users to reboot upon installing updates but Pulseway seems to be very restrictive in how it lets you set that up. It looks like all I can do is have it reboot immediately or give the users a 5 minute warning with a generic message. I work with a competitor product at my day job and it allows us to specify whatever message we want, set whatever timer amount we want and allow the users to defer the updates as many times as we want or force a reboot after a certain number of deferments. It does not appear Pulseway provides any of this customizability. It would be very nice to have these options so I can have choices other than forcing end users to reboot during the day or having systems that potentially go days without a reboot after installation. Thanks!

After playing around in my trial account for a bit, I have a few suggestions regarding policy configuration. Allow the creation of policies that inherit settings from other policies and track which settings were overridden. This would allow MSPs to create one or two "Global" policies (Servers/Workstations) as a base, and then create individual policies (for each client) that inherit settings from those global policies. Allow overrides to policy settings on specific systems, track which systems have policy overrides in place, and allow reverting the overrides to the policy defaults. Allow attaching scripts/tasks to policies to run during on-boarding (as in, when the Pulseway agent is initially installed). Instead of having separate Patch Management policies, group those settings with the System policies so they can be applied all at once. Alternatively, allow attaching Patch Management policies to System policies.

Would it be possible to expand the number of API endpoints available for the RMM? While the API is useful for gathering information about systems, it doesn't have much in the way of being able to perform many built-in operations that exist in the web application, like check for and install patches, run single line commands on the system, being able to run scripts on a system and not just tasks, add tags to systems, etc. This would be great for creating custom automation and would help with removing a lot of tedium in cleaning up small alerts.

Hi, i´m testing this RMM atm. Is it possible to implement WOL on a Probe? For example choosing the probe then the Machines Show up which are on the same Network or same Customer and Option to do WOL. If you´ve many Machines to Manage You would Need to Edit Firewall Rules for each Machine and Edit the Settings of each machine.Would be way to much work.

I know this would be a major change in the reporting interface, but how about an option to interact with the results of a report. Maybe one can choose an additional "Report Format" when editing a report and have an option for Interactive? When this is enabled the output of the report is immediately displayed in web format with hyperlinks to automate certain tasks by sending a back-end task/script to the agent. For example: Report Interaction Script Task (Relayed to the agent) Applications link next to each agent to uninstall the application Assets link to create asset tag if none exist OS Patching link to assign Policy / Update now 3rd Party Patching link next to each agent to update the application Drive Usage link to run a temp files cleanup job Anti-virus install AV / Run Scan / Update (not sure how this ties in to the existing Kaspersky deployment) ...

Afternoon It would be great if we could make Asset Info available when devices are offline. For example if a remote users PC fails to function and is still under warranty trying to explain to a user where to find the device Make, Model and serial number to log a warranty case is not always easy. If the asset information was available when the device was off line then it would make this process mach easier as it contains all the information required Cheers peter Example DAVID-O-MIIX Windows 10 Pro Offline Offline since 11 minutes ago Asset Info System DAVID-0-MIIX Name LENOVO Manufacturer 20M3 Model x64-based PC Type Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz CPU 1 Number of Processors 8 Number of Logical Processors DAVID-O-MIIX DNS Host Name TEST.local Domain Administrator Owner Name LM_Workstation, LM_Server, NT, Potential_Browser Roles OK Status BIOS YD05UDx7 Serial Number 6NCN33WW Name LENOVO Manufacturer 6NCN33WW SMBIOS Version 3 SMBIOS Major Version 0 SMBIOS Minor Version LENOVO - 1 Version Monday, 12 November 2018 1:00 PM Release Date OK Status 6NCN33WW Description Operating System Windows 10 Pro Name 10.0.17763.0 Version Multiprocessor Free Build Type systemadmin Registered User NF6EE-QH89W-F8WST-WWXZ4-WFG6P Product Key 00330-50000-00000-AAOEM Serial Number 0 Service Pack Major Version 0 Service Pack Minor Version \Device\HarddiskVolume3 System Device C:\WINDOWS\system32 System Directory C:\WINDOWS Windows Directory Monday, 11 March 2019 12:40 PM Install Date Monday, 20 May 2019 4:30 PM Local Date and Time Monday, 20 May 2019 8:10 AM Last Boot Up Time test\anton.rider Last Logged On User

Hello, I would like a feature where when I remote into a users computer, you are given the option to block the user from inputting any information and or block them from viewing what you are doing.

Just an FYI - their API docs are linked below. They just did a major overhaul or the web interface and agent. https://apidocs.symantec.com/home/SEPC Thanks!

Pulseway Dashboard (Currently 6.3) Data - All Notifications. Currently we can not: Ctrl + Select, Shift + Select All, Ctrl + A, Sort by columns. This is a daily task for me and so it would be fantastic to be able to use these simple functions.

Hello, I would love to see a rule added to the patching policy where you could filter patches by date. For example, only install patches that were released before a certain date. This would allow you pick a date that you were going to role out to your different environments and make sure you were installing the same patches on all systems (Dev, Test, Prod, etc) even if patches were released during the time you were moving from dev to prod for example.