Admin Questions about PDQ Deploy\Invetory

 

Hi Admin Arsenal Team,

Sorry about all the questions but we need to know this  to go further for security and Auditing purposes.

We are currently running a Multi site domain across WAN in 3 different countries, we have installed the 14 day trial and i have a a few questions:

1-Do you have a way to set role profiles for the people that will be using PDQ Deploy\Inventory: ie we would like to lock down just who can create packages or the scope to which an admin can target end clients in their site..like some sort of 2 way approval from the Head office Admins.

2-The Pull command is this DFS aware will remote clients pull the packages from local site to clients?

3-How does the PDQ Server connect to each client..a brief description? : winrm ? WMI ?

4-just a question on the server to client interaction ? what files are created in the Admin share and which processes or services continue to run on the clients? after deployment\Inventory

 

Thank you in Advance

Daniel 

0

Comments

1 comment
Date Votes
  • >-Do you have a way to set role profiles for the people that will be using PDQ Deploy\Inventory: ie we would like to lock down just who can create packages or the scope to which an admin can target end clients in their site..like some sort of 2 way approval from the Head office Admins.

    This feature is not available. The console can only be executed in an elevated (Admin) mode. Once it is running the Admin has control of building and deploying packages.

    >The Pull command is this DFS aware will remote clients pull the packages from local site to clients?

    Yes. Many of our customers use DFS namespaces to store their Install Files and/or PDQ Deploy repositories.

    >How does the PDQ Server connect to each client..a brief description? : winrm ? WMI ?

    SMB. PDQ Deploy and PDQ Inventory connect via File and Printer Sharing.

    >what files are created in the Admin share and which processes or services continue to run on the clients? after deployment\Inventory

    There are no files left over after a deployment or a scan. When a deployment/scan is initiated there are few files and directories created in ADMIN$\AdminArsenal. (Sub-directories PDQDeployRunner and PDQInventory-Scanner, PDQInventoryRemoteCommand are created once). A Windows service is called (one for Deploy and one for Inventory). The service for Deploy (PDQDeployRunner-x) will log on as the Deploy User (or local service if specified). The Inventory scanner is always started as Local Service. The install files are copied to the Exec subdirectory. Once the deployment or scan is completed the service is deleted and the service files and install files (for deployment) are deleted.

    The only exception to this is when you are viewing the running processes on a target via the Processes panel in a Computer window. In this case the folders called PDQInventoryMonitor and PDQInventoryMonitorStart are created and the files (which return the processes) stay on the target. 

     

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post