Endpoint Protection

HI all,

          We have offices in all capital cities connected to the head office in canberra by an average of 1mb/s each. I would like to setup the management console so a client out in a remote office will connect to a local share target in that office to install the 80MB package.

Any advice would be great...

Thanks in advance

B

You are able to create a local share in your remote office, copy the installation package to that share and use the Migration and Deployment wizard to install that package to your remote clients.  The clients will install from the remote local share and not use up bandwidth for the installation (except for uploading logs and connecting to the SEPM for communication).

  You will create an installation package and transfer it to a locally mapped drive. It's in page 100-101 of the installation guide.

Rick is right, BUT you should take care of your bandwidth by setting a client in each segment as a GUP so that you will save the bandwidth.
Otherwise after installation the wireless connections will be a bottleneck.

A GUP is a client which receives the definitions and other data from the SEPM and its neighbor clients will refer to that client for receiving the updates instead of referring to SEPM. Hence there will be only one request on your wireless connection instead of a mass of requests from your clients.

So Watch Out!

U can also deploy using Group policy if u hav a Domain Controller

We had a bit of an issue with some of our remote clients.  Several locations with low bandwidth (less than 1Mbps) were competing for space on a T1 connection back to the data center.  After the initial install all the clients were trying to get their policy and pull definitions down.   This maxed out the connection back to the data center and caused the install to run hours past the window.

Look at your network architecture and see what the bottlenecks are?  Do you have multiple sites that share a single connection?

Consider a Group Updater for remote locations.

Create a policy that uses the Group Updater.  Use this policy in your install.

Perhaps a build with the latest definitions incorporated.


Once everything was installed an up to date, network bandwidth usage has been minimal with no noticeable spikes.  It was just the initial roll-out.    I think we took on a bit much at once not realizing the network architecture and bottlenecks that were in place.

Hindsight....