Paul

Thanks for sharing this! Glad to hear everything works now. Have a great weekend as well! -Paul

That's odd, have you tried an online SMTP test tool like this (https://www.smtper.net/)? If this shows the same error you may need to reach out to their support to see maybe you're missing a setting. I am not familiar with Office 365. -Paul

Hi Joe, A couple of things you should try: Use the same FROM address as the username If you have 2FA configured try using an App Password Make sure you use encryption and port 587 Use a username in format of user@domain.com instead of DOMAIN\user Let me know how it goes, -Paul

I'd like to point out that disabling Windows Update related services is a very BAD idea. We've seen cases on Windows Server 2016 where if you stop, disable the Windows Update service, then use the GUI to check for available updates, the windows update component will crash and corrupt the system in a way where dism and sfc couldn't repair. Just something to keep in mind. -Paul

Hello Paulo, That reset code expires after a while. Did you enter it right after you've received it? -Paul

Thanks for letting us know. I've issued an internal bug report for this to be enhanced. -Paul

Hi there, I've sent you a PM to discuss your login problem further. -Paul

Hi Tob, Are those agents online? If you no longer want the policy to be assigned, change it from Server Admin -> Configuration for the org, site or agent group where it's assigned. Make sure you set it to No Policy so you can manually manage the policy assignment. -Paul

Hi Colm, Yes, if you remove the system from Pulseway it will also release the Webroot association however you should check on the Webroot GSM console if the system is still registered there and remove it. -Paul

Hello Richard, We are looking for integrating with Bitdefender in the next quarter. We'll be looking into the "cancel installation" command. -Paul

Thanks Susanne for the report. You're right, it seems that Kaspersky just needs a while to start. We're going to be adding a delay for that notification. -Paul

The API limits are different for each endpoint. What endpoints are you calling? -Paul

Personally, I'd keep the Pulseway integration active for the whole lifetime of your API. This way you'd also be able to post metrics for the API like how many requests you're getting per day and receive commands straight from the Pulseway app. The possibilities are endless. -Paul

Hi there, By calling the first two lines you've quoted you're registering the application with Pulseway and it will start showing up as online on my.pulseway.com until you close the application or call the .Stop method. Group is a legacy feature, just send a value there and the system will register under the Legacy Agent Group (gets created automatically). Then you'd be able to move the system from the Configuration page into the group you desire. That looks good but I would also display some information about the application so I'd subscribe to the OnDetailsRequest event and in that method I'd call Service.Instance.SetDetails(groups); to send the information back to the server. I'd also avoid calling Stop unless the application is stopping as this will only keep the application marked as "online" in Pulseway when you send notifications. -Paul

Hi Michael, Thank you for your feedback. We'll see what we can do there. -Paul

Hi, sorry for the delay. I've activated a subscription on your account for two weeks. Enjoy! -Paul

Hi there, The best course of action would be to have an adapter software that sits in the middle, receives notifications from the 3rd party cloud systems and then forwards them back to Pulseway using the .NET or Java Cloud API (link). Basically you'd register an application with Pulseway, you'd be able to offer information to the Pulseway clients when it's requested, receive commands and also be able to send notifications. -Paul

Hi there, Try extracting https://updates.pulseway.com/update.zip on M:\, then attempt to uninstall the product once again. -Paul

Hello, For sure, a SQL Express should do as it's only limit is the 10GB per database which won't be reached that easily. As for disk space, I'd worry more for the OS and SQL Server consuming disk space than Pulseway so I'd say 50GB to be sure. -Paul

Correct, purchasing the third license will activate remote control. We do mention on the plan comparison that the free plan doesn't include Remote Control. -Paul

Hi Benjamin, Thank you for your report. We're working on resolving this issue right now. -Paul

Hello @Rhea, We list the Pro plan on the website as "Starter". To be able to use the Pulseway Remote Control functionality you have to purchase a subscription (of any size). Also if you decide to add another system, you will not be charged for the two systems you have received free of charge. In other words a 3 system subscription will only cost you € 27.48 per year and will give you monitoring and remote control capabilities for all 3 systems. -Paul

Hi Martin, I don't have an update to your feature request just yet. We do have it on our todo list to support more granular controls but at this moment it's not part of our Roadmap. -Paul

Hi there, We don't support at this moment the arm64 CPU architecture. You could make use of our RESTful APIs to push some information to Pulseway using cron and curl, check them out at api.pulseway.com. -Paul

Hi there, I'd like to add that Pulseway does pull the S/N from systems, you can access it through the Assets Overview report template. I hope this helps. -Paul