We reinstalled Pulseway on a re-imaged system and after the install we noticed issues. In the patch mgmt section, the status was "assign failed" in red. We rebooted the system and then the service was not starting. We checked the service, it was set to start automatically and in the event log it was generating this error: "Service cannot be started. The handle is invalid" We removed the system from Pulseway, uninstalled, and reinstalled. Service is starting normally, but still getting the same issue of the patch policy failing to assign. I tried moving the system to another group that did not have a patch policy at all and got the same result.
I've implemented a script that retrieves and stores the Windows Build Version number to a custom field in the system overview. It works fine on MOST systems. However, there are a small number systems that are unable to run the script. The error message displayed includes: Start-Process : This command cannot be run due to the error: The system cannot find the file specified.
I used the "Insert Output Variable Code" in the script and verified that it includes the inserted text "Start-Process -FilePath "$env:PWY_HOME\CLI.exe" -ArgumentList ("setVariable .....".
For some reason, a few systems do not seem to have the environment variable PWY_HOME set.
It appears that these systems are using the Enable PowerShell User Impersonation option under Pulseway Manger > Settings > Runtime.
What is the easiest way to make sure that all of my systems have the PWY_HOME variable set so that any future scripts will not fail because of a missing environment variable?
I had installed Pulseway and then wanted to delete it but I was not able to find Pulseway in the control panel uninstall feature and so I tried manually uninstalling files but that also did not work. I tried running the .msi installer again but an error came up saying that Pulseway is already installed but it still was not showing up. Please help me with this.
TL;DR: Align timezones across reporting and web interface.
When raised during our trial to engineering, the feedback is that browser displays local time, and reports are generated using UTC.
The misalignment is visible in my example shown where a report shows a system was back online at 05:32:07, but it actually and factually came back online at 06:32:07.
Suggest either including "UTC" in the report, or allowing time zones to be configured globally or per site.
Also noticed, that the "Generated at 04 Sep 2020 01:20" footer on the report is 6 hours behind GMT (report generated 07:20am GMT), so this could also do with being aligned accordingly.