The key issue in Remote Site 2 is low bandwidth. However, 60 percent of the bandwidth
is free
during business hours when approximately 154 Kbits of bandwidth is available.
The best way to install the Security Agent is to use the same agent package in
MSI format used in Remote Site 1. However, since there is no available server, you
cannot use a Distributed File System (DFS).
One option is to use third-party management tools that allows
administrators to configure or create shared directories on remote
endpoints without having physical access to them. After creating
the shared directory on a single endpoint, copying the agent package to the directory requires
less overhead than installing the agent to
nine endpoints.
Use another Active Directory policy, but again, not specifying
the DFS share as the source.
These methods keep the installation traffic within the local
network and minimizes the traffic across the WAN.
To minimize the impact of component updates across the WAN, designate one agent to act as
an Update Agent. See Remote Site 1 Deployment for more
information.