Marius

Thanks Johnni, this is something we will definitely add. Best Regards, Marius

We are looking at ways of implement this. We don't want to delete the previous notification as it's important to know that something did happened at some point in time. I'm thinking of changing the priority of the existing notification to Normal and append the date/time when the problem was solved. Best Regards, Marius

Hi Jonni, We plan to support plug-ins for the client agent and this could be implemented as a plugin. Best Regards, Marius

Hi, Please check again now and let me know. Took a bit for the change to propagate to all the servers. Marius

Pulseway allows you to restrict access for Dashboard and Web Application by IP Address so only designated IPs will be able to connect. To add a restriction start Pulseway on a monitored PC and click "Change Account Details". On the account detail you can add IP addresses that are allowed to access either Dashboard or Web App or both.

Email notifications are disabled by default in Pulseway. To enable them start Pulseway app on your computer and click the "Change Account Details" button on the Account tab. You will then be able to enable email notifications in the Account Details dialog.

Thank you for your feedback, we will add this option.

With this project we are aiming to achieve the following: Send SMS notifications Expose a simple interface on TCP for specifying a phone number/message and eventually the number of retries On the same interface a status report of the SMS module will be required (No SIM, No signal, etc.) [*]Send Wake on LAN magic packets This can be done simply by running PC Monitor daemon on the device [*]Send notifications when power is off Future discussions needed [*]Use the device as a software/hardware bridge for monitoring other computers/devices Future discussions needed

Hi Chris, Thank you for your support! We are considering this - an editor to apply common settings to all computers (or for a group). Marius

You're welcome Daniele. Have a great day.

Hi Daniele, Thank you for your support, really glad you find our solution useful. You can get a 25 PC's subscription and you can upgrade later to 50 PC's by getting another 25 PC's subscription. If you know that you are going to need 45 it's better to get the 50 PC's subscription from the start. Marius

Thanks, looking forward to that.

Thank you for your support. We plan to enhance the AD module and will add the logged in users. Shares management is another one that we plan to add. The external IP - we are investigating this to see how to implement. We started the dashboard development for viewing the computer details and sending commands - should be available in a version or two. Please send us a picture with the dashboard on the big screen

Server Requirements Windows Server 2008 R2, 2012 or 2012 R2 2+ GB RAM .NET Framework 4.0 (or higher) SQL Server 2008/R2, 2012 or 2014 (Express Edition or higher) 1 static IP address 1 SSL Certificate or a Wildcard Certificate or SAN Certificate (self-signed certificates are not recommended) Required steps before installing the Pulseway Enterprise Server Obtain the SSL certificate for pulseway.<yourdomainname> Add a DNS entry for pulseway.<yourdomainname> -> Public IP address Install the SSL certificate in IIS Install SQL Server 2008/R2, 2012 or 2014 (Express Edition or higher) on your server Note: Pulseway Enterprise Server will also work on an Amazon EC2 small instance.

Pulseway supports Wake on LAN and Wake on WAN over Internet. The mobile application will send a magic packet in LAN while on WiFi. As well, our cloud servers will send the same magic packet to the public IP address on UDP 9 (you can change the port number and assign a different port number for each computer using the Pulseway app installed on your PC, go to System->Wake on WAN over Internet, default is 9). Please make sure that the router forwards those packets in the LAN and that the PC supports Wake on LAN (check BIOS and network interface settings). The only limitation at the moment using Wake on WAN over Internet occurs when our cloud servers have the last public IP used by your computer and your public IP changes. The magic packet will be sent to the last known public IP and will fail to wake the computer. We are planning to solve this problem in the future using a different method.

Thank you, we appreciate the support.

Thank you David, really glad our solution can make a difference. We are planning to introduce a live view of any user session (local or remote) soon and working on adding Remote Desktop support too.

Great, glad it worked. Thank you for your support and for posting the solution.

Most likely it's not a BIOS issue. What Operating System do you have on that computer? We are using performance counters for reading the total CPU usage, are the performance counters working for you?

We have seen a few isolated cases of this, usually happens on a new installation and it resolves after a computer restart. Are you using the latest PC agent (2.4.1)?

Thank you! Really appreciate the support.

We are working on the Mac version. The agent is working but there are still some features to be implemented and to complete the configuration UI module.

If you never installed or configured Pulseway on your Windows PC please read this guide: http://www.pulseway.com/getstarted

Pulseway can be installed on Windows 2008 R2 Server Core Installation. Before installing Pulseway you will need to download and install .NET Framework 4 for Server Core from: http://www.microsoft...s.aspx?id=22833 Instructions Important: Make sure that your computer has the latest Windows service pack and critical updates. To find security updates, visit Windows Update. If you are installing on Windows 2008 Server R2 on Server Core, you need to install Windows 2008 Server R2 SP1 and follow the instructions below before you install .NET Framework 4 Turn on WoW64: Start /w ocsetup ServerCore-WOW64 Turn on .NET 2.0 layer: Start /w ocsetup NetFx2-ServerCore Turn on .NET 2.0 layer for WoW64: Start /w ocsetup NetFx2-ServerCore-WOW64 On this page, locate the Download button and then click it to start the download. To save the download to your computer so that you can install it later, click Save. To cancel the download, click Cancel. After installing .NET Framework 4 on Windows 2008 R2 SP1 Server Core, it is highly recommended you install critical .NET Framework 4 updates available on Windows Update. System requirements Supported Operating Systems: Windows Server 2008 R2 SP1 Windows Server 2008 R2 SP1 Server Core or later Supported Architectures: x64 Hardware Requirements: Recommended Minimum: Recommended Minimum: Single processor with 1.4 GHz (x64 processor) or 1.3GHz (Dual Core) with 512 MB RAM or more Minimum disk space: 2 GB (32 GB or greater required for OS) Prerequisites: Windows Installer 3.1 or later