Jump to content

Chris

Staff
  • Content Count

    1178
  • Joined

  • Last visited

Everything posted by Chris

  1. Is it possible that you have previously deleted these registry keys to disable the network interface monitoring? If yes, then you will need to recreate it. Also, is it possible that you have configured PowerShell impersonation and that the user account which is used doesn't have admin rights.
  2. @RichardBUnfortunately the available features tab indicates whether this functionality is available on the remote system or not. In order to enable the Network interface monitoring you will need to configure it by selecting the required interfaces. Or alternatively you may run the built in script - 'Add Enabled Network Adapters in Pulseway' from the Pulseway WebApp to enable it. For more details regarding this please check out the following instructions.
  3. Hi @RichardB, Thank you for contacting us. Have you tried to use the pre-configured installer for the required group? If you use the username and password to authenticate system, then it is placed in default user group. In order to download the pre-configured agent for the specific group you will need to open the Pulseway WebApp -> Onboarding -> Downloads and copy the link which you can use in your script. msiexec /i "url_for_the _pulseway_agent" /qn
  4. Hi @dpbklyn, Thank you for contacting us. It sounds like a good idea. I will put it forward as the feature request.
  5. @Tyson, In order to update the details for the PS impersonation you will need to use the batch script. At first we need to configure the Powershel impersonation on one of monitored systems and the copy the required values from the registry. REG ADD "HKLM\Software\MMSOFT Design\PC Monitor" /v PowerShellUserImpersonation /t REG_SZ /d value_here /f REG ADD "HKLM\Software\MMSOFT Design\PC Monitor" /v PowerShellUserImpersonationDomain /t REG_SZ /d value_here /f REG ADD "HKLM\Software\MMSOFT Design\PC Monitor" /v PowerShellUserImpersonationPassword /t REG_SZ /d value_here /f REG ADD "HKLM\Software\MMSOFT Design\PC Monitor" /v PowerShellUserImpersonationPasswordCtrl /t REG_SZ /d value_here /f REG ADD "HKLM\Software\MMSOFT Design\PC Monitor" /v PowerShellUserImpersonationUsername /t REG_SZ /d value_here /f Or simply use this command to enable or disable it by changing the value from 1- enabled to 0 - disabled REG ADD "HKLM\Software\MMSOFT Design\PC Monitor" /v PowerShellUserImpersonation /t REG_SZ /d o /f
  6. Hi @dpbklyn, The idea here is to resolve tickets from the Pulseway PSA. Once the ticket is resolved or deleted into the Pulseway PSA, then it is automatically deleted from the Pulseway RMM. In order to open the ticket in PSA for certain system you may use the support request from the system on which are you working. Support requests will always be forwarded to the Pulseway PSA. For more details regarding this please check out the following links: 1. https://intercom.help/pulseway/windows-agent-configuration/general-configuration-for-the-system/enable-user-support-request 2. https://intercom.help/pulseway/windows-agent-configuration/manage-systems/how-to-configure-pulseway-group-policies
  7. Hi @will701, Yes, it is possible. At first you will need to create a new team and then you will need to configure the access rights for the team to required systems. For more details please check these articles. 1. https://intercom.help/pulseway/accounts-and-policies/user-access-management-in-pulseway-60 2. https://intercom.help/pulseway/product-updates/61-pulseway-update
  8. Hi, Have you tried to setup this monitoring for the host system? If the Pulseway agent can not be installed on that system, then you may try to monitor it via SNMP from the Pulseway agent on the Windows system which is not installed directly on the same system. For more details about this please check out the following link.
  9. @MickH2007 The Linux agent version 6.1 is already released. And libssl are embedded in the Pulseway agent, therefore this no longer should be an issue.
  10. I believe that access rights are configured on the external firewall (Sophos). It would be strange if it is configured on the Windows firewall on each machine separately. However I would not say that it is impossible.
  11. Hi @LouwrensE, Is it possible that these connections are blocked by the firewall? The Pulseway agent is using the following IP Addresses and HTTPS port 443 for the Pulseway RD: 69.65.40.236 69.65.43.163 69.65.48.240 13.237.174.172 99.81.62.236 3.93.221.213 54.176.91.130
  12. Hi @Moog Louisville, In order to execute this executable you may simply type this command into the terminal section into the Pulseway WebApp. If you want to run this command on multiple systems, then you may choose to use the Pulseway Automation.
  13. Hi @WWTTG, Yes, that is correct we send only one notification and in order to receive the next notification you will need to delete the previous one. This functionality is implemented to prevent your inbox to be flooded with emails if this process is crashing multiple times in a short period of time.
  14. Hi @DiegoAtravesar, This functionality is available for you from the Pulseway Manager on your monitored system. Also, you can configure this by using the Pulseway Group policies from the Pulseway WebApp. For more details how to do this please check out the following article.
  15. Hi, Unfortunately it is not so simple. Emails are sent by the Pulseway server, therefore all this information needs to be sent back to the Pulseway server and then server should know how to handle these addition email addresses if added. This would require some development to be done. I will put this forward as the feature request, therefore we will consider the possibility to introduce this functionality into the future release. Also, this functionality currently is requested only by you.
  16. Hi @Ue Khaung, Please post the screenshot showing the actual error message?
  17. Hi, This option will work for you if you know the name for the file which will be created.
  18. Hi, Unfortunately this functionality is not supported at this time, however I will put this forward as the feature request, therefore our developers will consider the possibility to introduce this functionality into the future release.
  19. Hi John, In order to resolve this issue, please restart the Pulseway service on that system by running the following PowerShell command from the Pulseway WebApp. restart-service pulseway
  20. Hi @ArrowNM, We'd really appreciate your input on how we can improve those integrations. I'll make sure that the right people sees your feedback. Thanks
  21. Hi All, Thank you for the suggestion, we will put this forward as the feature request.
  22. Chris

    This is not 2FA

    Hi @cmiller, We are actually working on the 2FA functionality, therefore it will be available into the near future.
  23. Hi @Guy Steels, Thank you for bringing this to our attention. We will fix this into the future release.
  24. Hi @Tommy, You might write a script which will run locally on your system and check count of the files into the folder and send the notification if the count has been increased by one. Note: when ever the new file is detected, then you will need to update the count for the files in script, therefore I would suggest you to write this variable in the registry or in some other location, so your script can read it before the next execution.
  25. Hi @Guy Steels, If are we talking about the Pulseway WebApp, then it is possible to increase the inactivity timer to 120 minutes = 2 hours. This option is available for you from the Pulseway WebApp -> Server Admin -> Settings -> Web Application.
×
×
  • Create New...