2 Replies Latest reply on Nov 5, 2012 4:55 AM by jeffreychirino

    AH vs SADR

    cakeboss

      Boss is asking why not to put an Agent Handler at every site as opposed to a SADR.  From what I understand the main difference is that the AH also handles Agent-Server communication whereas the SADR does not.  Also that SADRs are easier to manage within ePO and from my experience, the MA repository policies are more reliable than AH groups'

       

      edit: Guess I didn't ask a question.  Why not deploy AH's instead of SADRs all every time?

       

      Message was edited by: cakeboss on 11/2/12 11:29:46 AM CDT
        • 1. Re: AH vs SADR
          vrishchik

          Hello

           

          Utilizing any feature of a product should be purely based on the requirement or it will just be overhead of an administrator. Surely there are difference between AH and SA repo. If you are a large enterprise and ePO is heavily loaded where ePO server is a bottleneck then AH is necessary. If AH is implemented then the assigned clients will connect AH for policy and to upload events. AH will then forward events to db directly. AH is nothing but a seconday ePO without console.

           

          Regards

          San

          • 2. Re: AH vs SADR
            jeffreychirino

            And large enterprises are considerd to be 200K systems and more.

             

            Besides that, if you upgrade ePO, you will need to upgrade each AH to keep them working, so for each side a SADR require less maintenance.
            ANd if I remember correctly, If you have 250+ nodes connecting to the AH, it is recommended to have a dedicated server running the AH software.