How It Works: PDQ Deploy

Follow

Comments

9 comments

  • Jharper

    Just a tag question from the forum...

     

    I am pushing out a basic Powershell script for my SAN team to collect some server info. Using PDQ deploy. It worked fine. It only failed on boxes that had no Power shell installed (duh lol).   My question is where exactly does pdq deploy create its folder on the target machine to copy and run the ps1 script? and does it delete it afterwards?

    Reason being is at the end of the powershell script a .cvs output file is created in that same location of the .ps1 file... We want to know where that output file is going? If the share gets immediately deleted then we will have to change the out put location..

     

    Please let me know.

     

    Thanks 

    0
    Comment actions Permalink
  • Adam Ruth

    **Updated**The directory does get deleted when PDQ Deploy is finished. The directory is:

    C:\Windows\AdminArsenal\PDQDeployRunner\Service-n\exec

    Note: the "\service-_n_ is usually service-1 but it could be service-2, service-3, etc. depending on other concurrent deployments to the target from other PDQ Deploy consoles)

    0
    Comment actions Permalink
  • Jason Riggs

    I have a question concerning remote deployment preferences. Concerning deployment across a WAN, is it preferred/faster to have the installation files on a server on the same subnet as the machine to which you are installing, or to use files only on the main network server. When I use GPO to install msi files, I make copies on all of the domain controllers and create separate GPO's for each site. Should I follow this same idea when using PDQDeploy or will this actually double the time required as the files transfer back and forth across the WAN? Thank you.

    0
    Comment actions Permalink
  • Shane Corellian

    Hi Jason,

    If you have slow WAN links then you'll probably want to utilize the Pull Copy Mode along with Microsoft's DFS. You can specify the Copy Mode via a default global setting (File > Preferences > Performance or per package (edit the package, Select the Package node).

    Every package that uses a Pull copy must have the Install File (and any files specified in Additional Files) available via UNC. If you use DFS then move your Repository to a share in the DFS schema via Preferences > Repository. Copy all of your existing folders in your current repository folder to the new location. 

    0
    Comment actions Permalink
  • Jason Riggs

    Thank you Shane. I notice that none of those options are available on the free version of PDQDeploy, so therefore I will continue to push from one server across the WAN. Thank you for your quick response.

    0
    Comment actions Permalink
  • Shane Corellian

    Hi Jason,

    Remember this one point: Free mode uses the Push copy mode. This means that the PDQ Deploy console will literally push the install files down to each target. If the install files reside on a file server then the console machine will copy the files down to itself and then push them out to the targets.

    Basically, in Free mode it is best to have the packages stored on the console machine.

    0
    Comment actions Permalink
  • Travis Weber, Jr.

    I would like to add this. The service directory has changed, where # equals the number of the service

    Ran into this after updating PDQDeploy from v2 to v3 and 1 of my deployment stopped working (it passes a parameter to the service directory).

    0
    Comment actions Permalink
  • Remko de Koning

    I have a tool that runs on the PDQ Deploy server. It is called delprof2.exe and deletes all user profiles older than for example 90 days.

    syntax: delprof2.exe /c:<computername> /d:90

    How would I use this in PDQ deploy. I do not want to trigger this on the remote computer but on the deploy server itself. Any thoughts on this?

     

    0
    Comment actions Permalink
  • Shane Corellian

    @Remko,

    You would use PDQ Deploy only if you wanted to have DelProf2 executed from the target itself. If you want to run from the PDQ machine (using the /c:%computername% syntax) then I would recommend using PDQ Inventory and creating a Custom Tool.  Here is a video example of using the Custom Tools feature to initiate a DameWare Remote Control session on the selected target computer. In your case you'd be calling DelProf2. To pass the Computer Name of the selected computer you would use the variable %TARGET%.

    0
    Comment actions Permalink

Article is closed for comments.