PQDDeploy Monitoring

Comments

7 comments

  • sean johnson

    Deploy isn't set to not communicate out, it checks in for list of updated packages / Daily notifications of webcasts / Software updates (These minus package updates can be disabled in Alerts under Preferences). My guess would be that it's a simple AWS connection hosting these resources. Block it and see if any of those stop working.

    Only other guess I can think of is Agent to PDQ server to local PDQ inv/deploy communication described in https://www.pdq.com/optional-agent/

    0
    Comment actions Permalink
  • Katie Sorenson

    That would be Deploy checking into a resource on our Azure infrastructure. It's most likely looking for for new or downloading packages, since that's the bulk of what Deploy cares about.

    The sites that Deploy and Inventory will try to connect with for package and collection library updates, downloads, product updates, agent communications, etc. are listed here:

    https://support.pdq.com/knowledge-base/1023#external

    0
    Comment actions Permalink
  • rodrigo.stocco

    Yes, I think so. I have saw this link before but no one of those address match with this one: waws-prod-bay-023.cloudapp.net.

    For this reason i was curious.
    Thanks for your reply.

    0
    Comment actions Permalink
  • rodrigo.stocco

    I will try change it. Thanks for your reply.

    0
    Comment actions Permalink
  • Katie Sorenson

    It resolves to the same IP as library.pdq.com does, according to the all-knowing nslookup -- Non-authoritative answer: Name: waws-prod-bay-023.cloudapp.net Address: 104.45.226.98 Aliases: library.pdq.com pdq-library.azurewebsites.net waws-prod-bay-023.vip.azurewebsites.windows.net

    0
    Comment actions Permalink
  • rodrigo.stocco

    Make all sense, thanks a lot Katie!

    0
    Comment actions Permalink
  • Colby Bouma

    The Agent uses agentapi.pdq.com.

    0
    Comment actions Permalink

Please sign in to leave a comment.