Paul

Policies always override local configuration (with the exception of the two storage notifications from the policy that target the system and non-system drives). You can have a script check if there's a D drive to set a rule for that as well, maybe with a different threshold too. -Paul

Jan, Yes, it's possible to avoid having to connect to 130 servers however there are a couple of things to note. CPU and Memory notifications only support one threshold, only disk supports multiple thresholds. Also which partition you want me to create the notification checks for? 'c:'? -Paul

Yes, it's possible, tell me what you need I'll make it happen. -Paul

Hi Jan, A policy can have system and non-system drives notifications configured and it should let you pick a priority. Would this not work for you? -Paul

Hi Luis, Just edit the /etc/pulseway/config.xml to enable monitoring features with your favorite text editor. -Paul

Glad to hear you've managed to add your system. To increase your notification limit and enable remote control you just need to purchase an additional system license. This will upgrade your whole account to the Starter plan and make the 2 free systems go to the starter plan too. -Paul

Hi Beng, Welcome to the Pulseway community. Make sure that you don't enter a space character after or before your username. If this is not the case, please PM me your username and we'll take it from there. -Paul

Hello Arnd, I've responded to your email. Basically, the easiest way would be for you to have Pulseway take over the already installed Kaspersky Endpoint Security product and from there you'll be able to uninstall the product normally. -Paul

Hi Patrick, Our patch management feature will only restart the OS if the windows update component says a reboot is pending. I can help you fix the script if you share it here too. -Paul

Hi Jason, The remote control functionality for iOS devices is already available for paying customers. If you have a free account drop me your username and I will be activating a trial subscription. -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