Jump to content

Paul

Administrators
  • Posts

    1739
  • Joined

  • Last visited

6 Followers

About Paul

  • Birthday 11/23/1991

Profile Information

  • Gender
    Male
  • Location
    Dublin, Ireland

Recent Profile Visitors

15811 profile views
  1. 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
  2. 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
  3. 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
  4. 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
  5. 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
  6. We've just released the 9.3.1 Linux agent version which resolves the issue. I apologize for the inconvenience caused. -Paul
  7. 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
  8. 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
  9. Hello everyone, We're investigating the issue and will come back with an update as we hear back from the development team. -Paul
  10. 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
  11. Paul

    Pulseway down?

    Hi Billy, We're looking into it. I'll provide an update as soon as I have it. -Paul
  12. Update: The database server has finished loading all the databases and the service is now restored. -Paul
  13. We do have a DR plan, the problem with it is that the DNS TTL is set to 24 hours. We're still evaluating our options. -Paul Update: The storage gateway is now online and our database cluster is starting up. -Paul
  14. Nobody likes such situations but everyone's frustration is warranted. We keep asking our hosting provider for an ETA but we haven't received any so far. Our DR committee is evaluating the time it would take to restore the service in a failover DC. -Paul
  15. Some more context for this situation: The hosting provider has rebuilt their storage gateway and they are having stability issues with it. Right now they are working on restoring it. -Paul
×
×
  • Create New...