Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 0 subscribers
  • Views 12863 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

Rolling out agent via console.

Neil_Evolve

Good afternoon,

I'm scheduling a rollout of Endpoint protection and need to be able to give a rough estimate of timescales involved. I would normally push out on a per site / department approach in batches of 50 aiming for around 300 endpoints per day, but may need to aim for a higher rate due to the numbers involved.

This will be a multi-site deployment and all endpoints will use local servers for the initial install and updates.

As part of the install the incumbent AV will be removed by Sophos CRT.

Is there any guidance around how many installs should be kicked off at the same time and how long the installs can be expected to take? I have around 20 000 endpoints so need to give a reasonable estimate of the time required.

Regards.

:55574


This thread was automatically locked due to age.
Parents
  • 0

    Hello Neil,

    never had to do anything like this ...

    Is there any guidance around how many installs should be kicked off

    Initial install is nothing special. SEC has to contact all selected endpoints in turn and create the started task. Can't say how long this takes, I rarely use it and it seems that times vary significantly. Once this is done there's nothing to do for the console until the RMS install on the endpoints is complete and they try to register.

    An endpoint first runs CRT and if this is successful installs AutoUpdate which in turn downloads and installs the other components starting with RMS. Naturally depends on the performance of the endpoint so it's hard to give numbers, expect several minutes + the time CRT needs.

    I'd start Protect for a few dozen at one site, wait until the tasks are running (the yellow down-arrow overlay) and then do this for a similar batch at another site, repeat for a total of 100 or maybe 200 endpoints. This will give you a feeling how long it  takes in total, but I assume you can kick off another batch when the first one is at the installing stage. 

    SEC can only protect online endpoints (it does not store the request) and you have to deal with failed installs. 

    HTH

    Christian     

    :55576
Reply
  • 0

    Hello Neil,

    never had to do anything like this ...

    Is there any guidance around how many installs should be kicked off

    Initial install is nothing special. SEC has to contact all selected endpoints in turn and create the started task. Can't say how long this takes, I rarely use it and it seems that times vary significantly. Once this is done there's nothing to do for the console until the RMS install on the endpoints is complete and they try to register.

    An endpoint first runs CRT and if this is successful installs AutoUpdate which in turn downloads and installs the other components starting with RMS. Naturally depends on the performance of the endpoint so it's hard to give numbers, expect several minutes + the time CRT needs.

    I'd start Protect for a few dozen at one site, wait until the tasks are running (the yellow down-arrow overlay) and then do this for a similar batch at another site, repeat for a total of 100 or maybe 200 endpoints. This will give you a feeling how long it  takes in total, but I assume you can kick off another batch when the first one is at the installing stage. 

    SEC can only protect online endpoints (it does not store the request) and you have to deal with failed installs. 

    HTH

    Christian     

    :55576
Children
No Data
Unfiltered HTML