Enable/Fix Download Randomization for PULL method Communication Settings SEPM clients
Currently the download randomization does not function in combination with the PULL method of the communication settings for SEPM clients.
I have experienced the following behavior, confirmed by symantec support:
Settings on SEPM server:
- PULL method communication settings
- Randomization enabled communication settings
- No GUPs configured
- LiveUpdate in place, SEP clients are only configured to download updates from this source.
SEP clients communicate for management directly to the SEPM servers, and the randomization parameter has no effect whatsoever.
This will cause a network load at fixed times, and this cannot be spreaded via randomization, in other words the randomization does not work in this case. You don't wish this behaviour in low bandwith environments.
Also I have experienced a bug in the inheritance of the randomization settings. The setting is open/configurable inspite of the inheritance enabled on a sub group.
Comments
SEP clients communicate for
SEP clients communicate for management directly to the SEPM servers, and the randomization parameter has no effect whatsoever.
That randomization parameter is only for downloads of content (ie virus definitions) from the SEPM itself, not communication frequency. This is why it is called Download Randomization, not Heartbeat Randomization.
If all of your machines are powered on at the same time then they will all have the same communication cycle wtih the manager, but if they are set to update content via SEPM then they will honor the download randomization for content downloads only. This can be confirmed by sylink logging.
Would you like to reply?
Login or Register to post your comment.