Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 6222 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Update Managers and clients not updating from secondary share

steve_999

 We're currently in the finaly stages of setting up Enterprise console and preparing to roll out Endpoint protection to clients. We're a multi site setup with 3x main locations. The Manangement server is in SiteA and I have installed an update manager in Site B. Site C has an update share that has been added to the update manager of SiteA. I've rolled out a small number of to all 3x sites, but checking the clients logs, they are all updating from Site A. How do I get the client to update from the share that the client is nearest to, i.e. in it's local subnet. 

:55466


This thread was automatically locked due to age.
  • 0
    Hello steve_999,

    there is no "nearest" (unless you work with aliases or generic names and split DNS), the updating policy tells the endponts where to look for updates.

    Christian
    :55467
  • 0

    Hi Steve,

    Just to clarify what Christian has already stated, you need to set separate updating policies for each site to point to the "local" update manager. You could also set a secondary update location. See below;

    Capture1.PNG

    Capture2.PNG

    It also makes good sense to set the initial install source to the nearest available source. This can also be configured in an updating policy as shown below.

    Capture3.PNG

    Regards.

    :55472