Paul

I was able to successfully import the Host 11 configuration on my PC: -Paul

Hi there, Can you PM me the original XML and then the changed one? It should work. -Paul

The form should be resizable. Do you use a screen DPI other than 100%? -Paul

From the WebApp under Server Admin -> Endpoint Policies, create or edit a policy and make sure that the User Support Request feature is enabled under the System category. Then under Server Admin -> Configuration assign the endpoint policy to the organization, site or agent group. From that point a tray icon will show up on the agents and they will be able to request support from there.

This is possible through the User Support Request feature which will trigger a notification in Pulseway and if you have the Pulseway PSA, Zendesk, Autotask or ConnectWise integration then a ticket gets created as well. -Paul

Thanks for the continued support Nick! You rock ! -Paul

Hi there, We have released an agent update (v8.9.1) which addresses this issue. The update will reach all systems within 48 hours. -Paul

I'll have to look into it tomorrow. I'll reply back when I have more information. -Paul

You should be able to get the IDs of tickets from another API call used to list tickets: /v2/servicedesk/tickets/search -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