Brant

I've recently disabled powershell.exe for users to run directly and was notified by those users that they've seen a Windows Script Host error. The error is C:\PCBP\UnitrendsScripts\ApplySambaCredentials.vbs, line 14. That line leads back to a call on powershell.exe to run ManageSambaCredentials.ps1. Since this is the only change I've made in recent memory that would cause this behavior, is it not possible to run Unitrends Backup Agent if powershell.exe is disabled for the user? The comment in the .vbs states "This script is necessary so the ManageSambaCredentials.ps1 powershell script call be called by the system with no visible window." Any information about this would be appreciated.

Hi Jamie. Restarting the PW service seems to have done the trick. I'll watch it throughout the day to confirm. Thanks again, Brant

What is the proper way to disable a system from running network discovery probes? I no longer need device discovery on a network, and have removed the system from being designated as a probe, but it is still running scans daily via 'C:\Program Files\Pulseway\Probe\Nmap\nmap.exe'.

Thanks WYE!

I checked this a.m. and the program entry listed above in the registry was updated to reflect the installed version 20.9.1.0 after some time. I'm still curious that if I can force update these values or if there is a trigger that updates them periodically (4, 6, 12 hrs, etc.)? I don't see anything in the Task Manager except the PulsewayServiceCheck. Does anyone know how often are the application snapshots are refreshed/updated in "HKLM:\Software\MMSOFT Design\PC Monitor\InstalledApplicationsSnapshot"?

I've written a script that retrieves the application name, publisher and version from the registry entries located in "HKLM:\Software\MMSOFT Design\PC Monitor\InstalledApplicationsSnapshot". How can I make sure the software versions listed in this location are updated to the latest version of the applications installed? Is there a way to force update these records? For example, I have a mismatch in a system that the PW web dashboard is reporting Citrix Files being at version 20.9.1.0 (which is correct as of the last 24 hours), and the local registry entry for this application under the PC Monitor\InstalledApplicationsSnapshot is still reporting the previous version 20.7.7.0. $exportPath = "C:\temp\IT\" $exportFile = $exportPath + "installedApplications.json" $objArray = @() $installedApplications = Get-ChildItem "HKLM:\Software\MMSOFT Design\PC Monitor\InstalledApplicationsSnapshot" foreach($item in $installedApplications){ $obj = New-Object PSObject $obj | Add-Member -MemberType NoteProperty -Name "Id" -Value $item.GetValue('Id') $obj | Add-Member -MemberType NoteProperty -Name "Name" -Value $item.GetValue('Name') $obj | Add-Member -MemberType NoteProperty -Name "Publisher" -Value $item.GetValue('Publisher') $obj | Add-Member -MemberType NoteProperty -Name "Version" -Value $item.GetValue('Version') $objArray += $obj } $objArray | Sort-Object -Property Publisher, Name | ConvertTo-Json | Out-File ( New-Item -Path $exportFile -Force) $jsonOutput = Get-Content $exportFile | ConvertFrom-Json | Format-Table -Property Name, Publisher, Version -AutoSize Write-Output $jsonOutput

Hi Paul, Windows 8 and Windows 10. The impersonated user is local. I removed the option for the impersonated local user on one Windows 10 system that is part of AD and reran the script. It will return the set variable PWY_HOME as "C:\Program Files\Pulseway" so it appears to be the difference of the impersonated user option.

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? Thanks, Brant