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.

Does "Include Entire Directory" remove copied files after the package is deployed?

This is a bit of a mundane question, but do the files copied over to the target workstation using the "Include Entire Directory" option get deleted after the package deploys?  I have a massive folder and file set for Visual Studio 2019 (35GB) that is getting copied over to each machine in a computer lab.  I want it to install, but I don't want 35GB worth of install files left on those computers afterwards.  Can someone clarify this for me?

 

0

Comments

8 comments
Date Votes
  • Yes. All files that are copied to targets get deleted at the end of the deployment.

    1
  • Thank you!  I just wanted to make sure. 

    0
  • are partially copied files removed even if a deployment fails?

    0
  • I know this is an old thread but that does not appear to be how it is working in our environment. A lot of files are being left in C:\Windows\AdminArsenal\PDQDeployRunner\Installers.

    1
  • I checked a machine that we recently
    "PDQ'd" and I don't find anything in that directory.  In addition I checked a custom package that had the "entire directory" checkmarked.  Saw the files populate in the folder you mentioned then saw them dissapear after the job was finished installing.

     

      I didn't even know that is where files ended up when they temporarily copied them over to.  Perhaps it is failing permission wise or something strange?  Not sure how the user would successfully copy but then not be able to delete after.  Could be a timeout also of some kind, is the software massive you are installing?

      Are you on the latest and greatest version?  19.3.350.0

    0
  • The files are of a decent size. They are Autodesk packages. I just upgraded to the latest version but this was happening even last year around the same time and we were on the current version at that time. There doesn’t seem to be a timeout but maybe it’s one that isn’t logged. Either way I need to be able to get these files off of the machines. I guess for the time being can I just delete the Installers folder without doing any damage?

    0
  • So, Installation Requires Source was checked on several packages and that is why the install files were left on the machines. I still need to figure out how to delete the files without causing any issues though. 

    1
  • I didn't even check that setting, but now looking at the packages I see mine don't have this enabled at all for any of them.  Looks like this settings is seldom used except in special cases.  Good find and thanks for expanding on the knowledge here.  Well done.

     

    -JR-

    0