Paul

First, configure a windows agent with an account on the Team plan and validate the account to make sure the credentials are correct. Apply the configuration and write down the values of the following registry entries: AuthenticationToken AuthenticationTokenCtrl Now go to the WebApp on the professional server (link), login and go to the Automation -> Scripts view. Select (or create) a category and click on the Create Script button. Enter a script name and under Windows tab, enable the script and select PowerShell as the script type then paste the following script: Set-ItemProperty -Path "HKLM:\Software\MMSOFT Design\PC Monitor\" -Name AuthenticationToken -Value "Enter the saved AuthenticationToken from the machine you've just configured" Set-ItemProperty -Path "HKLM:\Software\MMSOFT Design\PC Monitor\" -Name AuthenticationTokenCtrl -Value "Enter the saved AuthenticationTokenCtrl from the machine you've just configured" Replace the values of AuthenticationToken and AuthenticationTokenCtrl to the values you've wrote down from the agent you've configured to connect to the Enterprise server Skip this step if you don't have any Linux agents configured. If you have, then you will need to configure one of your Linux agents to use your new Pulseway server and then you will need to copy the following line from the config.xml file from the Linux system which is configured to use your new server. <Account Username="" Password="" UseCustomServer="false" CustomServerAddress="" Token=""/> And then Under the Linux tab, enable the script and paste in the following script using the values from the line which you have copied previously: sed -i 's/\t<Account.*/\t<Account Username="" Password="" UseCustomServer="false" CustomServerAddress="" Token=""\/>/' /etc/pulseway/config.xml systemctl restart pulseway Save the task and then run it. Please note that the task will stop automatically in 15 minutes but the systems get moved right away. This is happening because you've moved the agents to a new Pulseway server and the SaaS Professional servers stop hearing back from your agents and will mark the systems as unresponsive in the task execution after 15 to 30 minutes of inactivity. Warning: Please note that if you make any mistakes in the values or break the xml configuration layout by removing a closing quote the agents will stop and you will have to manually reconfigure them. It is recommended that you create a system scope that only includes one system so that you can test that the migration script contains the correct values.

Hi Martin, Unfortunately there are no plans on exposing the SQL Servers to the public for security purposes. Check out our REST API documented here, it may already expose the information you're looking for. -Paul

Hi Aaron, Check out this post for more information on how the SNMP monitoring works: -Paul

Hello, Most definitely not, sorry for the confusion this old post brought. Please find the answer to your question over here: -Paul

POTS brought us the idea to support it natively and we're very thankful for making such a great plugin. I'm looking forward to see what changes are coming to the POTS plugin . -Paul

Hi, Welcome to the Pulseway community! You can change your password from the WebApp by clicking the forgot password link, if you have an Enterprise server then you can also change your password from the Account section of the WebApp and for the Professional plan you can change your password over here. When you change your password you will be prompted to select a password propagation window. During this window both passwords are accepted and when agents check-in with the old password they will receive a request to update the password. For this to work agent would need to be online obviously so select a propagation window that will ensure that most if not all your systems will be online at least once. If your systems are all online, select any password propagation (even as low as 1 hour) then all of them will receive the new password right away and you have nothing to worry about. -Paul

Hi Charles, Would you be able to send an email to support [at] pulseway [dot] com? I'll get pick up your email once I see it. -Paul

Hi Chris, Welcome to the Pulseway community. You'll need to download the MIB files form the device manufacturer's website then import them into a SNMP Browser (I recommend this one), navigate through the objects and see which variables you want to monitor. Once you've figured out which variables you'd like to monitor just copy and paste the OIDs into Pulseway and then configure the notification rules to notify you when those values exceed the normal values. -Paul

Hi Johnni, It's nice to see you back on the Pulseway forums. We're working on the scheduling functionality for the Automation and Advanced Reporting features as we speak . -Paul

Hi Tim, We've just released an update that fixes this issue. Thanks again for your report. -Paul

Hi Tim, Thank you for your report. Our development team is working on a fix as we speak. -Paul

I totally agree with this. I've added it on our list. Thanks for your feedback. -Paul

We are planning to support raid monitoring on our agents in the future, we share the same pain when we're monitoring our own servers. -Paul

Hi Phil, I've checked the support group and I seem to have rights to send emails to it from all my personal email addresses. Can you try again now and if it fails please PM me your message headers. -Paul

Hi Aaron, You could write an automation script that can run the StorCLI app, parse the output using grep (and read the exit code) and if the RAID is inconsistent then return an exit code different from 0 which will cause the script to be marked as failed. Then you can have the task notify you when the script fails. Trick is you'd have the run the script manually every now and then until we add the scheduling capabilities for automation and reporting. Alternatively, have the script installed locally on the machine, add it to crontab to run based on a schedule (every day?) and then call the Pulseway REST API to add a notification for the system (docs). You can find the system identifier of a Linux agent in the following file: /var/pulseway/pulseway.id . -Paul

Permanent. We store notifications for ever for auditing purposes. -Paul

Hi Tim, We do have support for running batch, powershell and bash scripts on subset of systems (or even all systems at once) through the Automation module. From the WebApp, go to the Automation menu and configure your script. Once you have the script go create a task, select the "All Systems" System Scope and include the newly create script into the task. Run the task and perform the victory dance . -Paul

Hi Jeremy, When you delete a notification it actually gets archived. You can access the notification archive from the web app -> server admin -> notifications. -Paul

Hi Jeremy, This is not a UI glitch it's just that we don't support showing the startup mode of the services on the remote system. We will add it in a future release. -Paul

I agree, we need some bulk actions on the policies. We'll see what we can do there. -Paul

Hi Jeremy, From what I know only the vCenter supports vSphere alarms. Am I wrong? -Paul

At this moment we don't have a report that shows hardware sensor information. Now that you mention it, it would be nice to see a trend for the average sensor data. We will consider adding this report template. -Paul

I'm afraid you can't. I've added this to our idea bank too. -Paul

Hi everyone, Are you referring to the Windows Metro app? Did you login with that app to the account that holds the other 19 systems? Once you login with the app to an account it registers as a monitoring device. Until you delete it from that account, you will receive PUSH notifications for that account even if you logoff and login with a new account. -Paul

Right click menu. -Paul