Paul

Hi @Aspect, You need to check the count in HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\ServicesExcludedFromNotifications\Count, iterate through the HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\ServicesExcludedFromNotifications\ServiceX where X is the 0 based index. If among the list of excluded services you find your service then you don't need to do anything but if it's not among the entries then you need to add another entry that will be like this: Name: ServiceX where X is Count - 1 Value: The service name you wish to exclude from the notification And finally you need to increment the Count value by 1. Please let me know how this goes. -Paul

I'm afraid that advanced reporting is the only way so far. Sorry about this. -Paul

Hi there, Welcome to the Pulseway community. The Linux agent doesn't support collecting historical information required for the advanced reporting module at this time. This will be added on a later release. -Paul

Hi @Michael12, To get a subscription for only 2 systems you would have to sign up for a Pro account using this sign-up page. -Paul

@Martin_T I have the confirmation that IT Glue will be integrating with the Pulseway PSA soon. -Paul

Hi Michael, If you do modify a MSI to contain your credentials and server name then the service should start up automatically after installation. Can you PM me your modified MSI so I can test it on a VM? -Paul

Hi @Aspect, We do allow you to configure the Web Antivirus from the Pulseway WebApp under the Antivirus -> Policies. Is this what you were looking for? -Paul

Hi there, Unfortunately performance counter names are localized to the OS locale and they don't really have any unique identifier. Also reading all performance counters just to display the list on the dashboard is going to take a very long time however it's something that we are going to be supporting in the future when we will be introducing web based configuration for the agents . -Paul

@Martin_T, let me see what I can dig up. I'll come back on this soon. -Paul

Normally it should install IIS itself and configure it. What OS did you use to install it on? -Paul

This indicates that the IIS web service didn't connect to slv.pulseway.com as there is a firewall blocking the connection or it simply didn't manage to do it yet. Now that some time has passed, does it work? If not please create an archive of the c:\logs folder and send it to support [at] pulseway [dot] com. -Paul

Hi @Aspect, Out of curiosity did you figure it out what happened with the installation? You've mentioned in a separate post that it didn't configure the IIS server. -Paul

Hi there, You need to create a port forward for the UDP 9 port towards the static IP address of your computer. Additionally your computer needs to be connected to the network via an Ethernet cord. -Paul

Hi guys, The IT Glue integration is now released and it's already available for everyone. See blog post: https://www.itglue.com/blog/it-glue-announces-integration-with-pulseway-rmm -Paul

Hi Clive, We removed it as we are transitioning to a new system where we can maintain the roadmap in an easier (and automated) way. -Paul

Hi Andre, We understand your excitement for the Webroot addon. Rest assured that we're doing all we can to push it out as soon as possible . PM me if you want I can add you to the early access list. -Paul

@chrisporosky We will support Webroot as an alternative to Kaspersky.

Hi, Sorry for the delay, can you rebuild the performance counters on the machine by running: lodctr /R See if this resolves the memory usage discrepancy. -Paul

@chrisporosky You can see all internal IP addresses for the NICs you have monitored from the Pulseway apps in the Network section. If the system is offline you can run the IP Summary report to get the list of IPs. -Paul

@Martin_T This issue was resolved and will be included in the 4.0.8 release coming up this weekend. -Paul

I'm glad to hear it works now . -Paul

Hi Johnny, Use IIS Crypto to set the same cipher suite from one server to another. The error says that the SQL Server has no matching SSL ciphers / protocols with the source machine. -Paul

Hi Daniel, Thanks for the feedback. We will definitely consider this option . -Paul

Hi Martin, This got released in yesterday's Windows Agent 5.3 release. Documentation is yet to be updated but you should find a new overload for the SendNotificationToAllDevices method with the new PCMonitorClient.dll. -Paul

Hi Elliott, Sorry for the confusion and thanks for reporting the mistake. The correct file is PCMonitorClient.dll . -Paul