Paul

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

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

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

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

We've just released the 9.3.1 Linux agent version which resolves the issue. I apologize for the inconvenience caused. -Paul

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

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

Hello everyone, We're investigating the issue and will come back with an update as we hear back from the development team. -Paul

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

Hi Billy, We're looking into it. I'll provide an update as soon as I have it. -Paul

Update: The database server has finished loading all the databases and the service is now restored. -Paul

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

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

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

Locking this thread, please use this thread instead as it has more context: -Paul

We're in contact with the hosting provider, the initial estimate is that it should be less than half an hour left. Sorry for the inconvenience caused, it seems that something didn't go as planned with their maintenance. -Paul Please reach out to your account manager for all billing questions. -Paul

Hi there, Apologies for this. Our hosting provider is running overtime on their scheduled maintenance. I'll post another update when the service is back up. -Paul

The service is now restored. We apologize for the inconvenience caused. -Paul

Hi Dan, For the past hour we've been working on resolving a storage issue with our hosting provider, please check out this announcement post over here: We will post updates as we have them. We appreciate your understanding. -Paul

Hi Alec, Apologies for that. We've installed an update to the EAP server and that went wrong. Everything should go right now. -Paul

Hi Tyler, Thank you for the report. We've managed to identify the issue and we're working on a fix as we speak. -Paul

You should see the same screen in Pulseway for Bitdefender, can you attach a screenshot of what you see? -Paul

Hey @DJB, Try running the commands in this KB article and let me know if that did the trick: https://intercom.help/pulseway/en/articles/964192-error-1001-the-specified-service-already-exists -Paul

Hi Darien, Yes. That would be the cause of the database server finally starting up. Apologies for the inconvenience. Databases are still starting, will post another update when all services are completely back up. Update: 7:10PM: All services are now fully operational. -Paul

We're providing updates in this thread: -Paul