1. PDQ Deploy & Inventory Help Center
  2. Community
  3. PDQ Inventory
 

Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Inventory and Deploy setup best practices

Avatar
Wayne Osteen

Hey guys! Looking over the products, they appear to be exactly what we need. So much so that my supervisor went ahead and purchased both before I even had a chance to test things. LOL

So my question is, what's best practices for setup with these products? We've got between 10k - 11k workstations, and about 300 servers in our environment. They're spread across 40 AD sites connected with a WAN. I've already got DFS setup, so the repository shouldn't be an issue, but I'm wondering about specific settings.

How much RAM for my server (ESX 5.5 running Windows Server 2012R2 guest OS), how many CPUs, and how much disk space? I want to make sure I get the environment sized properly.

I also saw an entry in the forum about setting the heartbeat high for large environments. I saw 1200 and 1800 seconds mentioned. What do you think?

If there's too much to cover here, should I setup a consult call?

Thanks!
Wayne

0

Comments

1 comment
Date Votes
  • Avatar
    Shane Corellian

    Hi Wayne,

    Do you intend to only use one console for all 10k plus computers? If so then I would recommend trying heartbeat at 1200 and then moving up from there.

    How aggressive are your deployments and scans going to be?

    I would suggest that you look into our private virtual training. This is where we meet up on the phone and via TeamViewer (or similar remote access service) and help you customize the products for your environment.

    0