AC_Martin_J

I appreciate you sharing the script, but please note that the password is stored unencrypted and visible to others in both the script itself (if you edit the code) and in the registry. 
You might want to consider using the Autologin-tool from Mark over at Windows SysInternals instead. It's a great tool to add autologin to kiosk-computers and such, while keeping the credentials safe since they will be encrypted. https://docs.microsoft.com/en-us/sysinternals/downloads/autologon To turn it back off, you simply run the tool again and disable the autologin feature.
 
In other situations, there's also a Cmdlet to gather credentials and store the password as a secure string which is handy. You can try the following to test it out: 
#Running this first line will open a prompt for you to enter username and password and store it in $Credentials $Credentials = Get-Credential #Running the second line will output the UserName that was entered previously, and in a readable formt $Credentials.UserName #Running the third line will output the Password as a secure-string (non readable) $Credentials.Password #You can then use the stored information when running the Invoke Cmdlet for example (ie running a scriptblock on another computer), or when connecting to Office 365. #Furthermore it's possible to convert the secure-string into an unreadable text format so you can save it in plain text but without the risk of having it compromised.  #Running the fourth line will convert the password from a SecureString and store it in $Password $Password = $Credentials.Password | ConvertFrom-SecureString #You can then compare the output of $Credentials.Password and $Password by running them separately. The first one will show the SecureString-data, and the second will show the same information but in plain text while it can also be exported/saved for future use, unlike a securestring.  #Running the fifth line will export the password in an unreadable plaintext-format and save it as a file, so you can import this at a later point in time (ideal when running scripts with the task scheduler where the script needs credentials in order to proceed). Set-Content "C:\temp\MyPasswordData.txt" $Password #Running the sixth line will import the password and convert it back to a securestring so you can use it in your scripts. $ImportedPassword = Get-Content "C:\temp\MyPasswordData.txt" | ConvertTo-SecureString  
Hope this helps!  
 

Have a notification appear when they have responded to chat
saves having to stay on the device or wait in the chat window

Instead of performing necromancy on this older thread, I will raise this question again. Why can we not see asset info for offline systems? 
I know this is available through reports, but that's a ton of steps to go through when it's already readily available offline (since the Reports can search it) and it should just be visible. This has been a big gotcha (along with not seeing internal IPs without running a report or being able to copy/paste in remote sessions) as we moved from another tool to Pulseway. I've seen more than one thread about this, and each time the response is 'run a report'. Please stop brushing it off as 'RTFM' and provide the functionality we're asking for. Thank you.

Hey guys! 
 
I think Pulseway would be even better if the alerts would clear themselves when resolved.. For example, a server with available windows updates will reboot during our custom maintenance window but the alert will stay until I manually clear it in either the webGUI or the Dashboard app. Those kind of alerts along with cpu spikes, short memory outtage etc are more like "white noise" in the monitoring for me and I'd like to focus on alerts where a proper action is needed in order to resolve. 
 
To build further on this idea an even better improvement would be to tie alerts to scripts, so if Alert X is triggered, script Y will run and Alert X will be cleared. 
Let me know what you think! // Martin
 
 

Afternoon
It would be great if we could make Asset Info available when devices are offline.
For example if a remote users PC fails to function and is still under warranty trying to explain to a user where to find the device Make, Model and serial number to log a warranty case is not always easy.
If the asset information was available when the device was off line then it would make this process mach easier as it contains all the information required
Cheers
peter
 
Example
DAVID-O-MIIX Windows 10 Pro Offline Offline since 11 minutes ago Asset Info   System DAVID-0-MIIX Name LENOVO Manufacturer 20M3 Model x64-based PC Type Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz CPU 1 Number of Processors 8 Number of Logical Processors DAVID-O-MIIX DNS Host Name TEST.local Domain Administrator Owner Name LM_Workstation, LM_Server, NT, Potential_Browser Roles OK Status BIOS YD05UDx7 Serial Number 6NCN33WW Name LENOVO Manufacturer 6NCN33WW SMBIOS Version 3 SMBIOS Major Version 0 SMBIOS Minor Version LENOVO - 1 Version Monday, 12 November 2018 1:00 PM Release Date OK Status 6NCN33WW Description Operating System Windows 10 Pro Name 10.0.17763.0 Version Multiprocessor Free Build Type systemadmin Registered User NF6EE-QH89W-F8WST-WWXZ4-WFG6P Product Key 00330-50000-00000-AAOEM Serial Number 0 Service Pack Major Version 0 Service Pack Minor Version \Device\HarddiskVolume3 System Device C:\WINDOWS\system32 System Directory C:\WINDOWS Windows Directory Monday, 11 March 2019 12:40 PM Install Date Monday, 20 May 2019 4:30 PM Local Date and Time Monday, 20 May 2019 8:10 AM Last Boot Up Time test\anton.rider Last Logged On User

Hey guys! 
 
