A software repository is a storage location where you can store software packages. You can access these software packages when required and install them on computers in your network. In Endpoint Central, there are two types of software repositories:
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 <setup>.exe or the <softwarename>.exe. Other applications have more than one installable file, however, these files are located in the same directory. Some complex applications, like Microsoft Office, have multiple installable files. Here each installable file is located in a different directory. It is recommended that you deploy such applications from a network share that is accessible from all the computers in your network.
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 group Everyone. 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:
To create a network-share repository, follow the steps given below:
You have created a network-share repository.
An HTTP repository is used to store executable files before you install them in 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 Desktop Central server.
For example, <Desktop Central server>\webapps\DesktopCentral\swrepository. You can change the location of the repository if required.
Using an HTTP repository enables you to do the following:
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
Click here to watch the video:
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: