Paul

Hi Norman, Since the 6.0 update, systems are no longer authenticating with a username and password so it's safe to change your password and it won't affect your systems. Make sure that your agents are running the agent version 6.0 or higher by running the Executive report which shows the agent version. -Paul

Hi Brian, Try running the pulseway-registration tool to re-register your system. Let me know how that goes. -Paul

Hey everyone, I'm proud to announce that you can now generate a report that includes the outputs of the scripts from an automation task. -Paul

3rd party patching is queued for Q2 2019 (wohoo ): -Paul

Hey Martin, I can see the more requests showing up about implementing custom levels for sending various other commands like access to screenview or file browser only for certain teams so we'll consider extending the team access to certain features. -Paul

Hi there, Run as an admin: net stop "PC Monitor" taskkill /f /im PCMonitorSrv.exe del "c:\Program Files\Pulseway\watchdog.bat" 2> NUL sc delete "PC Monitor" taskkill /f /im PCMonitorManager.exe taskkill /f /im pcmontask.exe taskkill /f /im PulsewayAddonManager.exe You should be able to reinstall the Pulseway agent now. -Paul

Hi John, Thanks for letting us know. Can you run this powershell commands and see if you can login after the system restarts? Remove-Item -path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers\{32674157-1879-4496-A847-695CAEF9B621}' Restart-Computer -Paul

This is a good idea, we've already went that route when we've added support for notification exclusions under the Account section. We'll consider it for the future. Your clients should not be part of the Administrators built-in team. If they are placed under a user-defined team then they will not have access to the Server Admin section and will not see other clients. -Paul

Hi Brian, For the RMM agent you need to open the following IP addresses: 69.65.47.163 69.65.47.165 69.65.50.4 69.65.50.5 69.65.50.6 69.65.50.9 69.65.38.27 69.65.49.8 69.65.48.112 69.65.48.240 13.237.174.172 Note: These IP addresses are subject to changes. -Paul

You can only disable it, if you delete it Pulseway will automatically create it. We will consider adding a setting to control whether or not to create that task. -Paul

Hi Steve, Our SaaS OPS team can clear the historical information that keeps the workflow locked. Can you send me a PM with the workflow names you'd like to delete and I'll get it sorted for you? -Paul

Hi Eric, You can achieve this by using a custom HTML template for the emails which you configure from the WebApp -> Settings -> Email -> Custom HTML Template. Let me know how that goes . -Paul

Hi there, We've added the confirmation prompt for the tasks as well. Thank you for your feedback! -Paul

Hi Abdul, Have you tried reinstalling the applications? -Paul

Hey everyone, We've released an update last week including a fix for the keyboard locking issue. Do you still see it happening? -Paul

Hi David, Thank you for your report. We've fixed this and it's coming out in the next release that's scheduled to go out this week. -Paul

I agree that this is a must-have for RD auditing. We'll most likely be adding a report to include the RD activity. Thanks for the feedback! -Paul

Hi Martin, This is still on our backlog for the SQL server module. As soon as we touch that module we'll be adding this notification too . -Paul

I've added this to our todo list, we will definitely add support for it! -Paul

This is on our todo list for the automation module 2.0 when we'll be adding event based triggers. It also comes with a tag editor to make it simpler to edit tags on machines. -Paul

Hi Martin, I did look into this and Windows APIs do not provide you with the information on who triggered the power event. It can be hardware triggered, it can be triggered through a software via the API, it can be a user signed into the console session or it can be one of the remote desktop sessions which are active. Guesswork will not be a great approach for this. -Paul

Hi Martin, We do like the idea but I am not sure of how often will this information be useful. We can add it as a built-in script to get all the bitlocker recovery keys but how often do you think you'll need this information? We'd like to keep the user interface with the bare minimum information avoid delivering too much information for no reason. -Paul

Hey Martin, You are not the only one looking for this and this feature just might come in when we're adding support for 3-rd party patch management next year. -Paul

Hi there, If you can send me the CSV file I'll build you the XML file you need to import. It's just a find & replace with a regular expression so it should be fairly easy . -Paul

That task is there to ensure that the Pulseway agent will start at the system boot. Is there any particular reason why you'd like it removed? -Paul