Pulseway’s mass installation feature and notification settings


Manage your IT environment from anywhere, using any device.

4.69/5 (143 reviews)

Pulseway’s mass installation feature and notification settings

Video Transcript

Speakers in this video: Jimmy (GetApp) and Edgar (Pulseway)

Edgar: Another common thing that Pulseway users usually ask us is how do they deploy the agents on all of their systems without having to manually go and install it on each computer. This is usually done using the Active Directory environment where they can push the installation to all of their systems and at their next system reboot, it will automatically deploy the agents and see all the agents being populated as the systems reboot.

This very commonly used feature of Pulseway for larger installations where you can quickly deploy agents on 300 and more systems in about a couple of minutes. Moving on to the notifications part of the Pulseway which is like a core feature to the product. You can get notifications when the service is getting offline, when the service started, when its public IP changes or when the user logs in which could be a corporate violation if a user isn't authorized to log in to a system that is logged in off the hours.

It may be a corporate violation password or hacker logging in to the system or so other corporate violations which could be like identify theft, their removal disk being a certain application installed, antivirus getting disabled due to a virus attack or something similar.

Yes. Pulseway is very configurable and allows you to customize it for each environment so there maybe systems which are generally used with larger amount of memory; a lot of systems that are used for multiple CPU computing. So you can customize the agent depending on the needs of each company.

For instance on this machine, I can set up to receive a notification if the free memory drops under 50 percent and the CPU usage stays above 90 percent for, let's say, 15 minutes. I would get a notification with an Elevated priority or Critical.

Furthermore, we can customize Event Log monitoring. We can select, for instance, if an application reports an error with the Event ID 200, we can receive a notification for each event that's being logged in the application event of these filters.

Also, these filters do not need to be configured on each agent everytime you want to apply a change. For instance, you’ve configured 300 systems and would like to change or to add a new Event Log filter, you can do it like a group ... level. You can centrally manage all these Event Log filters from one location and it will apply to all ... systems at once.