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.

PDQ Inventory details (RAM, H-Drive, CPU, Database)

We're looking to distribute Office 2013 to 2000+ target machines. Our console machine is on server - Windows Server 2012 R2.

What RAM is needed/recommended? What H-Drive size is needed? What database size is needed? And is the CPU usage high?

Any help would be appreciated.

0

Comments

2 comments
Date Votes
  • I deploy from a Win7 Virtual Machine on a MacBook Air (1.4 Ghz Intel Core i5, and 4GB RAM) I give my VM 1.5GB Ram and 2 CPU cores. I have the package files stored on a local Windows 2008 Server and set the packages to PULL from the 2008 server rather than PUSHING the package files from my MacBook.

    Hopefully this gives you an idea. With these low specs PDQ performs pretty well and is rather quick if you make sure to disable WOL option in Preferences so that it doesn't hang waiting for the computers to come online. Any computers that are not online at the time will be added to the retry queue anyways and will deploy once they come online.

    0
  • P. S. I deploy to a little over 1,500 machines.

    0