Search the Community

Pulseway Client Portal now includes a built-in chat function that allows the end user to communicate directly with a technician. This can be started automatically as a step in a troubleshooter, or you can give users the option to start it directly themselves. A summary of the chat is recorded and can be sent to the technician. Automation Workflows: Run assigned patch policy Start patching systems as they get added to Pulseway using the new Run Assigned Patch Policy action, now available for the System Registered workflow trigger. Remote Desktop Improvements Introducing Adaptive FPS to deliver the optimum resolution for the current network connection, resulting in an enhanced user experience.

A number of folks have requested the ability to manage bitlocker with Pulseway, so I thought I would share how I am doing this with Powershell scripts and Pulseway's custom fields feature. First, you will need to create a custom fields in Pulseway (Automation Tab --> Custom Fields). This fields should be a text variable that has the system context. I personally have 3, BitlockerKey, Protection Status (On/Off), and BitLockerVolumeStatus. BitlockerKey is probably the one most people will care about. . After Configuring the Custom fields, you will then need to create your PowerShell script. Notice you have inputs and outputs. You will want to click New for output. Name it what you wish, ensure it is a text variable type, and then turn on "set Custom Field Value" Now we toggle the flag for it being a windows powershell script. You should see in the top that it has created a comment #outputs with your defined output variable assigned the default value you gave it. Now we have our script: Update as of 4/18/2021, script now tracks 3 custom fields and will account for if a drive is encrypted but protection is off and no protectors have been added yet. # Outputs $ProtectionStatus = "na" $recoveryKey = "na" $VolumeStatus = "na" #region functions function Start-BitlockerEnable { Enable-BitLocker -MountPoint c: -EncryptionMethod XtsAes128 -UsedSpaceOnly -TpmProtector $today = Get-Date $scheduledtime = $today.Date.AddHours(23) [int]$SecondsToMidnight = ($scheduledtime - $today).TotalSeconds shutdown /r /t $SecondsToMidnight msg.exe * "Bitlocker Encryption has been enabled. A reboot is needed before the encryption will apply and has been scheduled for $scheduledtime local time. You can reboot before this if you prefer." #start-sleep 90 #msg.exe * "This Computer will reboot in 30 seconds to bitlocker Encryption" #start-sleep 30 #Restart-computer -force } #endregion functions #region execution $BitLockerStatus = Get-BitLockerVolume -MountPoint c: if ((Get-Tpm).tpmpresent -eq $true) { #If Volume is in the process of encrypting or decrypting the Volume status will not say fully. Don't make changes when it changes if (($BitLockerStatus.ProtectionStatus -match 'off') -and ($bitlockerstatus.VolumeStatus -notmatch 'progress')) { #NoBitlocker is enabled so run it. if ($BitLockerStatus.VolumeStatus -eq 'FullyDecrypted') { $recoverykey = $BitLockerStatus.KeyProtector | Select-Object -ExpandProperty recoverypassword if(!($recoveryKey)){ Add-BitLockerKeyProtector -MountPoint c: -RecoveryPasswordProtector } $newStatus = Get-BitLockerVolume -MountPoint c: $recoverykey = $newStatus.KeyProtector | Select-Object -ExpandProperty recoverypassword Start-Process -FilePath "$env:PWY_HOME\CLI.exe" -ArgumentList ("setVariable recoverykey ""$recoverykey""") -Wait if ($newStatus.KeyProtector -match 'Recovery') { Start-BitlockerEnable } } #Bitlocker must be Partially enabled where drive is fully encrypted, but protection is off and no protectors exist. #Typically this is using xtsAES128 so you may wish to disable-bitlocker, then re-enable it with your protectors and prefered encryption level. else{ Disable-BitLocker -MountPoint 'c:' $decryptInProgress = $true While($decryptInProgress -eq $true){ $decryptstatus = Get-BitLockerVolume -MountPoint 'c:' if($decryptstatus.VolumeStatus -match 'progress'){ Start-Sleep 2 } else{ $decryptInProgress = $false } } Add-BitLockerKeyProtector -MountPoint c: -RecoveryPasswordProtector $newStatus = Get-BitLockerVolume -MountPoint c: $recoverykey = $newStatus.KeyProtector | Select-Object -ExpandProperty recoverypassword Start-Process -FilePath "$env:PWY_HOME\CLI.exe" -ArgumentList ("setVariable recoverykey ""$recoverykey""") -Wait if ($newStatus.KeyProtector -match 'Recovery') { Start-BitlockerEnable } } } #BitLocker should already be enabled so log keys, volume status etc. else { $recoverykey = $BitLockerStatus.KeyProtector | Select-Object -ExpandProperty recoverypassword $ProtectionStatus = $BitLockerStatus.ProtectionStatus $VolumeStatus = $BitLockerStatus.VolumeStatus Start-Process -FilePath "$env:PWY_HOME\CLI.exe" -ArgumentList ("setVariable recoverykey ""$recoverykey""") -Wait Start-Process -FilePath "$env:PWY_HOME\CLI.exe" -ArgumentList ("setVariable ProtectionStatus ""$ProtectionStatus""") -Wait Start-Process -FilePath "$env:PWY_HOME\CLI.exe" -ArgumentList ("setVariable VolumeStatus ""$VolumeStatus""") -Wait } } else { $recoverykey = 'NoTpm' Start-Process -FilePath "$env:PWY_HOME\CLI.exe" -ArgumentList ("setVariable recoveryKey ""$recoveryKey""") -Wait } #endregion execution You can modify the above script as you wish. I personally have gone with a bit of a cautious approach where it will not skip the hardware check which will reboot the pc, but for me I prefer this approach to having it encrypt the drive without checking tpm is all good which could then result in the drive being encrypted and locking out the end user. At the end of all this, you now should be able to Both Enable bitlocker encryption as well as pull your recovery keys from pulseway like so :

After receiving a verification on my phone I get this nasty gram. So far: .Net 4.0 install was blocked because a later version was already installed. So I don't think it is a .net version issue. Any help would be appreciated. --Tim I blocked out the server name to keep it annonymous I blocked out the server name to keep it anonymous. Also, please ignore the localhost:8443 page. It is irrelevant as far as I know.

I've noticed lately that when I have a remote session live on a machine, my local keyboard input is not being accepted in items such as Notepad, Chrome, Outlook, etc. This seems fairly system wide and I'm not always able to replicate the problem. This is likely something to do with the keyboard forwarding method, but I can't isolate this myself. Also, this does occur on several different machines - not one workstation in particular. As soon as I close the remote session, the keyboard functions normally in my local Windows 10 environments. Good luck with this one - it seems very transient.

You can now trigger workflow executions from Performance Counter notifications and evaluate Name, Category and Instance in conditions to build even more customizable workflows for your IT processes.

You can now create interactive, conditional troubleshooters that can be used to ask questions, provide answers, and run self remediation scripts and tasks based on user input. Pulseway's Client Portal can be used to standardize IT processes, empower end-users and reduce the workload on your support team.

Hi Team, Has anyone tried the new feature custom titles? I have tried it with two applications and keep getting "Failed to read metadata". Can anyone help with this? Thank you, Sean Faria

Hey Fellow PW users, I've created a script which allows the system to change its name to %computername%-Current logged on username, which makes life a little easier when trying to remote to their computers on the remote control tool/Webapp. To get started, create your script in the script editor, in my example, Name: Update Computer Name with Logged on Username Windows/Powershell Code: $pwqusers = quser | Select-Object -skip 1 $pwquserfmt = $pwqusers.substring(1,22).Trim() -join "," Set-ItemProperty -Path "HKLM:\Software\MMSOFT Design\PC Monitor\" -Name ComputerName -Value "$env:computername-$pwquserfmt" Click Save. Next we create at new task, Name: Update Computer Name with Logged on Username Current Scope -> Windows Workstations Enable Scheduling -> (I've set it to run once a day) Every weekday (Monday to Friday), starting on 12 August 2018 at 09:00 (Australia/Brisbane) Scripts tab, Select/add your new script you just created and once that's done click save. You can now run the task on demand as well which will update all of the PC's in your windows workstations scope to Computer Name-Logged on usernames This works for RDSH hosts as well however it could get a bit of out hand if you have 5-10+ users logged in so I probably wouldn't recommend it to be used on servers. I Hope this helps you somehow, these scripts/suggestions come with no warranty and I bear no responsibility if this breaks anything, use at your own risk etc..etc.. Cheers, Quenten

