Jump to content

Chris

Staff
  • Posts

    1347
  • Joined

  • Last visited

Posts posted by Chris

  1. Hi @Van Der Hoff ICT,

    Have you tried to use our bult-in script to install these updates? For more details please check out the following link.

    From the error log I can see that you are trying to call download on the array element which is null. If you want to troubleshoot this error then please verify that that element in array is not null.

     

  2. Hi @BBjay,

    That is correct. Pulseway agents are no longer authenticated using username and password. However if you choose to use this method, then all systems are registered with in Default Group.

    Currently you have two options:

    1. download the customized installer for the specific group from the Pulseway WebApp -> Onboarding -> Doewnloads and then use it to install agent by executing this command.

    msiexec /i "c:/Pulseway_x64.msi" /qn

    2. or copy the URL for the customized installer from the Pulseway WebApp -> Onboarding -> Doewnloadsand then use it into the PS command:

    msiexec /i "URL_for_the_Installer" /qn

  3. Hi @Hendrik

    Thank you for your suggestion, we will consider the possibility to add this setting into the future.

    If this might works for you, then by the current design - If you will create only one organization and one site, then the name for the organization and site will not be displayed into Pulseway.

  4. Hi @ADIT,

    If there are systems in the same VLAN which can connect to the Pulseway and there are no specific network Rules (ACLs) in place which might block these connections, then try the following:

    Reset WINSOCK entries to installation defaults :

    netsh winsock reset catalog


    Reset TCP/IP stack to installation defaults :

    netsh int ip reset reset.log


    Flush DNS resolver cache :

    ipconfig /flushdns


    Renew DNS client registration and refresh DHCP leases :

    ipconfig /registerdns

    Flush routing table :

    route /f
    (reboot required)

     

     

  5. Hi @ADIT,

    This message usually is shown if the Pulseway agent can not connect to the Pulseway server or if the server which it is connecting to is not the Pulseway server. Please check the basic thinks:

    1.  Can you resolve the DNS name correctly? nslookup ourcompany.pulseway.com

    2. Can you ping your Pulseway instance?

    3. Try to use the tracert command to identify where the connection drops?

    4. Try to open https://ourcompany.pulseway.com/Server.svc using the Internet explorer? Any errors?

    5. Also check if the Pulseway network traffic is excluded from the Web content filter, because it is encrypted and Web content will not be able to read it, therefore it will be blocked.

  6. Hi @Ali Syed,

    Yes, you can monitor network devices if the SNMP monitoring is supported on those devices. Pulseway will monitor your network devices from the Windows system using SNMP. The instructions how to configure it is the same as in that KB article.

    Just make sure that SNMP is enabled for network devices on the required network interfaces so Pulseway can access it.

  7. Hi @David-,

    From your script I can see that you are trying to set the HKCU registry keys which are for the currently user account, therefore in order to set these keys for the required user account the powershell impersonation is required. If it is not configured, the the HKCU keys will be set for the System account and it will not affect the required user session.

  8. Hi @Jim,

    Currently we are logging the Pulseway RD connections into the audit log if the audit logging is enabled for the Pulseway account which is used to connect, however we do not log the duration of these connections and the fact whether it was confirmed.

    The audit logging can be enabled from the Pulseway WebApp -> Server Admin -> Teams and Users -> All users -> Select the user -> Details and enable Audit logging.

  9. 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.

     

  10. @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

     

  11. 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

     

  12. @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

  13. 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

     

×
×
  • Create New...