AC_Martin_J

I'm using the android app to remote control devices from a Chromebook, but it's far from ideal.. 
I've noticed that it bypasses the MFA-login for instance, and the actual remote session is a bit difficult to use (you have to use two fingers on the touchpad in order to control a remote cursor). 

These are issues I was looking forward to see resolved with a web based remote control solution, but that doesn't seem to be in development. At least not for the time being.
 
Here's a feature request I did about the web based solution: https://pulseway.featureupvote.com/suggestions/170678/web-based-remote-control

Is there a way to make Pulseway agent update automatically on mac instead of asking the user to Install and Relaunch?

Good update, but again weak delivery. The Dashboard Policy and the Local Policy is confusing and not trustful. Why, because you can never tell which policy takes priority. For example, you can setup in the Dashboard Policy that hard drive will notify you if the spaces goes below 25%, but when you go to the EndPoint directly you don't see this applied you only see what you manually applied. So you don't know which policy the endpoint is following, the dashboard or the local policy.
Again I've been with Pulseway for years and I've been telling them about this. What is the purpose of creating a Template Policy to be manage on the Dashboard if you can still alter the same policy locally, and the only solution they could come up with was a 'check mark", "hyphen" and "empty box" that should tell you if is dashboard or local or disabled, very brilliant. But useless because right now I cleared the box for Ping Performance so it can clear on every server but when I go back to the Dashboard I see the hyphen, which means servers are overwriting dashboard.
Solution, make the Dashboard overwrite the local settings and on the endpoint made those sections grey out or maybe with a message "these settings are managed by the administrator" or something like that.

Yea no problem.  If you go into Onboarding - Downloads - And then select your Windows download, you can make one for each customer, or if it's just for your internal machines (if that's what you use Pulseway for) then you just make the one, and you just do "Copy Link" and throw that link into your PowerShell script, call the URL to download the file, and then run it. It's an MSI so you can do silent install and it will fully register with Pulseway. 

I do not have the exact steps, and it's been awhile since I've actually done much inside Intune, but I do know using Intune, you can push scripts to systems.  Pulseway can definitely be scripted using PowerShell, so there should be no reason you can't push Pulseway to the machine once it's inside Intune.  I've pushed other RMMs in the past, such as Datto RMM via Intune.  

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.

Curious if we can be provided a bit more detailed road map.  It would be nice if when ideas from the Feature Requests page get approved, that we can an idea of the timeline until we see that feature.  For example, all the ones in my below screenshot marked "In Development" have been in that status for months.  When you look at the Roadmap thread, it doesn't show any of these specific items in there.  It would be nice to see an estimate on when we can expect some of these features to be released.

 
 
 

Hi there! 
 
I often find myself running scripts on our machines in a way that demands follow up/verification, so I thought it would be a good thing to be able to add scripts to a queue in Pulseway to have them run at a later point in time when a system becomes available online. Currently I tend to keep a document with all the machines listed, so I can mark them one by one in order to know which ones are done, and which ones remain. This is kinda tedious because our machines (especially laptops) tend to be offline for longer periods of time, and I have to follow up on a daily basis until the script ran successfully on all of them. 
 
I know about automation tasks in Pulseway and the possibility to schedule scripts to run daily, weekly etc. But they will continue to run on all computers for as long as the task is enabled. I've tried to cope with this by building scripts that won't reapply the software and/or settings if existing data is found. It seems to work, although it's not an optimal solution since the scripts will run tens or hundreds of times on our systems when they only really need to be ran once. 
 
