Deploy Software (Copy entire directory). Using my technician computer…

[ggcisssca]

Hi,

I need to use BatchPatch to deploy a software to over 100 computers where those computers are located in a WAN area. The package need to be copied locally first for a good installation.. and this package have a size near 1 GB. Then I told me “Nice, targeted computers and the file server share are on the same site and they are using 1-10 Gbps link.”

I tested my deployment and I observed a very slow time to copying files from the share through the target computers.

I analyzed my network traffic and I finally observed the option “Copy entire directory contents in addition to the specified file” is not did between the the target computer (BatchPatch Working Directory) and the source folder directly by a process on this machine. It did the job passing via my local computer !?!

Why the BatchPatch process doesn’t start directly the copy from the computer where I need the files to be copied (A command launched from this location) ?

Sample:

My Exe, msi, cmd, etc: \\share\mypackage\install.cmd *Where it contain 1 GB of necessary files)

Copy entire directory contents in addition to the specified file (Checked: ON)

Target working directory: C:\Program Files\BatchPatch\Deployment

The \\share located on site NY
The target computer located on site NY
My technician computer located on site LA

When I start the command, the files are copied from \\share server at NY through my technician computer at LA to be sended through the target computer…

BatchPatch should start the copy from a process running on the target computer direclty.

[doug]

Thank you for your feedback. At this time it is the BatchPatch computer that performs the copy, so for max performance in the scenario that you describe, you would need to run an instance of BatchPatch on the target network, and have that instance perform the deployment.

Thanks.

[ggcisssca]

How can I did that if I need to deploy my software over 500 computers? Not a solution.

If I need to install BatchPatch on each target computer, It will be more easier to take the control remotely (RDP) and just launch the script manually. But not realistic to do that over 500 computers.

[doug]

You don’t have to install BatchPatch on every target computer. The suggestion I made was to install a single instance of BatchPatch in the same geographic location as the target computers so that deployment stays local to the BatchPatch instance.

Alternatively if you keep the BatchPatch installation in a network that is remote to the target computer, then at a minimum you should also keep the deployment files in the same network as the BP installation so that when the deployment runs, it copies files only in a single direction. A better/faster option will be to do what I described previously, which is to install an instance of BatchPatch in the network where the target computers are located.

[ggcisssca]

Not realistic also… My sample was to explain the logistic. Our reality is that we have over 132 WAN sites with 2.5 Mbps through 10 Gpbs link and many users in VPN. Not possible to think to install an instance on every location.

[doug]

In that case then you should just keep the deployment files on the BP computer or in the same network as the BP computer so that when BP copies the files to target computers it only copies the files in one direction. There is not currently a better or more efficient option available.

[booster]

Some bulk idea that may help you:
Create a script to deploy on target computer. The script contains de installation command, the source share, and output the result to BP, a file or any code that can help. (logged output)

Considering an AD domain in such deployment an OU detection (executed on the target computer so) at first step and a list matching the share by OU is a nice to have.

A DFS share may help replicating the content on location too and avoid the location detection.

[Author]

Posts