I have a couple of things that would greatly improve my own workflow and also improving the remote desktop client in general, so I decided to collect them all in one thread. Please share your thoughts.
1. Adding sections for tags, notes and last logged on user in the Remote Desktop Client GUI. This is illustrated in the uploaded picture within this thread.
2. Transfer files. Both ways would be great, but at least being able to transfer from host to client at first.
3. Portable remote sessions. What I mean by this is to have a link that a user can go to (for example https://pulseway.yourdomain.com/help), and then download a portable version of Pulseway Remote. The user would then let me know of a PIN-code that can be entered within my Remote Desktop Client to remote control his/her desktop.
4. We are currently able to toggle the ask for confirmation-behavior, and I have configured a 1 minute timeout before it is automatically allowed. However, my suggestion is that the timeout won't apply when the "Login"-session is the only session available.
 
// Martin

Hey guys! 
 
I think Pulseway would be even better if the alerts would clear themselves when resolved.. For example, a server with available windows updates will reboot during our custom maintenance window but the alert will stay until I manually clear it in either the webGUI or the Dashboard app. Those kind of alerts along with cpu spikes, short memory outtage etc are more like "white noise" in the monitoring for me and I'd like to focus on alerts where a proper action is needed in order to resolve. 
 
To build further on this idea an even better improvement would be to tie alerts to scripts, so if Alert X is triggered, script Y will run and Alert X will be cleared. 
Let me know what you think! // Martin
 
 

Hey guys! 
 
I think Pulseway would be even better if the alerts would clear themselves when resolved.. For example, a server with available windows updates will reboot during our custom maintenance window but the alert will stay until I manually clear it in either the webGUI or the Dashboard app. Those kind of alerts along with cpu spikes, short memory outtage etc are more like "white noise" in the monitoring for me and I'd like to focus on alerts where a proper action is needed in order to resolve. 
 
To build further on this idea an even better improvement would be to tie alerts to scripts, so if Alert X is triggered, script Y will run and Alert X will be cleared. 
Let me know what you think! // Martin
 
 

Hi Martin,
I like the idea! We'll definitely be considering this .
-Paul

Hi Paul!
I thought I'd ask in this thread, rather than creating a new one.. Is it possible to set which email a support request should be sent to?
 
I'm asking because I would like to receive all support requests on a dedicated email address for that specific purpose (while the notifications are sent to another dedicated address). But it seems like the support request will be sent to the email address of the account which is connected to the Pulseway Manager on that specific client.
 
A working solution could be if those emails are sent to an address based on what is specified in the "Company email"-section at the "Support Info Details"-tab. 

Hi Nathan,
In about 1 month time we are planning to release a new Pulseway account management system. This system will allow you to assign a scope of the systems to the scope of users. And all users from this scope will be able to access all systems which are listed in the assigned scope (including Antivirus section and OS patch management). Also if you will add the system to the scope, then it will be shared with all users in this scope automatically.

Hey.. 
 
I've been moving clients between groups with the script below, and it might be useful to some of you.. If you need to do it in a bigger batch, then maybe you can create a scope and attach the script to a task that has the scope connected to it. Also, tags could be used to further narrow down the targeted clients.
 
#Replace 'NewGroupNameHere' with whatever group name you would like to use. #Example, $NewGroup = 'Servers' $PreviousGroup = Get-ItemProperty -Path "HKLM:\Software\MMSOFT Design\PC Monitor\" -Name GroupName $NewGroup = 'NewGroupNameHere' Write-Host 'The Pulseway group is currently set to:' $PreviousGroup.GroupName Write-Host 'The Pulseway group will be set to:' $NewGroup Set-ItemProperty -Path "HKLM:\Software\MMSOFT Design\PC Monitor\" -Name GroupName -Value $NewGroup Write-Host 'Verifying...' $Verification = Get-ItemProperty -Path "HKLM:\Software\MMSOFT Design\PC Monitor\" -Name GroupName Write-Host 'The Pulseway group was successfully changed to' $Verification.GroupName  

Thank you Martin for this. I had a few devices that were always failing to install Webroot and it wasn't made clear before that you could manually install them as you described. I just installed the Webroot agent, then issued the Install command from Pulseway and all is well. 
To be honest, I wish there was a little bit more information why an install failed in the first place, as I had no issues at all installing it manually. 

Hey.. 
 
I've been moving clients between groups with the script below, and it might be useful to some of you.. If you need to do it in a bigger batch, then maybe you can create a scope and attach the script to a task that has the scope connected to it. Also, tags could be used to further narrow down the targeted clients.
 
#Replace 'NewGroupNameHere' with whatever group name you would like to use. #Example, $NewGroup = 'Servers' $PreviousGroup = Get-ItemProperty -Path "HKLM:\Software\MMSOFT Design\PC Monitor\" -Name GroupName $NewGroup = 'NewGroupNameHere' Write-Host 'The Pulseway group is currently set to:' $PreviousGroup.GroupName Write-Host 'The Pulseway group will be set to:' $NewGroup Set-ItemProperty -Path "HKLM:\Software\MMSOFT Design\PC Monitor\" -Name GroupName -Value $NewGroup Write-Host 'Verifying...' $Verification = Get-ItemProperty -Path "HKLM:\Software\MMSOFT Design\PC Monitor\" -Name GroupName Write-Host 'The Pulseway group was successfully changed to' $Verification.GroupName  

Thank you for sharing this. Just what we have been looking for.
Gary