JohnnyJoker

How didn't I notice this before?! This is great and I feel a little dumb, thank you

Hey, I'd also second this. It would be great if we were able to select different notification sounds for critical/important/elevated/normal levels. Jonathan

Thanks for the confirmation Paul! I've snapshotted the server (just in case), applied IISCrypto Best-Practices and restarted. The (previously) only database on the server and the corresponding application still work and the Pulseway database server switch went without a hitch. Thanks everyone!

Thanks for the tip - would've been quite easy but sadly I get a fatal error: The target SQL Server resides on a Windows Server 2016 - maybe that's a new one? I don't see any failed login attempts in the target SQL Server's Error Logs nor any errors regarding this process in the Windows Event Log. With SQLCMD the Connection succeeds and I can query tables. Any ideas? Edit: After some thinking - Server 2016 out of the box has different cipher suites and protocols active than 2012R2 and I have the idea to run IISCrypto (https://www.nartac.com/Products/IISCrypto) on the SQL Server and to try best-practices but it would be better if someone knows what to (de-)activate ;)

Hello, we'd like to move our pcmonitor database from the current SQL Server (2014 Standard) in one Domain to another SQL Server (2016 Enterprise) in a different domain. The Pulseway Enterprise/Admin Server won't change and is already a member of the target domain. As far as I remember the process would be: Stop Pulseway Services Backup DB on old SQL Server Create SQL Login for the Service on the new SQL Server Restore DB on new SQL Server Edit the connectionstring in the Registry (HKLM\SOFTWARE\MMSOFT Design\PC Monitor Admin\DatabaseConnectionString) The connection string is encrypted - what would be the required format? Edit the connectionstring in the Hosting folder for the follwing web.config files ..\Hosting\Service\web.config Start Pulseway Services Did I miss anything important? If not, all I'd need would be the format of the connectionstring in the registry Cheers, Jonathan

Worked!

Hey, it seems the Download Link (and the Page hosting it) is down?!

Isn't this the Linux Subforum? I just came here and had a good laugh when I read HKLM Where is the ComputerIdentifier for Linux Agents? regards, Jonathan EDIT: Found it! Please delete the /var/pulseway/pulseway.id and restart the Pulseway daemon.

Okay, so I basically picked the wrong role Works like a charm now.

Hello dear friends of monitoring We're using SQL 2014 Enterprise Edition in production and it seems I can't setup the SQL Server Module. It's a named Instance and Connection Tests succeed. I've tried with Windows Authentication (Service runs as Local System) and a dedicated SQL Login with serveradmin role (not using a Domain Account there) but it shows the same behaviour. Also I have installed "Microsoft SQL Server 2008 R2 Management Objects (x64)" (Version 10.50.1600.1) and "Microsoft SQL Server System CLR Types (x64)" (Version 10.50.1600.1) but there are also the x86 Versions (without (x64) in their name - Version 10.51.2500.0) installed or rather were installed with the SQL Server 2014 itself. When I try to install them from a fresh download (https://www.microsoft.com/en-US/download/details.aspx?id=16978) the setup tells me that there is already a newer version installed. On the Client (Android App) it can't load any information from the SQL Server. I can see The Databases but can't do anything else. See attached trace.log and Screenshot of Programs and Features of said Server. Thank you and kind regards, Jonathan trace.log

+1 on the mountpoints and storage events Our new MS SQL Server will utilize mountpoints instead of drive letters which we would like to monitor with Pulseway. kind regards edit: My workaround for this is to setup System\Performance Counter for each Mountpoint found under "Logical Disk" just for viewing purposes and alerts through Notifications/Counters following the same procedure and additionally defining the treshold there. It's not as dynamic and easy to setup as the Harddisk Monitoring.