Hi Serge,

 

We plan on supporting restarting into safe mode with networking in the future. Thank you for your feedback.

 

Regards,

Chris

Pulseway Support

Hi Dave,

 

Welcome to the Pulseway community.

 

Pulseway has limited support for software automation and patching is not currently supported. We definitely plan on adding support for patching into Pulseway so we've noted your feedback on our backend system.

 

Regards,

Chris

Pulseway Support

Hi Remko,

 

Device policies are stored on your account and you don't need to configure them on each system.

 

Regards,

Chris

Pulseway Support

Hi Michael,

 

We are unable to provide any ETA at this stage as we have quite a big workflow for features to reach the development todo list however rest assured that the cogs are set in motion and it will eventually be implemented in Pulseway.

 

Regards,

Chris

Pulseway Support

Hi Michael,

 

Welcome to the Pulseway community. We love the idea and we're definitely going to support scheduling commands in Pulseway.

 

Regards,

Chris

Pulseway Support

Hi Michael,

 

Can you please follow this guide over here to help you migrate your server from one machine to another?

 

Regards,

Chris

Pulseway Support

Hi Serge,

 

You can monitor Windows Backups by enabling the Event Log notifications with the following configuration:

Filter name: Failed Backups

Event Id: 4106

Event Source: Windows Backup

Log: Application

 

Regards,

Chris

Pulseway Support

Hi,

 

No, we don't have any other server other than *.pulseway.com and we don't host our servers in Amazon AWS. Are you using a Pulseway Enterprise Server?

 

Regards,

Chris

Pulseway Support

Hi,

 

From what client application are you chatting with your users?

 

Regards,

Chris

Pulseway Support

Hi,

 

Thanks for sharing your configuration with the community. We're glad to see more and more configuration scenarios.

 

Regards,

Chris

Pulseway Support

Hi,

 

You need to allow outbound HTTPS (TCP 443) connections. No need to open inbound ports.

 

Regards,

Chris

Pulseway Support

Hi,

 

Can you please send an email to support [at] pulseway [dot] com? I will escalate your request to the operations team.

 

Regards,

Chris

Pulseway Support

Hi Bill,

 

Yes, the Dashboard app will not timeout if you leave it opened for an extended period of time.

 

Regards,

Chris

Pulseway Support

Hi Darfare,

 

There was a problem with the agent-client handshake in certain circumstances. Our development team has fixed it and we published the changes immediately. We apologise for the inconvenience.

 

Regards,

Chris

Pulseway Support

Hi Darfare,

 

We've made some changes on the server side, can you please try again now?

 

Regards,

Chris

Pulseway Support

Hi,

 

Welcome to the Pulseway community.

 

Pulseway app on the computer is the Pulseway agent. To monitor your systems, you need to install an agent. See the get started tutorial here.

 

Regards,

Chris
Pulseway Support

Hi Darfare,

 

We've replied to your email with some diagnostic questions, please reply when you have a moment.

 

Regards,

Chris

Pulseway Support

Hi,

 

Thank you for your report. The development team will look into it.

 

Edit: Can you please contact support [at] pulseway [dot] com?

 

Regards,

Chris

Pulseway Support

Hi affer,

 

The Remote Desktop libraries will propagate to the Pulseway Enterprise Servers in a maximum of 36 hours.

 

Regards,

Chris

Pulseway Support

Hi Darfare,

 

The error your happens when you restart the Pulseway service and the client application had an outdated list of sessions. This is resolved by simply waiting for the list of sessions to refresh (15 seconds) or closing the session list window and opening it one more time. If you continue experiencing problems please contact support [at] pulseway [dot] com and I will escalate your request.

 

Regards,

Chris

Pulseway Support

Hi,

 

An update on this: 

We have published the new Remote Desktop components and the update is rolling out now. 

In order to speed up the update process, simply restart the Pulseway service on the computer you are trying to connect to.

 

Regards,

Chris

Pulseway Support
 

Hi,

We did not release the remote desktop components yet. We plan on publishing them today.

Regards,

Chris

Pulseway Support

Hi,

 

Monday we are going to publish the remote desktop component updates.

 

Regards,

Chris

Pulseway Support

Hi,

 

We are in process of releasing the Pulseway Remote Desktop Release Candidate to the public and it is being published in stages. We will announce when the Remote Desktop libraries are fully released.

 

Regards,

Chris

Pulseway Support

Hi Chuck,

From the looks of it, Pulseway is connecting to the internet through a transparent proxy. Note that each host it has connected to, the port used is 8888.

We don't recommend putting Pulseway behind open HTTPS proxies as it might expose your Pulseway login credentials.

Regards,

Chris

Pulseway Support