Paul

Hi there, Check out the PSA REST API's here: https://api.psa.pulseway.com/. The link you have provided is for the RMM. -Paul

Hi @BShevchuck, In that case the server name is: psa.pulseway.com . Let me know how it goes ! -Paul

Hi Tor, You'd need the msi to be stored in a publicly accessible web server but you can put it over some complex path or file name so it wouldn't be easy to find. -Paul

Glad I could help! -Paul

Hi Tor, That's probably a policy from the Server Admin -> Configuration (or Systems -> Sites if you are on the Pro plan). Look at the Organization, Site and Agent Group to see if there's a Patch Management Policy assigned. -Paul

Hi there, We have indeed changed the messages for the user sessions to match the exact wording using by the operating system. We usually post in the release notes major changes to the platform so this is not a noteworthy change. -Paul

Hi David, We are in the process of introducing API keys which will allow executing tasks for accounts with 2FA. In the meantime you can disable 2FA and use a long password or wait for the API changes. -Paul

Hi Nate, Unfortunately we have do not have a personal plan at this moment however if you are interested in giving a go for our Teams plan we can offer a trial using your gmail address as well. -Paul

Hi Lars, You can enable CPU, RAM and HDD notifications from the configuration file at: /etc/pulseway/config.xml. Let me know how it goes. -Paul

Hey Peter, That's odd. Please PM me your config.xml file and I'll look into it. -Paul

Hi Nick, Many thanks for the report. Our development team has confirmed this as a defect and we're working on a fix. I'll keep you posted with updates as I get them. -Paul

Hi Ryan, Please PM me the config.xml file and I will review it. -Paul

Hi Ryan, It seems that your configuration file is broken. I'd reinstall the package and pay extra attention when editing the file to avoid breaking the XML structure (ideally change only the values that are between double quotes for starters and keep backup copies). To register your system use the pulseway-registration command. -Paul

My apologies, we do support Windows Server 2008R2 however Windows Server 2008 is not supported. Are you sure that the button is not disabled because of a configuration lock? Also make sure that you can load and use the WindowsServerBackup PowerShell module. If all's ok, you could try to force enable it by running this PowerShell command: Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\' -Name 'MonitorWindowsServerBackup' -Value '1' -Paul

Hi Joe, You can't. Pulseway uses PowerShell cmdlets to integrate with Windows Server Backup which are not supported on Windows Server 2008R2. -Paul

We've launched support for arm64: https://www.pulseway.com/download/pulseway_arm64.deb. Enjoy! -Paul

Hi Shean, Are you logging into https://my.pulseway.com? If so, what is the error message? -Paul

Android pushes the automatic updates in phases to avoid DDOS-ing itself when a popular app gets updated. I think all devices get the update within a week though. -Paul

Is that a Windows system? Also are you running version 8.8.9 on your phone? -Paul

Hi Jeremy, Unfortunately Bitdefender doesn't support yet creating policies through their APIs however you can definitely deploy the Antivirus software using the default policy in the GravityZone and then customize it directly from their portal at any time. -Paul

The process is simple: Detect if the software is installed and if not download the installer and run it silently. -Paul

Hey Cristi, Please reach out to support@pulseway.com and we can assist on recovering access to your account. -Paul

Here's a remote wipe script you can use: https://github.com/paulcsiki/pulseway-scripts/blob/main/remote-wipe/report-bitlocker-status.ps1 -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