Endpoint Protection Clients waits for timeout before trying the default management server

book

Article ID: 170097

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

SEP Clients with Group Update Provider (GUP) configured in Live Update Policy will abide by "Maximum time that clients try to download updates from a Group Update Provider before trying the default management server" configuration even if there is no GUP matching in either "Multiple Group Update Providers" or "Explicit Group Update Providers". 

There has been reports of an expected behaviour, where the defined GUPs does not match the details of a SEP Client (IP or Subnet), the endpoint will immediately try the default management server (SEPM).

Unfortunately, as long as GUP is enabled in the Live Update Policy, the endpoint whether it has a match in any of the defined GUPs or not, it will wait for the configured maximum time.

If "Maximum time that clients try to down updates from a Group Update Provider before trying the default management server" is set to Never, then the endpoint will never try the SEPM, even if there is no matching GUP to its IP/Subnet. 

 

 

 

Cause

Product is working as designed.

Resolution

Ensure "Maximum time that clients try to down updates from a Group Update Provider before trying the default management server" is not set to Never with a timeout that is reasonable for the environment.