Jump to content

PFMsupport

Members
  • Posts

    4
  • Joined

  • Last visited

  1. The issue is still present yes. Each client we connect to appears to work fine after that first 3-4 minutes to connect so they are likely updating after our connection attempt. We still have over 550 terminals to connect to and do maintenance. Is there a way to trigger client updates without attempting to connect?
  2. Seems as though our attempts to connect are triggering an update clientside, then when it is finished it will let us connect. Just a thought.
  3. Since Pulseway forced an update to 9.7 roughly a week ago connecting to clients has been extremely difficult. Almost 100% of the time when attempting to remote control via the app it sits at "Starting remote control Session..." for about a minute before giving the message in the attached image "Connection timeout while trying to start the remote control session." Sometimes the systems you are trying to connect to will go offline in Pulseway after the failed attempt; however, they are most certainly still online since I can RDP from systems right next to them that I also happen to be connected to via Pulseway. They will come back online in Pulseway a minute or two later and then we can connect. This happens across 149 sites almost every time, it happens to all Support staff in two offices in different areas of the country working for different companies as well as to the same Support staff working from home. All outgoing connections are rock solid, usually fibre. What's more the sites we are connecting to are working fine. So much so that when you eventually get a connection to the client system (it will connect after retrying 2-3 times) the other terminals at the same site will give the same problems, even though you are still connected to other terminals on the site, so clearly the internet is working fine. Again this is new to 9.7, we did not have these issues prior to that update. We have over 600 terminals to carry out manual software updates/maintenance on and this is taking forever.
  4. Little bit of background here, the company I work for supports approximately 400 systems for one of our clients, they use Pulseway for these systems therefore we are provided access to their Pulseway account to administer and support those systems. As a company we support thousands of other systems mainly on another non Pulseway platform we pay for. We were advised by the account owner that File transfer had been removed by Pulseway in a later version and we confirmed this since version 8 still has file transfer and version 9 just gives a message to use copy/paste instead. It is astonishing to us that file transfer is unavailable on any system with version 9 of Pulseway installed, this is a pretty standard feature for most remote software packages and it is rth reason we would not consider using pulseway in future. To make matters worse half of our support team receive a ping sound when they try to use Copy/Paste as suggested by the Pulseway app as an alternative leaving us to have to use VPN workarounds from systems to servers and back again. Any system with version 8 on has a working file transfer, though it seems as if Pulseway might be auto updating to 9 and so just sticking with v8 is not an option. Is there a reason why it was removed? Is it coming back?
×
×
  • Create New...