I would really like to see an outlook add-in that can be pushed through office 365 to all users that would allow them to submit tickets with drop down menus for ticket type, sub-type, priority and description.

Using USB external hard drive as backup devices and each drive can be recognized if manually added to the notifications/storage screen but I need to know if there is a way to set this to be automatic when the drive is replaced either daily or weekly. Also, where would this be set globally for are servers being monitored. Currently have 8.6.8. Thank you, Todd Kollars Onsite IT Services

How would I get a ticket status to change to "client responded" when a client responds to a "completed" ticket

Hi. When running Dashboard as an ordinary user, it asks for the password of an administrator. Are there anyway we can let the dashboard be executed as a normal user, so we don't have to leave an unattended computer been loged in as administrator? Br, Martin

I would like to move away from using TeamViewer. LTT was just advertising Pulseway, I thought I would try it out. I installed the Remote Control Desktop client (6.6.3) and the Dashboard client (6.5.1), and proceeded to set up an organization, group, site, and policy. Then I downloaded the "Agent" client to the desktop I would like to be able to remote into. I installed, registered my product, assigned it to my group, and checked the "Enable Remote Control" box. I was under the impression this is all I had to do. Although both the Remote Control Desktop and Dashboard show the computer, I'm unable to "Start Remote Control Session". It's grayed out. Interestingly, I am able to view all of the system specs, and even successfully restart the computer via the website! What might I be doing wrong? Thank you for your time!

