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

[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