Jump to content

David

Members
  • Content Count

    55
  • Joined

  • Last visited

About David

  • Rank
    IT Vigilante
  • Birthday 09/26/1982

Contact Methods

  • Website URL
    www.agilets.com.au

Profile Information

  • Gender
    Male
  • Location
    Newcastle, NSW, Australia

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. David

    About Patch Mgmt.

    I would assume it's because 3rd-party patching is a vendor-specific process and therefore takes significant time to implement properly.
  2. Well done to you dev team on the 6.1 Linux Agent. Pulseway-registration tool works very well. Could you update the web-app to reflect this: (Onboarding --> Setup Guide --> Agent Setup --> Debian). Regards,
  3. Email sent. Regards,
  4. Assume you mean the "\Patch" directory... I'll get onto this tonight.
  5. Also, why are these "error" tags present when no errors appear in the patch logs?
  6. @Paul My patch policy for the 3rd-party patching trial is ""keep up to date if already installed" for all apps but I'm getting these logs.
  7. marinhd, I know they have plans to add a file transfer tool to the Remote Desktop application but there is nothing to stop you scripting the download from a public URL. Or, if you prefer to use a private repo, Chocolately allows this.
  8. I'd be happy to pay for reliable 3rd-party patching but I hope there are plans to expand the application list...
  9. I have this feature set to trigger a notification upon > 90% CPU load for 2 minutes... however, the list of running processes that are returned with this notification are always very low CPU usage (< 5%). This suggests that either the Pulseway agent is not monitoring ALL running processes or it is not measuring CPU load correctly...?
  10. There seems to be a delay in the Web-App AntiVirus section (Kaspersky Lab agent integration). Yesterday I received a notification that multiple threats had been detected on a client machine. Today, these threats do not appear in the "Events" tab or the "History" tab. My understanding is that "Events" are threats that have not been dealt with yet, whereas "History" is threats that have either been quarantined or deleted... Therefore, based on the applied Group Policy, these threats should be quarantined and should appear in the "History" tab...? This is not the first time I've noticed this delay. What am I missing?
  11. Any time you include pre-paid labour in a contract, it becomes harder to manage. You then need to be using a strict policy of recording all support hours worked and reconciling that monthly, which in my view, is more hassle than it's worth.
  12. No, I'm simply saying that if your admin infrastructure already runs a non-Pulseway MFA solution (eg Duo, Google), then managing Pulseway from within that infrastructure should only require 2-Step Authentication.
  13. For this scenario, I just build multiple scripts and run in sequence.
  14. So long as the front-end admin platforms are protected by MFA, I would argue that 2-Step Authentication (email passphrase) for Pulseway is sufficient.
  15. Thanks, Chris. I was more interested in a search functionality within the web-app Event Log, to make regular triage work more powerful.
×
×
  • Create New...