This script will check to see if a VPN connection with the given name exists. If it does exist, it updates the VPN connection. If it does not exist, it creates a VPN connection with the given values. Note: I believe Pulseway runs PowerShell scripts under the Local System account by default (unless you have defined PowerShell User Impersonation in the Pulseway Manager, I think). In order to expose the VPN to users, this script runs against the Global Phone Book (-AllUserConnection switch). Therefore, this script does not check for the existence of VPN profiles stored in individual user Phone Books. (If an existing user VPN profile exists, this script will create a new VPN in the Global Phone Book, as it will not be able to see the existing user VPN.) This script was developed and tested on Windows 10, but should also work on Windows 8/8.1. PowerShell VpnClient documentation: https://docs.microsoft.com/en-us/powershell/module/vpnclient/?view=win10-ps ################################ # VARIABLES $Name = "VPN" $ServerAddress = "vpn.domain.com" # IP Address or FQDN $TunnelType = "Automatic" # Values: PPTP | L2TP | SSTP | IKEv2 | Automatic $L2tpPsk = '[Insert PSK Here]' $AuthenticationMethod = "MSCHAPv2" # Values: PAP | CHAP | MSCHAPv2 | EAP $EncryptionLevel = "Optional" # Values: NoEncryption | Optional | Required | Maximum $UseWinlogonCredential = $true $RememberCredential = $true $SplitTunneling = $true $DnsSuffix = 'domain.local' ################################ # If PowerShell supports VPN configuration, apply VPN configuration if (Get-Command 'Get-VpnConnection') { # If VPN exists, update VPN settings if (Get-VpnConnection -Name $Name -AllUserConnection -ErrorAction SilentlyContinue) { Set-VpnConnection -Name $Name -AllUserConnection -ServerAddress $ServerAddress -TunnelType $TunnelType -EncryptionLevel $EncryptionLevel -AuthenticationMethod $AuthenticationMethod -SplitTunneling $SplitTunneling -DnsSuffix $DnsSuffix -L2tpPsk $L2tpPsk -UseWinlogonCredential $UseWinlogonCredential -RememberCredential $RememberCredential -Force } # Else, create VPN connection else { Add-VpnConnection -Name $Name -AllUserConnection $true -ServerAddress $ServerAddress -TunnelType $TunnelType -EncryptionLevel $EncryptionLevel -AuthenticationMethod $AuthenticationMethod -DnsSuffix $DnsSuffix -L2tpPsk $L2tpPsk -Force Set-VpnConnection -Name $Name -AllUserConnection -SplitTunneling $SplitTunneling -UseWinlogonCredential $UseWinlogonCredential -RememberCredential $RememberCredential } return Get-VpnConnection -Name $Name -AllUserConnection exit } # Else, exit with failure code else { return "Client does not support VpnClient cmdlets" exit 1 }

Hello, I created a windows agent config file by exporting from an existing installation with the Remote Desktop module installed, but when I use that configuration with a fresh installation Remote Desktop module does not install. Is this normal? Is there something else that needs to be done to have the Remote Desktop module install automatically?

