Paul

Hi, I'll take a look at the plugin and get back to you. -Paul

Hi Aron, I would prefer using Group Policies (configured from Pulseway Manager -> Manage Systems -> Manage Group Policies) which is documented on the page 19 of the User Manual. You can import a configuration file (which can be exported from an already configured system by clicking the Export Configuration textual link at the bottom of the Pulseway Manager window) or import a registry patch with Jenkins but it would be troublesome to configure and maintain. -Paul

Actually msiexec does allow Lv* as an argument, try this command (note the allusers argument which will install the app for all users): msiexec /I "\\server\folder\Pulseway_x64.msi" /qb /Lv* "C:\install.log" ALLUSERS=1 -Paul

Try running the msi with msiexec and add the following logging arguments: /Lv* "install.log" Then PM me the install log. -Paul

Hi Aaron, Try to also add the following argument to the msi: ALLUSERS=1 When you install the agent silently I believe it's not ran by the same user but by the administrator user which is why you don't see it in the programs and features and also explains why the shortcuts are missing. For notifications you can either configure a group policy (from Pulseway Manager -> Manage Systems -> Manage Group Policies) or edit the configuration remotely using the Pulseway Dashboard app or import the configuration file like this: -Paul

Hi James, Our email server's IP address is: 167.89.85.223. This IP address is subject to change without notice. -Paul

Hi Dilbert, Thank you for your feedback. We plan on supporting custom icons for the API in the future. Great idea . -Paul

Hi Jaapyse, I'm not sure why Pulseway isn't detecting any hardware sensors on the proliant server. We're monitoring a couple of proliant servers ourselves and the hardware is correctly identified. Does the HP Management portal detect the hardware sensors? Can you run the following app to see what hardware information is displayed (link). -Paul

Hi David, We monitor the registry root key for uninstall and it's possible that there was some software that tested the access rights to see if they can create the registry values and then removed them, Pulseway might have caught that bogus data. Do let us know if this happens again. Paul

Hi Tom, We do some trickery there if you have another online agent in the same group with the system you're trying to wake and both have the same WAN IP address by sending a command to the online system to broadcast the WOL magic packet in the local network. Is this the case in your situation? -Paul

You could add the first field in the list (or maybe move it to a separate page) to be a text input item and when it changes it will filter the list. You could also refuse to list anything when the search query is empty so that you will never list all of the users. -Paul

Hi Grunta, We will improve agent credential management in the future, we agree there are cases when this mechanism doesn't perform well. -Paul

Hi Tom, Is WOL enabled in BIOS? Can you wake the system while you are on the same network? -Paul

Hi Grunta, It will be released in Q2 2016. -Paul

Hi Dilbert, That's a great idea, we are actually considering on introducing some sort of an access token which you can revoke at any time. This is something we will consider to improve the agent security in the future. -Paul

Hi, You can login as an administrator user and install the Pulseway app for "Current User" instead. When other users will look in the Programs and Features Pulseway will not be listed. Also, you can remove the user from the Administrators group, this will prevent them from uninstalling Pulseway. If nothing works just remove the Uninstall key from the registry using CCleaner or plain regedit (HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall). -Paul

We also require administrative privileges for editing the registry settings and updating the remote desktop libraries. We will consider requesting user elevation when administrative rights are required.

Hi Jaapyse, Chris has asked me to take a look at your case. You should be able to run as many agents as you'd like in the same network so this is not a known bug. Can you try to install two agents on a different network to see if the problem can be reproduced on a different environment? -Paul

Hi James, A system is considered as offline when you receive the offline notification. For the Professional product that is about 10 minutes after the agent stops communicating with the Pulseway Cloud Servers and for the Enterprise product this interval can be customized. -Paul

Hi Martin, Our current API (v1) doesn't support getting the list of notifications nor deleting them however we are working as we speak on the REST API v2 which will support these actions. The notification archive will not be exposed in the REST API v2, we will consider this for a future release. -Paul

Hi Bart, You don't need to include a closing XML tag when using the /> closing tag. Do you see any errors in the syslog related to the ping? -Paul

Hi Marc, It's odd that you still don't see the CPU temperatures. Try with HW-Monitor too: http://www.cpuid.com/softwares/hwmonitor.html . -Paul

Hi Adam, You can enable the VMware alarms notification from the Pulseway Manager in the Notifications -> Server Modules -> VMware tab. -Paul

Hi, You can customize the email template (see blog post) however all notifications should already include the system and group names. -Paul

Hi, I've sent you an email requesting remote access to your system to diagnose this issue. -Paul