ERAC installation location-best practices for MSPs?

Discussion in 'ESET Server & Remote Administrator' started by DavidWVa, Aug 11, 2011.

Thread Status:
Not open for further replies.
  1. DavidWVa

    DavidWVa Registered Member

    Joined:
    Aug 10, 2011
    Posts:
    3
    Hi Folks!

    We are a busy MSP (Managed Service Provider) - so that we have a bunch of SMB customers, most with single geographic site, with one or more servers at that site, along with a number of DTs, LTs and mobile devices, usually connected via Win Server in a domain set-up (Server or SBS) - and we are wondering about 'best practices' for installing ERAC?

    Some questions/thoughts, numbered to make replying easier:


    1. ERAS at each Customer site; ERAC at OUR Site
    --------------------------------------------

    We are assuming that ERAS should be installed onsite on one of the Servers at **each** customer's site - but we are unsure about **ERAC** installation best practices, even after pouring over all of the ESET documentation (official ESET Guides, KBs, etc., along with some 3rd party forum chat, etc.) that we could find.

    From what we understand so far, it appears that we can install a single instance of ERAC on one of OUR servers (hosted at our colo or onsite at our pemises) which of course is then REMOTE to each of our customer's ERAS.

    We then tell this single ERAC instance (located on our Server) which ERA Servers (Remote, at customer sites) that we want to connect to, and it will do so, and over the public Internet, with all comms encrypted.

    Is that correct/best practice for an MSP? Any issues/gotachas here that we may not have thought of?


    2. Master Config Policy, Cutomizable Via Parent/Child Relationship in ERAC
    --------------------------------------------------------------------

    Hoping Yes, are we correct in then thinking that we can also create a MASTER Config policy in ERAC, and, through Parent/Child relationships and Inheritance (or not), we can then start with this master policy but then **tailor** it for particular Groups (each customer) and sub-groups (Accounting, Marketing, etc. at each customer).


    3. NO Heavy WAN Traffic With this LAN/WAN ERAS/ERAC Structure
    -------------------------------------------------------------

    Further, we understand that THIS ERAS(on each customer LAN)/ERAC (single instance on our Server, remote from each customer) network topology would NOT result in undue traffic over the *WAN*, i.e., no Push NOD32 installs or AV updates would be pushed from ERAC, on our server, to each customer site's ERAS and then on to client stations at each remote customer?


    4. ERAS/ERAC Integration with MSP RMM/PSA Tools
    ----------------------------------------------
    Is there any talk of integrating ERAS/ERAC with additional RMM/PSA tools beyond the current (partial) integration with LabTech?

    We use currently Zenith for RMM and CommitCRM for PSA and are interested in any plans to integrate with either of these apps.


    5. MSP ERAS/ERAC *MSP* 'best practices'
    --------------------------------------
    Has ESET written any white papers/case studies re MSP ERAS/ERAC best practices? We hunted 'hi and low' online, with no luck finding anything.

    ---

    TIA and we look forward to your replies!

    David V
    Sunny Miami, FL
     
  2. agoretsky

    agoretsky Eset Staff Account

    Joined:
    Apr 4, 2006
    Posts:
    4,033
    Location:
    California
    Hello,

    Private message sent.

    Regards,

    Aryeh Goretsky
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.