2 Replies Latest reply on Oct 19, 2009 5:53 AM by JoeBidgood

    Local Clients Install From Remote Servers

      7 Sites all Windows 2003 Servers and XP Clients

      I have a single ePO Server in one site and 6 SuperAgents in the others. I have replicated all packages to the sites with the latest updates and Virus Scan 8.7i Patch 570.

      Within My Systems I have

      My Organization
      ---Site 1
      ---Site 2
      ---Site 3
      ---Site 4
      ---Site 5
      ---Site 6
      ---Site 7
      Lost and Found

      I have configured a separate Agent Policy for each site stating that it's local SuperAgent Repository is Enabled where the remote sites are DISABLED. I also have the McAfee HTTP enabled for failover.

      Here is where the problem occurs.

      At the My Organization level I have created a Client Task that deploys VirsuScan 8.7i to all computer without it. It is scheduled to enforce at 9am every morning and it does, however all the clients connect to the Primary ePO server across the WAN and not to their local SuperAgent. When this occurs it saturates the connection and brings down almost everything else. My only solution is to down the ePO Server and wait for the clients to timeout their attempt to install.

      Shouldn't it go to the local SuperAgent since 8.7 has been replicated there?
        • 1. RE: Local Clients Install From Remote Servers

          When you create the MA policy for each site, make sure you push the local target repository to the top and disable the others. You should put ePO as the second item in line.
          Now depending on when your clients check in and get a new sitelist.xml, if they haven't received it, they will continue to go to the ePO server for updates. No matter what, they will always go to the ePO server for new tasks and policies.

          RDP into a distant workstation and checkout the sitelist.xml and start to fix it from there. BTW, you may want to consider applying some randomization to your deployment task, the SADR cannot handle all those inbound connections at the same time..which reminds me, perhaps that's the reason your clients are hitting your ePO server - Overflow.
          I was not under the impression that the deploy task could figure out which clients do or do not have the software module. So, I assume that your clients are ALL trying to install VSE every day at the specified time. During install it realizes that it doesn't require and stops. But before it realizes that, it'll try. Once MA moves to P3, I believe that the SADR will queue up the clients, up to 250'ish before denying them.

          I suggest that you make a task to deploy your module with a schedule of run immediately or once at a given time and a randomization of x hours.

          Heck, create the task at the top level in disabled mode and turn it on per site until the site is adequately rolled and then move to the next site. Just don't make it run everyday. Use your reports/dashboards to figure out where you need to concentrate your one-off touch efforts.
          • 2. RE: Local Clients Install From Remote Servers

            Just a quick point - the tasks do have this ability. Basically tasks are driven by a pair of scripts: a detection script that works out if the product is installed, and an install script that actually does the installation (or removal.)
            When the task runs the detection script is run first - if the product is is already installed then the process doesn't go any further.

            HTH -