Paul

Came across this which seems to work if anyone else is having the same issues still: 
# "19041.867.1.8" = KB5000802
# "18362.1440.1.7" = KB5000808
$UpdateArray = @("19041.867.1.8", "18362.1440.1.7")
foreach ($UpdateVersion in $UpdateArray) {
    $SearchUpdates = dism /online /get-packages | findstr "Package_for" | findstr "$UpdateVersion"  
    if ($SearchUpdates) {
        $update = $SearchUpdates.split(":")[1].replace(" ", "")
        write-host ("Update result found: " + $update )
        dism /Online /Remove-Package /PackageName:$update /quiet /norestart
    } else {
        write-host ("Update " + $UpdateVersion + " not found.")
    }
}
exit 0

Hi @it4hoomanz,
We're making changes to the plans to be more accessible for everyone. Please PM me how many systems you're looking to monitor.
-Paul

Hi Matt,
Make sure that the gold image doesn't have the HKEY_LOCAL_MACHINE\SOFTWARE\MMSOFT Design\PC Monitor\ComputerName registry value. This will pick up the hostname as the computer name at startup.
-Paul

Thanks for the update Maruco. Glad to hear everything is clear now. We'll see how we can improve on the UX of the Agent Status page, I agree, this can be confusing.
-Paul

Hi Jamie,
You can remotely enable it through PowerShell:
Set-ItemProperty -Path 'HKLM:\Software\MMSOFT Design\PC Monitor' -Name 'DisableUserSessionTask' -Value '0' -Paul

Hello @MrNaz,
Thank you for the report. We have identified the problem and we're working on a fix. The fix will be included in the next release which is due to be out next week.
-Paul

Hi @MrNaz,
Thanks for the report. We have identified the problem and this will be resolved in the next release coming out next week.
-Paul

Hi there,
This is for HDD temperature sensor monitoring, the original post is here:
This will prevent some backup software from creating VSS snapshots, yes, you should still disable it if you see problems with your backup software.
-Paul

Thanks Paul!
I think I have worked around it by modifying the script "Set Pulseway Computer Name to Hostname" to use hostname.exe command:
...... $hostname = hostname.exe $PulsewayName = $VenueName +":::" + $hostname ...... Set-ItemProperty -Path "HKLM:\Software\MMSOFT Design\PC Monitor\" -Name ComputerName -Value $PulsewayName ..... I have some small changes to make but this is automating bringing in the customer name and hostname. We use a single agent file so it makes it MUCH easier to move them from the Server Admin screen if the name reflects the Customer (our host names are common to most customers). 
Cheers
Simon!

Thank you. We're looking into the problem right now.
-Paul

I've recently built this script which also identifies the serial number of the disk to fill in the ID field:
$query = 'SELECT VolumeSerialNumber FROM Win32_LogicalDisk where DriveType=3 AND Name=''' + $env:SystemDrive + '''' $serialNumber = (gwmi -Query $query).VolumeSerialNumber $count = 0 # rule 1: < 5000MB - Elevated Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('Id' + $count) -Value $serialNumber Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('Percentage' + $count) -Value '15' # not used Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('Priority' + $count) -Value '2' # elevated Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('SizeMB' + $count) -Value '5000' Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('UsePercentage' + $count) -Value '0' $count = $count + 1 # rule 2: < 2000MB - Critical Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('Id' + $count) -Value $serialNumber Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('Percentage' + $count) -Value '15' # not used Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('Priority' + $count) -Value '3' # critical Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('SizeMB' + $count) -Value '2000' Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('UsePercentage' + $count) -Value '0' $count = $count + 1 Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name 'Count' -Value $count Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor' -Name 'SendNotificationOnLowHDDSpace' -Value '1' -Paul

I've recently built this script which also identifies the serial number of the disk to fill in the ID field:
$query = 'SELECT VolumeSerialNumber FROM Win32_LogicalDisk where DriveType=3 AND Name=''' + $env:SystemDrive + '''' $serialNumber = (gwmi -Query $query).VolumeSerialNumber $count = 0 # rule 1: < 5000MB - Elevated Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('Id' + $count) -Value $serialNumber Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('Percentage' + $count) -Value '15' # not used Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('Priority' + $count) -Value '2' # elevated Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('SizeMB' + $count) -Value '5000' Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('UsePercentage' + $count) -Value '0' $count = $count + 1 # rule 2: < 2000MB - Critical Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('Id' + $count) -Value $serialNumber Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('Percentage' + $count) -Value '15' # not used Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('Priority' + $count) -Value '3' # critical Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('SizeMB' + $count) -Value '2000' Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name ('UsePercentage' + $count) -Value '0' $count = $count + 1 Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor\HDDList' -Name 'Count' -Value $count Set-ItemProperty -Path 'HKLM:\SOFTWARE\MMSOFT Design\PC Monitor' -Name 'SendNotificationOnLowHDDSpace' -Value '1' -Paul

Hi there,
We'll be releasing it next week .
-Paul

Hi Dwayne,
Please contact support@pulseway.com, you'll undergo an identity verification process and we'll release a new backup code for you to login. We're considering on dropping the 2FA new backup code registration method to increase the security, should this have happened after we would have dropped support for recovering account you would have lost access to your account and be forced to register another account with another email address. Keep this in mind next time you tick the "I have securely stored the backup codes" checkbox.
-Paul

Hi Martin,
I don't have an update to your feature request just yet. We do have it on our todo list to support more granular controls but at this moment it's not part of our Roadmap.
-Paul

When you run scripts through Pulseway they run as the local SYSTEM user which is the computer name with a dollar sign at the end. You could use a WMI query to get the username instead like this:
But make sure that you account for the case when there's no user logged into the system.
-Paul

Thanks Paul.  
I missed the info on the pricing page that explained that remote doesn't work on the free plan.  https://www.pulseway.com/pricing
 
That was quick. The feature is already available and working.  Connecting to the first system was super easy and straight forward.  I've only used it for a few hours but so far it looks like ill be paying for the starter plan since i only have a single system to remote to. 

Hi Dan,
This is not yet available as a native feature on Pulseway however I personally remembered the following powershell line whenever I needed to tell two processes apart using Pulseway:
gwmi win32_process -Filter "name='svchost.exe'" | select processid, name, commandline | fl -Paul

Well $env:USERNAME relies on the current user and Pulseway runs in the context of the SYSTEM account. Try using this instead:
$user= get-wmiobject -class win32_computersystem | select-object username wmic UserAccount where name=$user set Passwordexpires=true $username = $user.username if ($username -like '*\*') { $idx = $username.LastIndexOf('\') $username = $username.Substring($idx + 1) } net user $username /logonpasswordchg:yes It just removes the domain name or computer name from the username you get from WMI.
-Paul

Hi Cory,
It appears that there's a defect on this, we'll definitely be fixing this. Thanks for the report!
-Paul

Glad I could help!
-Paul

Thank you, it's working!  So far so good, I'll test from another location tomorrow but it looks perfect and like I'll be buying a subscription ... so far.  Again, thank you for letting me try before I plop down a few hundred for this.

Hi there,
Thank you for your feedback. I concur that our mechanism of informing users of upcoming reboots is rudimentary however we'll definitely work on improving it.
-Paul

Hi @morganc,
When you remove a system from Pulseway it's identifier gets blocked for a while. To get it registered again simply delete the ComputerIdentifier registry value from HKLM:\SOFTWARE\MMSOFT Design\PC Monitor and restart the Pulseway service.
-Paul

Hi Matt,
We're going to be adding ways to re-evaluate the notification condition using Automation Workflows (which is queued for this quarter).
-Paul