Can we get an official statement about the new agent option?

Comments

11 comments

  • Official comment
    Brigg Angus

    As mentioned elsewhere in this thread, we have two resources that explain the optional Agent:

    The Agent FAQ
    The Official Agent Blog Post (Provides an overview of the Agent and links to the documentation.)

    Comment actions Permalink
  • Shane Corellian

    Hi Robert,

    We are finishing up a FAQ on the agent. It should be completed soon and it will answer the questions everyone has been asking (such as encryption, communication, features, etc.) 

     

    1
    Comment actions Permalink
  • Christian Bacher

    I bet......the videocast tomorrow ;-)

    1
    Comment actions Permalink
  • Robert Basil

    I'm really excited about the agent option.

    I'm really hoping the agent will (in time) alleviate some of the issues I'm having trying to scan the inventory of 25,000 endpoints across 57 different sites. It sure would be nice to have the agents push that data to the server instead of having the server have to reach out and pull it from every endpoint.

     

    0
    Comment actions Permalink
  • Robert Basil

    Thanks Shane!

    0
    Comment actions Permalink
  • Colby Bouma

    @Robert Basil:

    The Community section is what correlates to this forum: https://beta.pdq.com/community

    I do not believe posts will be carried forward to the live version, so it's best to keep asking questions here for now. Please test out the beta site though, we'd love to get feedback!

    0
    Comment actions Permalink
  • Colby Bouma

    Here's the FAQ Shane mentioned: https://support.pdq.com/hc/en-us/articles/360003044012

    0
    Comment actions Permalink
  • Robert Basil

    Colby, Shane and the rest of the PDQ team.

     

    Thanks for the Agent FAQ, answers a lot of questions...

     

    1. Update the Current User field immediately as users log on and off.
    2. Update the Uptime field as soon as a computer boots back up.
    3. Keep a log of Events such as Logon, Logoff, Startup, and Shutdown. The Agent sends these as quickly as possible. If the Agent is unable to communicate with any servers, it will store these Events until it is able to communicate again.
    4. Run a Computer Details scan with every Agent Heartbeat (5 minutes, not currently configurable.)

     

    When the agent reports back to the server does that report also include the results of the computer details scan?

    I see a lot of details being sent from the Agent back to the Server and that's a good thing. One worry I do have though is with a large 25,000 endpoint network like ours and with students logging in and out of machines every class period (45 minutes long) I can see this overwhelming the server.

    In the future I would like to be able to limited (say every 90 minutes or so) the agent check-in?

    The Agent is defiantly a step in the right direction, thanks for all your hard work on this!

    0
    Comment actions Permalink
  • Colby Bouma

    > When the agent reports back to the server does that report also include the results of the computer details scan?

    Only when it sends an Agent Heartbeat, not when it sends Events.

     

    > I see a lot of details being sent from the Agent back to the Server and that's a good thing. One worry I do have though is with a large 25,000 endpoint network like ours and with students logging in and out of machines every class period (45 minutes long) I can see this overwhelming the server.

    We don't have a way to replicate an environment that large here, so we're hoping to hear back from customers like you on how it performs :)

     

    > In the future I would like to be able to limited (say every 90 minutes or so) the agent check-in?

    I believe we will have a way to configure this in the future. I have no ETA on that.

    0
    Comment actions Permalink
  • sean johnson

    Well that explains the spike in CPU use. We only have about 1000 clients and our PDQ VM got pelted. That probably explains why some of the agents keep going to external and back I assume a great deal of our agents have synced up 5min windows. McAfee's (Intel) agent has similar issues and has to randomize it's reporting window.

    0
    Comment actions Permalink
  • Colby Bouma

    @Sean Johnson

    Please open a ticket with support@pdq.com, they can help troubleshoot the high CPU usage.

    0
    Comment actions Permalink

Please sign in to leave a comment.