So, what am I suggesting?
The possibility to run one or multiple scripts (either directly or via an automation task depending on what the Pulseway devs prefer) With an option to run once. With an option to include offline systems (the script/s will be queued for when they come back online) With an option to send success/failure-reports to the administrator With an option to retry once, twice or three times whenever a script is unsuccessful. (in my case this is useful because Powershell Impersonation doesn't work in home environments when VPN is disabled, so a second attempt may succeed.) A section in Pulseway WebGUI where an administrator can see the deployment progress and success/failure-ratio.  
One of many scenarios: I have a script that will install a scheduled task with some predefined values, and upgrade an MSI-installation to a newer version. I want to make sure that all our computers run the script with a successful output.
 
Please let me know if you find this suggestion useful! 

@AC_Martin_J I completely agree with your points.  Especially being able to right click the tray icon much like "get support" if they could be taken to the client portal. 
Unfortunately, seems as Pulseway wants to use the CP as a means to collect more money which I mean, I get it, everyone has to make their money but perhaps if it was more flexible I could see a cost, but currently it's very limited.  
 

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.

I have an "onboarding" workflow set up that runs when a new machine is registered.   It determines if it's a workstation or server and then runs quite a number of custom scripts I created from installing some default software that I always deploy to my clients, such as additional remote access tool, Endpoint Protection as well as a few other installs.  
It also runs a few scripts that set certain aspects of the machines environment as well as filling in some custom fields I have in my portal that I use for additional data collection from devices.  
The client portal I've started to use more but it's admittedly limited.  However, 2 such use cases I use it for are..
1.  A customer purchases a new machine themselves and want me to manage it.  I let them log into the portal which displays a link to their client specific Pulseway installer.  They install it, then my onboarding workflow does the rest. 
2. Some of my clients have specific software applications that very infuriatingly have "known" issues that the software vendor refuses to currently fix, like a piece of the software disappearing off the screen and the "fix" is modifying some registry keys and a couple files.  I have a troubleshooter that lets the user having the issue run the script I wrote to auto fix the reg keys and files instead of having to rely on reaching out for help and waiting on a response.   

Kyle, 
It's not Pulseway, but have a look at LAPS from Microsoft. 
If you have an AD Environment, it works a treat, and meets the requirement of recording password "relatively" securely, and allows for password rotation. 

Very nice Thank you for sharing! I did not know this. 

No the performance is sub par. I have had issues with it fully locking up the mac during a remote session and it requiring a hard reset. the responsiveness to mouse and keyboard inputs lag badly. Not any of the 30+ macs i have deployed it on has worked great. Does not matter if the mac is hard wired or on wifi, performance is the same. I have also tried different internet connections. 

Yes this is what I'm looking for. I want to be able to install across different subnets. How quickly can this be added?

Hi there,
We'll be releasing it next week .
-Paul

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.

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.

one other thing with this add the ability to remain connected after logging out a user or during fast user switching. It's VERY annoying to have to log out a user to log in as an admin only to be disconnected and have to reconnect two or three times.
We also need the ability to reboot in safe mode with networking and reconnect to a machine.
we had both these capabilities in our old RMM (Solarwinds) so it's very technically possible.

Its very frustrating if you want to add newly added apps to the Third Party patch management section that you need to check what apps you already have in the list; See screenshot. 
It would be better to remove items from the dropdown list if they already are in a rule.
I understand that you will be able to have multiple rules (1 for install and 1 for update)
But you would be able to make a Checkbox or some other solution to get this done.
Or put a Checkbox in the dropdown list or whatever to quickly see what is already added to a rule. That way its easier to keep the list up to date since you are adding apps all the time.

The two-factor authentication as it stands now, is woefully incomplete.
Until such time that the timeout for my browser login can be lengthened, I cannot use two-factor ID whether it is a OTP or a Google Authenticator number.
As in most two-factor implementations, I should be able to whitelist my current browser for at least 30 days and not be asked for it again.
The purpose of two-factor authentication is to keep the bad guys from logging in ONE TIME and all times, not to continually inconvenience me each and every time my browser decides to terminate the session for inactivity!
 
Harumph, Harumph ... wait a second, I didn't hear a Harumph out of that guy .....

Nice!
Thanks a lot!

:-)

Hi there! 
 
I often find myself running scripts on our machines in a way that demands follow up/verification, so I thought it would be a good thing to be able to add scripts to a queue in Pulseway to have them run at a later point in time when a system becomes available online. Currently I tend to keep a document with all the machines listed, so I can mark them one by one in order to know which ones are done, and which ones remain. This is kinda tedious because our machines (especially laptops) tend to be offline for longer periods of time, and I have to follow up on a daily basis until the script ran successfully on all of them. 
 
I know about automation tasks in Pulseway and the possibility to schedule scripts to run daily, weekly etc. But they will continue to run on all computers for as long as the task is enabled. I've tried to cope with this by building scripts that won't reapply the software and/or settings if existing data is found. It seems to work, although it's not an optimal solution since the scripts will run tens or hundreds of times on our systems when they only really need to be ran once. 
 
So, what am I suggesting?
The possibility to run one or multiple scripts (either directly or via an automation task depending on what the Pulseway devs prefer) With an option to run once. With an option to include offline systems (the script/s will be queued for when they come back online) With an option to send success/failure-reports to the administrator With an option to retry once, twice or three times whenever a script is unsuccessful. (in my case this is useful because Powershell Impersonation doesn't work in home environments when VPN is disabled, so a second attempt may succeed.) A section in Pulseway WebGUI where an administrator can see the deployment progress and success/failure-ratio.  
One of many scenarios: I have a script that will install a scheduled task with some predefined values, and upgrade an MSI-installation to a newer version. I want to make sure that all our computers run the script with a successful output.
 
Please let me know if you find this suggestion useful! 

Hi @Parallax Abstraction,
Thank you for your suggestion. It sounds like a great idea, I will put it forward as a feature request, therefore our developers will consider the possibility to introduce this functionality into the future. 

Thank you for responding. I wasn't sure if I was missing something.  This is a consideration I need to take into account. There's only a handful of systems I would need to blank the screen on while I'm working, I may be able to get around that, will have to ponder this.