Deployment Files

[wayres]

Hey Doug. Testing our BatchPatch and love it so far, getting ready to pull the trigger. Quick question, is there any way during Patch Deployment of software to not have it delete the files off the remote machine after install. We have one main piece of software we use and that MSI need to stay on the machine because it looks for it each time a new user tries to open the software.

Thanks.

[doug]

Thanks! Im really happy to hear that you like the app. Unfortunately the current build doesn’t allow you to leave the files on the target. We can look into adding this option in a future build although I’d need a bit more info from you because right now it gets copied to a temp sub directory in the remote working directory, and this temp folder would not be a safe long term location. For the time being your best bet would be to have a separate script (you could use BP for this too) that copies the Msi back to the target after the installation is complete. However, I also then wonder where the Msi needs to be located in order to be found by the application that’s looking for it. Presumably it marks the original file location in some way so that it might actually require it to live in the temp BP working directory if that’s where it was originally installed from? Not sure.

-Doug

[wayres]

It does mark the original file location. I can probably just change the Remote Working Directory just during that deployment, to a more permanent location, then use a script like you suggested to copy the MSI back out.

[Author]

Posts