Paul

Yes, glad to hear everything is working well now . -Paul

That would be https://instanceName.pulseway.com/app/main/setup/guide but it looks like you've deleted the XML end comment marker. This section is an XML comment and it's ignored by the Pulseway agent: <!--Account Information - Username: administrator - Password: *** - UseCustomServer: enable this option only if you have a dedicated Enterprise Server assigned to your account - CustomServerAddress: ***.pulseway.com However it's missing the end multi-line comment marker. It should look like this: <!--Account Information - Username: administrator - Password: *** - UseCustomServer: enable this option only if you have a dedicated Enterprise Server assigned to your account - CustomServerAddress: ***.pulseway.com--> -Paul

The correct configuration file name is /etc/pulseway/config.xml and it appears that you've removed the double quotes after each XML attribute. Refer to the Setup -> Guide section of the WebApp for a sample configuration for the Linux agent. -Paul

Pulseway Remote Desktop is not available on the Pro plan at this time nor it's available for purchase as an addon. If you go for the Team plan you get 3 RD concurrent sessions for free. -Paul

Hi there, We've sent an email to the android developers support but we didn't get any response yet. Due to the nature of this issue, there is nothing we can do about it as it's an OS bug. -Paul

Hi there, Do you require a boot password during POST? Do you use Bitlocker or a similar encryption software? If so, Pulseway cannot enter the password at that time as the network stack and Windows services are not running at that time however if you are stuck at the Windows logon prompt then you can enable the Login feature and you will be able to remotely login into your computer from your phone. -Paul

Hi there, Thank you for trying Pulseway and taking the time to write your experience with it. Pulseway is not a virus and once it's uninstalled from your systems it will not leave anything behind. I can try to diagnose your system errors if you would post some screenshots or more information of what's happening. PS: Pulseway will never interfere with 3rd party products so if your antivirus product has stopped it can be related to the fact that system errors are showing up after a boot. -Paul

Hi Darien, Thank you for your feedback. We're definitely going to consider introducing another level of access control for teams so you can specify which accesses on systems too. As for notification rights, as long as you have access to a system you will receive notifications. We're going to be adding a way of unsubscribing from notifications (based on an org/site/agent group/system?) at an account level in a future release. -Paul

We have a Pixel 2 XL ourselves and we've reproduced the issue too. -Paul

Hey everyone, I've just found out that this is a more wide spread issue as it's affecting other apps as well. It appears to be due to an update: https://productforums.google.com/forum/#!topic/phone-by-google/Nfqx7JT0J9g. Go to Battery – Settings (three vertical dots) – Battery Optimization, open the All apps section from the drop down menu, go to Pulseway, and tap on “Don’t optimize.”. Let me know if this resolves the issue. -Paul

Thanks, we'll investigate and get back at you. -Paul

Hi there, I've checked your account and I can see that everything is setup properly (I see that it was registered 27 minutes ago). Can you try again to see if PUSH notifications are sent to your Pixel 2 XL or they only reach out your iPhone and iPad? -Paul

Sorry for late update. Please use the following KB article to batch reconfigure your Windows systems: https://intercom.help/pulseway/agents/migrate-agents-to-use-an-authentication-token-via-psexec. For macOS and Linux we do not remove the registration info, a simple restart of the systems (or restart of the Pulseway service) will do. Due to the nature of the problem, it's not the 6.0 software that caused this but an error with a migration script on our database which was corrected a minute later but it was a minute too late. This caused the agents to stop and deconfigure so a software rollback will not restore the agents. We apologize for the inconvenience this causes. -Paul

Hi there, It appears that there was an error while migrating your instance to the Pulseway 6.0. While we've taken steps to prevent this from happening some instances caused the agents to deconfigure. We apologize for the inconvenience this causes and we're working on setting up a KB article to automate the reconfiguration of your systems in one go. Our main focus is to get you back online ASAP. -Paul

Hi Matt, The PSA development team is investigating the issue with top priority. Thank you for your report. -Paul

Hi Martin, I like the idea! We'll definitely be considering this . -Paul

Hi Levi, Unfortunately we had to drop the integration we were building with a 3rd party software due to last minute disagreements so we are going to be improving our own RD in the following months. -Paul

Hey Nathan, We do support 2FA by email, why do you consider that not to be compliant? Also I'm excited to let you know that we have plans to support OTP (One Time Passcodes) and PUSH-based authorization in the future. -Paul

Hi Jonathan, Most of our development team is focused on getting the "Central Management" feature out and the rest is working on the Remote Desktop functionality. You can expect to see the central management release in about 2 weeks, it's going to be awesome ! -Paul

We will run maintenance tasks and apply updates to the Pulseway PSA servers on each Friday from 8AM until 9AM Irish Standard Time. -Paul

Hey guys, We're almost ready for a closed beta and guess what, both of you are on the list to get early access . -Paul

Thanks Max for sharing this with everyone . -Paul

No updates yet I'm afraid. -Paul

Simply rename the old symbolic link using the: command then create a new symbolic link using this command: -Paul

It's possible that you've setup powershell impersonation in the Pulseway Manager -> Settings -> Runtime and the user you're impersonating the scripts is not part of the local Administrators group. -Paul