A Software Repository is a centralized storage location where you can store software packages and access them as and when required to deploy as many times as you want. In Endpoint Central, there are two types of software repositories:
Depending upon your organization's size, you can store your packages in either a Network Share Repository or a HTTP Repository. Both repository types can be used to deploy packages to distribution servers and WAN agents within Endpoint Central.A network-share repository is used when you want to deploy a software application to multiple computers in a network. It is recommended that you store the software package that you want to deploy in a network share that is accessible from all the computers in the network. The software application will be installed directly in the computers that you specify.
Most software applications have a single installation file like
Using a network-share repository enables you to do the following:
The network-share repository should have the Read and Execute permission for all the users and computers in the network. You should set the permissions mentioned above for the Everyone group. This ensures that the network-share repository is accessible from all the computers in the network.
However, ensure that you do not set the permissions to Read and Execute for all the users and computers in the network when you want to do the following:
For example, assume that your network-share repository is in domain A and you deploy a software application from this repository to a computer in domain B. You should ensure that you do not set the permissions to Read and Execute for all the users and computers in the network.
In such cases, you can provide user credentials that provide Read and Execute access to the network-share repository in which the software package is stored.
To create a network-share repository, follow the steps given below:
Note: If you do not enter a path for the network share, it will be automatically created in the computer where the Endpoint Central server is installed
Note: If you are creating the network share on a domain computer, prefix the domain name to the username. For example, ZohoCorp\Administrator. If you are creating the network share on a workgroup computer, prefix the computer name to the username. For example,\\MachineName\DCAdmin.
If you are deploying a software through the Network Share Repository, the software binaries should be stored in the Network Share configured by the IT administrator before deploying the software.The software gets deployed depending upon the type of remote office in the following ways:
Remote office with a Distribution Server
In a remote office with a Distribution Server, the configuration files are replicated to the distribution server during the replication cycle configured by the IT administrator in the Central server. Once the configuration files are replicated, the WAN agents access the network-share containing the software binaries to deploy the software. The software deployment takes place during the 90-min refresh cycle, system startup, or user logon, whichever takes place earlier based on the Deployment Policy configured.
Remote office with WAN agents
In a remote office with WAN agents having direct communication with the Central server, the WAN agents collect the configuration files from the server. The WAN agents then execute the software deployment by accessing the network share containing the software binaries.The software deployment takes place during the 90-min refresh cycle, system startup, or user logon, whichever takes place earlier based on the Deployment Policy configured.
The HTTP repository is used to store executable files before you install them in your managed computers/computers in your network. You can use this repository when you want to deploy software packages to computers using the HTTP path. You can also change the location of the HTTP repository if required.
The HTTP repository is created automatically when you install the product. It is located in the same folder as the Endpoint Central server. For example,
You can change the location of the repository if required.
To change the location of the HTTP repository, follow the steps given below:
You have changed the location of the HTTP repository. If you are unable to change the location of the HTTP repository, see Cannot Change the Location of the HTTP Repository
If you want to change Software repository location on Distribution Server, refer here.
If you are deploying a software through the HTTP Repository, the software binaries will be stored in the default HTTP repository location in the Central server or in a new location configured by the IT administrator. The software gets deployed depending upon the type of remote office in the following ways:
Remote office with a distribution server
In a remote office with a distribution server, the distribution server contacts the Central server to replicate the configuration files, software binaries during the replication cycle configured by the IT administrator. Once the files required for the software deployment get replicated in the distribution server, the WAN agents will contact the distribution server and replicate/collect these files to execute the deployment.The software deployment takes place during the 90-min refresh cycle, system startup, or user logon, whichever takes place earlier based on the Deployment Policy configured.
Remote office with WAN agents
In a remote office with WAN agents having direct communication with the Central server, the WAN agents contacts the server and collects the configuration files, software binaries required to deploy the software.The software deployment takes place during the 90-min refresh cycle, system startup, or user logon, whichever takes place earlier based on the Deployment Policy configured.
While it is recommended that you have a common software repository, it is not mandatory. You also have an option to upload the executable files in the Endpoint Central server from where they are copied into the computers before being deployed. Using this approach will increase your bandwidth overhead as the executable files are copied into each of the computers.
Therefore, it is recommended that you use this approach when you are deploying software applications to computers in a remote location. This is because, in most cases, when you deploy software applications to computers in remote locations you do not have access to the respective network-share repository.
When you want to deploy software packages to computers in a LAN and WAN, create two packages for the same software application. Store one set of packages in the network-share repository. These will be deployed and installed in the computers in the LAN. Store the other set of packages in the HTTP repository. These will be uploaded and deployed to the computers in the WAN.
When you want to install multiple packages you can zip them and upload. For more information, see How to use the HTTP Path option to deploy software packages that have multiple executable files in different directory structures?
There are a few exceptional scenarios where executable files are copied to computers in your network when using network-share repository. This can happen when you do the following:
