Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Paul

  1. Hi Evan, winget is an msix (Windows Store Component, source) that must run in a per-user sandbox which is not available when running from the machine account (SYSTEM). You could force it to run against the logged in user (if any) through psexec but you'd need to distribute it somehow. -Paul
  2. Hi @nateb, We collect sample every minute but report only min, max and avg values for the day. -Paul
  3. The recommended way is to get a new Pulseway server installation with the new domain and move endpoints using a script as documented here: -Paul
  4. I have recently built a similar script but mine doesn't ignore NPCAP, feel free to issue a pull request to change it: https://github.com/paulcsiki/pulseway-scripts/blob/main/enroll-network-interfaces/enroll-network-interfaces.ps1 -Paul
  5. Hi Mickey, To eliminate everything try with an administrator vSphere account and make sure that the port 443 is accessible. You should be able to connect the VMware server module to an ESXi server or a vCenter server. -Paul
  6. Hi there, At this moment it's not possible to override the default notification priority from the user support request. -Paul
  7. Paul


    Hi @AMC, Based on the documentation, the DomainCredential parameter says: We run PowerShell in a non-interactive mode, this prevents inputs from being triggered. You can provide a PSCredential object instead of the username and that should do the trick. $password = "ThisIsAPlaintextPassword" | ConvertTo-SecureString -asPlainText -Force $username = "contoso\Administrator" [PSCredential] $credential = New-Object System.Management.Automation.PSCredential($username, $password) Rename-Computer -NewName "NewComputerName" -DomainCredential $credential -Restart -Paul
  8. Well yes, you can just export the configuration settings of an agent, just look for the "Export Settings" textual link at the bottom of the Pulseway Manager app. -Paul
  9. Oh, I see what is the problem now. It is skipped because it contains the same identifier as the previous host. Try changing the identifier field slightly and see that it will import now. Use only hexadecimal characters (0-9a-f). Let me know how it goes. -Paul
  10. I was able to successfully import the Host 11 configuration on my PC: -Paul
  11. Hi there, Can you PM me the original XML and then the changed one? It should work. -Paul
  12. The form should be resizable. Do you use a screen DPI other than 100%? -Paul
  13. From the WebApp under Server Admin -> Endpoint Policies, create or edit a policy and make sure that the User Support Request feature is enabled under the System category. Then under Server Admin -> Configuration assign the endpoint policy to the organization, site or agent group. From that point a tray icon will show up on the agents and they will be able to request support from there.
  14. This is possible through the User Support Request feature which will trigger a notification in Pulseway and if you have the Pulseway PSA, Zendesk, Autotask or ConnectWise integration then a ticket gets created as well. -Paul
  15. Thanks for the continued support Nick! You rock ! -Paul
  16. Hi there, We have released an agent update (v8.9.1) which addresses this issue. The update will reach all systems within 48 hours. -Paul
  17. I'll have to look into it tomorrow. I'll reply back when I have more information. -Paul
  18. You should be able to get the IDs of tickets from another API call used to list tickets: /v2/servicedesk/tickets/search -Paul
  19. Hi there, Check out the PSA REST API's here: https://api.psa.pulseway.com/. The link you have provided is for the RMM. -Paul
  20. Hi @BShevchuck, In that case the server name is: psa.pulseway.com . Let me know how it goes ! -Paul
  21. Paul

    Custom Titles

    Hi Tor, You'd need the msi to be stored in a publicly accessible web server but you can put it over some complex path or file name so it wouldn't be easy to find. -Paul
  22. Hi Tor, That's probably a policy from the Server Admin -> Configuration (or Systems -> Sites if you are on the Pro plan). Look at the Organization, Site and Agent Group to see if there's a Patch Management Policy assigned. -Paul
  23. Hi there, We have indeed changed the messages for the user sessions to match the exact wording using by the operating system. We usually post in the release notes major changes to the platform so this is not a noteworthy change. -Paul
  24. Hi David, We are in the process of introducing API keys which will allow executing tasks for accounts with 2FA. In the meantime you can disable 2FA and use a long password or wait for the API changes. -Paul
  • Create New...