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

Yes Josh, apologies again. The root cause of the issue is impacted disk I/O where the SAN has experienced multiple disk failures at the same time greatly reducing I/O capacity. We'll announce tomorrow a maintenance window for the window where we will transition to a SSD-backed SAN which will greatly increase the performance of our cluster. Update: 5:14PM - We're down again. We've decided to switch to the new storage now. Update: 5:50PM - We're 20% done with the move to the new storage, we anticipate another 2 hours before we can restore service. Update: 6:24PM - 69% done with the move. Update: 6:58PM - Move completed successfully, databases are starting up. -Paul

Hey everyone, Apologies for the post-Halloween scare. We've worked with the hosting provider and have restored the service. We will be announcing later this week a maintenance window when we will be switching to a more modern storage solution. -Paul

The Pulseway Manager app will not show settings overridden by the endpoint policy but they settings do take effect in the monitoring service. Sorry for the confusion caused. -Paul

Excellent, glad to hear you've managed to get it installed. -Paul

It looks like the Pulseway agent isn't even installed. That's odd. Your best bet would be to copy the Pulseway folder from another computer and then manually register the service. Alternatively try using a tool such as CCleaner to remove the Pulseway app registration from the registry. -Paul

Hi there, Try running the following command as an administrator and then restart the Pulseway Manager app: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\InstallUtil.exe "C:\Program Files\Pulseway\PCMonitorSrv.exe" -Paul

Hi there, You'd keep the double quotes in the script. -Paul

Hi there, If you have configured the Autotask integration from the Integrations page in the WebApp, you do not need to configure it again within endpoint policies. You get to pick which RMM Organizations, Sites and Agent Groups will forward notifications into tickets from the integration page. -Paul

Hey @TimStark, Please PM me the details and I'll work with you on getting it done. We do not provide any way of removing archived notifications within the product but we can organize an once-off exception for you to permanently delete the data but we'll need to go through a couple of steps, including identity verification. -Paul

Can you try to run it within a command prompt running as an administrator using this command? This will also generate an installation log file, please send us the log file in the event that the installation still errors out. Replace the Pulseway_x64.msi with the file name of the MSI. msiexec /i Pulseway_x64.msi /l*v install.log -Paul

Hi there, Can you look under the Account -> Manage Systems (there you should see all 3 systems and also have the ability of removing one of them). -Paul

Hi Evan, winget is an msix (Windows Store Component, source) that must run in a per-user sandbox which is not available when running from the machine account (SYSTEM). You could force it to run against the logged in user (if any) through psexec but you'd need to distribute it somehow. -Paul

Hi @nateb, We collect sample every minute but report only min, max and avg values for the day. -Paul

The recommended way is to get a new Pulseway server installation with the new domain and move endpoints using a script as documented here: -Paul

I have recently built a similar script but mine doesn't ignore NPCAP, feel free to issue a pull request to change it: https://github.com/paulcsiki/pulseway-scripts/blob/main/enroll-network-interfaces/enroll-network-interfaces.ps1 -Paul

Hi Mickey, To eliminate everything try with an administrator vSphere account and make sure that the port 443 is accessible. You should be able to connect the VMware server module to an ESXi server or a vCenter server. -Paul

Hi there, At this moment it's not possible to override the default notification priority from the user support request. -Paul

Hi @AMC, Based on the documentation, the DomainCredential parameter says: We run PowerShell in a non-interactive mode, this prevents inputs from being triggered. You can provide a PSCredential object instead of the username and that should do the trick. $password = "ThisIsAPlaintextPassword" | ConvertTo-SecureString -asPlainText -Force $username = "contoso\Administrator" [PSCredential] $credential = New-Object System.Management.Automation.PSCredential($username, $password) Rename-Computer -NewName "NewComputerName" -DomainCredential $credential -Restart -Paul

Well yes, you can just export the configuration settings of an agent, just look for the "Export Settings" textual link at the bottom of the Pulseway Manager app. -Paul

Oh, I see what is the problem now. It is skipped because it contains the same identifier as the previous host. Try changing the identifier field slightly and see that it will import now. Use only hexadecimal characters (0-9a-f). Let me know how it goes. -Paul

I was able to successfully import the Host 11 configuration on my PC: -Paul

Hi there, Can you PM me the original XML and then the changed one? It should work. -Paul

The form should be resizable. Do you use a screen DPI other than 100%? -Paul