Best Practices for Installing DTS agents?

Document ID : KB000015858
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

CA Client Automation by default does not install DTS on the Windows agents,

Software Delivery handles all software installations,

there are a few reasons why you might want to install DTS on an agent.

Question:

In what conditions should DTS Agents be Installed and Configured on Agent End Points?

What are Best Practices?

Environment:
CA Client Automation - All Versions
Answer:

In Most cases it is NOT recommended to install and configure DTS Agents on Client Automation

endpoints since it adds overhead to the agent machines as well as to the Domain Managers.

Here are some scenarios in which Installing and Configuring DTS Agents may be Considered:

 

  •        There is a need to transfer data FROM the Agent securely, reliably and efficiently

      

  •   This is the biggest single reason for installing DTS at the Agent. DTS can efficiently, securely and reliably transfer data FROM the Agent to other DTS endpoints, which may be other agents, scalability servers or Domain managers. Perhaps to an Agent which is set up as a central repository for such transfers.

   

  •   There is complex network routing required to the Agents where a specific route for data transfer of packages should be chosen over other available routes, especially if the native network configuration would otherwise select other routes by default. This is not a common requirement, and placement of a Scalability Server at the location then configuring the route to the SS is preferable in most cases.

   

  •   There is a need to ‘pre-deliver’ the content by scheduling a ‘deliver at’ time and an ‘activate at’ time on the jobs

      

  •   DTS is the simplest method to provide this capability on a wide scale for all packages, but generally if this is only required for one or two jobs it is preferable to create a package to pre-copy the installation media then either an activate procedure on the same package or another package to actually perform the installation.

   

  •   There is a need for hop-node type functionality to the Agents.

      

  •   This can be useful in a small branch environment where there are branches which have only a handful of Agents. A hop-node configuration can be configured where one Agent in the branch receives a package payload from the SS and redistributes it to the others.

       

  •   HOWEVER – Neighbor Aware for Software Delivery provides this functionality with less overhead and less configuration
Additional Information: