Chris

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 @bdoadmin,
You may change the system in Pulseway remotely by using the Pulseway Dashboard or using the Powershell command from the Pulseway WebApp -> Systems -> Systems ->select the required system -> PowerShell terminal and run the following command:
Set-ItemProperty -Path "HKLM:\Software\MMSOFT Design\PC Monitor\" -Name ComputerName -Value "New_Name_for_the_system"
Let us know how it goes.

Hi Martin,
 
This is a great idea, we already had it on our list however this involves a multitude of changes and we are still investigating the best way of achieving this.
 
Regards,
Chris
Pulseway Support

Hi Eder,
Thanks for contacting Pulseway support.Yes, by default all Linux agents are placed in Legacy group. Currently, the Legacy group is used for the systems which are registered using the Cloud API or the REST API. These systems don't use the Token to authenticate with your Pulseway server, therefore these systems are placed into the legacy group.You can rename the legacy group or the system can be moved from one group to another using the Pulseway WebApp ->Systems-> Systems -> Configuration -> select the Organization-Site-Group in which this system is currently located -> Systems and click on edit -> button 'Move Out' -> select the new Organization-Site-Group and save the changes. For more details about this, please check the following:
https://intercom.help/pulseway/en/articles/2343299-organizations-sites-and-groups-management-in-pulseway-6-0

Hi Martin,
Thanks for your valuable suggestion.I will put this forward as the feature request so our developers can consider the possibility to introduce this functionality in the future release.

Hi @ITiseasy,
According to current roadmap the release for Pulseway RD for MAC it is planned for Q3 2020.

Hi @ITiseasy,
Thank you for your suggestion. I have logged it as a feature request, therefore our developers will consider the possibility to introduce this functionality into the future.

Hi @Parallax Abstraction,
Thank you for your suggestion. It sounds like a great idea, I will put it forward as a feature request, therefore our developers will consider the possibility to introduce this functionality into the future. 

Hi @Louwrens,
This is happening because that session is no longer active (idle) and as soon as you connect to the console session that session is destroyed by Microsoft. The Pulseway RD is designed to join the currently active console session, therefore as soon as Microsoft makes changes to existing session you are asked to reconnect to that session. The same will happen if you will switch the user accounts while you are connected to that system. You will need to reconnect to that system using the Pulseway RD using the account to which you want to switch the console.

Hi All,
Thank you for your suggestion. We already have the functionality (Notification based actions) as the confirmed feature, therefore it will be implemented into the future.

Hi @francoism,
Please tel us what information are you looking for?
Also, have you checked /assets/id REST API.

Hi @Louwrens,
If Pulseway fails to read this data from your monitored systems, then it is not shown in report. Please verify that there are no issues with WMI on your monitored system.

Hi @Louwrens,
Thank you for your suggestion. I have logged it as a feature request, therefore our developers will consider the possibility to introduce this functionality into the future.

Hi @Spicy Support,
Currently this option is available for PowerShell scripts if the PowerShell impersonation is configured from the Pulseway Manager -> Settings -> Runtime on the remote system on which this script will run.
Note: this script will still be executed in session zero with no GUI.
Alternatively you may deploy PsExec on your systems to interact with user session with GUI. For more details abut this, please check out this post:
 
 

Hi @spicysupport, @Cyb3rBlitzX
The computer name can be changed from the terminal via the Pulseway WebApp using the following instructions.
Note: reboot is required to apply these changes:
And then you will need to update the Computer name into the Pulseway WebApp by executing this command:
Set-ItemProperty -Path "HKLM:\Software\MMSOFT Design\PC Monitor\" -Name ComputerName -Value ""
Regarding NetBIOS name changes - you may create the script which will run locally by the Windows scheduler and this script will check whether the NetBIOS name was changed and if it was, then it may send notification to the Pulseway using this plugin 'Notification Bridge'.
 

Hi @Chris1992,
Are you using domain user or local user in PowerShell impersonation?

Hi All,
We have reintroduced the option to see the date when Pulseway server has seen the system for the last time. This option is available under Account section -> Manage systems. Also, you can sort that column by date, therefore it is easy to see old systems.
 

Hi @Chris1992,
Another option in this case would be create a script on your Synology storage which would run on schedule and report required parameters to Pulseway via REST API. If you will chose to use the REST API to monitor this instance, then you will be able to register it as separate system using REST API. For more details regarding the REST API for Pulseway, please check out the following link.
Let us know if you have any further questions regarding this.

Hi All,
This feature is on our roadmap and it will be added to Pulseway when we will introduce Trigger Based Automation module.

Hi @Martti Nuudi,
We have managed to identify the issue and the fix for it will be released next week.

Hi @Louwrens,
Thank you for your suggestion. Yes, this is a good idea and we are looking into the possibility to introduce the option for users to build their own reports into future.

Hi @Nicola Farina,
Yes, it is possible to monitor the folder size via scripts. If you will create the script which checks the Folder size and returns the exit code (exit 1 - failure and exit 0 - success), then based on the exit code from the script you may send the notifications if you will run it as an automated task. For more details about automated tasks please check out the following link.
 
 

Hi @Flalpalay,
Thank you for contacting us. We are currently working on this issue and it will be fixed today.

Hi @Martin Stevnhoved,
Thank you for bringing our attention to this. We will add this switch into our application for PowerShell when we execute PS scripts via Pulseway.

Hi @David,
For more details why is this error reported, please check the WindowsUpdate.log file. If there are any errors in this process, then Pulseway will report that there was some Errors.