Paul

We've identified a bug in the PSA/RMM integration where the PSA would incorrectly overwrite customizations made to the hardware assets that are populated when RMM notifications are converted into PSA tickets. We are currently working on resolving this. I'll update this topic when this the bug gets fixed. -Paul

Hi Kev, Did you update the OS on that system to a higher major version? If so, you need to install available Windows updates as this is a known .NET issue which was resolved in one of the Windows patches. -Paul

Hi, Unfortunately we don't support detecting hanged applications on macOS just yet. We will consider it for a future release. -Paul

Hi, Thanks for the update. Glad to hear it works now. -Paul

Hi, You can override the local configuration of all the agents in a group with Pulseway Group Policies (configured from any Pulseway Manager in the Manage Systems -> Manage Group Policies dialog) or you can setup a Script that runs the Set-ItemProperty powershell command to update the registry settings directly. -Paul

Hi Jaapyse, Thank you for reporting this. It's the small things that matter in the end, I'll have this fixed ASAP . -Paul

Hi Bryan, From what I understand you're running a script which runs Ninite to update third party software. After the script ends you can run another script that parses the output of the log file and if it contains the keywords that interest you call the Notification Bridge plugin to send a notification to Pulseway. -Paul

Hi Sjakkie, We have support for none of the following at the moment but we will definitely consider on adding this in the future. -Paul

Hi Sjakkie, Welcome to the Pulseway community. I don't think it's possible for one to write a script to report the daily usage unless you do some complicated Event Log parsing and analysis. -Paul

I've updated the first post with an updated plugin which supports Windows Server 2012 (or newer).

Hi James, Yes, it's a machine specific setting. -Paul

Hi, This is a great idea, we've added it on our wishlist. -Paul

Hi James, Please open the Pulseway Manager and under the Devices tab, is the agent configured to accept commands from all devices? -Paul

Hi James, We do have it as a confirmed feature as announced bellow so it's definitely going to be supported in the future: -Paul

Hi, Support for the SQL Server server module in the WebApp is not yet ready. We are working on aligning all the features available on the mobile app with the webapp. -Paul

Hi Martin, I've sent you a PM with the CSV file as requested. We will add a feature in the webapp which will give you the possibility of downloading the notification archive matching your filter. -Paul

Hi, Does the cleanmgr process start when you're invoking the script from the Pulseway automation? Please note that when you're running the script it will run under the LOCALSYSTEM account, if you want it to run under the local user account you have to setup the powershell impersonation from the Pulseway Manager -> Settings -> Runtime. -Paul

Hi Jaapyse, Did you also enable the notifications when you've configured the associated accounts? Check out this blog post for more information. -Paul

Hi everyone, In regards to the inputs on the WebApp, we don't support any form of API inputs for the HTML WebApp at this moment, they are planned to be introduced in the future. I'm sorry for the confusion this caused. -Paul

Hi guys, We're planning to introduce this in a more general way which allows you to specify an account-wide priority filter per delivery mechanism: Email: Critical Elevated Normal Low Push: Critical Elevated Normal Low Which allows you to opt out of certain priorities just like the Slack integration works. -Paul

Hi, Try changing the start mode to Automatic (Delayed). We've noticed that Windows sometimes gives up on starting some services if the system is low on resources during boot. -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