Jump to content


  • Posts

  • Joined

  • Last visited


About Paul

  • Birthday 11/23/1991

Profile Information

  • Gender
  • Location
    Dublin, Ireland

Recent Profile Visitors

16391 profile views
  1. Hi @Jerdal, Please contact customer support at support@pulseway.com. We'll help you recover access to your account. Please be advised that you will have to undergo an identity verification process. -Paul
  2. Version 9.6 is the latest version. Please note that the Windows Metro app is discontinued and it will cease to function later this year. Please use the WebApp instead. -Paul
  3. Thanks for letting us know. Did you change the resolution recently? Do you use a custom scale factor (DPI)? @Mark here's an interesting one for you. -Paul
  4. Hi @Starscreem, This is not the case. This needs to be done only on client machines from where you connect to other systems. Running the application as an administrator will enable the secure communication protocol TLS 1.2 which is required to ensure product security. -Paul
  5. Hi @techtedg, You can definitely do this through an automation script. You can create a custom field called "AssignedUser" and make it be of system scope. Then assign the custom field to the systems you want to name (you don't have to do it for all systems, the script I have built below will only overwrite the computer name for systems that have a custom field value assigned). Then you will need to create a powershell automation script, add an input variable that is bound to the custom field you've just created and use the powershell script below: $AssignedUser = ''; # this will get automatically generated for you when you create the input variable, you don't need to add this line if ([string]::IsNullOrEmpty($AssignedUser)) { Write-Output "Missing AssignedUser custom field value, aborting..."; exit 0; } $newComputerName = "$AssignedUser $env:COMPUTERNAME"; Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor' -Name 'ComputerName' -Value $newComputerName; Write-Output "Computer display name changed to '$newComputerName'."; exit 0; Let me know how it goes -Paul
  6. Hi @at26574, There was a problem with a cloud service that just got resolved. Can you try again now and let us know if everything goes well? -Paul
  7. The Pulseway service runs scripts under the local SYSTEM user. You will probably need to load the correct user registry and make changes there. -Paul
  8. It does get applied to all systems automatically unless you have turned off automatic agent updates. Does your systems not have the 9.3.1 windows agent? -Paul
  9. We've just released the 9.3.1 Linux agent version which resolves the issue. I apologize for the inconvenience caused. -Paul
  10. Hi @BromTeque, Many thanks for the detailed report. I've raised the alarm with the development team. I'll keep you posted with updates as I have them. -Paul
  11. We have identified the issue and have released the Windows Agent version 9.3.1 with the fix. This seems to be localized to users who have never set up global rules through the WebApp. We apologize for the inconvenience caused. -Paul
  12. Hello everyone, We're investigating the issue and will come back with an update as we hear back from the development team. -Paul
  13. Paul

    Pulseway down?

    Update: We seem to have experienced another storage disconnect which was promptly resolved. I apologize for the inconvenience this has caused. Work in underway to move away to a different hosting provider. -Paul
  14. Paul

    Pulseway down?

    Hi Billy, We're looking into it. I'll provide an update as soon as I have it. -Paul
  15. Update: The database server has finished loading all the databases and the service is now restored. -Paul
  • Create New...