Hello, We are long-term Pulseway customers but lately the Pulseway client has developed a bug and continuously uses up to 20%+ CPU utilisation. We logged this with Pulseway on the 4th of July this year but they have been completely ignoring the ticket. I regularly reply to the email thread for an update (at least once a week) but I am ignored. The only time I had a meaningful response was when I threatened to cancel our subscription. This was short lived and now I am back to being ignored with no status updates on my ticket. We like the product but we have a handful of servers with this bug and I am simply installing other monitoring products on them. Today I have sent my usual email to Pulseway support asking for a status update on my ticket but I'm certain I'll get nothing back... The next step will then be to install a better monitoring product like Infradog and to write the same post on Spiceworks so people know that Pulseway doesn't offer good technical support.

Hi all, I'm trying to follow the guide to starting to program a plug in but I'm falling at the first hurdle. I'm following the guide to "create your first plugin" https://www.pulseway.com/api/clientnet but when I get to where it says "From solution explorer rename "Class1.cs" to "SimplePlugin.cs" and open it. Now we need to add a project reference to our PulsewayClient.dll file which is located in the directory of Pulseway. See Figure B." I cannot for the life of me find a dll called PulseWayClient.dll. I presume it's taking about the installation directory of the pulseway agent, but this file does not seem to exist in any machine that I've checked and for what it's worth figureB does not appear to be of any help at all either. I feel I must be missing something perhaps completely obvious and I hope someone out there and point me in the right direction. Thanks in advance

In order to import a Pulseway configuration file you need to start PCMonitorManager (Pulseway Manager) from Pulseway's installation directory with the following parameters: PCMonitorManager.exe /config=C:\Configuration\NoPassword.pcmcfg If the exported configuration file contains the account details then you need to provided the configuration password as well: PCMonitorManager.exe /config=C:\Configuration\WithPassword.pcmcfg /configpassword=s3cr3tpassw0rd Note: The PCMonitorManager will not provide any console output or custom exit codes based to indicate the success of the operation.

Hi all, I recently did a clean upgrade to Windows 10 on 2 WKSTs previously running Windows 7 with Pulseway installed. I am now at a loss as to how to re-add these units to my Pulseway instance. I see they are still showing up in the “Deployment Successful” tab under “Discovery & Deployment”. Is there a way to re-add these units without manually installing the Pulseway app on these WKSTs?

When u use the built-in script "Add Automatically Started Services in Pulseway" some services wil be monitored that are triggert and not always on. This wil result in unwanted notifications. The first variable has the servicenames you want to disable. $services = @('gupdate', 'ShellHWDetection', 'sppsvc', 'RemoteRegistry', 'MapsBroker', 'tiledatamodelsvc', 'WbioSrvc', 'WinDefend', 'CDPSvc') $servicesRegex = [string]::Join('|', $services) # create the regex $regservices = Get-ItemProperty "HKLM:\Software\MMSOFT Design\PC Monitor\Services" $regservicesSplit = $regservices -split ";" foreach ($regservice in $regservicesSplit) { If ($regservice -match $servicesRegex ) { $servicesSplit = $regservice -split "=" $servicesTrim = $servicesSplit[0] $servicesTrim = $servicesTrim.Trim() Remove-ItemProperty -Path "HKLM:\Software\MMSOFT Design\PC Monitor\Services" -Name $servicesTrim Write-Host $regservice " Verwijderd" } } Hope it helps.

Hello, I have a question about the Pulseway app. When the pc is on all of the commands work great and are perfect for managing the pc. But I am attempting to turn on my pc when I am away from my home and then be able to fully control it like I was there. The issue is how the wake up command from sleep or from powered down will not work even when on my home network. How can I fix this. Also a side question, is there a way I would be able to see a live view of the screen or does it only allow screenshots of the screen. Thanks

Hi there, I have installed Pulseway on 2 PC's and according to my subscription page. I get 2 free licences. I was using Pulseway quite successfully last night till I received an email saying I had reached the Notification limit and to remove this limitation I should consider getting a subscription. I have logged on today to try and purchase a subscription for 2 licences as luckily that is all I need at this stage but due to it saying the first 2 agents are free I can't purchase a full subscription for just 2 licences How can I get unlimited notification for my 2 free licences?

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

Remote Control really needs the ability to both trigger a reboot and to automatically reconnect when the system you're connected to completes the restart. Having it immediately disconnect when a reboot is triggered (usually if it's running as a service, it should be able to hold the session open for things like the first phase of installing Windows updates) and having to manually try over and over again to see if the machine has completed its reboot is really frustrating when you're trying to solve an issue remotely that requires a lot of reboots or even when you're just trying to do a number of updates to a system.