mchristensen

@Mariale_Pulseway - Thanks. Been down that road already but willing to try again. The result was the certificate DigiCertGlobalRootG2.crt only supports TLS 1.3 whereas I need TLS 1.2. The migration turned this whole well established concept on its head, and even though we have future plans to eventually upgrade our Server Core version, it works just fine now as a Hyper-V solution. So I am turning to the forum to find an answer. Is there a different certificate by chance? I can't imagine that Pulseway would give TLS 1.2 the one finger salute when it is still being utilized. Any ideas would be most helpful, thanks.

Holy cow! Talk nostalgia... You guys helped me out way back in the day! Got another issue which has been a headache ever since the recent migration. My Server Core 2008 (still going strong) was working just fine with Pulseway up until this latest migration. Ugh. For years it worked. I was instructed to uninstall and reinstall by the migration team but now Pulseway Manager 9.14 says service is not installed. Checking the registry shows it is there but not able to load. Good news is that was the backup server. The main server still has PCM 9.14 installed with the original problem. The service is running but there is an error which states "an error occurred while making the http request to https.... This could be due to the fact that the server certificate is not configured properly with HTTP.sys in the HTTPS case..." After further research, it was determined to manually update the cert: DigiCertGlobalRootG2.crt however this one does not use TLS 1.2? We need TLS 1.2! Is there a cert available that provides TLS 1.2? So my first concern is getting Pulseway back to being operational on the main server. Then to somehow fix the backup server's PCM reinstallation. Ideas?

On the Android we have 4 as well listed as Set Filters, View Groups, Settings, & Share This App. I do not see an option anywhere that allows a restored status alert to remove the corresponding elevated/critical alert.

Hmm. I logged into the Monitor and the Dashboard but I am unable to find the "Clear badges on exit."

Maybe this feature exists and I just don't see it, but it would really be handy if on my HTC the "normal" status updates would remove the "elevated" and "critical" updates as to clear the phone vs. having to manually delete each one.

I am using the HTC Sensation over a 4g network. Would that matter though as wouldn't the signal go from the HTC -> PC Monitor servers -> my modem?

Excuse me, I'm using pfSense and I have both the NAT and Rules configured for UDP 9. However, even without the router in place and hooking up my system directly to the modem there still is an issue. I thought maybe I had a bum card but I've now tried 3 different connections with 2 being integrated with the options set in the bios. Just stumped as to why this isn't working out. Thoughts?

This has been an interesting project towards my next step with PC Monitor. 1) Removed router has culprit by directly plugging workstation into modem 2) BIOS settings are set, as well as settings within Device Manager 3) Enabled the Simple TCPIP services within Programs and Features of W7 4) Firewall is off however UDP 9 is allowed just in case. 5) Tried a second PCIe NIC and still no dice 6) BIOS for wake on PCIe enabled. 7) Wake on WAN over Internet is also set within PC Monitor Manager 4.1.2 Completely stumped. The app responds "sent" when router in place but "failed" when workstation is directly plugged into modem. NIC is Intel Gigabit CT Desktop Adapter. Thoughts?

THANK YOU! I really appreciate your willingness to hang in there. It looks really good on my phone. I got my own rig running for fun and I will feel better now while on vacation. Going to test the Wake Up feature later on. Again, thank you. Matthew

UPDATE: Well I made a little headway. I ran msiexec /a pcmonitor_x64.msi and it did install but when I open the interface it says "The service is not installed." I then went ahead and attempted a msiexec /i pcmonitor_x64.msi which returned the same error: "There is a problem with the Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor." I do have two identical systems running Core and both give the same error message. Is there a reason the Service is not installing? Please advise.

Sure did. Just to be sure I tried both x64 and x86 msi files. I doubt they're corrupt as the x64 did work just fine for a Server 2008 install. Just trying to figure out what I'm doing wrong for the server core CLI install. msiexec /i pcmonitor_x64.msi

Unfortunately I didn't see anything. I was able to install a different .msi through the same process. Any other ideas? My Virtual Server went down last night and I'd really like to be able to start it up by my phone. Thanks.

I have a Windows 2008 R2 Server Core running Hyper-V. I first installed the app on the Virtual Server and it works like a champ, great. I figured it would make more sense to install it on the Server Core however I'm having some problems. I've installed .NET Framework 4 and all of the Windows Updates. I then execute msiexec /i pcmonitor_x64.msi From there I receive a mid-install error: "There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor." Ideas? Thank you.