Home » Configuring Software Repository
 

Configuring Software Repositories

A Software Repository is like a library where you can store software packages and access them as and when required to deploy as many time as you want. Depending upon your organization's size, you can store your packages in either a Network Share Repository or a HTTP Repository. In Endpoint Central, there are two types of software repositories:

  • Network-share repository
  • HTTP repository

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 <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.

Advantages

Using a network-share repository enables you to do the following:

  • Ensure that you do not have multiple copies of the same software application in your network
  • Fill the details of your network-share repository automatically whenever you add a package
  • 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 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:

  • 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 have the Read and Execute access to the network-share repository in which the software package is stored. Endpoint Central will use these credentials to access the repository and deploy the software.

Creating a Network-share Repository

To create a network-share repository, follow the steps given below:

  1. Navigate to Software Repository from Software Deployment tab.
  2. Click the Create a Network Share option
  3. Enter the path for the network share
  4. If you do not enter a path for the network share, it will automatically be created in the computer where Endpoint Central server is installed.
  5. Check the Accessing the Share using Credentials checkbox
  6. Enter a username and password
  7. 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, \DCAdmin.
  8. Click Save

You have created a network-share repository.

HTTP 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.

Advantages

Using an HTTP repository enables you to do the following:

  • Install software applications in computers that do not have access to a network-share repository
  • Access computers when the computers are unable to access a network-share repository because the required number of connections have been reached
  • 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

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?

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