Endpoint Protection

I have No live update server. As soon as my SEPM server gets updates from internet it pushes to clients. Now i want to schedule the client update procedure like 200 clients after each hour( sepm will push defination updates to only 200 selected clients at a perticular time .next 200 at other set time). I can sechedule the scan time but how to schedule client update time.

The updates that clients receive can be scheduled only by adjusting the heartbeat interval when the source is SEPM.

If you have clients put up in different groups then you can adjust the heartbeat interval for certain groups and set them to be 1 hours and set the communication mode as "PULL"

For some other groups you shall set it up as "2 hours" again with "PULL" mode.

However, this can't be expected to be working well on the schedule as we will not be able to control the heartbeat intervals at certain given time. Depending on the last heartbeat interval, the clients will try and contact the SEPM in this frequency.

Check if the above could be adjusted to best suit your needs...

Hope that helps!

Regards,

Elango M.

You can schedule client update time from SEPM server only if you are using liveupdate server (Internal/External)for updating the client. If you use SEPM to update the clients, you will not able to schedule it. But you can still do some adjustments by adjusting heart beat interval.

Scheduling LU for GUP or from SEPM is not possible.

It is possible only for LUA.

Hi,

please, don't complicate things where not required.

You want to distribute the content over a wider time, is it so important to control which set of peer clients is served first or second, etc? I don't think so, maybe servers faster, clients slower is enough.

Let's make an example with fake numbers to explain my approach:

- you can set the SEPM to get updates daily at fixed time (you will skip two content releases per day)

- you have 1,000 clients you want to update over 6 hours (remember that your users usually work 8 hours per day)

- you have 100 servers you want to update over 2 hours because you want them more secure

- changing the heartbeat is not the right approach, if too small, you have too frequent connections and high traffic, if too high, you lose the control of your clients (slow update of policies, status, logs, commands, etc.), keep it at a reasonable value (15-45 minutes)

- in the same place were you set the heartbeat, there is the option to randomize the content update, this will slow down the content update without impacting on the rest of the communication

- set it to 6 hours for the clients (1000 clients/6 h= 166 c/h)

- set it to 2 hours for the clients (100 servers/2 h= 50 s/h)

Of course, the wider are the above intervals, the less and slower your clients are updated which result in a less secure network.