Paul

A simple logout and login again should do the trick, can you confirm? Yes, that is the case. We will be migrating the license into the new system in the upcoming days. -Paul

Hi Dragos, Under the WebApp -> Antivirus -> Agent Status you should see BitDefender listed for Windows Agents. If it's still not showing up, try logging in again into the WebApp. -Paul

If you send the install command to your agents it will detect an already installed Bitdefender endpoint or it will install it if it's not present. Bitdefender does not allow 3rd party applications to edit policies at this moment. Check to see that you don't have an antivirus policy configured under the Server Admin -> Configuration that disables manual antivirus management. First start the Bitdefender trial from the WebApp -> Antivirus -> License (if you haven't already done so) and then from the WebApp -> Antivirus -> Agent Status you can deploy the antivirus endpoint. -Paul

Hi Mark, Release notes are in the about section of the Pulseway Manager for the Windows agent. We usually only announce major product improvements but we will consider extending the granularity of our announcements. -Paul

Hey Mark, Agent version 8.8.4 was released on Monday and it takes about 24 hours to propagate so I think you may be confusing this with the solution 8.8.3 release. -Paul

Hi @Milind Patel, We enforce the first few posts of new members to go into a moderation queue in order to combat forum spam. I can check to see what has happened with your post, can you please tell me what topic subject you've used? -Paul

Hi there, Can you let me what antivirus product (if any) you have on the agent and client side? -Paul

Hi @flydev, Apologies for that. Our hosting provider GigeNET had a scheduled network maintenance which was expected to upgrade the network infrastructure and it has caused continuous interruptions for the storage network used by the database clusters which eventually has caused the database connection to be interrupted. Our team has identified the issue and resolved it. All services are now operational. We apologize for the inconvenience caused. -Paul

Hi Nathan, Apologies for that. Our hosting provider GigeNET had a scheduled network maintenance which was expected to upgrade the network infrastructure and it has caused continuous interruptions for the storage network used by the database clusters which eventually has caused the database connection to be interrupted. Our team has identified the issue and resolved it. All services are now operational. We apologize for the inconvenience caused. -Paul

Preconfigured MSIs are, well, preconfigured with a set of agent-specific credentials and the URL of the server where it needs to connect to. The best part of these MSIs is that they will also be automatically placed in the Organization, Site and Agent Group of your choice so as soon as new systems register, endpoint, antivirus and patch management policies kick in. -Paul

@WYE, I've removed the SERVER property from your msiexec line as it is not necessary. Preconfigured MSIs contain the server already. @PlaceboMessiah, Once you have a preconfigured MSI, you can just send them to your clients and they can install it just like any other application and they will not be prompted to enter any credentials. -Paul

Can you please send me the API request with * instead of your actual password as a PM? -Paul

Hi @pim, After too many invalid authentication attempts we block your IP address. You should use the your username and password for the API v2. Documented here: https://api.pulseway.com/#authentication. -Paul

Hi @Mr. C, We use static code analysis to ensure that our code doesn't contain any vulnerabilities along with industry standard procedures for reviewing and testing code and binaries before any release. -Paul

Hey @Tim Hall, The error indicates a problem with the server. On the server side, open the Pulseway Admin (if there are any errors upon starting please post a screenshot here) and then go to the Server Settings and enable logging. Try to register the system again and after the error message shows up send us the server logs from the c:\logs folder (archive the folder as there will be more than one file) to the email address: support@pulseway.com. -Paul