# Configuring Software Repositories Last Updated On: 07 Jul 2026 15 minutes read A [Software Repository](https://www.manageengine.com/products/desktop-central/software-repository.html) 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. ## Network-share Repository 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 `.exe` or the `.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 subsequent directory. It is recommended that you deploy such applications from a network share that is accessible from all the computers in your network. ### Advantages Using a network-share repository enables you to do the following: - Once network share is configured with credentials, whenever you create a package, it will be automatically used. - Save your network bandwidth as executable files are not copied into the computers. ### Required Permissions 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. - Restrict certain users from accessing the network-share repository directly. - Deploy a software application to users or computers across multiple domains or workgroups. 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. ### Creating a Network-share Repository To create a network-share repository, follow the steps given below: 1. Navigate to **Software Deployment** Tab > **Software Repository** under Settings. 2. Under **Network Share > Create Type > Create a Network Share** option. 3. Enter the path for the network share. **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. 4. Check the **Accessing the Share using Credentials** checkbox. 5. Enter a username and password of the domain where the network share exists. **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`. 6. Click **Save**. ### Understanding Software Deployment in Remote Office through Network Share Repository 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. ## HTTP Repository 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, `\webapps\DesktopCentral\swrepository`. You can change the location of the repository if required. ### Advantages - Install software on computers that cannot access a network-share repository. - Deploy software to computers when network-share repository connections are exhausted. - Do not have to set any permissions when using an HTTP repository. ### Changing the Location of the HTTP Repository To change the location of the HTTP repository, follow the steps given below: 1. Click the **Software Deployment** tab. 2. In the **Settings** section, click **Software Repository**. 3. Click the **HTTP Repository** tab. 4. Enter the path of the new location. 5. Click **Save**. 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](https://www.manageengine.com/products/desktop-central/help/server/http-uploads-store-location-invalid-kb.html). If you want to change Software repository location on Distribution Server, refer [here](https://www.manageengine.com/products/desktop-central/moving-software-repository-location.html). ### Understanding Software Deployment in Remote Office through HTTP Repository 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 and 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 contact the server and collect the configuration files and 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. ## Network Share VS. HTTP Upload 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?](https://www.manageengine.com/products/desktop-central/help/software-deployment/deploy-software-file-upload.html). 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: - Choose the Copy Files/Folders option while defining a configuration to install software applications. - Are required to use user credentials to access the network-share repository. - Use the Run As option while installing software packages as a user, other than the administrator.