Mark G38

You can just use the RunAs PowerShell module as well to accomplish this if you don't feel like dealing with psexec and having to distribute the package yourself. This works fine for logged in users. It will check if you have the RunAs module installed and if not, install it first. $ErrorActionPreference = "SilentlyContinue" if (!(Get-InstalledModule | Where-Object { $_.Name -eq "RunAsUser" })) { Write-Host "Not Installed. Installing" Install-Module RunAsUser -Force } $ScriptBlock = { winget install Microsoft.PowerToys --source winget } Invoke-ASCurrentUser -ScriptBlock $ScriptBlock Write-Host "Check Device to ensure PowerToys installed successfully." Exit 0

Why not just exclude the updates that are giving you trouble?

You should have saved backup codes when you set up your 2FA the first time, that allow you into the account. You have to select Try Another Way after entering your creds. Assuming you no longer have your old phone. Aside from this, if you don't have your codes, good luck, you should probably reach out directly to support.

lol. Settings - Show Session Health on the remote connection window.

Systems - Groups - Look at the total in the group assuming you have them set up as each client is a group/organization. Account - Manage Systems - Download CSV, Sort, Sum them. Server Admin - Configuration - Click Organziation/Group - Show Systems Or use API to make your own quick report.

Nope. Still not possible.

First off, you should never call Win32_Product. It's slow for starters, but it also triggers Windows to perform a Windows Installer reconfiguration on EVERY single msi app installed on the system. This is terrible and could cause apps to do a repair if it thinks it found an issue. The impact and possible damage that could be caused by running that command is not worth the hassle. I highly recommend instead you run this: Get-ItemProperty "HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*" | Where-Object {$_.DisplayName -eq "Pulseway"} You can grab the UninstallString and perform an uninstall that way. LMK if you need further assistance scripting this.

lol nope. This is not possible unfortunately, but it's something that is constantly requested by users of Pulseway. The thread below contains a list of improvements and links to the Feature Upvote section so you can upvote this very idea.

Yea no problem. If you go into Onboarding - Downloads - And then select your Windows download, you can make one for each customer, or if it's just for your internal machines (if that's what you use Pulseway for) then you just make the one, and you just do "Copy Link" and throw that link into your PowerShell script, call the URL to download the file, and then run it. It's an MSI so you can do silent install and it will fully register with Pulseway.

Don't run it against those machines. Create a scope in Pulseway and apply the job / script to that scope and don't include those machines. If you don't want to do that, then modify the script and using this. Change the PCNames to the ones you don't want it to run on, and then yea, it will just exit with a success if it sees those names. If you are on machines that are all PowerShell 3.0 and above, then you can also use $env:computername -in $Exclusions as well. -contains is PowerShell 2 compatible. $Exclusions = @("PCName1", "PCName2", "PCName3") if ($Exclusions -contains $env:COMPUTERNAME) { Exit 0 } else { PLACE REST OF CODE HERE }

I haven't experience these issues personally, but the only other thing I can offer as a possible solution than, is to tell your patch policy to NOT reboot anything, and then schedule a job/task on a recurring schedule to reboot the devices at a specific time.

I do not have the exact steps, and it's been awhile since I've actually done much inside Intune, but I do know using Intune, you can push scripts to systems. Pulseway can definitely be scripted using PowerShell, so there should be no reason you can't push Pulseway to the machine once it's inside Intune. I've pushed other RMMs in the past, such as Datto RMM via Intune.

Cool. Another step in the right direction. It would be awesome if we could have options for self-remediation on these. Hey if this process is stopped, attempt to start it, alert if start fails or alert all the time, etc.

Yep working.

That's certainly interesting. I'm doing mine directly through PowerShell, but I can't imagine that "should" make a difference. Maybe I'll install Postman and see if it has any different output on mine. EDIT - Unfortunately, I just downloaded and installed Postman and sent the request. My info still is populating as it should. Sorry man, was hoping I could help. Sounds like perhaps an issue with your instance. Are the other API endpoints working fine for you?